[Desktop-packages] [Bug 1746658] Re: package bamfdaemon 0.5.3+17.10.20170810-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

** Changed in: bamf (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1746658

Title:
  package bamfdaemon 0.5.3+17.10.20170810-0ubuntu1 failed to
  install/upgrade: triggers looping, abandoned

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  system is hang up

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bamfdaemon 0.5.3+17.10.20170810-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 31 11:35:32 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-05-04 (272 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3+17.10.20170810-0ubuntu1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-01-31 (0 days ago)

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

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

[Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific) in totem and VLC

[Daniel van Vugt]

Installing vdpau-va-driver is only a workaround, and also one that we do
not wish to include in normal Ubuntu because it is known to be buggy and
cause performance problems for some GPUs.

This bug remains a valid bug for the case where vdpau-va-driver is not
installed. As such bug 1727232 may very well be related.

If you are happy with the workaround of installing vdpau-va-driver and
do not wish to pursue this bug further then it will expire automatically
after 60 days. No further investigation required.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1757301

Title:
  Brightness, contrast issues (possibly NVidia specific) in totem and
  VLC

Status in totem package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1423773

Title:
  Gnome-Shell don't free ram when I change a wallpaper

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be

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

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

Re: [Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific)

[Paul Dorman]

Clearly you did not bother to read my complete report. If you had you would
not have linked to a completely unrelated existing issue. I clearly stated
that installing vdpau-va-driver solved the problem. This is a missing
dependency issue.

I know you folks do your best, but you need to understand that not
everybody with something useful to offer has the free time to familiarise
themselves with the minutiae of Canonical's bug reporting guidelines.


On Wed, 21 Mar 2018 at 15:25, Daniel van Vugt 
wrote:

> Please try the workaround mentioned in bug 1727232
>
> ** Tags added: nvidia visual-quality
>
> ** Summary changed:
>
> - Brightness, contrast issues (possibly NVidia specific)
> + Brightness, contrast issues (possibly NVidia specific) in totem and VLC
>
> ** Also affects: vlc (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: totem (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: vlc (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1757301
>
> Title:
>   Brightness, contrast issues (possibly NVidia specific) in totem and
>   VLC
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1757301/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1757301

Title:
  Brightness, contrast issues (possibly NVidia specific) in totem and
  VLC

Status in totem package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757320] kdesudo can go soon

[Simon Quigley]

kdesudo can be removed from the archive as soon as my merged
ubuntu-release-upgrader change has been uploaded and has migrated.

$ reverse-depends src:kdesudo
Reverse-Depends
===
* ubuntu-release-upgrader-qt(for kdesudo)

$ reverse-depends -b src:kdesudo
No reverse dependencies found

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1757320

Title:
  Remove Qt 4 from the archive

Status in acoustid-fingerprinter package in Ubuntu:
  New
Status in adwaita-qt package in Ubuntu:
  New
Status in akonadi4 package in Ubuntu:
  New
Status in alsoft-conf package in Ubuntu:
  New
Status in alt-key package in Ubuntu:
  New
Status in amarok package in Ubuntu:
  New
Status in amora-server package in Ubuntu:
  New
Status in ams package in Ubuntu:
  New
Status in analitza4 package in Ubuntu:
  New
Status in appmenu-qt package in Ubuntu:
  New
Status in aseba package in Ubuntu:
  New
Status in attal package in Ubuntu:
  New
Status in attica package in Ubuntu:
  New
Status in auralquiz package in Ubuntu:
  New
Status in automoc package in Ubuntu:
  New
Status in autopilot-qt package in Ubuntu:
  New
Status in avogadro package in Ubuntu:
  New
Status in bacula package in Ubuntu:
  New
Status in ball package in Ubuntu:
  New
Status in baloo package in Ubuntu:
  New
Status in basket package in Ubuntu:
  New
Status in boats package in Ubuntu:
  New
Status in bodega-client package in Ubuntu:
  New
Status in bppphyview package in Ubuntu:
  New
Status in breeze package in Ubuntu:
  New
Status in cagibi package in Ubuntu:
  New
Status in cdcat package in Ubuntu:
  New
Status in chinese-calendar package in Ubuntu:
  New
Status in choreonoid package in Ubuntu:
  New
Status in clementine package in Ubuntu:
  New
Status in cmtk package in Ubuntu:
  New
Status in codelite package in Ubuntu:
  New
Status in codequery package in Ubuntu:
  New
Status in collatinus package in Ubuntu:
  New
Status in colord-kde package in Ubuntu:
  New
Status in connectome-workbench package in Ubuntu:
  New
Status in cortina package in Ubuntu:
  New
Status in cppreference-doc package in Ubuntu:
  New
Status in daemonfs package in Ubuntu:
  New
Status in dc-qt package in Ubuntu:
  New
Status in dee-qt package in Ubuntu:
  New
Status in dgedit package in Ubuntu:
  New
Status in dhcpcd-ui package in Ubuntu:
  New
Status in doomsday package in Ubuntu:
  New
Status in dssi package in Ubuntu:
  New
Status in enki-aseba package in Ubuntu:
  New
Status in eqonomize package in Ubuntu:
  New
Status in esperanza package in Ubuntu:
  New
Status in fbreader package in Ubuntu:
  New
Status in fcitx package in Ubuntu:
  New
Status in fcitx-kkc package in Ubuntu:
  New
Status in felix-latin package in Ubuntu:
  New
Status in flightcrew package in Ubuntu:
  New
Status in fmit package in Ubuntu:
  New
Status in fraqtive package in Ubuntu:
  New
Status in freecad package in Ubuntu:
  New
Status in freemat package in Ubuntu:
  New
Status in freemedforms-project package in Ubuntu:
  New
Status in freeplayer package in Ubuntu:
  New
Status in gammaray package in Ubuntu:
  New
Status in gebabbel package in Ubuntu:
  New
Status in genpo package in Ubuntu:
  New
Status in gle-graphics package in Ubuntu:
  New
Status in gmic package in Ubuntu:
  New
Status in gnash package in Ubuntu:
  New
Status in gnudoq package in Ubuntu:
  New
Status in gr-fosphor package in Ubuntu:
  New
Status in gr-radar package in Ubuntu:
  New
Status in grantlee package in Ubuntu:
  New
Status in gwenrename package in Ubuntu:
  New
Status in hamfax package in Ubuntu:
  New
Status in hedgewars package in Ubuntu:
  New
Status in heimdall-flash package in Ubuntu:
  New
Status in holdingnuts package in Ubuntu:
  New
Status in hydrogen package in Ubuntu:
  New
Status in ibus-qt package in Ubuntu:
  New
Status in ifpgui package in Ubuntu:
  New
Status in ifrit package in Ubuntu:
  New
Status in ike package in Ubuntu:
  New
Status in imagevis3d package in Ubuntu:
  New
Status in jovie package in Ubuntu:
  New
Status in jreen package in Ubuntu:
  New
Status in kaccessible package in Ubuntu:
  New
Status in kactivities package in Ubuntu:
  New
Status in kalternatives package in Ubuntu:
  New
Status in kamerka package in Ubuntu:
  New
Status in karlyriceditor package in Ubuntu:
  New
Status in kate4 package in Ubuntu:
  New
Status in kchmviewer package in Ubuntu:
  New
Status in kcm-qt-graphicssystem package in Ubuntu:
  New
Status in kcollectd package in Ubuntu:
  New
Status in kdbg package in Ubuntu:
  New
Status in kde-baseapps package in Ubuntu:
  New
Status in kde-runtime package in Ubuntu:
  New
Status in kde-thumbnailer-openoffice package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kde4pimlibs package in Ubuntu:
  New
Status in kdepim4 package in Ubuntu:
  New
Status in kdesudo package in Ubuntu:
  Confirmed
Status in kdiff3 package in Ubuntu:
  New
Status 

[Desktop-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

[Simon Quigley]

** Changed in: kdesudo (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1757320

Title:
  Remove Qt 4 from the archive

Status in acoustid-fingerprinter package in Ubuntu:
  New
Status in adwaita-qt package in Ubuntu:
  New
Status in akonadi4 package in Ubuntu:
  New
Status in alsoft-conf package in Ubuntu:
  New
Status in alt-key package in Ubuntu:
  New
Status in amarok package in Ubuntu:
  New
Status in amora-server package in Ubuntu:
  New
Status in ams package in Ubuntu:
  New
Status in analitza4 package in Ubuntu:
  New
Status in appmenu-qt package in Ubuntu:
  New
Status in aseba package in Ubuntu:
  New
Status in attal package in Ubuntu:
  New
Status in attica package in Ubuntu:
  New
Status in auralquiz package in Ubuntu:
  New
Status in automoc package in Ubuntu:
  New
Status in autopilot-qt package in Ubuntu:
  New
Status in avogadro package in Ubuntu:
  New
Status in bacula package in Ubuntu:
  New
Status in ball package in Ubuntu:
  New
Status in baloo package in Ubuntu:
  New
Status in basket package in Ubuntu:
  New
Status in boats package in Ubuntu:
  New
Status in bodega-client package in Ubuntu:
  New
Status in bppphyview package in Ubuntu:
  New
Status in breeze package in Ubuntu:
  New
Status in cagibi package in Ubuntu:
  New
Status in cdcat package in Ubuntu:
  New
Status in chinese-calendar package in Ubuntu:
  New
Status in choreonoid package in Ubuntu:
  New
Status in clementine package in Ubuntu:
  New
Status in cmtk package in Ubuntu:
  New
Status in codelite package in Ubuntu:
  New
Status in codequery package in Ubuntu:
  New
Status in collatinus package in Ubuntu:
  New
Status in colord-kde package in Ubuntu:
  New
Status in connectome-workbench package in Ubuntu:
  New
Status in cortina package in Ubuntu:
  New
Status in cppreference-doc package in Ubuntu:
  New
Status in daemonfs package in Ubuntu:
  New
Status in dc-qt package in Ubuntu:
  New
Status in dee-qt package in Ubuntu:
  New
Status in dgedit package in Ubuntu:
  New
Status in dhcpcd-ui package in Ubuntu:
  New
Status in doomsday package in Ubuntu:
  New
Status in dssi package in Ubuntu:
  New
Status in enki-aseba package in Ubuntu:
  New
Status in eqonomize package in Ubuntu:
  New
Status in esperanza package in Ubuntu:
  New
Status in fbreader package in Ubuntu:
  New
Status in fcitx package in Ubuntu:
  New
Status in fcitx-kkc package in Ubuntu:
  New
Status in felix-latin package in Ubuntu:
  New
Status in flightcrew package in Ubuntu:
  New
Status in fmit package in Ubuntu:
  New
Status in fraqtive package in Ubuntu:
  New
Status in freecad package in Ubuntu:
  New
Status in freemat package in Ubuntu:
  New
Status in freemedforms-project package in Ubuntu:
  New
Status in freeplayer package in Ubuntu:
  New
Status in gammaray package in Ubuntu:
  New
Status in gebabbel package in Ubuntu:
  New
Status in genpo package in Ubuntu:
  New
Status in gle-graphics package in Ubuntu:
  New
Status in gmic package in Ubuntu:
  New
Status in gnash package in Ubuntu:
  New
Status in gnudoq package in Ubuntu:
  New
Status in gr-fosphor package in Ubuntu:
  New
Status in gr-radar package in Ubuntu:
  New
Status in grantlee package in Ubuntu:
  New
Status in gwenrename package in Ubuntu:
  New
Status in hamfax package in Ubuntu:
  New
Status in hedgewars package in Ubuntu:
  New
Status in heimdall-flash package in Ubuntu:
  New
Status in holdingnuts package in Ubuntu:
  New
Status in hydrogen package in Ubuntu:
  New
Status in ibus-qt package in Ubuntu:
  New
Status in ifpgui package in Ubuntu:
  New
Status in ifrit package in Ubuntu:
  New
Status in ike package in Ubuntu:
  New
Status in imagevis3d package in Ubuntu:
  New
Status in jovie package in Ubuntu:
  New
Status in jreen package in Ubuntu:
  New
Status in kaccessible package in Ubuntu:
  New
Status in kactivities package in Ubuntu:
  New
Status in kalternatives package in Ubuntu:
  New
Status in kamerka package in Ubuntu:
  New
Status in karlyriceditor package in Ubuntu:
  New
Status in kate4 package in Ubuntu:
  New
Status in kchmviewer package in Ubuntu:
  New
Status in kcm-qt-graphicssystem package in Ubuntu:
  New
Status in kcollectd package in Ubuntu:
  New
Status in kdbg package in Ubuntu:
  New
Status in kde-baseapps package in Ubuntu:
  New
Status in kde-runtime package in Ubuntu:
  New
Status in kde-thumbnailer-openoffice package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kde4pimlibs package in Ubuntu:
  New
Status in kdepim4 package in Ubuntu:
  New
Status in kdesudo package in Ubuntu:
  Confirmed
Status in kdiff3 package in Ubuntu:
  New
Status in kdoctools package in Ubuntu:
  New
Status in keepassx package in Ubuntu:
  New
Status in kepas package in Ubuntu:
  New
Status in keurocalc package in Ubuntu:
  New
Status in kffmpegthumbnailer package in Ubuntu:
  New
Status in 

[Desktop-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

[handsome_feng]

** Changed in: youker-assistant (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntukylin-meta (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1757320

Title:
  Remove Qt 4 from the archive

Status in acoustid-fingerprinter package in Ubuntu:
  New
Status in adwaita-qt package in Ubuntu:
  New
Status in akonadi4 package in Ubuntu:
  New
Status in alsoft-conf package in Ubuntu:
  New
Status in alt-key package in Ubuntu:
  New
Status in amarok package in Ubuntu:
  New
Status in amora-server package in Ubuntu:
  New
Status in ams package in Ubuntu:
  New
Status in analitza4 package in Ubuntu:
  New
Status in appmenu-qt package in Ubuntu:
  New
Status in aseba package in Ubuntu:
  New
Status in attal package in Ubuntu:
  New
Status in attica package in Ubuntu:
  New
Status in auralquiz package in Ubuntu:
  New
Status in automoc package in Ubuntu:
  New
Status in autopilot-qt package in Ubuntu:
  New
Status in avogadro package in Ubuntu:
  New
Status in bacula package in Ubuntu:
  New
Status in ball package in Ubuntu:
  New
Status in baloo package in Ubuntu:
  New
Status in basket package in Ubuntu:
  New
Status in boats package in Ubuntu:
  New
Status in bodega-client package in Ubuntu:
  New
Status in bppphyview package in Ubuntu:
  New
Status in breeze package in Ubuntu:
  New
Status in cagibi package in Ubuntu:
  New
Status in cdcat package in Ubuntu:
  New
Status in chinese-calendar package in Ubuntu:
  New
Status in choreonoid package in Ubuntu:
  New
Status in clementine package in Ubuntu:
  New
Status in cmtk package in Ubuntu:
  New
Status in codelite package in Ubuntu:
  New
Status in codequery package in Ubuntu:
  New
Status in collatinus package in Ubuntu:
  New
Status in colord-kde package in Ubuntu:
  New
Status in connectome-workbench package in Ubuntu:
  New
Status in cortina package in Ubuntu:
  New
Status in cppreference-doc package in Ubuntu:
  New
Status in daemonfs package in Ubuntu:
  New
Status in dc-qt package in Ubuntu:
  New
Status in dee-qt package in Ubuntu:
  New
Status in dgedit package in Ubuntu:
  New
Status in dhcpcd-ui package in Ubuntu:
  New
Status in doomsday package in Ubuntu:
  New
Status in dssi package in Ubuntu:
  New
Status in enki-aseba package in Ubuntu:
  New
Status in eqonomize package in Ubuntu:
  New
Status in esperanza package in Ubuntu:
  New
Status in fbreader package in Ubuntu:
  New
Status in fcitx package in Ubuntu:
  New
Status in fcitx-kkc package in Ubuntu:
  New
Status in felix-latin package in Ubuntu:
  New
Status in flightcrew package in Ubuntu:
  New
Status in fmit package in Ubuntu:
  New
Status in fraqtive package in Ubuntu:
  New
Status in freecad package in Ubuntu:
  New
Status in freemat package in Ubuntu:
  New
Status in freemedforms-project package in Ubuntu:
  New
Status in freeplayer package in Ubuntu:
  New
Status in gammaray package in Ubuntu:
  New
Status in gebabbel package in Ubuntu:
  New
Status in genpo package in Ubuntu:
  New
Status in gle-graphics package in Ubuntu:
  New
Status in gmic package in Ubuntu:
  New
Status in gnash package in Ubuntu:
  New
Status in gnudoq package in Ubuntu:
  New
Status in gr-fosphor package in Ubuntu:
  New
Status in gr-radar package in Ubuntu:
  New
Status in grantlee package in Ubuntu:
  New
Status in gwenrename package in Ubuntu:
  New
Status in hamfax package in Ubuntu:
  New
Status in hedgewars package in Ubuntu:
  New
Status in heimdall-flash package in Ubuntu:
  New
Status in holdingnuts package in Ubuntu:
  New
Status in hydrogen package in Ubuntu:
  New
Status in ibus-qt package in Ubuntu:
  New
Status in ifpgui package in Ubuntu:
  New
Status in ifrit package in Ubuntu:
  New
Status in ike package in Ubuntu:
  New
Status in imagevis3d package in Ubuntu:
  New
Status in jovie package in Ubuntu:
  New
Status in jreen package in Ubuntu:
  New
Status in kaccessible package in Ubuntu:
  New
Status in kactivities package in Ubuntu:
  New
Status in kalternatives package in Ubuntu:
  New
Status in kamerka package in Ubuntu:
  New
Status in karlyriceditor package in Ubuntu:
  New
Status in kate4 package in Ubuntu:
  New
Status in kchmviewer package in Ubuntu:
  New
Status in kcm-qt-graphicssystem package in Ubuntu:
  New
Status in kcollectd package in Ubuntu:
  New
Status in kdbg package in Ubuntu:
  New
Status in kde-baseapps package in Ubuntu:
  New
Status in kde-runtime package in Ubuntu:
  New
Status in kde-thumbnailer-openoffice package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kde4pimlibs package in Ubuntu:
  New
Status in kdepim4 package in Ubuntu:
  New
Status in kdesudo package in Ubuntu:
  Confirmed
Status in kdiff3 package in Ubuntu:
  New
Status in kdoctools package in Ubuntu:
  New
Status in keepassx package in Ubuntu:
  New
Status in kepas package in Ubuntu:
  New
Status in keurocalc package in 

[Desktop-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

[Simon Quigley]

** Description changed:

  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support case.
  
  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 must either get ported to Qt 5 and
  uploaded to the development release or get removed (by means of demotion
  to -proposed or the whole source package removal) before the 19.04
  release. If it is possible to do this by the 18.10 release, please do so.
  
  No new packages entering the Ubuntu archive should depend on qt4-x11 or
  any package which directly or indirectly depends on it.
  
  [1] https://wiki.debian.org/Qt4Removal
- 
-  affects ubuntu/acoustid-fingerprinter
-  importance medium
-  affects ubuntu/adwaita-qt
-  importance medium
-  affects ubuntu/akonadi4
-  importance medium
-  affects ubuntu/alsoft-conf
-  importance medium
-  affects ubuntu/alt-key
-  importance medium
-  affects ubuntu/amarok
-  importance medium
-  affects ubuntu/amora-server
-  importance medium
-  affects ubuntu/ams
-  importance medium
-  affects ubuntu/analitza4
-  importance medium
-  affects ubuntu/appmenu-qt
-  importance medium
-  affects ubuntu/aseba
-  importance medium
-  affects ubuntu/attal
-  importance medium
-  affects ubuntu/attica
-  importance medium
-  affects ubuntu/auralquiz
-  importance medium
-  affects ubuntu/automoc
-  importance medium
-  affects ubuntu/autopilot-qt
-  importance medium
-  affects ubuntu/avogadro
-  importance medium
-  affects ubuntu/bacula
-  importance medium
-  affects ubuntu/ball
-  importance medium
-  affects ubuntu/baloo
-  importance medium
-  affects ubuntu/basket
-  importance medium
-  affects ubuntu/boats
-  importance medium
-  affects ubuntu/bodega-client
-  importance medium
-  affects ubuntu/bppphyview
-  importance medium
-  affects ubuntu/breeze
-  importance medium
-  affects ubuntu/cagibi
-  importance medium
-  affects ubuntu/cdcat
-  importance medium
-  affects ubuntu/chinese-calendar
-  importance medium
-  affects ubuntu/choreonoid
-  importance medium
-  affects ubuntu/clementine
-  importance medium
-  affects ubuntu/cmtk
-  importance medium
-  affects ubuntu/codelite
-  importance medium
-  affects ubuntu/codequery
-  importance medium
-  affects ubuntu/collatinus
-  importance medium
-  affects ubuntu/colord-kde
-  importance medium
-  affects ubuntu/connectome-workbench
-  importance medium
-  affects ubuntu/cortina
-  importance medium
-  affects ubuntu/cppreference-doc
-  importance medium
-  affects ubuntu/daemonfs
-  importance medium
-  affects ubuntu/dc-qt
-  importance medium
-  affects ubuntu/dee-qt
-  importance medium
-  affects ubuntu/dgedit
-  importance medium
-  affects ubuntu/dhcpcd-ui
-  importance medium
-  affects ubuntu/doomsday
-  importance medium
-  affects ubuntu/dssi
-  importance medium
-  affects ubuntu/enki-aseba
-  importance medium
-  affects ubuntu/eqonomize
-  importance medium
-  affects ubuntu/esperanza
-  importance medium
-  affects ubuntu/fbreader
-  importance medium
-  affects ubuntu/fcitx
-  importance medium
-  affects ubuntu/fcitx-kkc
-  importance medium
-  affects ubuntu/felix-latin
-  importance medium
-  affects ubuntu/flightcrew
-  importance medium
-  affects ubuntu/fmit
-  importance medium
-  affects ubuntu/fraqtive
-  importance medium
-  affects ubuntu/freecad
-  importance medium
-  affects ubuntu/freemat
-  importance medium
-  affects ubuntu/freemedforms-project
-  importance medium
-  affects ubuntu/freeplayer
-  importance medium
-  affects ubuntu/gammaray
-  importance medium
-  affects ubuntu/gebabbel
-  importance medium
-  affects ubuntu/genpo
-  importance medium
-  affects ubuntu/gle-graphics
-  importance medium
-  affects ubuntu/gmic
-  importance medium
-  affects ubuntu/gnash
-  importance medium
-  affects ubuntu/gnudoq
-  importance medium
-  affects ubuntu/grantlee
-  importance medium
-  affects ubuntu/gr-fosphor
-  importance medium
-  affects ubuntu/gr-radar
-  importance medium
-  affects ubuntu/gwenrename
-  importance medium
-  affects ubuntu/hamfax
-  importance medium
-  affects ubuntu/hedgewars
-  importance medium
-  affects ubuntu/heimdall-flash
-  importance medium
-  affects ubuntu/holdingnuts
-  importance medium
-  affects ubuntu/hydrogen
-  importance medium
-  affects ubuntu/ibus-qt
-  importance medium
-  affects ubuntu/ifpgui
-  importance medium
-  affects ubuntu/ifrit
-  importance medium
-  affects ubuntu/ike
-  importance medium
-  affects ubuntu/imagevis3d
-  importance medium
-  affects ubuntu/jovie
-  importance medium
-  affects ubuntu/jreen
-  importance medium
-  affects ubuntu/kaccessible
-  importance medium
-  affects ubuntu/kactivities
-  importance medium
-  affects ubuntu/kalternatives
-  importance medium
-  affects ubuntu/kamerka
-  importance medium
-  affects ubuntu/karlyriceditor
-  importance medium
-  affects ubuntu/kate4
-  importance medium
-  affects 

[Desktop-packages] [Bug 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices

[Jeff Conner]

I had a similar problem with my Dell Latitude 5289 using Ubuntu 17.10.
After trying different things, I got it to work by using hdajackretask.
I got a clue from norteo on this thread:

https://askubuntu.com/questions/926590/headphone-not-working-on-
ubuntu-17-04-dell-xps-15

To get it to work for my specific setup, I ran hdajackretask, checked
the box to "show unconnected pins," selected "override" for pin 0x21,
and set it to "Headphone." I did not override or adjust any of the other
pins.

I realize you're using a different version of Ubuntu, but I hope this
might help you or someone else using a Dell Latitude 5289.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1728093

Title:
  [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize
  Devices

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289
  Ultrabook that has a single 3.5mm jack for both input and output. This
  installation is in a dual-boot situation with Windows 10. This device
  has UEFI secure boot enabled.

  The combo jack works perfectly in Windows 10, however, when I plug in
  a headset or headphone of any kind, it does not register that anything
  has been plugged in. The laptop is connected to a Dell dock via USB-C,
  so there is also USB Audio (Output only) available on the dock, but
  that also does not work. It worked for one session yesterday on my
  dock at work, however it does not work at my dock that I have at home.
  The internal speakers and the microphone built into the lid work fine.
  The Combo jack also does not work disconnected from the dock.

  I have installed gnome and gnome-shell, but it does not work in either
  gnome or unity (I continue to use lightdm so that I can switch back
  and forth).

  Neither Unity nor Gnome bring up any kind of "What Did You Plug In"
  dialog.

  alsamixer does not have a headphone option as expected

  pavucontrol does not allow me to select "Headphones" under the Built-
  in Audio Analog Stereo Port

  I have attempted to tweak settings in hdajackretask to no success

  I have attempted to add:

  options snd_hda_intel model=dell-headset-multi(dell-headset-dock,
  generic, auto, headset-mic, etc) to no success

  I have also tried updating my kernel to 4.13.10, to no success.

  I also tried 17.10 to no success.

  Outputs:
  --
  uname -sr
  Linux 4.10.0-37-generic
  --
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  cat /proc/asound/car*/co* | grep Codec
  Codec: Realtek ALC3253
  Codec: Intel Kabylake HDMI

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

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

[Desktop-packages] [Bug 1757321] [NEW] Can't mount encrypted USB drive after upgrade to bionic

[Joe Barnett]

Public bug reported:

after upgrading to bionic, attempts to mount an encrypted USB drive fail
with the error "function bd_crypto_luks_open_blob called but not
implemented"

Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting
appears to have fixed it, but should that be necessary?  or at least
better documented?
(https://www.distrowatch.com/weekly.php?issue=20171113 is the only
reference I could find on the error)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-2ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules
Date: Tue Mar 20 20:28:39 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (942 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
MachineType: Apple Inc. MacBookPro11,4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1
SourcePackage: udisks2
UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321

Title:
  Can't mount encrypted USB drive after upgrade to bionic

Status in udisks2 package in Ubuntu:
  New

Bug description:
  after upgrading to bionic, attempts to mount an encrypted USB drive
  fail with the error "function bd_crypto_luks_open_blob called but not
  implemented"

  Installing libblockdev-crypto2 and libblockdev-crypto-dev and
  rebooting appears to have fixed it, but should that be necessary?  or
  at least better documented?
  (https://www.distrowatch.com/weekly.php?issue=20171113 is the only
  reference I could find on the error)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-2ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules
  Date: Tue Mar 20 20:28:39 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (942 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1756184] Re: Search making excessive requests for snap details and search

[Robert Ancell]

3.28.0-0ubuntu5 should now not do a detail request for each of the
featured snaps (uses the metadata from the search result instead). It
will now do a detail lookup the first time you click on a snap.

Note that we do still do a detail lookup on each installed snap when you
start - this is a long standing issue due to the icon information not
being reliable on local snaps. If these requests are an issue we should
tackle that in another bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1756184

Title:
  Search making excessive requests for snap details and search

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  If you turn on snapd debugging and watch the log, you will see some
  excessive hits when working in Gnome Software. In particular, it
  seems:

  - Search makes the search request and then a details hit for every result
  - After clicking into a snap detail page and returning to the list, the query 
is repeated.

  Details requests should only be needed when clicking on a result, and
  returning to the search results should not repeat the query.

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

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

[Desktop-packages] [Bug 1757320] Re: Remove Qt 4 from the archive

[Simon Quigley]

** Description changed:

  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support case.
  
  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 must either get ported to Qt 5 and
  uploaded to the development release or get removed (by means of demotion
  to -proposed or the whole source package removal) before the 19.04
  release. If it is possible to do this by the 18.10 release, please do so.
  
  No new packages entering the Ubuntu archive should depend on qt4-x11 or
  any package which directly or indirectly depends on it.
  
  [1] https://wiki.debian.org/Qt4Removal
  
-  affects ubuntu/acoustid-fingerprinter
-  importance medium
-  affects ubuntu/adwaita-qt
-  importance medium
-  affects ubuntu/akonadi4
-  importance medium
-  affects ubuntu/alsoft-conf
-  importance medium
-  affects ubuntu/alt-key
-  importance medium
-  affects ubuntu/amarok
-  importance medium
-  affects ubuntu/amora-server
-  importance medium
-  affects ubuntu/ams
-  importance medium
-  affects ubuntu/analitza4
-  importance medium
-  affects ubuntu/appmenu-qt
-  importance medium
-  affects ubuntu/aseba
-  importance medium
-  affects ubuntu/attal
-  importance medium
-  affects ubuntu/attica
-  importance medium
-  affects ubuntu/auralquiz
-  importance medium
-  affects ubuntu/automoc
-  importance medium
-  affects ubuntu/autopilot-qt
-  importance medium
-  affects ubuntu/avogadro
-  importance medium
-  affects ubuntu/bacula
-  importance medium
-  affects ubuntu/ball
-  importance medium
-  affects ubuntu/baloo
-  importance medium
-  affects ubuntu/basket
-  importance medium
-  affects ubuntu/boats
-  importance medium
-  affects ubuntu/bodega-client
-  importance medium
-  affects ubuntu/bppphyview
-  importance medium
-  affects ubuntu/breeze
-  importance medium
-  affects ubuntu/cagibi
-  importance medium
-  affects ubuntu/cdcat
-  importance medium
-  affects ubuntu/chinese-calendar
-  importance medium
-  affects ubuntu/choreonoid
-  importance medium
-  affects ubuntu/clementine
-  importance medium
-  affects ubuntu/cmtk
-  importance medium
-  affects ubuntu/codelite
-  importance medium
-  affects ubuntu/codequery
-  importance medium
-  affects ubuntu/collatinus
-  importance medium
-  affects ubuntu/colord-kde
-  importance medium
-  affects ubuntu/connectome-workbench
-  importance medium
-  affects ubuntu/cortina
-  importance medium
-  affects ubuntu/cppreference-doc
-  importance medium
-  affects ubuntu/daemonfs
-  importance medium
-  affects ubuntu/dc-qt
-  importance medium
-  affects ubuntu/dee-qt
-  importance medium
-  affects ubuntu/dgedit
-  importance medium
-  affects ubuntu/dhcpcd-ui
-  importance medium
-  affects ubuntu/doomsday
-  importance medium
-  affects ubuntu/dssi
-  importance medium
-  affects ubuntu/enki-aseba
-  importance medium
-  affects ubuntu/eqonomize
-  importance medium
-  affects ubuntu/esperanza
-  importance medium
-  affects ubuntu/fbreader
-  importance medium
-  affects ubuntu/fcitx
-  importance medium
-  affects ubuntu/fcitx-kkc
-  importance medium
-  affects ubuntu/felix-latin
-  importance medium
-  affects ubuntu/flightcrew
-  importance medium
-  affects ubuntu/fmit
-  importance medium
-  affects ubuntu/fraqtive
-  importance medium
-  affects ubuntu/freecad
-  importance medium
-  affects ubuntu/freemat
-  importance medium
-  affects ubuntu/freemedforms-project
-  importance medium
-  affects ubuntu/freeplayer
-  importance medium
-  affects ubuntu/gammaray
-  importance medium
-  affects ubuntu/gebabbel
-  importance medium
-  affects ubuntu/genpo
-  importance medium
-  affects ubuntu/gle-graphics
-  importance medium
-  affects ubuntu/gmic
-  importance medium
-  affects ubuntu/gnash
-  importance medium
-  affects ubuntu/gnudoq
-  importance medium
-  affects ubuntu/grantlee
-  importance medium
-  affects ubuntu/gr-fosphor
-  importance medium
-  affects ubuntu/gr-radar
-  importance medium
-  affects ubuntu/gwenrename
-  importance medium
-  affects ubuntu/hamfax
-  importance medium
-  affects ubuntu/hedgewars
-  importance medium
-  affects ubuntu/heimdall-flash
-  importance medium
-  affects ubuntu/holdingnuts
-  importance medium
-  affects ubuntu/hydrogen
-  importance medium
-  affects ubuntu/ibus-qt
-  importance medium
-  affects ubuntu/ifpgui
-  importance medium
-  affects ubuntu/ifrit
-  importance medium
-  affects ubuntu/ike
-  importance medium
-  affects ubuntu/imagevis3d
-  importance medium
-  affects ubuntu/jovie
-  importance medium
-  affects ubuntu/jreen
-  importance medium
-  affects ubuntu/kaccessible
-  importance medium
-  affects ubuntu/kactivities
-  importance medium
-  affects ubuntu/kalternatives
-  importance medium
-  affects ubuntu/kamerka
-  importance medium
-  affects ubuntu/karlyriceditor
-  importance medium
-  affects ubuntu/kate4
-  importance medium
-  affects 

[Desktop-packages] [Bug 1757320] [NEW] Remove Qt 4 from the archive

[Simon Quigley]

Public bug reported:

Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support case.

Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 must either get ported to Qt 5 and
uploaded to the development release or get removed (by means of demotion
to -proposed or the whole source package removal) before the 19.04
release. If it is possible to do this by the 18.10 release, please do so.

No new packages entering the Ubuntu archive should depend on qt4-x11 or
any package which directly or indirectly depends on it.

[1] https://wiki.debian.org/Qt4Removal

 affects ubuntu/acoustid-fingerprinter
 importance medium
 affects ubuntu/adwaita-qt
 importance medium
 affects ubuntu/akonadi4
 importance medium
 affects ubuntu/alsoft-conf
 importance medium
 affects ubuntu/alt-key
 importance medium
 affects ubuntu/amarok
 importance medium
 affects ubuntu/amora-server
 importance medium
 affects ubuntu/ams
 importance medium
 affects ubuntu/analitza4
 importance medium
 affects ubuntu/appmenu-qt
 importance medium
 affects ubuntu/aseba
 importance medium
 affects ubuntu/attal
 importance medium
 affects ubuntu/attica
 importance medium
 affects ubuntu/auralquiz
 importance medium
 affects ubuntu/automoc
 importance medium
 affects ubuntu/autopilot-qt
 importance medium
 affects ubuntu/avogadro
 importance medium
 affects ubuntu/bacula
 importance medium
 affects ubuntu/ball
 importance medium
 affects ubuntu/baloo
 importance medium
 affects ubuntu/basket
 importance medium
 affects ubuntu/boats
 importance medium
 affects ubuntu/bodega-client
 importance medium
 affects ubuntu/bppphyview
 importance medium
 affects ubuntu/breeze
 importance medium
 affects ubuntu/cagibi
 importance medium
 affects ubuntu/cdcat
 importance medium
 affects ubuntu/chinese-calendar
 importance medium
 affects ubuntu/choreonoid
 importance medium
 affects ubuntu/clementine
 importance medium
 affects ubuntu/cmtk
 importance medium
 affects ubuntu/codelite
 importance medium
 affects ubuntu/codequery
 importance medium
 affects ubuntu/collatinus
 importance medium
 affects ubuntu/colord-kde
 importance medium
 affects ubuntu/connectome-workbench
 importance medium
 affects ubuntu/cortina
 importance medium
 affects ubuntu/cppreference-doc
 importance medium
 affects ubuntu/daemonfs
 importance medium
 affects ubuntu/dc-qt
 importance medium
 affects ubuntu/dee-qt
 importance medium
 affects ubuntu/dgedit
 importance medium
 affects ubuntu/dhcpcd-ui
 importance medium
 affects ubuntu/doomsday
 importance medium
 affects ubuntu/dssi
 importance medium
 affects ubuntu/enki-aseba
 importance medium
 affects ubuntu/eqonomize
 importance medium
 affects ubuntu/esperanza
 importance medium
 affects ubuntu/fbreader
 importance medium
 affects ubuntu/fcitx
 importance medium
 affects ubuntu/fcitx-kkc
 importance medium
 affects ubuntu/felix-latin
 importance medium
 affects ubuntu/flightcrew
 importance medium
 affects ubuntu/fmit
 importance medium
 affects ubuntu/fraqtive
 importance medium
 affects ubuntu/freecad
 importance medium
 affects ubuntu/freemat
 importance medium
 affects ubuntu/freemedforms-project
 importance medium
 affects ubuntu/freeplayer
 importance medium
 affects ubuntu/gammaray
 importance medium
 affects ubuntu/gebabbel
 importance medium
 affects ubuntu/genpo
 importance medium
 affects ubuntu/gle-graphics
 importance medium
 affects ubuntu/gmic
 importance medium
 affects ubuntu/gnash
 importance medium
 affects ubuntu/gnudoq
 importance medium
 affects ubuntu/grantlee
 importance medium
 affects ubuntu/gr-fosphor
 importance medium
 affects ubuntu/gr-radar
 importance medium
 affects ubuntu/gwenrename
 importance medium
 affects ubuntu/hamfax
 importance medium
 affects ubuntu/hedgewars
 importance medium
 affects ubuntu/heimdall-flash
 importance medium
 affects ubuntu/holdingnuts
 importance medium
 affects ubuntu/hydrogen
 importance medium
 affects ubuntu/ibus-qt
 importance medium
 affects ubuntu/ifpgui
 importance medium
 affects ubuntu/ifrit
 importance medium
 affects ubuntu/ike
 importance medium
 affects ubuntu/imagevis3d
 importance medium
 affects ubuntu/jovie
 importance medium
 affects ubuntu/jreen
 importance medium
 affects ubuntu/kaccessible
 importance medium
 affects ubuntu/kactivities
 importance medium
 affects ubuntu/kalternatives
 importance medium
 affects ubuntu/kamerka
 importance medium
 affects ubuntu/karlyriceditor
 importance medium
 affects ubuntu/kate4
 importance medium
 affects ubuntu/kchmviewer
 importance medium
 affects ubuntu/kcm-qt-graphicssystem
 importance medium
 affects ubuntu/kcollectd
 importance medium
 affects ubuntu/kdbg
 importance medium
 affects ubuntu/kde4libs
 importance medium
 affects ubuntu/kde4pimlibs
 importance medium
 affects ubuntu/kde-baseapps
 importance medium
 affects ubuntu/kdepim4
 importance medium
 affects ubuntu/kde-runtime
 

[Desktop-packages] [Bug 1526155] Re: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Daniel van Vugt]

** Also affects: nvidia-graphics-drivers-384 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => Confirmed

** Tags added: artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1526155

Title:
  nvidia-* kernel module failed to build [cc: error: unrecognized
  command line option ‘-fstack-protector-strong’]

Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-340 340.96-0ubuntu0.14.04.1
  Uname: Linux 4.0.4-040004-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  DKMSKernelVersion: 4.3.2-040302-generic
  Date: Tue Dec 15 01:29:18 2015
  DuplicateSignature: dkms:nvidia-340:340.96-0ubuntu0.14.04.1:cc: error: 
unrecognized command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2014-10-15 (425 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 340.96-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.96-0ubuntu0.14.04.1: nvidia-340 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.340.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1526155/+subscriptions

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

[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

I did intentionally omit some ffmpeg packages that I thought should be
irrelevant, but you can try reinstalling those too. It won't hurt.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

I worked it out from experience and the common version number
7:2.8.11-0ubuntu0.16.04.1

However more generally you can see the full list of binary ffmpeg packages here:
https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/12004843

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific)

[Daniel van Vugt]

Please try the workaround mentioned in bug 1727232

** Tags added: nvidia visual-quality

** Summary changed:

- Brightness, contrast issues (possibly NVidia specific)
+ Brightness, contrast issues (possibly NVidia specific) in totem and VLC

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1757301

Title:
  Brightness, contrast issues (possibly NVidia specific) in totem and
  VLC

Status in totem package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

[Daniel van Vugt]

Also your kernel log (dmesg.txt) is showing a lot of errors from the
nouveau graphics driver. Nouveau is known to have lots of bugs, so
please try installing this one instead:

  sudo apt install nvidia-driver-390

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756877

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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

[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

[Daniel van Vugt]

Please also try updating again. Just 1 hour ago we got a newer version
of libinput: 1.10.3

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756877

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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

[Desktop-packages] [Bug 1757307] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1757307

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386 while trying to install Epson
  Perfection V300 photo driver  and trying to fix broken packages with
  synaptics

Status in sane-backends package in Ubuntu:
  New

Bug description:
  was trying to install iscan-gt-f720-bundle-1.0.1.x86.deb to run my
  Epson Perfection V300 Photo scanner using the install.sh script ; got
  errors so tried to fix broken packages with synaptics which resolved
  some but was not able to install libsane1. Will run synaptics from
  time to time to see if you guys fixed the package. Thx

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Mar 21 09:45:25 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-84qUMV/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-15 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-21 (150 days ago)

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Jeremy Bicha]

** Description changed:

+ Impact
+ --
+ webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).
+ 
+ Deja Dup's monitor background service had "ulimit -v 100" (that's 1
+ GB) set as a workaround for a memory leak issue that the developer was
+ unable to reproduce.
+ 
+ After upgrading to the new webkit2gtk version, Deja Dup's monitor
+ service will crash because of that virtual memory limit.
+ 
+ Test Case
+ -
+ Install the deja-dup update.
+ Install the webkit2gtk update from a PPA (not prepared yet).
+ Log out. Log in.
+ After a few minutes, check /var/crash/ for any Deja Dup crash reports.
+ 
+ Regression Potential
+ 
+ This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.
+ 
+ Other Info
+ --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1751460

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Triaged
Status in deja-dup source package in Artful:
  Triaged
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Desktop-packages] [Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)

[Daniel van Vugt]

Marco's fix is in progress here:

  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/4

** Summary changed:

- Object ..., has been already finalized. Impossible to get any property from 
it. ... (stack trace in tweener.js)
+ syslog fills with messages: Object ..., has been already finalized. 
Impossible to get any property from it. ... (stack trace in tweener.js)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1747566

Title:
  syslog fills with messages: Object ..., has been already finalized.
  Impossible to get any property from it. ... (stack trace in
  tweener.js)

Status in GNOME Shell:
  Expired
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not
  getting a lot of stacktraces in my syslog:

  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to get any property from it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to set any property to it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb 

[Desktop-packages] [Bug 1757307] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Dimitri Volpe]

Public bug reported:

was trying to install iscan-gt-f720-bundle-1.0.1.x86.deb to run my Epson
Perfection V300 Photo scanner using the install.sh script ; got errors
so tried to fix broken packages with synaptics which resolved some but
was not able to install libsane1. Will run synaptics from time to time
to see if you guys fixed the package. Thx

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Wed Mar 21 09:45:25 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-84qUMV/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-10-15 (156 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: Upgraded to artful on 2017-10-21 (150 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1757307

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386 while trying to install Epson
  Perfection V300 photo driver  and trying to fix broken packages with
  synaptics

Status in sane-backends package in Ubuntu:
  New

Bug description:
  was trying to install iscan-gt-f720-bundle-1.0.1.x86.deb to run my
  Epson Perfection V300 Photo scanner using the install.sh script ; got
  errors so tried to fix broken packages with synaptics which resolved
  some but was not able to install libsane1. Will run synaptics from
  time to time to see if you guys fixed the package. Thx

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Mar 21 09:45:25 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-84qUMV/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-15 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-21 (150 days ago)

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

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Daniel van Vugt]

This bug is closed.

Please log new bugs if you have any issues at all.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1721428

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Jeremy Bicha]

I am closing the webkit2gtk part of this bug.

It was mentioned that someone might set a virtual memory limit for their
entire system. I don't think setting that makes sense on a desktop and
it's my understanding that doing so will also break Java apps for a
similar reason.

To test the impact of this, I added this to my ~/.profile

ulimit -v 400

After logging out and logging back in, I was still able to run GNOME
Shell (although presumably the Captive Portal feature won't work). Any
webkit using apps won't work (and that includes Epiphany, gnome-control-
center, evolution, etc.).

At least the systemd journal records this basic error message:

org.gnome.Epiphany.desktop[12949]: FATAL: Could not allocate gigacage
memory with maxAlignment = 34359738368, totalSize = 103079215104.

.

The next upstream release of webkit2gtk will also add this to that error
message: "Make sure you have not set a virtual memory limit."

So the remaining task here is to provide a deja-dup update to all
supported Ubuntu releases so that we can safely provide webkit2gtk
security updates there.

** No longer affects: webkit2gtk (Ubuntu Bionic)

** Changed in: webkit2gtk (Ubuntu)
   Status: Triaged => Invalid

** No longer affects: webkit2gtk (Ubuntu Xenial)

** No longer affects: webkit2gtk (Ubuntu Artful)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1751460

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Triaged
Status in deja-dup source package in Artful:
  Triaged
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

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

[Desktop-packages] [Bug 1756508] Re: Gnome-shell cpu load dramatically high and stuck high with Eclipse

[Daniel van Vugt]

If I had to guess, I would guess that Eclipse is using a software-
rendered toolkit. And those are particularly expensive to render in
Gnome Shell. The reason why nobody has paid much attention to such bugs
so far is that the problem is pretty uncommon. You need both a software-
rendered toolkit, AND an app that redraws constantly.

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

** Tags added: performance

** Summary changed:

- Gnome-shell cpu load dramatically high and stuck high with Eclipse
+ Gnome-shell CPU load dramatically high and stuck high with Eclipse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell CPU load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Daniel van Vugt]

If you don't like waiting for mirrors, then you can open app 'Software & 
Updates' and change:
  Download from = Main server

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice

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

[Daniel van Vugt]

Alex,

The mutter fix does set its own settings for TapButtons. And gnome-
control-center (for reasons unexplained) has no GUI to configure it. But
you can affect those settings by installing and running 'gnome-tweak-
tool' and then set:

  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Mouse Click Emulation
= Fingers

which is the same as TapButton1=1 TapButton2=3 TapButton3=2.

If that's not enough then you can also force your own settings by
running command 'synclient'. Once you know the synclient syntax you want
you can apply it automatically at login by running 'gnome-session-
properties'.

And if that's still not enough then you can also log a bug if you like:
https://bugs.launchpad.net/ubuntu/+source/mutter/+filebug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center 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 gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

[Daniel van Vugt]

Also make sure you have Settings > Mouse & Touchpad > Touchpad > Tap to Click = 
ON
:)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center 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 gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1757301] [NEW] Brightness, contrast issues (possibly NVidia specific)

[Paul Dorman]

Public bug reported:

This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
The NVidia drivers was installed using the Additional Drivers dialog.

Videos, in both Totem (the default video player) and VLC, are quite
dark. The NVidia settings do not provide the color correction controls
I've seen with previous versions (possibly due to PRIME).

If I open Totem's display preferences, and try to change any value for
brightness, contrast, saturation, or hue, the video window goes
completely black. Clicking the "Reset to Defaults" button restores the
video playback. When the screen is black, subtitles and audio play as
per normal.

I traced this down to the package vdpau-va-driver not being installed on
the system. I presume this is a missing dependency. I did have vdpau-
driver-all:amd64 installed, but this is probably unrelated.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 21 13:32:28 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2018-03-15 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_NZ:en
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1757301

Title:
  Brightness, contrast issues (possibly NVidia specific)

Status in totem package in Ubuntu:
  New

Bug description:
  This issue pertains to a fresh install of Ubuntu 17.10 on a Dell
  Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed.
  The NVidia drivers was installed using the Additional Drivers dialog.

  Videos, in both Totem (the default video player) and VLC, are quite
  dark. The NVidia settings do not provide the color correction controls
  I've seen with previous versions (possibly due to PRIME).

  If I open Totem's display preferences, and try to change any value for
  brightness, contrast, saturation, or hue, the video window goes
  completely black. Clicking the "Reset to Defaults" button restores the
  video playback. When the screen is black, subtitles and audio play as
  per normal.

  I traced this down to the package vdpau-va-driver not being installed
  on the system. I presume this is a missing dependency. I did have
  vdpau-driver-all:amd64 installed, but this is probably unrelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 13:32:28 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-03-15 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757299] Re: xorg hangs

[gregrwm]

** Attachment added: "output from second ubuntu-bug xserver-xorg (see OP)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/+attachment/5085482/+files/apport.xserver-xorg.i_uz953i.apport

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1757299

Title:
  xorg hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux

  xorg stopped responding, ctl-alt-Fn don't respond either

  logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
  noticed twm no longer running
  launched ubuntu-bug xserver-xorg
  answered its question re display manager log files
  i left it printing endless periods for over an hour

  killed xorg
  launched startx again
  started a second ubuntu-bug xserver-xorg
  answered its questions re display manager log files and additional debugging 
work

  noticed the first ubuntu-bug xserver-xorg is no longer printing periods
  answered its questions re additional debugging work and Send problem report

  attached copy of htop output

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles    
[ OK ]
* Restoring resolver state...    
[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-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/1757299/+subscriptions

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

[Desktop-packages] [Bug 1757299] [NEW] xorg hangs

[gregrwm]

Public bug reported:

launched startx,
launched an xterm via twm,
launched another xterm via the first,
launched tmux,
launched firefox-esr, bluetooth-manager, and pavucontrol,
maximized the xterm running tmux

xorg stopped responding, ctl-alt-Fn don't respond either

logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
noticed twm no longer running
launched ubuntu-bug xserver-xorg
answered its question re display manager log files
i left it printing endless periods for over an hour

killed xorg
launched startx again
started a second ubuntu-bug xserver-xorg
answered its questions re display manager log files and additional debugging 
work

noticed the first ubuntu-bug xserver-xorg is no longer printing periods
answered its questions re additional debugging work and Send problem report

attached copy of htop output

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog:
 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  * Starting AppArmor profiles    
[ OK ]
  * Restoring resolver state...    
[ OK ]
CompositorRunning: None
Date: Tue Mar 20 17:15:16 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
JournalErrors:
 -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
 Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
 Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
 Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
 Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon already 
running.
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 LC_TIME=en_DK.utf8
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-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

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

** Attachment added: "see OP"
   https://bugs.launchpad.net/bugs/1757299/+attachment/5085469/+files/htop

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1757299

Title:
  xorg hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux

  xorg stopped responding, ctl-alt-Fn don't respond either

  logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
  noticed twm no longer running
  launched ubuntu-bug xserver-xorg
  answered its question re display manager log files
  i left it printing endless periods for over an hour

  killed xorg
  launched startx again
  started a second ubuntu-bug xserver-xorg
  answered its questions re display manager log files 

[Desktop-packages] [Bug 1757290] [NEW] gnome-control-center crashed with SIGABRT in g_assertion_message()

[Huzaeni]

Public bug reported:

crash report show on startup, i just reporting this

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Wed Mar 21 06:39:03 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-03-07 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: gnome-control-center background
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 ()
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash bionic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757290

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  crash report show on startup, i just reporting this

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Mar 21 06:39:03 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-07 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  ProcCmdline: gnome-control-center background
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1757290] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757290

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  crash report show on startup, i just reporting this

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Mar 21 06:39:03 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-07 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  ProcCmdline: gnome-control-center background
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1752530] Re: Logitech touchpad hesitates or stops

[Timo Aaltonen]

there's libinput 1.10.3-2 in bionic-proposed that you could try

** Package changed: xorg (Ubuntu) => libinput (Ubuntu)

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752530

Title:
  Logitech touchpad hesitates or stops

Status in libinput package in Ubuntu:
  Incomplete

Bug description:
  Under 18.04, for about a week now, my touchpad’s pointer is very hesitant and 
just stops most of the time. It will only starts moving again after clicking 
buttons a couple times and will work for a second or two.
  I have a similar problem running Bionic 2018-02-28 Live USB.
  The hardware is not at cause here since it works perfectly under 17.10 on the 
same system.
  Don,t know if it is xorg or kernel related.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  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:Unity7:ubuntu
  Date: Thu Mar  1 04:16:40 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-9-generic.efi.signed 
root=UUID=e7e6966f-9ca5-4778-a2bc-ad2522e9e73d ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/26/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90+git1803010630.bca585~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803010730.ba642e~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803010730.ba642e~oibaf~b
  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
  xserver.bootTime: Thu Mar  1 04:05:28 2018
  xserver.configfile: default
  xserver.errors:
   modeset(0): eglGetDisplay() failed
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1757280] [NEW] Night Light only on one Monitor

[Ivo Ruetsche]

Public bug reported:


Hi

If I activate the Night Light mode with an external monitor connected,
the mode is only on the external monitor activated.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompositorRunning: None
Date: Tue Mar 20 23:12:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2018-03-19 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
MachineType: LENOVO 20HF0016MZ
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET45W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HF0016MZ
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HF0016MZ
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
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

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


** Tags: amd64 apport-bug bionic reproducible ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1757280

Title:
  Night Light only on one Monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Hi

  If I activate the Night Light mode with an external monitor connected,
  the mode is only on the external monitor activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Mar 20 23:12:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2018-03-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  MachineType: LENOVO 20HF0016MZ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0016MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0016MZ
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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:

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10

[ramas]

This bug is serious for me as I use my scanner everyday.

I am under Lubuntu 17.10.

For who like me cannot wait the official patch, can follow how I did
solve:

1. get the source not from git but from the official package manager with 
command:
apt-get source libsane1
it did download and create the directory sane-backends-1.0.27/

2. modify the lines 2075-2077 of file sane-backends-1.0.27/backend/genesys.c 
into:
  if (dev->model->flags & GENESYS_FLAG_SHADING_REPARK && 
dev->model->cmd_set->slow_back_home)
{
  status = dev->model->cmd_set->slow_back_home (dev, dev->model->flags );

3. build the dependencies with command:
 sudo apt-get build-dep libsane1

4. I had to copy the file /usr/share/aclocal/libtool.m4 into sane-
backends-1.0.27/m4 as the build process complained it was missing

5. then build the fixed package with command:
  cd sane-backends-1.0.27
  dpkg-buildpackage -rfakeroot -uc -b

6. then install the updated package with command:
  cd ..
  sudo dpkg -i libsane1_1.0.27-1~experimental2ubuntu2.1_amd64.deb

7. I did restart my PC (but I do not know if this is necessary)

8. My simple-scan gui program did output a clean scan!!

reference here: https://askubuntu.com/questions/28372/how-do-i-get-and-
modify-the-source-code-of-packages-installed-through-apt-get/28373#28373

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

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

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

[Desktop-packages] [Bug 1755717] Re: FFE: xcb-proto/libxcb 1.13

[Timo Aaltonen]

I happened to sync xcb-proto already..

** Changed in: xcb-proto (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1755717

Title:
  FFE: xcb-proto/libxcb 1.13

Status in libxcb package in Ubuntu:
  New
Status in xcb-proto package in Ubuntu:
  Fix Released

Bug description:
  This will be needed for the first HWE stack in 18.04.2, so best to add
  them now and not as an SRU which will be more painful.

  xcb-proto
  Release 1.13 (2018-02-28)
  =
  * dri3: Add multi-plane/modifier protocol for v1.2
  * present: Add suboptimal-copy protocol for v1.2
  * randr: Add output-lease protocol for v1.6
  * Add support for variable-sized lists of FDs
  * xge: Add safe generic-event sending support
  * Fix initial connection handshaking
  * Updated XML DTD
  * Python 3.x cleanups and compatibility

  libxcb
  Release 1.13 (2018-02-28)
  =
  * Add support for variable-sized lists of FDs
  * Poll for events when blocking waiting for special events
  * xinput: Enable XInput extension by default
  * ge: Add explicit support for GenericEvent extension
  * Fix documentation warnings from clang
  * Cosmetic cleanups

  although it's hard for me to prove, but libxcb should fix a number of
  threading issues seen in the past.

  These are already in Debian testing, so they build and haven't caused
  regressions.

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

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

[Desktop-packages] [Bug 1752530] Re: Logitech touchpad hesitates or stops

[Fr-coord]

As of 2018-03-20, the problem is still present in Bionic. Installing
xserver-xorg-input-synaptics seem to have fixed the issue, but shouldn’t
libinput have been sufficient?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752530

Title:
  Logitech touchpad hesitates or stops

Status in xorg package in Ubuntu:
  New

Bug description:
  Under 18.04, for about a week now, my touchpad’s pointer is very hesitant and 
just stops most of the time. It will only starts moving again after clicking 
buttons a couple times and will work for a second or two.
  I have a similar problem running Bionic 2018-02-28 Live USB.
  The hardware is not at cause here since it works perfectly under 17.10 on the 
same system.
  Don,t know if it is xorg or kernel related.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  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:Unity7:ubuntu
  Date: Thu Mar  1 04:16:40 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-9-generic.efi.signed 
root=UUID=e7e6966f-9ca5-4778-a2bc-ad2522e9e73d ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/26/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90+git1803010630.bca585~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803010730.ba642e~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803010730.ba642e~oibaf~b
  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
  xserver.bootTime: Thu Mar  1 04:05:28 2018
  xserver.configfile: default
  xserver.errors:
   modeset(0): eglGetDisplay() failed
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1757266] [NEW] /etc/polkit-1/localauthority.conf.d/ parsed in wrong order?

[TJ]

Public bug reported:

On 16.04 and using the Xubuntu session (this isn't limited to XFCE) I
noticed that my notebook fails to suspend via power-management when the
idle timeout expires. When returning to it, if it still has power, I see
a polkit-agent GUI dialog asking me to authenticate.

In /var/log/auth.log is:

polkitd(authority=local): Operator of unix-session:c2 FAILED to
authenticate to gain authorization for action
org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46]
(owned by unix-user:tj)

So I started digging:

# inactive sleep is enabled
$ xfconf-query -c xfce4-power-manager -lv | grep inactivity
/xfce4-power-manager/inactivity-on-ac   14
/xfce4-power-manager/inactivity-on-battery  15
/xfce4-power-manager/inactivity-sleep-mode-on-battery   1

$ awk '/login1\.suspend"/ {E=1;print} /defaults/ && E == 1 {E++} E > 1 {print} 
/<\/action>/ && E > 1 {exit}' 
/usr/share/polkit-1/actions/org.freedesktop.login1.policy


auth_admin_keep
auth_admin_keep
yes



# member of sudo and adm
$ groups
tj adm dialout cdrom sudo dip plugdev lpadmin sambashare sbuild lxd libvirtd 
two_factor_auth

$ sudo find /etc/polkit-1/ -type f -exec sh -c 'echo === {} ===; cat {}' \; | 
egrep -v '^(#|$)'
=== /etc/polkit-1/localauthority/50-local.d/com.ubuntu.desktop.pkla ===
[Enable hibernate by default in upower]
Identity=unix-user:*
Action=org.freedesktop.upower.hibernate
ResultActive=yes
ResultInactive=yes
[Enable hibernate by default in logind]
Identity=unix-user:*
Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.handle-hibernate-key;org.freedesktop.login1;org.freedesktop.login1.hibernate-multiple-sessions;org.freedesktop.login1.hibernate-ignore-inhibit
ResultActive=yes
ResultInactive=yes
=== /etc/polkit-1/nullbackend.conf.d/50-nullbackend.conf ===
[Configuration]
Priority=-10
=== /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf ===
[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin
=== /etc/polkit-1/localauthority.conf.d/50-localauthority.conf ===
[Configuration]
AdminIdentities=unix-user:0

ubuntu-admin.conf policy sets AdminIdentities to include group 'sudo'
but seems to be ignored

"man 8 pklocalauthority" states that these files are parsed in C locale
lexical order, and gives examples of "...given the name 60-desktop-
policy.conf to ensure that it is evaluted after the
50-localauthority.conf file shipped with PolicyKit."

However:

$ sudo inotifywait -r -m /etc/polkit-1/localauthority.conf.d
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/etc/polkit-1/localauthority.conf.d/ OPEN,ISDIR
/etc/polkit-1/localauthority.conf.d/ ACCESS,ISDIR
/etc/polkit-1/localauthority.conf.d/ ACCESS,ISDIR
/etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE,ISDIR
/etc/polkit-1/localauthority.conf.d/ OPEN 51-ubuntu-admin.conf
/etc/polkit-1/localauthority.conf.d/ ACCESS 51-ubuntu-admin.conf
/etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE 51-ubuntu-admin.conf
/etc/polkit-1/localauthority.conf.d/ OPEN 50-localauthority.conf
/etc/polkit-1/localauthority.conf.d/ ACCESS 50-localauthority.conf
/etc/polkit-1/localauthority.conf.d/ CLOSE_NOWRITE,CLOSE 50-localauthority.conf

This seems to show that the sort order might be high-low not low-high
(unless they're sorted once in memory).

In view of the fact that ubuntu-admin.conf appears to be ignored I
suspect 50-localauthority.conf is replacing the ubuntu conf with the
default:

AdminIdentities=unix-group:sudo;unix-group:admin
AdminIdentities=unix-user:0

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  On 16.04 and using the Xubuntu session (this isn't limited to XFCE) I
  noticed that my notebook fails to suspend via power-management when the
  idle timeout expires. When returning to it, if it still has power, I see
  a polkit-agent GUI dialog asking me to authenticate.
  
  In /var/log/auth.log is:
  
  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46]
  (owned by unix-user:tj)
  
  So I started digging:
  
  # inactive sleep is enabled
  $ xfconf-query -c xfce4-power-manager -lv | grep inactivity
  /xfce4-power-manager/inactivity-on-ac   14
  /xfce4-power-manager/inactivity-on-battery  15
  /xfce4-power-manager/inactivity-sleep-mode-on-battery   1
  
- $ awk '/login1\.suspend"/ {E=1;print} /defaults/ && E == 1 {E++} E > 1 
{print} /<\/action>/ && E > 1 {exit}' 
/usr/share/polkit-1/actions/org.freedesktop.login1.policy 
- 
- 
- 

[Desktop-packages] [Bug 702452]

[Alexandre Julliard]

Closing bugs fixed in 3.4.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/702452

Title:
  [launcher] Wine applications are wrongly matched

Status in BAMF:
  Confirmed
Status in libwnck:
  Fix Released
Status in Unity:
  Confirmed
Status in Wine:
  Fix Released
Status in bamf package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  After launching a Wine app from terminal or via gnome-do, it appears in the 
launcher with the Wine icon, instead of its own icon. The title is "Wine Window 
Program Loader" instead of the proper application name.
  It can't be favorited since it will favorite the wine executable itself.
  And obviously different wine apps are all grouped under the same launcher 
icon.

  See also bug #635223 about Wine applications not showing up in the
  dash.

  
-

  A way to fix this is to make all the Wine generated .desktop file to
  include a StartupWMClass value that matches the instance name of the
  related program (generally the .exe file name to be executed).

  So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding 
this parameter:
   StartupWMClass=firefox.exe

  Wine should try to add this information at file generation time.

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

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

[Desktop-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Bug Watch Updater]

** Changed in: glib
   Status: Incomplete => Confirmed

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

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

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

[Desktop-packages] [Bug 1719462] Re: [Translation] "Left" and "Right" must be translated differently in different contexts

[Jeremy Bicha]

** Also affects: gnome-control-center (Ubuntu Bionic)
   Importance: Low
 Assignee: Didier Roche (didrocks)
   Status: Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1719462

Title:
  [Translation] "Left" and "Right" must be translated differently in
  different contexts

Status in Ubuntu Translations:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center source package in Bionic:
  Triaged

Bug description:
  In 17.10 artful in GNOME Control Center, there are two places where
  words "Left" and "Right" are encountered: the Mouse settings and the
  Dock settings. Both of the words have only one item to translate in
  Rosetta with indication that they are located in two different places
  in the sources:

  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

  When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
  I can guess that this is also valid for some other languages, not only 
Russian.

  Please make two independent translations in Rosetta for "Left" and
  "Right" in these two different contexts.

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

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

[Desktop-packages] [Bug 1757264] [NEW] Remote windows work with Xterm, but not gnome-terminal

[Bill Morita]

Public bug reported:

Ubuntu 17.10.1
Using ssh from a remote system, I am able to open remote windows on the remote 
system.
I am not able to do the same with gnome-terminal.

Both gnome-terminal and xterm were able to do this on 16.10

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1757264

Title:
  Remote windows work with Xterm, but not gnome-terminal

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10.1
  Using ssh from a remote system, I am able to open remote windows on the 
remote system.
  I am not able to do the same with gnome-terminal.

  Both gnome-terminal and xterm were able to do this on 16.10

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

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

[Desktop-packages] [Bug 1719462] Re: [Translation] "Left" and "Right" must be translated differently in different contexts

[Doctor Rover]

My apologies again, but I’m worried about possibility of yet another 
it’s-too-late situation like it was during artful development cycle (comment 
#7). 
I agree with Sebastien, it must be just a matter of giving context to two 
translatable strings.
Please give us -- Ubuntu translators -- possibility to provide quality 
translation. Thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1719462

Title:
  [Translation] "Left" and "Right" must be translated differently in
  different contexts

Status in Ubuntu Translations:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  In 17.10 artful in GNOME Control Center, there are two places where
  words "Left" and "Right" are encountered: the Mouse settings and the
  Dock settings. Both of the words have only one item to translate in
  Rosetta with indication that they are located in two different places
  in the sources:

  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

  When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
  I can guess that this is also valid for some other languages, not only 
Russian.

  Please make two independent translations in Rosetta for "Left" and
  "Right" in these two different contexts.

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Nish Aravamudan]

@cran: you can wait for your mirror, or download the debs from
archive.ubuntu.com.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :VAEntrypointVLD
 

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Sebastian Stark]

Excuse me if that is a stupid question: Where can I get the package for
trying it out? Or is the only way to way until it has propagated to the
mirrors?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

[Mark Vinod Sinnathamby]

I installed Ubuntu 17.10.1 today on my laptop, and got the same problem.
Opened settings and moved the dock to the bottom, and the settings
window just disappeared. The answer given in the following link helped
me to disable the second virtual monitor from the command line, and
restored the settings window back to my normal laptop screen view:

Link: https://askubuntu.com/questions/366813/disable-second-non-
existent-screen-from-command-line

Of course, this second monitor may come up again when you restart your
machine, so it would be a good option to follow the latter part of the
answer in above link, and put the command in a script which you can
schedule to run at startup. This is a workaround though, and this not
the proper fix, which hopefully may come in a future update/patch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1721637

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1252909] Re: Nautilus takes no notice of my selection in File --> Properties

[Ads20000]

Sebastien can you make this Won't Fix (or Invalid - your call)? As per
#5 it seems like there's now no Properties menu item that's not
available by right click.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1252909

Title:
  Nautilus takes no notice of my selection in File --> Properties

Status in nautilus package in Ubuntu:
  New

Bug description:
  1. Select directory.
  2. Go to File --> Properties.
  3. Nautilus shows properties of the wrong thing.

  Nautilus doesn't appear to have any idea what it's doing.

  Cut and Copy are also not an option so I've had to revert to the
  command line!

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Nov 20 01:03:12 2013
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+437+144'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 235
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757195] Re: Xwayland crashed with SIGABRT

[Jordan Hansen]

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

bug #1754693 is private so I can't follow the status or workarounds to
try. Is there a public version of that bug I can follow?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1757195

Title:
  Xwayland crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  When I plug in an external monitor and I am using wayland the screen
  freezes and I have to perform a hard reboot. I didn't have this issue
  in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 10:13:37 2018
  DistUpgraded: 2018-03-16 10:26:05,388 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1520935141
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e5]
 Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5]
  InstallationDate: Installed on 2017-04-27 (325 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision 5510
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/hansenji
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=fe1aa429-9782-4ada-bb28-60a1d8fe2049 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-16 (2 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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-server/+bug/1757195/+subscriptions

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

[Desktop-packages] [Bug 1252018] Re: "Loading..." message shown for folders with hidden files

[Ads20000]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

Additionally I've tested this on Ubuntu 17.10 and can't reproduce the
bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1252018

Title:
  "Loading..." message shown for folders with hidden files

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When a directory containing only hidden files but Natulis setting for
  displaying hidden files is disable, is expanded in the "List View"
  mode  the "Loading..." message is displayed rather than another one
  more appropriate like the "(Empty)".

  1)$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  2)$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.4.2-0ubuntu8
Candidate: 1:3.4.2-0ubuntu8
Version table:
   *** 1:3.4.2-0ubuntu8 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  3) To display the label "(Empty)" 
  4) Displaying the label "Loading..."

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

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

