[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Daniel van Vugt
Thanks. That seems to agree with comment #31.

** Summary changed:

- gnome-shell filling up syslog with thousands of entries (stack traces ending 
in osdWindow.js:206/207)
+ gnome-shell filling up syslog with thousands of entries with stack traces 
ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

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

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB 

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Andrew Keynes
Reinstalled the same NUC with 18.10, installed package updates &
rebooted.

Relevant syslog attached, detail starts at timestamp Oct 29 15:32:28
when installation was locked.

The stack traces appear to occur every 10 seconds once locked when
checking the output of "grep osdWindow.js syslog".


Log excerpt with one block of traces:

Oct 29 15:32:28 grcnuc16 gnome-shell[3808]: Object St.Icon (0x556511f83350), 
has been already deallocated — impossible to set any property on it. This might 
be caused by the object having been destroyed from C code using something such 
as destroy(), dispose(), or remove() vfuncs.
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: == Stack trace for 
context 0x5565111331c0 ==
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #0   5565119fed20 i   
resource:///org/gnome/shell/ui/osdWindow.js:223 (7f11417c78b0 @ 231)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #1   7ffeba144840 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f11419b0b80 @ 71)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #2   7ffeba145450 b   
self-hosted:977 (7f11419f01f0 @ 413)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #3   7ffeba145540 b   
resource:///org/gnome/gjs/modules/signals.js:128 (7f11419c18b0 @ 386)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #4   5565119fec98 i   
resource:///org/gnome/shell/ui/layout.js:538 (7f1141704310 @ 127)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #5   5565119febf0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f11419b0b80 @ 71)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #6   5565119feb30 i   
self-hosted:977 (7f11419f01f0 @ 413)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: == Stack trace for 
context 0x5565111331c0 ==
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #0   5565119fed20 i   
resource:///org/gnome/shell/ui/osdWindow.js:224 (7f11417c78b0 @ 273)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #1   7ffeba144840 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f11419b0b80 @ 71)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #2   7ffeba145450 b   
self-hosted:977 (7f11419f01f0 @ 413)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #3   7ffeba145540 b   
resource:///org/gnome/gjs/modules/signals.js:128 (7f11419c18b0 @ 386)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #4   5565119fec98 i   
resource:///org/gnome/shell/ui/layout.js:538 (7f1141704310 @ 127)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #5   5565119febf0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f11419b0b80 @ 71)
Oct 29 15:32:28 grcnuc16 org.gnome.Shell.desktop[3808]: #6   5565119feb30 i   
self-hosted:977 (7f11419f01f0 @ 413)
Oct 29 15:32:28 grcnuc16 gnome-shell[3808]: Object St.BoxLayout 
(0x5565118f0710), has been already deallocated — impossible to set any property 
on it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+attachment/5206619/+files/syslog

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 

[Desktop-packages] [Bug 1794282] Re: warning dialog when closing multiple private tabs can become unresponsive

2018-10-28 Thread hbchoong
Understood, sorry.
May I ask what actually happens next in this process?

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

Title:
  warning dialog when closing multiple private tabs can become
  unresponsive

Status in firefox package in Ubuntu:
  New

Bug description:
  Affecting Firefox 60 with Ubuntu 18.04.1: (Private Browsing)

  When closing down Private Browsing with 2 tabs or more, the 'warning'
  dialog box appears but if no selection is made after a while, the
  'Gnome' dialog box appears behind it incorrectly indicating Firefox is
  'unresponsive'. This causes the application to freeze as no selection
  can then be made as the 'Gnome' dialog box's selection is hidden
  (inactive window) behind Firefox's 'warning' dialog box (active
  window) which has now frozen (...awaiting the 'Gnome' dialog box's
  selection which cannot be made!)

  Thank you for passing this on to the appropriate teams for action.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1794282/+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 1351876] Re: Keyboard not working after resuming from suspend

2018-10-28 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Keyboard not working after resuming from suspend

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I upgraded my Xubuntu 13.04 to 14.04 lately, and since then sometimes
  if I suspend my machine with chromium-browser running, after the
  resume Chromium looks like it does not receive keyboard input. All
  other windows work fine. The bug does not occur with all suspends, I
  suspect that Chromium has to be the active window before the suspend.

  Chromium version: Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1351876/+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 1296011] Re: thunderbird crashed with SIGSEGV

2018-10-28 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbird crashed with SIGSEGV

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  just started the soft and entered the master password, after reduction
  to the dashboard it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:24.4.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yoritomo   1910 F pulseaudio
  BuildID: 20140318000702
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Mar 22 11:26:05 2014
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-02-02 (47 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.3  metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   Java(TM) Plug-in 10.51.2 - 
/usr/lib/jvm/java-7-oracle/jre/lib/amd64/libnpjp2.so
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   VLC Web Plugin - /usr/lib/mozilla/plugins/libvlcplugin.so 
(browser-plugin-vlc)
  PrefSources: prefs.js
  ProcCmdline: /usr/lib/thunderbird/thunderbird
  Profiles: Profile0 (Default) - LastVersion=24.4.0/20140318000702
  RelatedPackageVersions: browser-plugin-vlc 2.0.6-2
  RfKill:
   
  RunningIncompatibleAddons: False
  Signal: 11
  SourcePackage: thunderbird
  StacktraceTop:
   ?? () from /usr/lib/thunderbird/libxul.so
   ?? () from /usr/lib/thunderbird/libxul.so
   ?? () from /usr/lib/thunderbird/libxul.so
   ?? () from /usr/lib/thunderbird/libxul.so
   ?? () from /usr/lib/thunderbird/libxul.so
  Themes: extensions.sqlite corrupt or missing
  Title: thunderbird crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1296011/+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 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Daniel van Vugt
We know 18.04 has this bug.

If anyone experiences it in 18.10 then please also paste some output of
it here so we can see how the bug has changed in the new release.

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work 

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Andrew Keynes
I can also confirm that this is lock-screen related as it starts logging
as soon as the screen is locked and stops when un-locked.

No notifications are evident.

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work for 

[Desktop-packages] [Bug 1800210] Re: dose not work rite

2018-10-28 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => 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/1800210

Title:
  dose not work rite

Status in Ubuntu:
  Incomplete

Bug description:
  APP STOR DOES NOT WORK RITE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct 26 15:04:24 2018
  DistUpgraded: 2018-10-25 22:05:32,733 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2c9d5f71-ce27-4b3c-8018-0404d4ab5fb9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite C655
  dmi.product.sku: Montevina_Fab
  dmi.product.version: PSC08U-03C01K
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Thu Oct 25 19:03:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5760 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1800210/+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 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Andrew Keynes
I can confirm that this bug still exists in 18.04.

In my case in a completely fresh install with nothing added / configured
except for chromium being installed (and packages updated).

Installed Friday afternoon and came back in to work Monday to find the
disk full as per the original report.

Hardware in this instance is an Intel NUC7i3BNH - an identical system
just installed does exactly the same thing.

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: 

[Desktop-packages] [Bug 1798360] Re: Invalid read in the snap plugin

2018-10-28 Thread Robert Ancell
I tried today and wasn't able to reproduce at all.

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

Title:
  Invalid read in the snap plugin

Status in gnome-software package in Ubuntu:
  In Progress
Status in snapd-glib package in Ubuntu:
  New

Bug description:
  On cosmic, open gnome-software, type some text to search, it easily
  leads to snapd related warnings on stdout and those corresponding
  valgrind invalid read errors

  ==31017== Invalid read of size 8
  ==31017==at 0x4913AC5: g_type_check_instance_is_fundamentally_a 
(gtype.c:4023)
  ==31017==by 0x48F4AF4: g_object_unref (gobject.c:3243)
  ==31017==by 0x497D4E2: g_source_callback_unref (gmain.c:1551)
  ==31017==by 0x497DF1D: g_source_destroy_internal (gmain.c:1236)
  ==31017==by 0x4980B77: g_main_dispatch (gmain.c:3206)
  ==31017==by 0x4980B77: g_main_context_dispatch (gmain.c:3847)
  ==31017==by 0x4980ED7: g_main_context_iterate.isra.26 (gmain.c:3920)
  ==31017==by 0x49811D1: g_main_loop_run (gmain.c:4116)
  ==31017==by 0x12C6EB5E: end_sync (snapd-client-sync.c:33)
  ==31017==by 0x12C6EB5E: snapd_client_find_section_sync 
(snapd-client-sync.c:646)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: g_task_thread_pool_thread (gtask.c:1331)
  ==31017==by 0x49A9AD2: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==31017==by 0x49A9134: g_thread_proxy (gthread.c:784)
  ==31017==by 0x5CFC163: start_thread (pthread_create.c:486)
  ==31017==by 0x5E2FDEE: clone (clone.S:95)
  ==31017==  Address 0xdccd330 is 96 bytes inside a block of size 184 free'd
  ==31017==at 0x483897B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==31017==by 0x49128C3: g_type_free_instance (gtype.c:1936)
  ==31017==by 0x12C67046: request_data_unref (snapd-client.c:178)
  ==31017==by 0x497D4E2: g_source_callback_unref (gmain.c:1551)
  ==31017==by 0x497DF1D: g_source_destroy_internal (gmain.c:1236)
  ==31017==by 0x4980B77: g_main_dispatch (gmain.c:3206)
  ==31017==by 0x4980B77: g_main_context_dispatch (gmain.c:3847)
  ==31017==by 0x4980ED7: g_main_context_iterate.isra.26 (gmain.c:3920)
  ==31017==by 0x49811D1: g_main_loop_run (gmain.c:4116)
  ==31017==by 0x12C6EB5E: end_sync (snapd-client-sync.c:33)
  ==31017==by 0x12C6EB5E: snapd_client_find_section_sync 
(snapd-client-sync.c:646)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: g_task_thread_pool_thread (gtask.c:1331)
  ==31017==by 0x49A9AD2: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==31017==by 0x49A9134: g_thread_proxy (gthread.c:784)
  ==31017==by 0x5CFC163: start_thread (pthread_create.c:486)
  ==31017==by 0x5E2FDEE: clone (clone.S:95)
  ==31017==  Block was alloc'd at
  ==31017==at 0x483774F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==31017==by 0x4986650: g_malloc (gmem.c:99)
  ==31017==by 0x499E5B2: g_slice_alloc (gslice.c:1024)
  ==31017==by 0x499EBE8: g_slice_alloc0 (gslice.c:1050)
  ==31017==by 0x49124F9: g_type_create_instance (gtype.c:1836)
  ==31017==by 0x48F5397: g_object_new_internal (gobject.c:1805)
  ==31017==by 0x48F7223: g_object_new_valist (gobject.c:2128)
  ==31017==by 0x48F7558: g_object_new (gobject.c:1648)
  ==31017==by 0x12C5C70A: _snapd_get_find_new (snapd-get-find.c:34)
  ==31017==by 0x12C6A967: snapd_client_find_section_async 
(snapd-client.c:2119)
  ==31017==by 0x12C6EB4D: snapd_client_find_section_sync 
(snapd-client-sync.c:645)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: g_task_thread_pool_thread (gtask.c:1331)
  ==31017==by 0x49A9AD2: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==31017==by 0x49A9134: g_thread_proxy (gthread.c:784)
  ==31017==by 

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2018-10-28 Thread Sergio
Ran into this issue with Audacity 2.2.1 on Ubuntu 18.04.
Restarting doesn't fix it. Headphones were detected but didn't work.

Steps to Fix:
* Open Audacity. Set source to "default: internal mic: 0"
* Close Audacity
* Open Audacity again. Suddenly headphones start working

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

Title:
  Headphones stopped working after use of Audacity. They are detected,
  but no sound is produced.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I'm running 13.10 and the latest GNOME. I've just fresh installed
  everything and the problem has occured again the same way. I would
  like to be able to use audacity, but I suppose in the mean time I will
  just reinstall everything.

  Steps to reproduce : 
  1) Install audacity 2.0.3 from official Ubuntu repositories
  2) Open Audacity and play something with it
  3) That's it : no more headphones sound.

  
  - alsa log created with 'alsa-info.sh' 
(https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/

  - pulse log when I plug in my headphones, I run a MP3 file with VLC,
  close VLC then unplug headphones
  (https://wiki.ubuntu.com/PulseAudio/Log) :
  http://paste.ubuntu.com/7131713/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+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 1797835] Re: Shutdown or logout button have to click twice

2018-10-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1799293 ***
https://bugs.launchpad.net/bugs/1799293

** This bug has been marked a duplicate of bug 1799293
   gnome session: Must ask twice to lock the screen

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

Title:
  Shutdown or logout button have to click twice

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Dear developers,

  How are you? I've been fresh install the Ubuntu 18.04.1 LTS and facing
  a new bug randomly, that is the shutdown and logout button sometimes
  have to be clicked twice to take effects.

  Best,
  syscl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797835/+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 1800294] Re: Xorg freeze black scr

2018-10-28 Thread taeler
Sorry to have to tell you this but I installed linux mint on my HP
laptop because the freezing black screen on ubuntu 18.04.1 it was
becoming a big issue that was affecting the reliability and usability of
my HP laptop, and I needed something more reliable. I love and support
ubuntu and run ubuntu in a virtual box on my HP laptop and my old
Toshiba laptop still with out issue. So I can't send you the files you
need. Sorry.


Sent from my Samsung Galaxy smartphone.
 Original message From: Daniel van Vugt 
 Date: 2018-10-28  11:31 PM  (GMT-04:00) To: 
taelerderb...@gmail.com Subject: [Bug 1800294] Re: Xorg freeze black scr 
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Xorg freeze black screen hang up

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i've had this issue twice this morning where during boot up my screen
  turns black and i can't get it to come back, then i'm forced to to a
  hard reboot, this issue often times happens about 99% of the time at
  the login screen if i don't log in with in about 10 seconds, my screen
  goes black and i can not get it to come back and i need to do a hard
  reboot. also sometimes the issue happens during boot up the screen
  goes purple for a few seconds then black and stay's like that and the
  can't get it to comes back and have to do a hard reboot, but this
  happens about 1 or 2 times out of ten boots i would say. so i'm hoping
  that this issue can be resolved in some way.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 12:40:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d]
  InstallationDate: Installed on 2018-10-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 808D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 90.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 096C120800405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  

[Desktop-packages] [Bug 1800062] Re: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops

2018-10-28 Thread William.Yeung
Dear Till,

   We(RICOH printer driver developer) are still working hard to looking for an 
workaround to make sure our printer user can do their job normally before 
your(or ghostscript) official release. 
We appreciate that you can private it to us if you have one.

   By the way, can you offer us the approximate time that Ubuntu release
a patch of fixed this bug? If you can't, just tell us can you release
the patch before November 12(11/12)?

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

Title:
  Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined
  in .putdeviceprops

Status in GS-GPL:
  Unknown
Status in ghostscript package in Ubuntu:
  New

Bug description:
  PDF file data fail to rendering to raster data.

  We were reported a bug from our printer users:
  I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay.

  But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 
9.25, I print the same file with the same driver there is an error reports:
  "Filter Error"

  I figure out that all the papersize with define "LeadingEdge" can't print 
success after update.
  (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay).

  
  I view the "CUPS Error Log",there is an error reports when print job fails:
  "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE 
-dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout 
-sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 
-dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 
-dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 
-scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_

  Unrecoverable error: undefined in .putdeviceprops"

  Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem.

  --
  ghostscript had confirm that this a bug of ghostscript 9.22(and the later 
version).

  Below information is the correspondence of ghostscript:
  https://bugs.ghostscript.com/show_bug.cgi?id=700023
  ---

  Our printer driver users(also users of Ubuntu 16.04) can't do their normal 
print jobs. 
  So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix 
this bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1800062/+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 1800352] Re: desktop and current applications displayed when resuming from lock

2018-10-28 Thread Daniel van Vugt
Thanks for the bug report. You seem to have found exactly the right
existing bug reports but both of those are closed for the case of Gnome
Shell on Ubuntu. So let's use this bug for now.

Next, please run this command to send us more information about the
system:

  apport-collect 1800352

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

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800294] Re: Xorg freeze black screen hang up

2018-10-28 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1800294

Title:
  Xorg freeze black screen hang up

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i've had this issue twice this morning where during boot up my screen
  turns black and i can't get it to come back, then i'm forced to to a
  hard reboot, this issue often times happens about 99% of the time at
  the login screen if i don't log in with in about 10 seconds, my screen
  goes black and i can not get it to come back and i need to do a hard
  reboot. also sometimes the issue happens during boot up the screen
  goes purple for a few seconds then black and stay's like that and the
  can't get it to comes back and have to do a hard reboot, but this
  happens about 1 or 2 times out of ten boots i would say. so i'm hoping
  that this issue can be resolved in some way.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 12:40:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d]
  InstallationDate: Installed on 2018-10-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 808D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 90.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 096C120800405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1800309] Re: not installed during update to ubuntu 18