[Desktop-packages] [Bug 1738410] Re: application icon is too low resolution

[Pander]

see screenshot

** Attachment added: "screenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1738410/+attachment/5085174/+files/screenshot.png

** Tags added: bionic

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/1738410

Title:
  application icon is too low resolution

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  Application icon shown in Lubuntu 17.10, e.g. with Alt+Tab, is of too
  low resolution. I can easily count the pixels, is something of 16, 22,
  24, 32 or in between pixels in width and height.

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

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

[Desktop-packages] [Bug 1306849] Re: Printing error

[Pander]

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to foomatic-db in Ubuntu.
https://bugs.launchpad.net/bugs/1306849

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

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

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

[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

[John Rose]

How did you work out to do 
sudo apt install --reinstall libavutil-ffmpeg54/xenial 
libavresample-ffmpeg2/xenial libavformat-ffmpeg56/xenial 
libavfilter-ffmpeg5/xenial libavdevice-ffmpeg56/xenial 
libavcodec-ffmpeg-extra56/xenial libavcodec-extra/xenial
as per comment #19?
i.e. how did you identify the particular packages?
The reason that I ask is that there are other packages containing the 
characters "libav" (other than "libavahi" ones) in all.txt:
gstreamer1.0-libav
libav-tools
libavc1394-0
libav-idemux2.6
Similarly, there are other packages containing the characters "ffmpeg" (but not 
"libav") in all.txt:
libpostproc-ffmpeg53
libswresample-ffmpeg1
libswscale-ffmpeg3
I'm going to check if there are other packages containing the characters 
"libav" (other than ones containing the characters "libavahi") or "ffmpeg" in 
all.txt on the Barebones & Laptop PCs that play sound Ok.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755144

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1252018] Re: "Loading..." message shown for folders with hidden files

[Ads20000]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1252018

Title:
  "Loading..." message shown for folders with hidden files

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When a directory containing only hidden files but Natulis setting for
  displaying hidden files is disable, is expanded in the "List View"
  mode  the "Loading..." message is displayed rather than another one
  more appropriate like the "(Empty)".

  1)$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  2)$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.4.2-0ubuntu8
Candidate: 1:3.4.2-0ubuntu8
Version table:
   *** 1:3.4.2-0ubuntu8 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  3) To display the label "(Empty)" 
  4) Displaying the label "Loading..."

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

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

[Desktop-packages] [Bug 1675544] Re: nautilus crashed with SIGABRT in g_assertion_message()

[Ads20000]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1675544

and any other logs that are relevant for this particular issue.

I know this bug doesn't seem all that old but it is filed against Ubuntu
17.04 which is no longer supported.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1675544

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Memory very heavily oversubscribed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 23 14:48:09 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'845x521+277+27'"
  InstallationDate: Installed on 2017-03-17 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170126)
  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.
  ProcCmdline: nautilus -n
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_file_monitor_source_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu6

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

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

[Desktop-packages] [Bug 1757195] Re: Xwayland crashed with SIGABRT

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754693, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085109/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085112/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085121/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085123/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085124/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085125/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757195/+attachment/5085126/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1754693

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1757195