2018-10-28 Thread Daniel van Vugt
Can you please provide a screenshot, photo, or log output showing the
error?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  not installed during update to ubuntu 18

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  some errors on installing video xorg intel, some corrupted
  files/dependencies

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 22:14:06 2018
  DistUpgraded: 2018-10-27 15:51:41,727 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002]
  InstallationDate: Installed on 2018-03-29 (212 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K54HR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d5e3b7bd-e24f-42fc-9840-8e671d6e8c81 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-27 (0 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54HR.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54HR
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54HR.205:bd06/20/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54HR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 27 12:38:54 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800309/+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 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Daniel van Vugt
** No longer affects: nvidia-graphics-drivers-390 (Ubuntu)

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

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to release device: Device not taken
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800292/+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 1800263] Re: black screen at start up

2018-10-28 Thread Daniel van Vugt
Please run this command from the machine to send us more information:

  apport-collect 1800263

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  black screen at start up

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i have this issue often, about 99% of the time i can get it to happen
  at the login screen if i don't log in with in about 10 seconds my
  screen goes black and i can not get it to come back and i need to do a
  hard reboot. also sometimes the issue happens during boot up the
  screen goes purple for a few seconds then black and stay's like that
  and the can't get it to comes back and have to do a hard reboot, but
  this happens about 1 or 2 times out of ten boots i would say. so i'm
  hoping that this issue can be resolved in some way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800263/+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 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card

2018-10-28 Thread Daniel van Vugt
Please run this command:

   dpkg -l > all.txt

and then send us the file 'all.txt'.

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

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

Title:
  [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails
  to detect card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After update to 18.10 no sound in internal speakers and jackport.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 11:10:22 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (820 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails 
to detect card
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (6 days ago)
  dmi.bios.date: 02/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCE Ver. F.00
  dmi.board.name: 161D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.3E
  dmi.chassis.asset.tag: CNU14045VQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCEVer.F.00:bd02/14/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.3E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 6460b
  dmi.product.sku: LG643EA#AKD
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+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 1800165] Re: GNOME shell RAM usage is more than double than on identical setup on other distro

2018-10-28 Thread Daniel van Vugt
The new leak in gnome-shell 3.30.1 is probably:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/653

** Summary changed:

- GNOME shell RAM usage is more than double than on identical setup on other 
distro
+ New memory leaks in gnome-shell 3.30.1

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

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/653
+ 
+ ---
+ 
  I have installed GNOME on ArchLinux with pretty much the same setup as in 
Ubuntu, (same extensions, same programs and same libs).
  Nevertheless, on Arch, GNOME Shell RAM usage is 30/60 MB, on Ubuntu 150/160 
MB. In general Ubuntu is way slower and heavier than arch in pretty much all 
tasks.
  I do not understand why that should hold.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  Uname: Linux 4.19.0-999-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 26 16:42:02 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-01-12 (652 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-07-24 (94 days ago)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2018-08-03T04:50:07.694860

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

Title:
  New memory leaks in gnome-shell 3.30.1

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/653

  ---

  I have installed GNOME on ArchLinux with pretty much the same setup as in 
Ubuntu, (same extensions, same programs and same libs).
  Nevertheless, on Arch, GNOME Shell RAM usage is 30/60 MB, on Ubuntu 150/160 
MB. In general Ubuntu is way slower and heavier than arch in pretty much all 
tasks.
  I do not understand why that should hold.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  Uname: Linux 4.19.0-999-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 26 16:42:02 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-01-12 (652 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-07-24 (94 days ago)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2018-08-03T04:50:07.694860

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800165/+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 1800120] Re: please find the solution to the display problem asap

2018-10-28 Thread Daniel van Vugt
The bad resolution is due to 'nomodeset' on your kernel command line.

To fix that you need to edit /etc/default/grub, remove "nomodeset" and
then run:

  sudo update-grub

and reboot.

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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  please find the solution to the display problem asap

Status in Ubuntu:
  Invalid

Bug description:
  i have recently purchased an asus rog gl504gm and i have dual booted
  it with ubuntu . but as soon as i dual booted it i started facing a
  lot of problems with the display resolution as well as trackpad
  recognition also with the working of my gtx geforce 1060 driver kindly
  help me out as this is interfering with my project.

  hoping to hear from you soon

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 26 15:18:00 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:19ae]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:19ae]
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: ASUSTeK COMPUTER INC. Strix GL504GM_GL504GM
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=15579d78-0db7-4ca0-b847-d143de8810f6 ro quiet nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL504GM.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL504GM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL504GM.303:bd05/31/2018:svnASUSTeKCOMPUTERINC.:pnStrixGL504GM_GL504GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL504GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Strix
  dmi.product.name: Strix GL504GM_GL504GM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 26 14:46:03 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1800120/+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 1800118] Re: NVHDA does not persist after Suspend or Hibernating

2018-10-28 Thread Daniel van Vugt
** Summary changed:

- [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] 
Playback problem
+ NVHDA does not persist after Suspend or Hibernating

** No longer affects: pulseaudio (Ubuntu)

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

Title:
  NVHDA does not persist after Suspend or Hibernating

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Below is a Cut and paste of a recent Ubuntu Forum Page where I posted the 
issues
  https://ubuntuforums.org/showthread.php?t=2404566
  Note that though it says "Solved" it is just workarounds of Bigger ACPI 
Issues!

  ubuntu 18.10

  OK,

  This is a new thread, and I will make it HUGE!
  Edit Solution/ Work Around for the "2/" Problem
  see Post # 4, Thanks PeterSaints 

  Ubuntu, Please Listen!

  Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, or 
HDMI Audio, or Surround Sound 5.1-7.1 etc. ...
  NVHDA stands for Nvidia HDA. Just for anyone who does not know the Jargon! 

  What does Work ... (and I will post ALL my Notes and Links for others below!)
  1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and 
  2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend!

  First my System, and most importantly is it is a NEW Cutting Edge Hp Omen X 
Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel!
  -Computer-
  Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz
  Memory: 16245MB (3330MB used)
  Machine Type  : Notebook
  Operating System  : Ubuntu 18.10
  -Display-
  Resolution: 1920x1080 pixels
  OpenGL Renderer   : GeForce GTX 1080/PCIe/SSE2
  X11 Vendor: The X.Org Foundation

  -Audio Devices-
  Audio Adapter : HDA-Intel - HDA Intel PCH
  Audio Adapter : HDA-Intel - HDA NVidia
  -Input Devices-

  Video Bus
  ST LIS3LV02DL Accelerometer
  HDA Intel PCH Mic
  HDA Intel PCH Mic
  HDA Intel PCH Headphone
  HP WMI hotkeys
  HDA NVidia HDMI/DP,pcm:3
  HDA NVidia HDMI/DP,pcm:7
  HDA NVidia HDMI/DP,pcm:8
  So the LATEST 2 Problems I am looking for a SOLUTION that would indeed help 
THOUSANDS and/or MILLIONS of people Now and/or in the near future! 
  1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem!
  and MORE IMPORTANTLY!

  2/ Why is the fixed Patch System NOT working after a Suspend or Hibernation
  (Yes I am reiterating my issue once again!)
  After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, 
  1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or 
  2/ Visible but in a Dysfunctional State, ... Showing 3 version of the NVHDA 
0,1&2 ...
  and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when testing 
them. 

  So I will leave it here, and to show my continued Good Faith and
  Obvious Continued Support For Ubuntu, below are ALL my Solutions to
  Date!

  1st Solution - 
  Install the patch to get the INVISIBLE and/or Unloaded HDA Visible and/or 
Loaded
  ∘ I can confirm that kernel module, posted by 
  ‣ Maik Freudenberg (https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27),
  • Kernel module to toggle audio function
  ∘ is working fine on my system. Thank you for the fix. The HDMI audio device 
now works as it should (now detected).
  ∘ The steps I did to enable HDMI audio device:
  • 1. Download and extract the file nvhda.tar.xz. (from above link)
  • 2. Run these commands in Terminal, in the location of the extracted folder 
  Code:
  • $ make
  • $ sudo make install
  • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules
  • $ echo "options nvhda load_state=1" | sudo tee /etc/modprobe.d/nvhda.conf
  • $ sudo update-initramfs -u
  ‣ 3. Reboot.
  ## SOLVED ## ###

  2nd Solution
  Hibernation/Suspend Working (Not HDA Sound of Course)

  Troubleshooting
  ‣ Prerequisites - does your kernel support suspend-to-disk?
  • Kernel supports whatever is listed in /sys/power/state, so:
  Code:
  cat /sys/power/state
  ∘ Allowed (to my knowledge) entries there include: mem, standby, freeze, 
disk. Explanation:
  ‣ mem - has several meanings, which one exactly on your system you'll find 
out via cat /sys/power/mem_sleep. I have: s2idle [deep]
  ‣ standby - Power-On Suspend (if supported)
  ‣ freeze - Suspend To Idle (STI)
  ‣ disk - Hibernate - Suspend To Disk (STD), This - you want.
  ∘ mine says : freeze mem disk - PERFECT!

  • Then we need to check
  Code:
  $ cat /sys/power/disk
  ‣ If (good) shows ... 
  ‣ [platform] shutdown reboot suspend test_resume 

  • if : (Bad)
  • [disabled] 
  • (not very good)
  ‣ Enable Hibernate and put it in menu - Easy-Peasy

  • Software Prerequisites
  Code:
  sudo apt install pm-utils  cpufrequtils
  1. Edit a specific file with this command.
  Code:
   sudo gedit 
/var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla
  ∘ 2. Scroll down the Text Document and find 

[Desktop-packages] [Bug 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

2018-10-28 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => New

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

Title:
  [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178/+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 1799787] Re: gnome-shell crashes when forcing a restart if applications are started on multiple workspaces

2018-10-28 Thread Daniel van Vugt
Paul,

Please repeat the steps from comment #2 so that we can try and verify if
this really is a duplicate of bug 1796607.

I would like to see a second stack trace so we can be sure this is a
duplicate, or to verify this is really a new bug.

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

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

Title:
  gnome-shell crashes when forcing a restart if applications are started
  on multiple workspaces

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  What should happen:

  With any number of applications running or workspaces enabled, gnome-
  shell should restart gracefully by using 'Alt F2 > r and enter'.

  What does happen:

  With just one workspace enabled, several applications can be started
  and gnome-shell can be restarted with 'Alt F2 > r and enter' without
  issue.

  With multiple workspaces enabled, several applications can be started
  and gnome-shell can be restarted with 'Alt F2 > r and enter' provided
  all applications are started on the first workspace.

  With multiple workspaces enabled, if several applications are started
  on different workspaces then gnome-shell will crash if restarted with
  'Alt F2 > r and enter'. My last application was started on workspace
  4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 24 21:01:13 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-10-02 (22 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181002)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799787/+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 1799796] Re: Freeze to stop responding