Title:
  Xwayland crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  When I plug in an external monitor and I am using wayland the screen
  freezes and I have to perform a hard reboot. I didn't have this issue
  in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 10:13:37 2018
  DistUpgraded: 2018-03-16 10:26:05,388 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1520935141
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e5]
 Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5]
  InstallationDate: Installed on 2017-04-27 (325 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision 5510
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/hansenji
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=fe1aa429-9782-4ada-bb28-60a1d8fe2049 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-16 (2 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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
  

[Desktop-packages] [Bug 1747566] Re: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)

[Andreas Hasenack]

andreas@nsnx:~$ grep tweener /var/log/syslog|wc -l
21664
andreas@nsnx:~$ grep tweener /var/log/syslog.1|wc -l
51874
andreas@nsnx:~$

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1747566

Title:
  Object ..., has been already finalized. Impossible to get any property
  from it. ... (stack trace in tweener.js)

Status in GNOME Shell:
  Expired
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not
  getting a lot of stacktraces in my syslog:

  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to get any property from it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to set any property to it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb  5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), 
has been already finalized. Impossible to get any property from it.
  Feb  5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), 
has been already finalized. Impossible to set any property to it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == 

[Desktop-packages] [Bug 1755232] Re: Xorg crashes when tapping Unity system tray icons

[krzychoocpp]

@jnavila: It looks like it could be related, but I couldn't reproduce
your crash (or at least I think so). With context menu opened in chrome
I tried tapping on the window border, Unity bar and system tray - both
when Chrome was maximized and when it wasn't. No crash. Should I do
something else?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1755232

Title:
  Xorg crashes when tapping Unity system tray icons

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug requires some prerequisites to reproduce:

  0. Make sure you've got multitouch-enable display
  1. Start Unity+xorg session
  2. Verify that four-finger tap gesture works (shows unity app search tool)
  3. Wait some time for this gesture to stop working - this is another bug, not 
necessarily xorg one,  already known and thought to be connected with Google 
Chrome running.
  4. Once it stops working, quickly tap all icons in the Unity system tray like 
you would be pretending to play a piano (tapping them individually or slowly 
does not cause any problems).
  5. Xorg crashes immediately.

  This scenario is 100% reproducible on my setup.

  I recompiled xorg with debug info enabled and got this nice trace:

  
  [ 22705.385] (EE) 
  [ 22705.385] (EE) Backtrace: 
  [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f]  
   
  [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) 
[0x7f382f64414f]   
  [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f382f2880bb] 
  [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) 
[0x7f382f289f5d]  
  [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) 
[0x7f382f2d22bd]  
  [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) 