2018-10-28 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  Freeze to stop responding

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu does not start right away 18.04. Having passed the Grub menu,
  the system starts up and then a black screen. Reboot, so maybe several
  times. Hard drives: Smart OK.

  How to boot I enter the password. Run Chrome. looking through YouTube.
  Hangs tightly. The mouse does not move. I hear the last sound from the
  video, on repeat.

  Before that, I started the Java game. It occupies almost all the
  operational memory. It needs at least 4Gb, I have 6Gb. In one moment
  freeze and not responding Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 24 23:26:29 2018
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-10-16 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799796/+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 1799612] Re: Suspend doesn't clear the display

2018-10-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  Suspend doesn't clear the display

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am on a Dell Precision 5520 running 18.10 with default settings,
  nvidia drivers, and updated this morning. The bug started yesterday or
  the day before.

  I have the laptop set to suspend on lid close. Since yesterday, when I
  open the lid and the display comes back on, the lock screen doesn't
  display. I see the dock bar on the left, the menu at the top, and
  either all black or whatever I was working on in the middle. I can
  move the mouse, but cannot interact with anything in the dock or the
  main display. I CAN interact with the power dropdown at the top right,
  where I can select a "pause" logo- which will cause the power to go
  off (fully suspending the machine presumably)... and from there when I
  wake it back up, the lock screen is properly displayed. I have ALSO
  tried mashing function keys to restart the GUI, and a couple times
  some combination of alt-ctrl-shift and some function keys have gotten
  me to a working login screen (and after typing my password, back to my
  working session) but it hasn't worked that way when trying to do it
  scientifically and press the buttons slowly to figure out which ones
  caused it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 19:37:49 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-15 (161 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-11 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799612/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

2018-10-28 Thread Daniel van Vugt
Franck, that's very strange. If you would like to keep discussing your
issue then please log a new bug.

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799242] Re: gnome-shell crashes when locking screen while dock widget is in focus

2018-10-28 Thread Daniel van Vugt
Kilian, yes, see step 2 in comment #2.

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

Title:
  gnome-shell crashes when locking screen while dock widget is in focus

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-shell crashes with signal 11 (segmentation fault) when I try to
  lock the screen while a widget  in the dock is in focus. The end
  result is that the screen either does not lock, and gnome-shell
  reloads, or it hangs (can move mouse, but mouse clicks or keyboard
  presses don't seem to have any effect). Either way no screen lock
  occurs.

  This is on a dual-screen setup, where I have the dock visible on both
  screens.

  Steps to reproduce:

  1) Open a terminal (or any app, terminal is just an example)
  2) Open a new terminal with cntrl+N 
  3) Click on the terminal icon on the dock, so it shows both instances of the 
terminal app
  4) Try to lock the screen with super+L
  5) Observe crash

  Attached is the output of syslog at the exact moment the crash occurs.

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Output of apt-cache policy gnome-shell:
  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.2
Candidate: 3.28.3-0ubuntu0.18.04.2
Version table:
   *** 3.28.3-0ubuntu0.18.04.2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799242/+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 1797518] Re: System freezes on resume from suspend

2018-10-28 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

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

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

Title:
  System freezes on resume from suspend

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Linux Version: 4.15.0-36-generic
  on resume from suspend, this could be a login or a minute after the screen 
freezes. Mouse does not move any longer.
  Total crash/hang this is new since about 3 weeks or so.
  All updates are installed.
  I attached kern.log, about 9:14 this morning I had to reboot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 09:30:00 2018
  DistUpgraded: 2018-07-08 17:00:19,279 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 640 OEM] [1043:8597]
  InstallationDate: Installed on 2018-05-28 (136 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: ASUSTeK COMPUTER INC. M70AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2fab21eb-af61-44eb-8a0a-f863dcc151ee ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-07-08 (95 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M70AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd03/19/2014:svnASUSTeKCOMPUTERINC.:pnM70AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM70AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: M70AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jul  9 17:58:45 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797518/+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 1800262] Re: screen rotates randonly

2018-10-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726160 ***
https://bugs.launchpad.net/bugs/1726160

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1726160, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1726160
   On login, display rotates to wrong orientation [HP Pavilion]

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

Title:
  screen rotates randonly

Status in xorg package in Ubuntu:
  New

Bug description:
  i've had this issue several times and twice during a new installation.
  it will happen randomly but mostly a few mins in to a boot up after
  being logged in, the screen will turn black for a moment and when it
  comes back the screen that is being displayed will be displaying 90
  degrees rotated counterclockwise. the only way i can get it to go back
  is to restart the system, and after several times i found a auto
  rotate lock option but i don't know why my laptop would be thinking
  it's being rotated while sitting level on a table?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 03:03:29 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d]
  InstallationDate: Installed on 2018-10-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 808D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 90.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 096C120800405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800262/+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 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

2018-10-28 Thread Daniel van Vugt
No the bug is not fixed in 18.04 yet.

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Triaged
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+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 1800358] Re: ubuntu xenial crashes after exiting any fullscreen

2018-10-28 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Changed in: 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/1800358

Title:
  ubuntu xenial crashes after exiting any fullscreen

Status in Ubuntu:
  Incomplete

Bug description:
   lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  
  apt-cache policy pkgname
  N: Unable to locate package pkgname

  i try to exit any fullscreen and it freezes and the only way out is to
  restart the system manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Oct 28 11:52:57 2018
  DistUpgraded: 2016-08-05 02:01:44,662 WARNING no activity on terminal for 300 
seconds (Installed klibc-utils (i386))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-137-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-138-generic, i686: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:0136]
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:0136]
  InstallationDate: Installed on 2016-07-28 (822 days ago)
  InstallationMedia: It
  MachineType: Acer Aspire 5315
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-138-generic 
root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (814 days ago)
  dmi.bios.date: 04/29/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Acadia
  dmi.board.vendor: Acer
  dmi.board.version: V1.35
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.35
  dmi.modalias: 
dmi:bvnAcer:bvrV1.35:bd04/29/2008:svnAcer:pnAspire5315:pvrV1.35:rvnAcer:rnAcadia:rvrV1.35:cvnAcer:ct1:cvrV1.35:
  dmi.product.name: Aspire 5315
  dmi.product.version: V1.35
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.96+git1810220630.9d07fb~oibaf~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1612070730.9871bd~gd~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810240730.0ff1cc~oibaf~x
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1810191934.f892d3~oibaf~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1810221934.0932a6~oibaf~x
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1805201934.ac8f7b~oibaf~x
  xserver.bootTime: Sun Oct 28 11:19:31 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   10100 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1788937] Re: intel hd4600

2018-10-28 Thread Daniel van Vugt
Please keep each bug report about a single problem. It sounds like this
is about graphics performance. And the PPA you say fixed it is:

  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

Are you able to test Ubuntu 18.10:

  http://releases.ubuntu.com/18.10/

and tell us if that also contains the bug?


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

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

Title:
  intel hd4600

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  intel hd4600 no support 3d

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 24 23:20:16 2018
  DistUpgraded: 2018-08-24 19:16:53,465 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0250]
  InstallationDate: Installed on 2018-08-24 (0 days ago)
  InstallationMedia: Xubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Wortmann_AG TERRA_MOBILE_1541H
  ProcEnviron:
   LANGUAGE=uk
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=68556d80-aa29-43b8-abad-a9d08b5469fb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W25CSW
  dmi.board.vendor: Clevo
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Clevo
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/08/2014:svnWortmann_AG:pnTERRA_MOBILE_1541H:pvrNotApplicable:rvnClevo:rnW25CSW:rvrNotApplicable:cvnClevo:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TERRA_MOBILE_1541H
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Wortmann_AG
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94+git1808241830.bcb9d9~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.99+git1808241930.cba8fe~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1807201025.3d3950~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788937/+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 1788937] Re: intel hd4600

2018-10-28 Thread Daniel van Vugt
** Changed in: xorg-server (Ubuntu)
   Status: Expired => New

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

Title:
  intel hd4600

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  intel hd4600 no support 3d

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 24 23:20:16 2018
  DistUpgraded: 2018-08-24 19:16:53,465 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0250]
  InstallationDate: Installed on 2018-08-24 (0 days ago)
  InstallationMedia: Xubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Wortmann_AG TERRA_MOBILE_1541H
  ProcEnviron:
   LANGUAGE=uk
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=68556d80-aa29-43b8-abad-a9d08b5469fb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W25CSW
  dmi.board.vendor: Clevo
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Clevo
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/08/2014:svnWortmann_AG:pnTERRA_MOBILE_1541H:pvrNotApplicable:rvnClevo:rnW25CSW:rvrNotApplicable:cvnClevo:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TERRA_MOBILE_1541H
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Wortmann_AG
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94+git1808241830.bcb9d9~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.99+git1808241930.cba8fe~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1807201025.3d3950~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788937/+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 1783452] Re: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications

2018-10-28 Thread Oleg
I added another screenshot that shows how to easily reproduce this issue
using pango-view utility.

It also shows the difference in rendering between 16.04 and 18.04.

** Attachment added: "Screenshot demonstrating how to reproduce the issue with 
pango-view"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+attachment/5206604/+files/pango-view-example.png

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