[0x7f382f2d9f7a]
  [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) 
[0x7f382f2de0fe]   
  [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) 
[0x7f382f2e044e]   
  [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32]
  [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) 
[0x562a3698428f]   
  [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) 
[0x562a3698ea8b]   
  [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) 
[0x562a369bc371]  
  [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] 
   
  [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) 
[0x562a3696e488] 
  [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9]
  [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3]
   
  [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] 
   
  [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7f382f2721c1]  
  [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a]   
   
  [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] 


  Looks like FreeGrab tries to free pGrab for the second time (some
  multithreading issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  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:Unity7:ubuntu
  Date: Mon Mar 12 17:03:34 2018
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2017-09-01 (192 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HES2130Q
  ProcEnviron:
   LANGUAGE=pl_PL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y 
acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 
i915.enable_guc_submission=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to 

[Desktop-packages] [Bug 1749688] Re: 16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

[Timo Aaltonen]

should be fixed now with 3:14.1 in the archive

** Changed in: xorg-lts-transitional (Ubuntu Bionic)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-lts-transitional in Ubuntu.
https://bugs.launchpad.net/bugs/1749688

Title:
  16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg-lts-transitional package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg-lts-transitional source package in Bionic:
  Fix Released

Bug description:
  When upgrading from a 16.04 installation which had HWE (later point
  releases) xorg is getting held back as apt is having trouble resolving
  the path from xserver-xorg-core-hwe-16.04 to xserver-xorg-core.

  In at least one instance I've seen a system from a user POV completely
  break because of that as it failed to get any keyboard input. Forcing
  xorg to get properly installed fixes any and all issues as expected.

  - devel upgrade from xenial to bionic
  - restart
  - xorg not upgraded
  - try to get a hold of tty or repair mode
  - sudo apt install dist-upgrade && sudo apt install xorg
  - restart
  - working system

  I am going to attach logs for an ubuntu-desktop system, but I've also
  seen this with kubuntu-desktop and the derived neon-desktop. It's a
  bit unclear to me why apt is having trouble with the resolution, it
  does seem like a fairly serious problem though.

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

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

[Desktop-packages] [Bug 1756508] JournalErrors.txt

[Alex B]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1756508/+attachment/5085077/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell cpu load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1756508] ProcCpuinfoMinimal.txt

[Alex B]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1756508/+attachment/5085078/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell cpu load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1756508] ProcEnviron.txt

[Alex B]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1756508/+attachment/5085079/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell cpu load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1756508] GsettingsChanges.txt

[Alex B]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1756508/+attachment/5085076/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell cpu load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1756508] Re: Gnome-shell cpu load dramatically high and stuck high with Eclipse

[Alex B]

apport information

** Tags added: apport-collected artful

** Description changed:

  Hello,
  
  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.
  
  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM
  
  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2
  
- Other info needed, please let me know... not sure how to circle this
- closer. Once it happens, it's over .
+ Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2016-02-20 (759 days ago)
+ InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-37-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1756508/+attachment/5085075/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1756508

Title:
  Gnome-shell cpu load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1747566] Re: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)

[Ivanov Yuriy]

** Description changed:

  I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not
  getting a lot of stacktraces in my syslog:
- 
  
  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to get any property from it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b   
resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I   
resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b   
resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b   
resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386)
  Feb  5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), 
has been already finalized. Impossible to set any property to it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b   
resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I   
resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I   
self-hosted:917 (0x7f38c40ee5e8 @ 394)
  Feb  5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), 
has been already finalized. Impossible to get any property from it.
  Feb  5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), 
has been already finalized. Impossible to set any property to it.
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 
0x55c40593a000 ==
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f6ff970 b   
resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f6ffa10 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36)
  Feb  5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f6ffab0 b   
resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52)
  Feb  5 16:14:04 fog 

[Desktop-packages] [Bug 1756389] Re: evolution-calendar-factory slows down session startup

[Iain Lane]

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1756389

Title:
  evolution-calendar-factory slows down session startup

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+subscriptions

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

[Iain Lane]

** Also affects: gnome-software (Ubuntu Bionic)
   Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
   Status: New

** Tags removed: rls-bb-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1756379

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Bionic:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756625] Re: gnome-calculator issues

[Paul White]

** Package changed: gedit (Ubuntu) => gnome-calculator (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1756625

Title:
  gnome-calculator issues

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  ***
  Please change this bug from gedit to the correct package.
  ***

  The default system calculator has lost its options feature (comma
  separator, deg/rad, precision, etc.)

  It displays left justified instead of right justified.

  Clicking on its icon in launcher with the mouse wheel to launch
  another instance does not work.  That is a monumental problem.

  Trying to report these bugs with ubuntu-bug -w produces the attached
  screenshot except that you cannot scroll to the bottom to continue the
  reporting process (hence the gedit proxy).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 20:42:19 2018
  InstallationDate: Installed on 2018-03-10 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Amr Ibrahim]

** Changed in: hundredpapercuts
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1652466

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Fix Released
Status in libva package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in libva source package in Xenial:
  Fix Released
Status in totem source package in Xenial:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no code changes at all, I cannot think of any regressions.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757180] [NEW] nvidia-prime can't switch off the discrete GPU

[Alberto Milone]

Public bug reported:

nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a
change in the nvidia packaging, and a change of behaviour in logind,
broke this feature.