Title:
  Some font glyphs are rendered incorrectly (with additional vertical
  spacing) in GTK applications

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  After switching from 16.04 to 18.04 I noticed that fonts are now (in
  18.04) rendered differently in GTK+ apps.

  For example, there is a vertical bar charcter `│` 
[U+2502](https://unicode-table.com/en/2502), that is used extensively to create 
solid vertical lines using just text characters.
  You can see it in console apps such as `mc` or `pstree`.
  While it is rendered correctly in Terminal in both 16.04 and 18.04, when 
rendered inside GTK apps it has unexpected vertical gap in-between characters 
on 18.04 (16.04 renders it correctly).
  The issue can be seen in GTK apps such as gVIM, Geany, GEdit, but Qt apps 
seem to render it properly.

  I have attached a screenshot that clearly demonstrates the difference.
  It shows brand new Ubuntu 16.04 on a left side where you can see
  vertical line in GEdit is completely solid, as it should be. On a
  right side it shows Ubuntu 18.04 where you can see line now has gaps
  that should not be there.

  I built a small GTK2 test app that reproduces the problem (sources at
  https://pastebin.com/WCH1ds4P), and using it I found that the problem
  occurs when libfreetype 2.8+ is used. I tested FreeType 2.6, 2.7,
  2.7.1 and all of them work fine. While 2.8 and above has this gap.

  I am not 100% sure if this is an Ubuntu font configuration issue, or
  bug in FreeType, or GTK or some other Ubuntu components, but I hope
  someone at least can point me at the right direction.

  Please also check my post on AskUbuntu which has additional detail and
  screenshots: https://askubuntu.com/questions/1054779/incorrect-font-
  glyphs-rendering-in-gtk-applications-in-ubuntu-18-04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+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 1799907] Re: package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

2018-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Unable to remove chromium browser.
  Ubuntu 18.04.1 LTS
  69.0.3497.81-0ubuntu0.18.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-browser-l10n:amd64: Remove
   chromium-browser:amd64: Remove
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLRoNVkxaWhAaAQOAMBt4KlKVpVZUnSUOUFS/74BxT4HAgQCBgJUAqcCzAAEBAjqAGHE4LUBYLEUA3QwRAAAe/QAySx5REQAKICAgICAg/ABTMjJGMzUwCiAgICAg/wBINFpINDExNzA5CiAgAf8CAxGxRpAEHxMSA2UDDAAQAAEdALxS0B4guChVQN0MEQAAHowK0JAgQDEgDEBVAN0MEQAAGIwK0Iog4C0QED6WAN0MEQAAGAAAUA==
   modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 
1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Thu Oct 25 10:46:48 2018
  Desktop-Session:
   'None'
   'None'
   'None'
  DpkgTerminalLog:
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  DuplicateSignature:
   package:chromium-browser:69.0.3497.81-0ubuntu0.18.04.1
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
  Env:
   'None'
   'None'
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2018-10-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Fri Aug  3 08:18:24 2018)
  Load-Avg-1min: 5.92
  Load-Processes-Running-Percent:   0.3%
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=98ec02f9-f4a2-4059-b2db-89f6add91501 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  SourcePackage: chromium-browser
  Title: package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1800398] [NEW] login password not showing

2018-10-28 Thread Jim Sherick
Public bug reported:

6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE
18.10. I saved a login password but it did not show in the keyring when
I looked. I did not check any other parts of Seahorse since I don't plan
to use encryption. Reloaded MATE 18.04 and it works fine there. #327481
did not seem to let me re-open that issue from 2010 so reporting again.

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

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

Title:
   login password not showing

Status in seahorse package in Ubuntu:
  New

Bug description:
  6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE
  18.10. I saved a login password but it did not show in the keyring
  when I looked. I did not check any other parts of Seahorse since I
  don't plan to use encryption. Reloaded MATE 18.04 and it works fine
  there. #327481 did not seem to let me re-open that issue from 2010 so
  reporting again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1800398/+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 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread brian_p
The link is not similar to the previous one. It looks like the upgrade
did not adjust it correctly. A ghostscript bug?

-- 
Brian.

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-10-28 Thread AzureRaptor
I have installed the "edge" hwe packages as denoted in these two
comments:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/comments/148

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/comments/149

I can confirm that after this action hibernation is working properly for
me.  Previously I was stuck on a specific mainline 4.15 release and was
afraid to move off it; hibernation is vital for my workflow (and sanity
in general).

: uname -a
Linux hostname 4.15.0-38-generic #41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1799995] Re: simple scan can not detect my printer/scanner

2018-10-28 Thread Robert Ancell
According to http://sane-project.org/sane-mfgs.html#Z-EPSON this should
be supported by the SANE drivers. This will need to be solved in the
driver in the SANE project. Note that connecting via USB using different
protocols than network scanning which is why it works only over the
network.

** Package changed: simple-scan (Ubuntu) => sane-backends (Ubuntu)

** Summary changed:

- simple scan can not detect my printer/scanner
+ Epson DX8400 not detected

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

Title:
  Epson DX8400 not detected

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I am using an Epson DX8400 printer/sacanner on a ubuntu 18.04 64 bit
  installation. When I connect the printer via USB on my fritzbox3490
  router, the system sees the printer/scanner and it prints correctly.
  However when I activate simple scan I get the message "no scanner
  detected".

  If I plug the printer/scanner direct to my pc USB port everything
  works okay both printing and scanning. However this prevents others on
  my small network from using the scanner.

  Why cant the system detect the scanner app when it detects the printer
  perfectly when connected via the router.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/175/+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 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread tomdean
On 10/28/18 9:31 AM, brian_p wrote:
> ls -l/usr/share/ghostscript/

 > ls -l /usr/share/ghostscript/
total 8
drwxr-xr-x 4 root root 4096 Oct 28 06:49 9.25
lrwxrwxrwx 1 root root   37 Aug  8  2017 current -> 
/etc/alternatives/ghostscript-current
drwxr-xr-x 2 root root 4096 Oct 19 12:44 fonts

Tom Dean

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread Alex Garel
@grzesiekc thanks for the comment, on my side I have no such specific
content.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:65
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1  - 
Power Button: is tagged by 

[Desktop-packages] [Bug 1800210] Re: dose not work rite

2018-10-28 Thread Cristian Aravena Romero
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: xorg (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/1800210

Title:
  dose not work rite

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  APP STOR DOES NOT WORK RITE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct 26 15:04:24 2018
  DistUpgraded: 2018-10-25 22:05:32,733 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2c9d5f71-ce27-4b3c-8018-0404d4ab5fb9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite C655
  dmi.product.sku: Montevina_Fab
  dmi.product.version: PSC08U-03C01K
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Thu Oct 25 19:03:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5760 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800210/+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 1800380] Re: Back button doesn't work

2018-10-28 Thread Paul White
*** This bug is a duplicate of bug 1798053 ***
https://bugs.launchpad.net/bugs/1798053

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

** This bug has been marked a duplicate of bug 1798053
   [SRU] Click on the back icon in gnome-software doesn't work

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

Title:
  Back button doesn't work

Status in gnome-software package in Ubuntu:
  New

Bug description:
  To reproduce:

  0. Do a completely fresh install of Ubuntu 18.10.
  1. Download Dropbox .deb (or any other I assume), open it with the software 
center.
  2. Install it.
  3. Try to click the back button in the top left hand corner.
  4. Nothing happens. Quality software here.
  5. Ok I'll restart it - click the close button in the top right.
  6. Launch it again.
  7. It's still on the Dropbox page? WTF? Back button still does not work.

  This is rubbish.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1800380/+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 1800380] [NEW] Back button doesn't work

2018-10-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

To reproduce:

0. Do a completely fresh install of Ubuntu 18.10.
1. Download Dropbox .deb (or any other I assume), open it with the software 
center.
2. Install it.
3. Try to click the back button in the top left hand corner.
4. Nothing happens. Quality software here.
5. Ok I'll restart it - click the close button in the top right.
6. Launch it again.
7. It's still on the Dropbox page? WTF? Back button still does not work.

This is rubbish.

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

-- 
Back button doesn't work
https://bugs.launchpad.net/bugs/1800380
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

-- 
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 1798888] Re: Displays shows only one display

2018-10-28 Thread Donald Gordon
Which is to say this is more of a usability issue than a "this
functionality is unavailable."

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

Title:
  Displays shows only one display

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

Bug description:
  Upon upgrading from 18.04 to 18.10, only one of my displays is
  working.

  Only one display shows in control centre.  I have two, one connected
  via DisplayPort, one via VGA.

  The VGA works, DP doesn't.

  If I unplug the VGA display, then the DisplayPort display turns on.
  Plug it back in, the DisplayPort display turns off.

  XRANDR shows both displays.  Confusingly, the VGA display appears as
  "DP-2" in XRANDR, and the DisplayPort connected display shows as
  "HDMI-1."

  If I manually enable the second display with

  xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080

  then the second display starts to work, and it appears in the Displays
  section of the control centre, as it used to in Ubuntu 18.04.

  Here's the output of xrandr prior to manually enabling the second
  display:

  donald@silver:~$ xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  LVDS-1 connected (normal left inverted right x axis y axis)
 1600x900  60.06 +  59.9959.9459.9559.8240.04  
 1440x900  59.89  
 1400x900  59.9659.88  
 1440x810  60.0059.97  
 1368x768  59.8859.85  
 1360x768  59.8059.96  
 1280x800  59.9959.9759.8159.91  
 1152x864  60.00  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  59.90  
 1280x960  60.00  
 1280x800  74.9359.91  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  DP-1 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  HDMI-3 disconnected (normal left inverted right x axis y axis)
  DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 521mm x 293mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1280x800  74.9359.81  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  DP-3 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 20 08:10:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-08-13 (67 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1798888] Re: Displays shows only one display

2018-10-28 Thread Donald Gordon
OK so I've just found out where my extra displays were hiding.  The
Button that says 3 Viewsonic Corp ... can be clicked on to choose
another monitor.

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

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

Title:
  Displays shows only one display

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

Bug description:
  Upon upgrading from 18.04 to 18.10, only one of my displays is
  working.

  Only one display shows in control centre.  I have two, one connected
  via DisplayPort, one via VGA.

  The VGA works, DP doesn't.

  If I unplug the VGA display, then the DisplayPort display turns on.
  Plug it back in, the DisplayPort display turns off.

  XRANDR shows both displays.  Confusingly, the VGA display appears as
  "DP-2" in XRANDR, and the DisplayPort connected display shows as
  "HDMI-1."

  If I manually enable the second display with

  xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080

  then the second display starts to work, and it appears in the Displays
  section of the control centre, as it used to in Ubuntu 18.04.

  Here's the output of xrandr prior to manually enabling the second
  display:

  donald@silver:~$ xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  LVDS-1 connected (normal left inverted right x axis y axis)
 1600x900  60.06 +  59.9959.9459.9559.8240.04  
 1440x900  59.89  
 1400x900  59.9659.88  
 1440x810  60.0059.97  
 1368x768  59.8859.85  
 1360x768  59.8059.96  
 1280x800  59.9959.9759.8159.91  
 1152x864  60.00  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  59.90  
 1280x960  60.00  
 1280x800  74.9359.91  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  DP-1 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  HDMI-3 disconnected (normal left inverted right x axis y axis)
  DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 521mm x 293mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1280x800  74.9359.81  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  DP-3 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 20 08:10:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-08-13 (67 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center

[Desktop-packages] [Bug 1782510] Re: lightdm automatically logs in after logout

2018-10-28 Thread bastafidli
This defect may not be in lightdm package. I was just able to reproduce
it on Ubuntu 18.04.01 distribution. Here is how I did it.

I am using 18.04.01 with KDE.
I installed the skypeforlinux package
This package had unsatisfied dependency gnome-keyring as without it skype will 
not log in automatically.
I installed gnome-keyring and seahorse so that I can reset the keyring.
After these three I wasn't able to logout from my KDE session as I was logged 
back in.
It didn't help to uninstall skypeforlinux or seahorse. 
Only after I uninstalled gnome-keyring and restarted my computer I am able to 
normally logout from my KDE session.

On a side node now even after I log out, I can still see my session hanging 
around using
sudo loginctl
If I log in it till create second session as reported by the above command but 
at least I can logout reliably.


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

** Also affects: gnome-keyring
   Importance: Undecided
   Status: New

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

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

Title:
  lightdm automatically logs in after logout

Status in GNOME Keyring:
  New
Status in Light Display Manager:
  New
Status in skype:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Lightdm makes it impossible to logout. After I logout the lightdm logs
  me automatically backs in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul 19 01:18:52 2018
  InstallationDate: Installed on 2016-04-26 (814 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/1782510/+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 1799796] Re: Freeze to stop responding

2018-10-28 Thread JmAbuDabi
loading occurred for the third time.

Freeze occured in Unity environment.

I think that the gnome-shell has nothing to do with my problem


** Attachment added: "journalctl -b-1 > previous_boot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799796/+attachment/5206565/+files/previous_boot.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/1799796

Title:
  Freeze to stop responding

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu does not start right away 18.04. Having passed the Grub menu,
  the system starts up and then a black screen. Reboot, so maybe several
  times. Hard drives: Smart OK.

  How to boot I enter the password. Run Chrome. looking through YouTube.
  Hangs tightly. The mouse does not move. I hear the last sound from the
  video, on repeat.

  Before that, I started the Java game. It occupies almost all the
  operational memory. It needs at least 4Gb, I have 6Gb. In one moment
  freeze and not responding Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 24 23:26:29 2018
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-10-16 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799796/+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 1265898] Re: thunderbird doesn't remember maximized window state in Ubuntu Gnome

2018-10-28 Thread NJ
Cf.:

https://bugzilla.mozilla.org/show_bug.cgi?id=732812

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

Title:
  thunderbird doesn't remember maximized window state in Ubuntu Gnome

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Not sure if this is thunderbird or gnome-shell related issue.

  Steps to reproduce:
  1. Run thunderbird.
  2. Maximize thunderbird window.
  3. Close thunderbird.
  4. Run thunderbird again.
  5. Notice that thunderbird window is not maximized - maximized window state 