** Affects: nvidia-prime (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-settings (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: ubuntu-drivers-common (Ubuntu)
Milestone: None => ubuntu-18.04

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

** Changed in: nvidia-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: nvidia-settings (Ubuntu)
   Status: New => In Progress

** Changed in: nvidia-settings (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-settings (Ubuntu)
Milestone: None => ubuntu-18.04

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1757180

Title:
  nvidia-prime can't switch off the discrete GPU

Status in nvidia-prime package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress

Bug description:
  nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a
  change in the nvidia packaging, and a change of behaviour in logind,
  broke this feature.

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

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

[Desktop-packages] [Bug 1756389] Re: evolution-calendar-factory slows down session startup

[Iain Lane]

We just discussed this on IRC - I'm not happy with the proposed solution
of inserting a delay into the startup file like this. It'll make
timeouts and it's not really acceptable to have calendar events broken
for 60 seconds in my opinion.

I think we should talk with upstream, but a better solution might be
gnome-shell not activating evolution-calendar-factory until later in its
startup, or not activating it at all and finding a clever place in the
session to activate it.

** Summary changed:

- Delay startup of evolution-calendar-factory
+ evolution-calendar-factory slows down session startup

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1756389

Title:
  evolution-calendar-factory slows down session startup

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+subscriptions

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

[Desktop-packages] [Bug 1756600] Re: Ubuntu 18.04 beta install DVD cannot encrypt home

[Paul White]

** Package changed: gedit (Ubuntu) => ubiquity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1756600

Title:
  Ubuntu 18.04 beta install DVD cannot encrypt home

Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  ***
  Please change this bug from gedit to the correct product.
  ***

  On the screen where you define your user name, computer name, id,
  etc., you no longer have the option of asking for an encrypted home
  directory.

  On the trivial side, note that the installer artwork is still aardvark
  and once installation is complete, the desktop is also aardvark.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 16:52:48 2018
  InstallationDate: Installed on 2018-03-10 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

[Will Cooke]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1756379

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Bionic:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

[cement_head]

Okay, even weirder.

If I connect to the root of the share, it works, but not to the
subdirectory. HMMmmm..

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1715582

Title:
  "Operation not supported by backend" when backing up to smb server

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1715582/+subscriptions

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

[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

[cement_head]

I can connect with nautilus and browse drive.  BUT, when I try and start
DejaDup, I get this error:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1380, in main
action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1127, 
in ProcessCommandLine
globals.backend = backend.get_backend(args[0])
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 223, in 
get_backend
obj = get_backend_object(url_string)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 209, in 
get_backend_object
return factory(pu)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 97, in __init__
self.remote_file.make_directory_with_parents(None)
 Error: g-io-error-quark: Operation not supported by backend (15)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1715582

Title:
  "Operation not supported by backend" when backing up to smb server

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1715582/+subscriptions

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

[Desktop-packages] [Bug 1756068] Re: .

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1756068

Title:
  .

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  .

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Ugh, yeah doing some simple helloworld tests confirms these are armhf
gcc *defaults*.

> it's what *defines* armhf as armhf.

Defines: This appears true for -march=armv7-a -mfloat-abi=hard. As for
-mfpu, adding -mfpu=neon results in some assembly differences, namely
using register d16 and above.

> Unless something is explicitly setting those things differently

The Firefox build log has some instances of -mfpu=neon, particularly in
Skia. However, Chromium does as well so indeed this is a longshot.

Looks like we're back to the drawing board. Still some hope with changes
like building Skia using clang, adding -mthumb, or -fstack-protector-
strong, but none of these other differences stand out as something
present in both the Chromium and Arch Linux builds.

I think I misunderstood earlier about the intent of looking at Firefox
57's about:buildconfig. As that's technically still a Skia-broken build,
we can continue to examine that configuration for other differences vs
the Arch Linux one.

> [herrtimson] If there's a chance to get the output of
about:buildconfig regardless the segfault at startup, I'm all eager to
learn about this.

With broken browsers like Firefox 58 and 59 armhf, find the build config
like so:

strings /usr/lib/firefox/omni.ja | grep -A 31 "Built from"

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1711337

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1749398] Re: Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

[Amr Ibrahim]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1749398

Title:
  Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

Status in libva package in Ubuntu:
  Fix Released

Bug description:
  Libva 2.1.0 has been released: https://github.com/intel/libva/releases

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libva2 2.0.0-2
  Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 14 11:46:06 2018
  InstallationDate: Installed on 2017-08-28 (169 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libva
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago)

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

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

[Desktop-packages] [Bug 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication

[Chewie]

Hi all

I just stumpled accross the very same issue
At the moment i run network manager version:
network-manager-gnome   1.2.6-0ubuntu0.16.04.4 

so it should be fixed -> but I was unable to select my key..

I exported the key following and old HowTo to get wlan running in a
linux pc as the company is running windows domains with wpa2 enterprise
..

pfx=my_exported_cert.pfx

openssl pkcs12  -in $pfx  -out cacert.pem -cacerts -nokeys
openssl pkcs12  -in $pfx  -out cert.pem -clcerts -nokeys
openssl pkcs12  -in $pfx  -out key.pem -nocerts

that generated all files required -> prior to that I had to request a
new cert with exportable private keys on a windows pc ..

key resulting key.pem was:
file key.pem 
key.pem: ASCII text

with header of:
Bag Attributes
localKeyID: 01 00 00 00 
Microsoft CSP Name: Microsoft Strong Cryptographic Provider
friendlyName: 
le-Auth_Ses_ClientUser_KNAPPD-0485e131-adac-48b4-bd80-417a8495e1f3
Key Attributes
X509v3 Key Usage: 80 
-BEGIN ENCRYPTED PRIVATE KEY-

And I think that was the issue with this key:

After converting the key to RSA format it worked for me and network
manager detected it !.

openssl rsa -in key.pem -out secure.key.key
file secure.key.key 
secure.key.key: PEM RSA private key

And now i an running my WPA2 enterprise WLAN :)

regards
Chewie

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

Title:
  [SRU]Can't select p12 secret key for TLS auth for 802.1X
  authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

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

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

[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

[cement_head]

Nevermind; bloody NAS drive was stuck in a loop - hard reset fixed it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1715582

Title:
  "Operation not supported by backend" when backing up to smb server

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1715582/+subscriptions

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

[Desktop-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

[Iain Lane]

** Also affects: mesa (Ubuntu Bionic)
   Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
   Status: Triaged

** Also affects: wayland (Ubuntu Bionic)
   Importance: Medium
   Status: Invalid

** Also affects: gdm3 (Ubuntu Bionic)
   Importance: Medium
   Status: Invalid

** Tags removed: rls-bb-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1753776

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Confirmed
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  Triaged
Status in wayland source package in Bionic:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.
  

[Desktop-packages] [Bug 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

[Till Kamppeter]

Ralph Gauges, can you please attach all files which you have in
/etc/cups/ppd/? Please attach the files one by one, do not compress them
and do not package them together.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1756160

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1757160] Re: gnome-shell crashed with signal 5

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084984/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084986/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084990/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084991/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084992/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084993/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757160/+attachment/5084994/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1757160

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 19:55:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2016-01-08 (802 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-01-24 (54 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

This is CVE-2018-1000135. For some reason the 'Link to CVE' option above
doesn't seem to work.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000135


** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-1000135

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1757158] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084963/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084965/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084968/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084969/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084970/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084971/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757158/+attachment/5084972/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1757158

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happens on boot up. Also, System still hangs when HDMI is plugged in.
  If I remove the HDMI on reboot and only plug it back in after login is
  initiated then it continues to boot. Otherwise I need to reboot again
  with the HDMI unplugged. A new occurrence is the fact that I now get
  Dummy Audio Output along with Surround 5.1, 7.1, HDMI and Speakers. I
  must reboot, turn off the monitor and then pull the HDMI cable and
  replug in. I have swapped HDMI cables to no avail. Just FYI. Before
  the last 3 updates all of these things worked fine. Thanks!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 10:21:05 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-06-27 (265 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756389] Re: Delay startup of evolution-calendar-factory

[Jeremy Bicha]

Could you please propose this upstream (with a patch if you can) ?

https://bugzilla.gnome.org/enter_bug.cgi?product=evolution-data-server

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1756389

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+subscriptions

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Matt Mahin]

Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1721428

Title:
  Artful (17.10) Session 

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Matt Mahin]

Issue is mitigated by enabling Automatic screen lock when screen turns
off.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1721428

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

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

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

[Desktop-packages] [Bug 1757154] Re: can't start lightdm.service unit

[JoK]

** Attachment added: "test-mode with debug"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757154/+attachment/5084940/+files/lightdm.test-mode.debug

** Description changed:

+ On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1757154

Title:
  can't start lightdm.service unit

Status in lightdm package in Ubuntu:
  New

Bug description:
  On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Launchpad Bug Tracker]

This bug was fixed in the package intel-vaapi-driver - 2.1.0-0ubuntu1

---
intel-vaapi-driver (2.1.0-0ubuntu1) bionic; urgency=medium

  * New upstream release. (LP: #1729467)
- support Cannonlake
  * Un-split the package, restore support for shaders. (LP: #1756380)
  * control: Update maintainer, add new platforms to description.

 -- Timo Aaltonen   Tue, 20 Mar 2018 14:28:10 +0200

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD

[Desktop-packages] [Bug 1757154] [NEW] can't start lightdm.service unit

[JoK]

Public bug reported:

On today Ubuntu 18.04 daylibuild
i can launch it without error with lightdm –-test-mode --debug
but i can't start systemd unit
error : lightdm.service: Start request repeated too quickly

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

** Attachment added: "journalctl logs"
   
https://bugs.launchpad.net/bugs/1757154/+attachment/5084939/+files/journalctl.lightdm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1757154

Title:
  can't start lightdm.service unit

Status in lightdm package in Ubuntu:
  New

Bug description:
  On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

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

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

Re: [Desktop-packages] [Bug 1074617] Re: liferea crashes when I add a new subscription

[Paul Gevers]

@Bèr,

On 20-03-18 13:59, Bèr Kessels (berkes) wrote:
> Happens also when running `liferea-add-feed` which is a wrapper around
> `liferea --add-feed`. The latter also causes a crash.

Which version of liferea are you using? (Or, on which version of Ubuntu
are you running?)

> Attached is a strace log, created by running `strace -o liferea-
> crash.log /usr/bin/liferea --add-feed
> http://feeds.bbci.co.uk/news/rss.xml`.
> 
> ** Attachment added: "Attached is a strace log, created by running `strace -o 
> liferea-crash.log /usr/bin/liferea --add-feed 
> http://feeds.bbci.co.uk/news/rss.xml`.;
>
> https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1074617/+attachment/5084904/+files/liferea-crash.log

This exact same command doesn't crash for me (on Debian buster in KDE).
The issue may be resolved in the mean time, or we need to figure out
what really triggers the issue.

Paul

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liferea in Ubuntu.
https://bugs.launchpad.net/bugs/1074617

Title:
  liferea crashes when I add a new subscription

Status in liferea package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a subscription using the button Liferea you close
  without completing the operation

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: liferea 1.8.3-0.1ubuntu2 [modified: usr/bin/liferea]
  Uname: Linux 3.6.5-030605-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sat Nov  3 12:27:11 2012
  InstallationDate: Installed on 2012-09-05 (58 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  MarkForUpload: True
  SourcePackage: liferea
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (15 days ago)

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

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

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

[Christian Niemeyer]

** Summary changed:

- [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf
+ [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf (intel mesa driver)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf (intel mesa driver)

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Matt Mahin]

Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1721428

Title:
  Artful (17.10) Session 

[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

[cement_head]

Just upgraded to 17.10; can't use DejaDup to backup to network NAS
drive.  Got this error.  Is there a workaround, or do I have to wait for
the new 18.04 release?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1715582

Title:
  "Operation not supported by backend" when backing up to smb server

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1715582/+subscriptions

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

[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-contacts - 3.28.0-1ubuntu1

---
gnome-contacts (3.28.0-1ubuntu1) bionic; urgency=medium

  * Disable building telepathy support and drop related dependencies
(LP: #1754803)

 -- Tim Lunn   Tue, 20 Mar 2018 23:06:31 +1100

** Changed in: gnome-contacts (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-contacts in Ubuntu.
https://bugs.launchpad.net/bugs/1754803

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Fix Released

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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

[Desktop-packages] [Bug 1757133] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084906/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084908/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084911/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084912/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084913/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084914/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757133/+attachment/5084915/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1757133

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  sorry it just give me message system problem

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 19 21:39:38 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Julian Andres Klode]

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Committed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :

[Desktop-packages] [Bug 1757129] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754924, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084895/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084897/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084899/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084900/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084901/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084902/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1757129/+attachment/5084903/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757129

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Occurred shortly after update and restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 07:45:06 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-17 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  JournalErrors:
   -- Logs begin at Sat 2018-03-17 04:03:20 CDT, end at Tue 2018-03-20 07:50:56 
CDT. --
   Mar 20 07:30:58 hostname wpa_supplicant[966]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
   Mar 20 07:30:58 hostname wpa_supplicant[966]: dbus: Failed to construct 
signal
   Mar 20 07:31:09 hostname pulseaudio[1422]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 07:31:13 hostname spice-vdagent[1552]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
  ProcCmdline: gnome-control-center background
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5575de6eb641:mov0x90(%rbp),%rsi
   PC (0x5575de6eb641) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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