was not saved during closing.

  Expected behaviour:
  In 5. thudnderbird window is open in maximized state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:24.2.0+build1-0ubuntu1
  Uname: Linux 3.13.0-031300rc6-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dotnokato   1431 F pulseaudio
   /dev/snd/pcmC0D0p:   dotnokato   1431 F...m pulseaudio
  BuildID: 20131206222054
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Jan  3 21:02:28 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-15 (79 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  IpRoute:
   default via 10.100.10.1 dev eth0  proto static 
   10.100.10.0/24 dev eth0  proto kernel  scope link  src 10.100.10.8  metric 1 
   10.100.10.0/24 dev wlan0  proto kernel  scope link  src 10.100.10.12  metric 
9
  Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources:
   prefs.js
   
[Profile]/extensions/gnomeintegrat...@davidmartinez.net/defaults/preferences/gnomeintegration.js
  Profiles: Profile0 (Default) - LastVersion=24.2.0/20131206222054 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.1-1ubuntu8
   gnome-shell   3.8.4-0ubuntu6
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (59 days ago)
  dmi.bios.date: 05/08/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68TT2 Ver. F.07
  dmi.board.name: 30B0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.15
  dmi.chassis.asset.tag: CNU7110B09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx6325 (EY349EA#AKD)
  dmi.product.version: F.07
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1265898/+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 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

2018-10-28 Thread Cristian Aravena Romero
** Summary changed:

- 20% of volume is like 0%
+ [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

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

Title:
  [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178/+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 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Rodrigo Melotto
Update:

Hello Cristian,
So I havent changed anything, im watching Youtube all day long today and the 
autoclicks just stopped.
Since it was happening nonstop yesterday but today it didnt had one single 
"auto" click I think its over.
Lets wait for one more day and I think it can be closed.


*Just to stress that I didnt do anything to mouse/touchpad/video drivers. 
Yesterday before I open this topic I've shutdown my note and turn it on again 
but the autoclicks persisted.
I turned of my note the whole night.
I dont use any macro of any kind, be it mouse, keyboard or whatever.
Its weird.

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to release 

[Desktop-packages] [Bug 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Cristian Aravena Romero
** Summary changed:

- Mouse click every 1-2 minutes
+ [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to release device: Device not taken
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800292/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-10-28 Thread Hartmut Jürgens
Brother MFC-215C: Installing drivers from support.brother.com is not sufficient.
But it worked after setting two symbolic links:
~$ sudo ln -s /usr/lib/sane/libsane-brother2.so.1.0.7 
/usr/lib/x86_64-linux-gnu/sane/libsane-brother2.so.1.0.7
~$ sudo ln -s /usr/lib/x86_64-linux-gnu/sane/libsane-brother2.so.1.0.7  
/usr/lib/x86_64-linux-gnu/sane/libsane-brother2.so.1

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread brian_p
There is nothing to be done by you, but I have seen this issue appear at
least five times so it wouldn't be unreasonable to see the upgrade
process as flawed. What do you get now for

  ls -l /usr/share/ghostscript/ ?

Thanks for the feedback.

-- 
Brian.

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1790122] Re: Skype snap crashes Xwayland

2018-10-28 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  Skype snap crashes Xwayland

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The Skype snap segfaults GNOME Shell on Wayland, crashing the session
  and sending the user back to the login screen.

  ```
  $ snap info skype
  name:  skype
  summary:   One Skype for all your devices. New features. New look. All Skype.
  publisher: Skype✓
  contact:   https://www.skype.com/
  license:   unset
  description: |
Skype keeps the world talking. Say “hello” with an instant message, voice 
or video call – all for
free, no matter what device they use Skype on. Skype is available on 
phones, tablets, PCs, Macs
and Linux.

• Video calls – Don’t just hear the cheers, see it! Get together with 1 or 
24 of your friends and
family on a video call. Watch your everyone’s smiles and cries when you 
tell them “We’re
engaged!!!"

• Chat – Reach people instantly. Send messages to your friends, liven up 
conversations with
emoticons and Mojis, or create a group chat to make weekend plans with up 
to 300 people.

• Share – Do more together. Easily share your screen, photos, videos, 
documents, and files with
your family and friends. Unlike email, Skype will transfer up to 300MB per 
file.

• Voice calls – Camera shy? Make voice calls to anyone on Skype. You can 
also call mobile and
landlines at low rates.
  commands:
- skype
  snap-id:  QRDEfjn4WJYnm0FzDKwqqRZZI77awQEV
  tracking: insider/stable
  refresh-date: today at 12:56 CEST
  channels:  
stable:8.28.0.41  (51) 148MB classic
candidate: ↑ 
beta:  ↑ 
edge:  ↑ 
insider/stable:8.29.76.16 (52) 148MB classic
insider/candidate: ↑ 
insider/beta:  ↑ 
insider/edge:  ↑ 
  installed:   8.29.76.16 (52) 148MB classic

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Aug 31 12:58:26 2018
  DistUpgraded: 2018-05-14 22:56:54,009 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-32-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 530 [1025:105b]
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GM204M [GeForce GTX 980M] [1025:105b]
  InstallationDate: Installed on 2017-04-10 (507 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Lsusb:
   Bus 002 Device 046: ID 0bda:0316 Realtek Semiconductor Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Predator G9-791
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic 
root=UUID=30803519-0e69-413b-baaa-2adab2ea4c1e ro rootflags=subvol=@ 
nouveau.modeset=0 intel_iommu=on nouveau.runpm=0 i915.modeset=1 
nvidia_drm.modeset=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to bionic on 2018-05-14 (108 days ago)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Challenger_SLS
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  

[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2018-10-28 Thread ldmpub
Thanks Theo => your tip fix it for me.

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778069/+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 1800360] [NEW] Unity Control Center doesn’t allow to select Yaru theme

2018-10-28 Thread Adolfo Jayme
Public bug reported:

The Appearance section of the application still hardcodes Adwaita,
Ambiance, Radiance and High Contrast. Other GTK+ themes are not listed
at all.

** Affects: unity-control-center (Ubuntu)
 Importance: Medium
 Status: Triaged

** Changed in: unity-control-center (Ubuntu)
   Status: New => Triaged

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unity Control Center doesn’t allow to select Yaru theme

Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  The Appearance section of the application still hardcodes Adwaita,
  Ambiance, Radiance and High Contrast. Other GTK+ themes are not listed
  at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1800360/+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 1739634] Re: Can we please get Mouse Acceleration as a GUI control?

2018-10-28 Thread Adolfo Jayme
** Changed in: unity-control-center (Ubuntu)
   Status: New => Triaged

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Can we please get Mouse Acceleration as a GUI control?

Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  Can we please get a GUI control for adjusting and turning off Mouse
  Acceleration? This is really important for gaming.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unity-control-center 15.04.0+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 21 08:51:55 2017
  InstallationDate: Installed on 2015-07-20 (884 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1739634/+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 1800358] [NEW] ubuntu xenial crashes after exiting any fullscreen

2018-10-28 Thread T.Vex
Public bug reported:

 lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04


apt-cache policy pkgname
N: Unable to locate package pkgname

i try to exit any fullscreen and it freezes and the only way out is to
restart the system manually.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
Uname: Linux 4.4.0-138-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Oct 28 11:52:57 2018
DistUpgraded: 2016-08-05 02:01:44,662 WARNING no activity on terminal for 300 
seconds (Installed klibc-utils (i386))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-137-generic, i686: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-138-generic, i686: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:0136]
   Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:0136]
InstallationDate: Installed on 2016-07-28 (822 days ago)
InstallationMedia: It
MachineType: Acer Aspire 5315
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-138-generic 
root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-05 (814 days ago)
dmi.bios.date: 04/29/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.35
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.35
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.35
dmi.modalias: 
dmi:bvnAcer:bvrV1.35:bd04/29/2008:svnAcer:pnAspire5315:pvrV1.35:rvnAcer:rnAcadia:rvrV1.35:cvnAcer:ct1:cvrV1.35:
dmi.product.name: Aspire 5315
dmi.product.version: V1.35
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.96+git1810220630.9d07fb~oibaf~x
version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1612070730.9871bd~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810240730.0ff1cc~oibaf~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1810191934.f892d3~oibaf~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1810221934.0932a6~oibaf~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1805201934.ac8f7b~oibaf~x
xserver.bootTime: Sun Oct 28 11:19:31 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   10100 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial

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

Title:
  ubuntu xenial crashes after exiting any fullscreen

Status in xorg package in Ubuntu:
  New

Bug description:
   lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  
  apt-cache policy pkgname
  N: Unable to locate package pkgname

  i try to exit any fullscreen and it freezes and the only way out is to
  restart the system manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Oct 28 11:52:57 2018
  DistUpgraded: 2016-08-05 02:01:44,662 WARNING no activity on terminal for 300 
seconds (Installed klibc-utils (i386))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-137-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-138-generic, i686: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
 

[Desktop-packages] [Bug 1800359] [NEW] libosmesa6 is not installable in 18.04

2018-10-28 Thread Doug McMahon
Public bug reported:

currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at version
18.0.5-0ubuntu0~18.04.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libosmesa6 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 28 10:55:42 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
 NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
InstallationDate: Installed on 2018-10-13 (14 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=e8def74e-6e50-4d6e-9adb-07d2b230cb55 ro quiet splash
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1.1~ppa
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu

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

Title:
  libosmesa6 is not installable in 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at
  version 18.0.5-0ubuntu0~18.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libosmesa6 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Oct 28 10:55:42 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2018-10-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=e8def74e-6e50-4d6e-9adb-07d2b230cb55 ro quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 

[Desktop-packages] [Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses

2018-10-28 Thread Adolfo Jayme
** Project changed: ubuntu-gnome => hundredpapercuts

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  Too many icons in Gnome Shell Activities Overview require ellipses

Status in GNOME Shell:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Several apps in the default Ubuntu 17.04 or 17.10 install have
  Ellipses when shown in GNOME Shell's Activities Overview.

  This was made worse by switching GNOME Shell to use the Ubuntu font
  because the Ubuntu font is a bit wider than GNOME's default Cantarell
  font so some apps that didn't require ellipses in 17.04 require them
  now in 17.10 Alpha.

  The upstream GNOME bug proposes that apps names be allowed to use 2
  lines. This is similar to what the Settings app (gnome-control-center)
  does.

  This is also really bad for languages that use more characters than
  English.

  Original Bug Title
  --
  Gnome Shell Activities Overview should show full names on mouse hover

  Original Bug Report
  ---
  The title says it all --- especially when choosing recent documents, if they 
start with the same say 12 or 14 letters, it's impossible to differentiate them 
 (see attached screenshot).

  When mouse is hovering an icon, the full name of the
  application/document should be shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/968213/+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 1800352] Re: desktop and current applications displayed when resuming from lock

2018-10-28 Thread Harry P
possibly related bugs from previous versions:

https://bugs.launchpad.net/debian/+source/gnome-shell/+bug/1532508
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768786

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] [NEW] desktop and current applications displayed when resuming from lock

2018-10-28 Thread Harry P
Public bug reported:

after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
laptop lid), before typing password (or indeed anything), the whole
desktop including running apps is displayed. although they are not
interactable/responsive, sensitive info is displayed.

possibly related, super+l seems to put the desktop into a similar state
- apps visible, but not interactable.  pressing it a second time
produces a more normal lock reaction.

gnome-shell:  Installed: 3.30.1-2ubuntu1

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

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread tomdean
HP Officejet Pro 8620 fails printing with filter failed message
sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common
in cups, localhost:631, restart jobs
printed all jobs.

My issue seems to be fixed.

Does something need to be done in the upgrade process?

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1785587] Re: lide100 scanners produce a white/orange band in scanned images on Ubuntu 18.04

2018-10-28 Thread Chris
Followed the instructions from "Gabriel N. <1731...@bugs.launchpad.net>", 
posted Fri, 05th Oct 2018,
works fine for me, just changed the ./configure-option from defaults to 
"--prefix=/usr --sysconfdir=/etc --localstatedir=/var".

After install the patched
libsane1_1.0.27-1~experimental3ubuntu2_amd64.deb, do a "ldconfig" and
start the simple-scan prog, booting the OS was not necessary.

Both of my Lide 100 now works as expected.

Hope the ubuntu-guys would insert this simple patch in the near time
also ...

greetings to all
/chris

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

Title:
  lide100 scanners produce a white/orange band in scanned images on
  Ubuntu 18.04

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Maybe this bug is the same shown in
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459
  ...

  I've 2 Canon Lide 100 scanners. Both works well with ubuntu 16.04. 
  Running them on ubuntu 18.04 it first shows a black bar across the scanned 
page,
  after some updates (apt-get update) it currently shows white and orange bars.

  Booting my system with the old installed 16.04 both scanners works well,
  running 18.04 both scanners show the black/white/orange-bar effect.

  Reading at bug-report 1731459 that this is fixed in 1.0.27 original, I 
downloaded
  the daily-tar-gz from 
http://www.sane-project.org/snapshots/sane-backends-git20180806.tar.gz,
  compile and replace the 
/usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1.0.27.

  Unfortunately it does not work as describe. Removing this lib, simple-scan 
could not find
  the scanner, so i think a replaced the right one.

  This bug is now nearly 9 month old and reported, please Canonical
  could you fix this !

  /chris

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  All Update included since Aug 6. 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1785587/+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 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread brian_p
>From your error log:

 > D [27/Oct/2018:14:09:05 -0700] [Job 466] ./base/gsicc_manage.c:1244: 
 > gsicc_open_search(): Could not find default_gray.icc 
 > D [27/Oct/2018:14:09:05 -0700] [Job 466] | ./base/gsicc_manage.c:2025: 
 > gsicc_set_device_profile(): cannot find device profile
 > D [27/Oct/2018:14:09:05 -0700] [Job 466] Unrecoverable error: rangecheck in 
 > .putdeviceprops

See
  https://bugs.launchpad.net/hplip/+bug/1799104

How do you go on?

-- 
Brian.

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1756597] Re: Rhythmbox plugin "Song Lyrics" not working

2018-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Rhythmbox plugin "Song Lyrics" not working

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  With either rhythmbox-plugins-3.0.2-0ubuntu2 (Linux Mint 17.3 Cinnamon) or 
rhythmbox-plugins-3.3-1ubuntu7 (Linux Mint 18.2 XFCE) when the "Song Lyrics" 
plugin is enabled and the following are checked, lyrics are never displayed:
  * WinampCN (www.winampcn.com)
  * Dark Lyrics (darklyrics.com)
  * Jetlyrics (jetlyrics.com)
  * I didn't use the other two since I speak only English

  Looking at the code in '/usr/lib/rhythmbox/plugins/lyrics/' and
  experimenting with the queries suggests that the remote web sites have
  changed.

  For example, 'JetlyricsParser.py' has:
  * q = title + ' - ' + artist
  * url = 'http://www.jetlyrics.com/search.php?q=%s' % (q)

  But http://www.jetlyrics.com/search.php?q=acdc-hells+bells is 404,
  while doing it manually from http://www.jetlyrics.com/ yields
  http://lyrics.jetmute.com/search.php?q=acdc+hells+bells=Search
  with some results.

  Likewise DarkLyricsParser.py has:
  * url = 'http://www.darklyrics.com/lyrics/%s/%s.html' % (best_match.artist, 
best_match.album)

  But http://www.darklyrics.com/lyrics/acdc/hells+bells.html returns a
  404/search page and the  search "acdc hells bells" from that page is
  null but manually working through the form you can get
  https://www.azlyrics.com/lyrics/acdc/hellsbells.html.

  In those examples both the base web site and search strings have
  changed, rendering the plugin code out of date.

  Also, CTRL-L no longer works in either Mint 17's RB 3.0.2 or Mint 18's
  3.0.0, but "View > Song Lyrics" works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1756597/+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 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

2018-10-28 Thread A Raghuram
Has this been fixed in 18.04.1 as well ?  Please confirm.

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Triaged
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread GrzesiekC
Hello again all,

In my #10 comment, I forgot to mention that my system it is upgraded
from ubuntu 16.04.4.

As it is, on Thursday (25-10-2018), two major things happened:
1. The kernel was updated to - Linux E7470 4.15.0-39-generic #42-Ubuntu SMP Tue 
Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

2. I "rewound" my bash history file. I was looking for any workarounds,
I performed during the lifespan of my 16.04.x. I found a line where I
was messing with my Intel driver. To be honest, ATM I'm not sure why,
but I added this file to resolve some other forgotten issue.

/usr/share/X11/xorg.conf.d/20-intel.conf

and here is the content:

Section "Device"
Driver "Intel"
Identifier "Intel"
EndSection

I deleted the file.

Why I bother you with this long post - since Thursday , I haven't had any 
single lock-up. 
So, it looks like, one of those two helped in my case. 
Finger cross it will stay this why for a bit longer.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Mathieu Barquin
Hi All,
any progress here ?
Thanks

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work for me.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  

[Desktop-packages] [Bug 1800328] [NEW] HP Office Jet Cups reports Filter Failed. Works OK with 16.04

2018-10-28 Thread tomdean
Public bug reported:

After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
On a 16.04 system printing is OK.
Printer: Network HP-Officejet-Pro-8620
No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sat Oct 27 23:58:29 2018
Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
MachineType: System76 Meerkat
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
dmi.bios.date: 11/22/2017
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
dmi.board.name: NUC7i7BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J31145-304
dmi.chassis.type: 3
dmi.chassis.vendor: System76
dmi.chassis.version: meer3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
dmi.product.name: Meerkat
dmi.product.version: meer3
dmi.sys.vendor: System76

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  HP Office Jet Cups reports Filter Failed.  Works OK with 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails 
to print with the status "Filter Failed".
  On a 16.04 system printing is OK.
  Printer: Network HP-Officejet-Pro-8620
  No changes were made other than the do-release-upgrade and 'apt dist-upgrade'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 27 23:58:29 2018
  Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100
  MachineType: System76 Meerkat
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: meer3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3:
  dmi.product.name: Meerkat
  dmi.product.version: meer3
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1800328/+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 1800327] Re: local movies are broken

2018-10-28 Thread Shayan Zahed
** Description changed:

- when i watch local videos that are on my pc, they look pixelated and
- red, orange, and purple, I expected it to show my movie normally, I have
- installed restricted extras. My Graphics card is an rx580 8gb and cpu is
- an 8700k (integrated graphics might have something to do with it) I have
- tried opening the same video files on linux mint 19 Tara and have had no
- issues. and when i try openning them in ubuntu on wayland it just shows
- a blank screen and videos freezes. I am having these issues on 18.10
+ when i watch local videos that are on my pc, they look pixelated and red, 
orange, and purple, I expected it to show my movie normally, I have installed 
restricted extras. My Graphics card is an rx580 8gb and cpu is an 8700k 
(integrated graphics might have something to do with it) I have tried opening 
the same video files on linux mint 19 Tara and have had no issues. and when i 
try openning them in ubuntu on wayland it just shows a blank screen and videos 
freezes. I am having these issues on 18.10
+ Edit: videos work fine on VLC, so that means the default video player is 
broken? because I moved from ubuntu 18.04 to LM 19 because videos didn't work 
at all even on VLC, VlC just crashed and games didn't load even after fresh 
install of Ubuntu 18.04, so I decided to move to LM 19, and after the new 
Ubuntu update I decided to install Ubuntu 18.10 this time as a secondary OS 
beside LM 19 to check if it still has that issue and once I saw that videos 
looked glitched in the default video player I automatically thought It would 
have the other issues too because I thought they were all related.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 23:55:29 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0517]
+  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0517]
  InstallationDate: Installed on 2018-10-27 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd. MS-7B47
  ProcEnviron:
-  LANGUAGE=en_CA:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_CA:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=88fb35a0-129f-4c56-a10d-d00bf598a085 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 TOMAHAWK (MS-7B47)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd05/17/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B47:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370TOMAHAWK(MS-7B47):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B47
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

** Package changed: xorg (Ubuntu) => gnome-media-player (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.

[Desktop-packages] [Bug 1800309] Re: not installed during update to ubuntu 18

2018-10-28 Thread Seth Arnold
Hello, please note that you may have a hardware issue, your CPUs are
overheating a lot. Try cleaning the fans, heatsinks, etc.

Thanks

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

Title:
  not installed during update to ubuntu 18

Status in xorg package in Ubuntu:
  New

Bug description:
  some errors on installing video xorg intel, some corrupted
  files/dependencies

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 22:14:06 2018
  DistUpgraded: 2018-10-27 15:51:41,727 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002]
  InstallationDate: Installed on 2018-03-29 (212 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K54HR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d5e3b7bd-e24f-42fc-9840-8e671d6e8c81 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-27 (0 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54HR.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54HR
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54HR.205:bd06/20/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54HR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 27 12:38:54 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800309/+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 1800327] [NEW] local movies are broken

2018-10-28 Thread Shayan Zahed
Public bug reported:

when i watch local videos that are on my pc, they look pixelated and
red, orange, and purple, I expected it to show my movie normally, I have
installed restricted extras. My Graphics card is an rx580 8gb and cpu is
an 8700k (integrated graphics might have something to do with it) I have
tried opening the same video files on linux mint 19 Tara and have had no
issues. and when i try openning them in ubuntu on wayland it just shows
a blank screen and videos freezes. I am having these issues on 18.10

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 27 23:55:29 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0517]
InstallationDate: Installed on 2018-10-27 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Micro-Star International Co., Ltd. MS-7B47
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=88fb35a0-129f-4c56-a10d-d00bf598a085 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: Default string
dmi.board.name: Z370 TOMAHAWK (MS-7B47)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd05/17/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B47:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370TOMAHAWK(MS-7B47):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B47
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

** Attachment added: "A screenshot of a movie with this issue"
   
https://bugs.launchpad.net/bugs/1800327/+attachment/5206438/+files/Screenshot%20from%202018-10-28%2000-16-55.png

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

Title:
  local movies are broken

Status in xorg package in Ubuntu:
  New

Bug description:
  when i watch local videos that are on my pc, they look pixelated and
  red, orange, and purple, I expected it to show my movie normally, I
  have installed restricted extras. My Graphics card is an rx580 8gb and
  cpu is an 8700k (integrated graphics might have something to do with
  it) I have tried opening the same video files on linux mint 19 Tara
  and have had no issues. and when i try openning them in ubuntu on
  wayland it just shows a blank screen and videos freezes. I am having
  these issues on 18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 23:55:29 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7)