date:20190108

To clarify, when the original problem was discovered in cosmic the CPU
usage was around 80%, and the fix made it less than 50% [1].

But now even without the fix (although in bionic, still using the same
hardware), CPU usage for the same test case is around 50%. So indeed the
main issue seems to be gone.

What I can't figure out is why the problem isn't reproducible in bionic
even when the root cause was introduced in bionic version
1.52.1-1ubuntu1. The bug and the effect of the fix was much more obvious
in cosmic and disco...

Still, gjs version 1.52.5-0ubuntu18.04.1 eliminates even the theoretical
possibility of the CPU problem and it allows us to drop all patches \o/

[1] https://gitlab.gnome.org/GNOME/gjs/merge_requests/236

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

Title:
  [regression] Much higher CPU during some gnome-shell operations

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Fix Committed
Status in gjs source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  Since fixing bug 1672297 in release 18.04 we experience much higher (almost 
double) CPU usage during gnome-shell JavaScript operations, such as the icon 
spring animation [1]. Even just moving the mouse is a little more expensive now 
[2].
  [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  [2] https://gitlab.gnome.org/GNOME/mutter/issues/283

  [Test Case]

  Use 'top' to measure the CPU usage of the gnome-shell process while
  tapping Super+A repeatedly. It should be much lower with the fix than
  without.

  [Regression Potential]

  Low. This particular fix is tiny
  (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been
  released and used in a couple of upstream gjs versions already without
  issue.

  [Other Info]

  The fix is already released to 19.04 as part of gjs version 1.54.2-1.
  And already released to 18.10 as part of gjs version
  1.54.3-1~ubuntu18.10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels

gnome-shell-extension-ubuntu-dock (64ubuntu1) disco; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release: 64
  * dash, docking: remove Shell.GenericContainer.

  [ Adolfo Jayme Barrientos ]
  * Update Spanish translation.

  [ franglais125 ]
  * Settings.ui: Fix GtkEntry property to make the shortcut editable.

  [ Michele ]
  * Add Gnome Shell 3.30 support.
  * Bump version (v64).

  [ vantu5z ]
  * Update Russian translation.

  [ Andrea Azzarone ]
  * docking: Fix leaking signal connection

  [ Michele Gaio ]
  * Update Readme with official extension badge.

  [ Michele ]
  * Add a .default class to the appiconindicators.
  * Make window previews order stable in the dedicated popup (LP: #1809129).
  * Recreate windows preview whenever the popup is open.

  [ Daniel van Vugt ]
  * Avoid repainting an unchanging dock.

 -- Marco Trevisan (Treviño)   Wed, 19 Dec 2018
10:06:26 -0500


** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-shell is wasting CPU repainting unchanging panels

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the
  panel get repainted. But the panels mostly doesn't change, so should
  be cached via offscreen-redirect instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1743976/+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 1797373] Re: 3D slide transitions don't work at all or tear when played + repeat animations don't work

2019-01-08 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: New => Incomplete

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

Title:
  3D slide transitions don't work at all or tear when played + repeat
  animations don't work

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.
  Animations don't repeat when checked "Repeat until next slide" or "Repeat 
until next click".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1797373/+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 1797373]

2019-01-08 Thread Xiscofauli

Thank you for reporting the bug.
Could you please try to reproduce it with a master build from 
http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 
'UNCONFIRMED' if the bug is still present in the master build

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

Title:
  3D slide transitions don't work at all or tear when played + repeat
  animations don't work

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.
  Animations don't repeat when checked "Repeat until next slide" or "Repeat 
until next click".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1797373/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations

The new version 1.52.5-0ubuntu18.04.1 seems to work well on bionic.

Strange I was unable to reproduce the original bug before installing it.
But after installing it, there is still no problem either.


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  [regression] Much higher CPU during some gnome-shell operations

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Fix Committed
Status in gjs source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  Since fixing bug 1672297 in release 18.04 we experience much higher (almost 
double) CPU usage during gnome-shell JavaScript operations, such as the icon 
spring animation [1]. Even just moving the mouse is a little more expensive now 
[2].
  [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  [2] https://gitlab.gnome.org/GNOME/mutter/issues/283

  [Test Case]

  Use 'top' to measure the CPU usage of the gnome-shell process while
  tapping Super+A repeatedly. It should be much lower with the fix than
  without.

  [Regression Potential]

  Low. This particular fix is tiny
  (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been
  released and used in a couple of upstream gjs versions already without
  issue.

  [Other Info]

  The fix is already released to 19.04 as part of gjs version 1.54.2-1.
  And already released to 18.10 as part of gjs version
  1.54.3-1~ubuntu18.10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1799686] Re: Enable v4l2 hardware accelerated video decode

More information about VP9 and other decoding in V4L2:
https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/extended-controls.html

I think that relates to Digital TV tuners only, and am not sure it
applies to machines that don't have any digital TV hardware attached.

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

Title:
  Enable v4l2 hardware accelerated video decode

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+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 1799686] Re: Enable v4l2 hardware accelerated video decode

Seems both statements are true :)

The above patches relate to parts of the Chromium source named V4L2. But
for the most efficient desktop video decoding you need to use VAAPI
(https://bugs.chromium.org/p/chromium/issues/detail?id=463440).

I'm not sure those two are related, or that the former can be used to
help desktop like the latter does. So the Bug Description is very
confused at the moment. To resolve that confusion please log a bug with
Chromium upstream requesting whatever you think is missing and we can
then rely on upstream's answer:

https://bugs.chromium.org/p/chromium/issues/list

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

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

Title:
  Enable v4l2 hardware accelerated video decode

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+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 1799686] Re: Enable v4l2 hardware accelerated video decode

V4L2 doesn't have anything to do with video decoding that I know of, but
maybe ARM is different...

Yes I think that should read "VAAPI", not "V4L2".

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

Title:
  Enable v4l2 hardware accelerated video decode

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+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 1811000] Re: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] Pulseaudio fails to detect card

Interestingly the same model laptop with the same Ubuntu release and the
same PulseAudio version is reported to partially work in bug 1788121.

I'm not sure "Pulseaudio fails to detect card" is the right description
here. What problems are you actually experiencing that make you think
PulseAudio has failed to detect the card?


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

Title:
  [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at d472 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  8 21:55:38 2019
  InstallationDate: Installed on 2018-10-23 (77 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Right
  Title: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SSU Ver. F.02
  dmi.board.name: 162B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 04.1E
  dmi.chassis.asset.tag: CNU14700DL
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SSUVer.F.02:bd07/26/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2560p
  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/1811000/+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 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

This looks odd: PulseAudio is not running, so of course you won't get
any sound:

!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - No

To try and fix that please add a line to /etc/pulse/daemon.conf:

  realtime-scheduling = no

and then reboot.

If that doesn't fix the problem then please also follow these
instructions to search for possible pulseaudio crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810022] Re: Totem does not play MOV file with x264 encoding

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

preethi,

Please run:

  lspci -k

and send us the output, so that we can see what GPUs (and drivers) you
are using.

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

Title:
  Totem does not play MOV file with x264 encoding

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device
  'default': No such file or directory

  (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver 
proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
  ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High 
Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, 
interlace-mode=(string)progressive, chroma-format=(string)4:2:0, 
bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder)
  ** Message: 14:48:03.811: PackageKit: xid = 18874384
  ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) 
decoder
  ** Message: 14:48:03.812: PackageKit: ignoring field named level
  ** Message: 14:48:03.812: PackageKit: ignoring field named profile
  ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode
  ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma
  ** Message: 14:48:03.812: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling 
StartServiceByName for org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.PackageKit exited with status 1
  ** Message: 14:48:03.864: No installation candidate for missing plugins found.

  
  The gstreamer1.0* packages are installed and ubuntu-restricted-extras. 

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  totem:
Installed: 3.26.0-0ubuntu6.1
Candidate: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+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 1810022] Re: Totem does not play MOV file with x264 encoding

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

Moving to bug 1810929.

** This bug has been marked a duplicate of bug 1810929
   totem crashed with SIGSEGV

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

Title:
  Totem does not play MOV file with x264 encoding

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device
  'default': No such file or directory

  (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver 
proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
  ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High 
Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, 
interlace-mode=(string)progressive, chroma-format=(string)4:2:0, 
bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder)
  ** Message: 14:48:03.811: PackageKit: xid = 18874384
  ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) 
decoder
  ** Message: 14:48:03.812: PackageKit: ignoring field named level
  ** Message: 14:48:03.812: PackageKit: ignoring field named profile
  ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode
  ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma
  ** Message: 14:48:03.812: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling 
StartServiceByName for org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.PackageKit exited with status 1
  ** Message: 14:48:03.864: No installation candidate for missing plugins found.

  
  The gstreamer1.0* packages are installed and ubuntu-restricted-extras. 

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  totem:
Installed: 3.26.0-0ubuntu6.1
Candidate: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+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 1810929] Re: totem crashed with SIGSEGV

I'm not yet convinced this is the same as bug 1730241.

The stack trace is different, and the above Xorg logs shows there is
Nvidia hardware:

[57.822] (II) NVIDIA(0): NVIDIA GPU GeForce 210 (GT218) at PCI:3:0:0 (GPU-0)
[57.822] (--) NVIDIA(0): Memory: 524288 kBytes

** This bug is no longer a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used [in 
__GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() 
from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() 
from _cogl_gpu_info_init() from _cogl_driver_update_features() from 
_cogl_winsys_context_init()]

** Summary changed:

- totem crashed with SIGSEGV
+ totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from 
_cogl_driver_update_features() from _cogl_winsys_context_init()

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

Title:
  totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()

Status in totem package in Ubuntu:
  New

Bug description:
  ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

  result of the  [Totem does not play MOV file with x264 encoding ]
  Bug # - 1810022

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 04:41:26 2019
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 154218
  InstallationDate: Installed on 2018-11-12 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 
IST. --
   -- No entries --
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcCmdline: totem DJI_0001.MOV
  ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810929/+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 1730241] Re: Apps segfault when NVidia driver is installed but not used

** Summary changed:

- Evolution segfaults when NVidia driver is installed but not used
+ Apps segfault when NVidia driver is installed but not used

** Summary changed:

- Apps segfault when NVidia driver is installed but not used
+ Evolution segfaults when NVidia driver is installed but not used [in 
__GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() 
from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() 
from _cogl_gpu_info_init() from _cogl_driver_update_features() from 
_cogl_winsys_context_init()]

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

Title:
  Evolution segfaults when NVidia driver is installed but not used [in
  __GI_strtoul_l_internal() from __GI___strtoul_l() from
  g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from
  check_mesa_driver_package() from _cogl_gpu_info_init() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()]

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+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 1809826] Re: Gnome Activites view on multiple desktops wrong applications

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

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

** This bug has been marked a duplicate of bug 1743736
   In overview, windows from all workspaces are shown for the second display 
(when using "Workspaces span displays")

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

Title:
  Gnome Activites view on multiple desktops wrong applications

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view
  on the second monitor only it shows the application windows for all
  2nd monitor workspaces together. On the primary monitor it only shows
  the applications that exist for that monitor on that workspace. I
  believe it should show on the 2nd display only the applications that
  exist for that display in the current work space. This is how it
  functioned on the previous version of Ubuntu I was using prior to
  install of Ubuntu 18.10.

  Thanks!

  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+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 1809885] Re: Gnome-shell onscreen keyboard performance issues

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

Title:
  Gnome-shell onscreen keyboard performance issues

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Default gnome-shell keyboard is unresponsive on low-end hw. It have a big 
typing lag (200-300 ms) and periodically misses touches (especially the 
spacebar).
  Have this issue on ASUS M80TA tablet and just-installed Ubuntu 18.10, minimal 
installation, english locale.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-27 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.20.0-042000-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809885/+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 1811008] Re: Xwayland crashed with SIGSEGV in dixGetPrivate() from dixLookupPrivate() from present_screen_priv() from present_wnmd_flip() from present_wnmd_execute() from prese

I couldn't find any existing reports of this crash. Although bug 1811024
and bug 1811025 look related.

** Summary changed:

- Xwayland crashed with SIGABRT ending session upon DP monitor switch-away 
+ Xwayland crashed with SIGSEGV in dixGetPrivate() from dixLookupPrivate() from 
present_screen_priv() from present_wnmd_flip() from present_wnmd_execute() from 
present_wnmd_event_notify() from xwl_present_events_notify() from 
xwl_present_timer_callback()

** Information type changed from Private to Public

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

Title:
  Xwayland crashed with SIGSEGV in dixGetPrivate() from
  dixLookupPrivate() from present_screen_priv() from present_wnmd_flip()
  from present_wnmd_execute() from present_wnmd_event_notify() from
  xwl_present_events_notify() from xwl_present_timer_callback()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have some daisy-chained DisplayPort monitors connected via a
  DisplayPort KVM switch. This crash occurs at the moment the switch is
  switched "away" from host 1 to another host. Upon switching back to
  host 1, the gnome-session & gui processes have exited and the login
  screen is displayed. Makes it difficult to get much work done.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xwayland 2:1.20.1-3ubuntu2.1
  Uname: Linux 4.20.0-042000-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  8 17:44:27 2019
  DistUpgraded: 2018-10-25 13:46:36,654 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064]
  InstallationDate: Installed on 2016-10-05 (825 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.20.0-042000-generic 
root=/dev/mapper/ubuntu--vg-root ro splash crashkernel=512M-:192M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-10-25 (75 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-404
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0:
  mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:58:28.409903
  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: Mon Nov  5 11:41:45 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.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.1-3ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811008/+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 1811024] [NEW] Xwayland crashed with SIGABRT in dixGetPrivate() from present_window_priv() from present_send_complete_notify() from present_vblank_notify() from present_wnmd_fl

2019-01-08 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/6d18e5ae44e375885a66a754cb0b86d1dd1d5eb3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: cosmic

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

Title:
  Xwayland crashed with SIGABRT in dixGetPrivate() from
  present_window_priv() from present_send_complete_notify() from
  present_vblank_notify() from present_wnmd_flip_notify()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/6d18e5ae44e375885a66a754cb0b86d1dd1d5eb3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811024/+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 1801110] Re: gnome-shell crashes ending session upon DP monitor switch-away

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

Thanks. Moving to bug 1811008...

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

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

Title:
  gnome-shell crashes ending session upon DP monitor switch-away

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a DisplayPort switching arrangement consisting of a 4way DP
  switch that switches 2, daisy-chained DP monitors.

  Many times, but not always, when switching the displays away from this
  host, gnome-shell crashes. Later, switching back, I'm presented with
  the gdm login screen, previous session is gone.

  journal trace.


  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.735610:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.828123:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.829899:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.844313:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:19 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142619.936305:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999619 s, l
  Oct 31 14:26:20 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142620.866151:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00119 s, la
  Oct 31 14:26:21 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142621.876094:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00083 s, la
  Oct 31 14:26:22 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142622.866910:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00015 s, la
  Oct 31 14:26:23 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142623.866649:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999805 s, l
  Oct 31 14:26:24 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142624.866857:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00075 s, la
  Oct 31 14:26:25 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142625.867939:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00054 s, la
  Oct 31 14:26:26 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142626.867620:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999784 s, l
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Backtrace:
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x561135c42c39]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fd818e74e1f]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 2: 
/usr/bin/Xwayland (present_extension_init+0xce6) [0x561135bab416]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 3: 
/usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x390) [0x561135aed380]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 4: 
/usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x533) [0x561135aed6f3]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 5: 
/usr/bin/Xwayland (TimerSet+0x180) [0x561135c3c4b0]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 6: 
/usr/bin/Xwayland (TimerSet+0x1f8) [0x561135c3c578]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 7: 
/usr/bin/Xwayland (WaitForSomething+0x277) [0x561135c3c657]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 8: 
/usr/bin/Xwayland (SendErrorToClient+0x10c) [0x561135c0c95c]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 9: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x561135c10b36]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 10: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fd818c9c09b]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 11: 
/usr/bin/Xwayland (_start+0x2a) [0x561135ae21ea]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Segmentation 
fault at address 0x0
  Oct 31 14:26:27

[Desktop-packages] [Bug 1811023] [NEW] /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2019-01-08 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: cosmic disco kylin-18.10

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

Title:
  /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384:
  dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811023/+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 1811025] Re: Xwayland crashed with SIGABRT in present_vblank_notify() from present_wnmd_flip_notify() from present_wnmd_event_notify() from xwl_present_sync_callback() from ffi

** Summary changed:

- 
/usr/bin/Xwayland:6:present_vblank_notify:present_wnmd_flip_notify:present_wnmd_event_notify:xwl_present_sync_callback:ffi_call_unix64
+ Xwayland crashed with SIGABRT in present_vblank_notify() from 
present_wnmd_flip_notify() from present_wnmd_event_notify() from 
xwl_present_sync_callback() from ffi_call_unix64()

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

Title:
  Xwayland crashed with SIGABRT in present_vblank_notify() from
  present_wnmd_flip_notify() from present_wnmd_event_notify() from
  xwl_present_sync_callback() from ffi_call_unix64()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/fd75a0028bbd6bf33c99b2401b4373222e38fdc4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811025/+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 1811025] [NEW] Xwayland crashed with SIGABRT in present_vblank_notify() from present_wnmd_flip_notify() from present_wnmd_event_notify() from xwl_present_sync_callback() from f

2019-01-08 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/fd75a0028bbd6bf33c99b2401b4373222e38fdc4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: cosmic

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

Title:
  Xwayland crashed with SIGABRT in present_vblank_notify() from
  present_wnmd_flip_notify() from present_wnmd_event_notify() from
  xwl_present_sync_callback() from ffi_call_unix64()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/fd75a0028bbd6bf33c99b2401b4373222e38fdc4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811025/+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 1811024] Re: Xwayland crashed with SIGABRT in dixGetPrivate() from present_window_priv() from present_send_complete_notify() from present_vblank_notify() from present_wnmd_flip

** Summary changed:

- 
/usr/bin/Xwayland:6:dixGetPrivate:present_window_priv:present_send_complete_notify:present_vblank_notify:present_wnmd_flip_notify
+ Xwayland crashed with SIGABRT in dixGetPrivate() from present_window_priv() 
from present_send_complete_notify() from present_vblank_notify() from 
present_wnmd_flip_notify()

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

Title:
  Xwayland crashed with SIGABRT in dixGetPrivate() from
  present_window_priv() from present_send_complete_notify() from
  present_vblank_notify() from present_wnmd_flip_notify()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.1-3ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/6d18e5ae44e375885a66a754cb0b86d1dd1d5eb3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811024/+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 1802569] Re: RM openssl1.0 from Ubuntu

2019-01-08 Thread Bug Watch Updater

** Changed in: radsecproxy (Debian)
   Status: Confirmed => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in cfengine2 package in Ubuntu:
  Confirmed
Status in ckermit package in Ubuntu:
  Confirmed
Status in conserver package in Ubuntu:
  Confirmed
Status in cqrlog package in Ubuntu:
  Confirmed
Status in freerdp package in Ubuntu:
  New
Status in libpam-ssh package in Ubuntu:
  New
Status in mailavenger package in Ubuntu:
  Confirmed
Status in moonshot-trust-router package in Ubuntu:
  Confirmed
Status in netkit-ftp-ssl package in Ubuntu:
  Confirmed
Status in netty-tcnative-1.1 package in Ubuntu:
  New
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in osslsigncode package in Ubuntu:
  New
Status in pam-ssh-agent-auth package in Ubuntu:
  New
Status in pidentd package in Ubuntu:
  New
Status in qpid-proton package in Ubuntu:
  New
Status in radsecproxy package in Ubuntu:
  New
Status in reconserver package in Ubuntu:
  Confirmed
Status in resiprocate package in Ubuntu:
  New
Status in ruby-eventmachine package in Ubuntu:
  New
Status in stunserver package in Ubuntu:
  New
Status in validns package in Ubuntu:
  New
Status in cfengine2 package in Debian:
  New
Status in ckermit package in Debian:
  New
Status in conserver package in Debian:
  New
Status in cqrlog package in Debian:
  New
Status in freerdp package in Debian:
  Fix Released
Status in libpam-ssh package in Debian:
  Fix Released
Status in mailavenger package in Debian:
  Fix Released
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in netty-tcnative-1.1 package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New
Status in osslsigncode package in Debian:
  Fix Released
Status in pam-ssh-agent-auth package in Debian:
  New
Status in pidentd package in Debian:
  New
Status in qpid-proton package in Debian:
  Fix Released
Status in radsecproxy package in Debian:
  Fix Released
Status in reconserver package in Debian:
  New
Status in resiprocate package in Debian:
  Confirmed
Status in ruby-eventmachine package in Debian:
  Fix Released
Status in stunserver package in Debian:
  Confirmed
Status in validns package in Debian:
  Confirmed

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2019-01-08 Thread Christopher Smith

Hey all, there is so much technical jargon here and on that github page.
I have an HP Pavilion so I'm trying to remove that iio sensor-proxy, but
I'm a bit confused. Where should I be looking on that github page for
directions to remove the iio sensor-proxy? Thanks!

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/iio-sensor-proxy/+bug/1726160/+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 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

2019-01-08 Thread Mark Preston

In the above post, I was in error about hplip causing the high CPU
usage. I have changed my Desktop management from Gnome to Unity. The hp
systray icon is back on the panel. I apologize for the CPU usage
mistake.

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1714659/+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 1811009] [NEW] Searching in GtkFileChooserDialog stops after first characters (broken behaviour)

2019-01-08 Thread Amr Ibrahim

Public bug reported:

Steps:
1. Open Gedit
2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
3. Press on the search button next to Open
4. Type what you are searching for

Expected behaviour:
Focus remains in the search input until I finish typing then results come up

What happens instead:
Searching stops after I enter the first characters because focus is lost from 
the search input

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgtk-3-0 3.22.30-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  8 23:42:23 2019
InstallationDate: Installed on 2018-11-29 (40 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Searching in GtkFileChooserDialog stops after first characters (broken
  behaviour)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  8 23:42:23 2019
  InstallationDate: Installed on 2018-11-29 (40 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1811009/+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 1801110] Re: gnome-shell crashes ending session upon DP monitor switch-away

2019-01-08 Thread John

...following step 3 in comment 1
...rewiring monitors...

Please see newly filed bug 1811008

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

Title:
  gnome-shell crashes ending session upon DP monitor switch-away

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a DisplayPort switching arrangement consisting of a 4way DP
  switch that switches 2, daisy-chained DP monitors.

  Many times, but not always, when switching the displays away from this
  host, gnome-shell crashes. Later, switching back, I'm presented with
  the gdm login screen, previous session is gone.

  journal trace.


  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.735610:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.828123:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.829899:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142617.844313:ERROR:gl_surface_presentation_helper.cc(237)] 
GetVSyncParametersIfAvailable() failed!
  Oct 31 14:26:19 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142619.936305:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999619 s, l
  Oct 31 14:26:20 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142620.866151:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00119 s, la
  Oct 31 14:26:21 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142621.876094:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00083 s, la
  Oct 31 14:26:22 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142622.866910:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00015 s, la
  Oct 31 14:26:23 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142623.866649:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999805 s, l
  Oct 31 14:26:24 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142624.866857:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00075 s, la
  Oct 31 14:26:25 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142625.867939:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=1.00054 s, la
  Oct 31 14:26:26 u24b6-skull org.gnome.Shell.desktop[16220]: 
[16887:16887:1031/142626.867620:ERROR:sync_control_vsync_provider.cc(141)] 
Calculated bogus refresh interval=0.999784 s, l
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Backtrace:
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x561135c42c39]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fd818e74e1f]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 2: 
/usr/bin/Xwayland (present_extension_init+0xce6) [0x561135bab416]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 3: 
/usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x390) [0x561135aed380]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 4: 
/usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x533) [0x561135aed6f3]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 5: 
/usr/bin/Xwayland (TimerSet+0x180) [0x561135c3c4b0]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 6: 
/usr/bin/Xwayland (TimerSet+0x1f8) [0x561135c3c578]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 7: 
/usr/bin/Xwayland (WaitForSomething+0x277) [0x561135c3c657]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 8: 
/usr/bin/Xwayland (SendErrorToClient+0x10c) [0x561135c0c95c]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 9: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x561135c10b36]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 10: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fd818c9c09b]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 11: 
/usr/bin/Xwayland (_start+0x2a) [0x561135ae21ea]
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Segmentation 
fault at address 0x0
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
  Oct 31 14:26:27 u24b6-skull

[Desktop-packages] [Bug 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference

Thanks for reporting the issue upstream!

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Horizontal scroll doesn't honor Natural Scrolling preference

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

Bug description:
  It appears that the horizontal scroll setting is locked to only one
  direction and does not honor the natural scrolling preference.

  This has been posted on askubuntu.com
  (https://askubuntu.com/questions/1029128/inverted-horizontal-
  scrolling-ubuntu-18-04), but hasn't been reported as a bug yet (as per
  my searches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+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 1810660] Re: vpn configuration requires to enter a gateway

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  vpn configuration requires to enter a gateway

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

Bug description:
  After upgrading to 18.04 I can no longer create a vpn with a static
  route unless a gateway is specified.

  Before (with 16.04) I could add 1 or more destination networks without
  a gateway for each. Once the VPN connection was established, all
  static routes defined would have a gateway the VPN device (e.g ppp0,
  tun0, etc), as below.

  192.168.xxx.0/24 is the local network
  10.0.xxx.0/24 are remote networks accessible through the VPN.

  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.xxx.254 0.0.0.0 UG20100  00 
enp0s25
  10.0.1.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.2.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.3.00.0.0.0 255.255.255.0   UH50 00 ppp0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810660/+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 1810660] Re: vpn configuration requires to enter a gateway

2019-01-08 Thread Efthymios

Yes, seems to be the same. Running nm-connection-editor instead allows
to save the configuration without a specific gateway.

Thanks

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

Title:
  vpn configuration requires to enter a gateway

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

Bug description:
  After upgrading to 18.04 I can no longer create a vpn with a static
  route unless a gateway is specified.

  Before (with 16.04) I could add 1 or more destination networks without
  a gateway for each. Once the VPN connection was established, all
  static routes defined would have a gateway the VPN device (e.g ppp0,
  tun0, etc), as below.

  192.168.xxx.0/24 is the local network
  10.0.xxx.0/24 are remote networks accessible through the VPN.

  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.xxx.254 0.0.0.0 UG20100  00 
enp0s25
  10.0.1.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.2.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.3.00.0.0.0 255.255.255.0   UH50 00 ppp0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810660/+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 1811000] [NEW] [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] Pulseaudio fails to detect card

2019-01-08 Thread corinne

Public bug reported:

00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at d472 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  8 21:55:38 2019
InstallationDate: Installed on 2018-10-23 (77 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Right
Title: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] 
Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SSU Ver. F.02
dmi.board.name: 162B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 04.1E
dmi.chassis.asset.tag: CNU14700DL
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SSUVer.F.02:bd07/26/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1E:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 2560p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at d472 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  8 21:55:38 2019
  InstallationDate: Installed on 2018-10-23 (77 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Right
  Title: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SSU Ver. F.02
  dmi.board.name: 162B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 04.1E

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

2019-01-08 Thread Mark Preston

I think that is error is now causing very high CPU usage. Typically my
CPU load averages are under 1. They usually range like thus: .5 to .8
for all time frames (1 min, 5 min, 15 min). Currently my avgs. are 3.00
to 4.00. These high loads started after HPLIP's "No systray" on daily
power up.

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1714659/+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 1809826] GsettingsChanges.txt

apport information

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

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

Title:
  Gnome Activites view on multiple desktops wrong applications

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view
  on the second monitor only it shows the application windows for all
  2nd monitor workspaces together. On the primary monitor it only shows
  the applications that exist for that monitor on that workspace. I
  believe it should show on the 2nd display only the applications that
  exist for that display in the current work space. This is how it
  functioned on the previous version of Ubuntu I was using prior to
  install of Ubuntu 18.10.

  Thanks!

  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+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 1809826] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Gnome Activites view on multiple desktops wrong applications

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view
  on the second monitor only it shows the application windows for all
  2nd monitor workspaces together. On the primary monitor it only shows
  the applications that exist for that monitor on that workspace. I
  believe it should show on the 2nd display only the applications that
  exist for that display in the current work space. This is how it
  functioned on the previous version of Ubuntu I was using prior to
  install of Ubuntu 18.10.

  Thanks!

  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations

Hello Daniel, or anyone else affected,

Accepted gjs into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.52.5-0ubuntu18.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gjs (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [regression] Much higher CPU during some gnome-shell operations

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Fix Committed
Status in gjs source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  Since fixing bug 1672297 in release 18.04 we experience much higher (almost 
double) CPU usage during gnome-shell JavaScript operations, such as the icon 
spring animation [1]. Even just moving the mouse is a little more expensive now 
[2].
  [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  [2] https://gitlab.gnome.org/GNOME/mutter/issues/283

  [Test Case]

  Use 'top' to measure the CPU usage of the gnome-shell process while
  tapping Super+A repeatedly. It should be much lower with the fix than
  without.

  [Regression Potential]

  Low. This particular fix is tiny
  (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been
  released and used in a couple of upstream gjs versions already without
  issue.

  [Other Info]

  The fix is already released to 19.04 as part of gjs version 1.54.2-1.
  And already released to 18.10 as part of gjs version
  1.54.3-1~ubuntu18.10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1809181] Re: SRU 1.52.5 to bionic

Hello Marco, or anyone else affected,

Accepted gjs into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.52.5-0ubuntu18.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gjs (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  SRU 1.52.5 to bionic

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  The fifth release in the 1.52 series.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  The "big-hammer patch" (memory leak fix) that this new point release
  fixes is already included in Ubuntu (bionic) for some time, while this
  new version includes a fix to reduce the CPU usage, while keeping the
  memory usage low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1809181/+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 1809826] Re: Gnome Activites view on multiple desktops wrong applications

The bug 1743736 seems to be the same issue from what I can tell from the
description. I ran the apport-collect. Please let me know if there's
anything else I can provide to help with this. Much 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/1809826

Title:
  Gnome Activites view on multiple desktops wrong applications

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view
  on the second monitor only it shows the application windows for all
  2nd monitor workspaces together. On the primary monitor it only shows
  the applications that exist for that monitor on that workspace. I
  believe it should show on the 2nd display only the applications that
  exist for that display in the current work space. This is how it
  functioned on the previous version of Ubuntu I was using prior to
  install of Ubuntu 18.10.

  Thanks!

  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+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 1809826] Re: Gnome Activites view on multiple desktops wrong applications

apport information

** Tags added: apport-collected

** Description changed:

  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view on
  the second monitor only it shows the application windows for all 2nd
  monitor workspaces together. On the primary monitor it only shows the
  applications that exist for that monitor on that workspace. I believe it
  should show on the 2nd display only the applications that exist for that
  display in the current work space. This is how it functioned on the
  previous version of Ubuntu I was using prior to install of Ubuntu 18.10.
  
  Thanks!
  
  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-19 (20 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Gnome Activites view on multiple desktops wrong applications

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view
  on the second monitor only it shows the application windows for all
  2nd monitor workspaces together. On the primary monitor it only shows
  the applications that exist for that monitor on that workspace. I
  believe it should show on the 2nd display only the applications that
  exist for that display in the current work space. This is how it
  functioned on the previous version of Ubuntu I was using prior to
  install of Ubuntu 18.10.

  Thanks!

  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-01-08 Thread Tim Richardson

I switched to KDE to have a look at it, by installing KDE Neon from the
PPAs. Otherwise the same environment. The slow suspend doesn't happen in
plasma, it suspends in five seconds, while still suspending properly
(including open VMWare virtual machines). So it's not simply Chrome, the
bug needs gnome as well.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

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

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 1810987] Re: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2019-01-08 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

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

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

Title:
  package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in ghostscript package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgs9 9.22~dfsg+1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  8 19:14:24 2019
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: ghostscript
  Title: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1810987/+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 1810861] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227734/+files/WifiSyslog.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227733/+files/UdevDb.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227732/+files/ProcModules.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227729/+files/Lsusb.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227731/+files/ProcInterrupts.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227725/+files/CRDA.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227728/+files/Lspci.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] Dependencies.txt

apport information

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] CurrentDmesg.txt

apport information

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

apport information

** Tags added: apport-collected cosmic

** Description changed:

- I use a logitech z200 that works fine, i use it with a usb type c
- adapter that came with my pixel 3, my speakers arent shown at all in the
- settings or make sound, its not the usb c adapter because it works fine
- on my windows dual boot and has worked at one point on ubuntu,
- regardless of the fact that ubuntu has never recognized my thunderbolt
- port, i use ubuntu 18.10 by the way when i use lsusb, one of the results
- is google inc., which is my headphone adapter, i can tell because when i
- unplug it it goes away, even when i plug it into the 3.5 mm headphone
- jack it doesn't work, i don't know if im forgetting something or not,
- this is the second time im typing this because i accidentally closed the
- first tab of this, whats interesting, is now that i go to alsamixer, and
- press f6 i see option 1.Headphone Adapter, i select it and set the
- volume all the way up and go to something that makes audio and nothing
- happens, then i unplug it and see if it disappears, surely enough it
- does
+ I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-10-21 (78 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp37s0   no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: pulseaudio 1:12.2-0ubuntu4
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-13-generic N/A
+  linux-backports-modules-4.18.0-13-generic  N/A
+  linux-firmware 1.175.1
+ RfKill:
+  
+ Tags:  cosmic
+ Uname: Linux 4.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P5.00
+ dmi.board.name: AB350 Gaming K4
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227724/+files/AlsaInfo.txt

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

[Desktop-packages] [Bug 1810987] Re: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2019-01-08 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in ghostscript package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgs9 9.22~dfsg+1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  8 19:14:24 2019
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: ghostscript
  Title: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1810987/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

Hello Jenka, or anyone else affected,

Accepted gnome-shell-extension-ubuntu-dock into cosmic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/63ubuntu1.18.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Desktop-packages] [Bug 1804742] Re: package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned err

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/1804742

Title:
  package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to
  install/upgrade: installed gnome-shell-common package post-
  installation script subprocess returned error exit status 2

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  dpkg: dependency problems prevent configuration of gnome-shell:
   gnome-shell depends on gnome-shell-common (= 3.28.3-0ubuntu0.18.04.3); 
however:
Package gnome-shell-common is not configured yet.

  dpkg: error processing package gnome-shell (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Setting up libpython3.6-dev:amd64 (3.6.7-1~18.04) 
...
  Setting up libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.4) ...
  Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.3) ...
  Setting up gir1.2-mutter-2:amd64 (3.28.3-2~ubuntu18.04.2) ...
  dpkg: dependency problems prevent configuration of update-manager:
   update-manager depends on policykit-1-gnome | polkit-kde-agent-1 | lxpolkit 
| lxqt-policykit | mate-polkit | polkit-1-auth-agent; however:
Package policykit-1-gnome is not installed.
Package polkit-kde-agent-1 is not installed.
Package lxpolkit is not installed.
Package lxqt-policykit is not installed.
Package mate-polkit is not installed.
Package polkit-1-auth-agent is not installed.
Package gnome-shell which provides polkit-1-auth-agent is not configured 
yet.

  dpkg: error processing package update-manager (--configure):
   dependency problems - leaving unconfigured
  Setting up python3-gdbm:amd64 (3.6.7-1~18.04) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Setting up packagekit-tools 
(1.1.9-1ubuntu2.18.04.4) ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-common 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 10:56:40 2018
  DisplayManager: gdm3
  ErrorMessage: installed gnome-shell-common package post-installation script 
subprocess returned error exit status 2
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-08-21 (93 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python3.6, Python 3.6.7, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: gnome-shell
  Title: package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to 
install/upgrade: installed gnome-shell-common package post-installation script 
subprocess returned error exit status 2
  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/1804742/+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 1810987] [NEW] package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2019-01-08 Thread Tomas Kubinec

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgs9 9.22~dfsg+1-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
Date: Tue Jan  8 19:14:24 2019
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.3
SourcePackage: ghostscript
Title: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in ghostscript package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgs9 9.22~dfsg+1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  8 19:14:24 2019
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: ghostscript
  Title: package libgs9 9.22~dfsg+1-0ubuntu1.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1810987/+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 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

This bug was fixed in the package network-manager - 1.12.6-0ubuntu3

---
network-manager (1.12.6-0ubuntu3) disco; urgency=medium

  * debian/tests/nm.py: Make assert_iface_down() not check the interface's
state. We call nmclient.deactivate_connection() to terminate connections
that the testsuite sets up, and according to upstream this is not
guaranteed to do anything in particular to the link state. It seems that
dnsmasq 2.80 somehow alters the previous assumption that it would be
'state DOWN', so the implementation detail we were checking previously no
longer holds. The testsuite does still check that the IPs are removed from
the interface, which is logically what we want anyway. (LP: #1805857)
  * debian/control: Fix Vcs-Git

 -- Iain Lane   Wed, 19 Dec 2018 13:12:58 +

** Changed in: network-manager (Ubuntu Disco)
   Status: Triaged => Fix Released

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Disco:
  New
Status in network-manager source package in Disco:
  Fix Released

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1805857/+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 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference

2019-01-08 Thread shine

I've reported this to the GNOME Gitlab - https://gitlab.gnome.org/GNOME
/gnome-control-center/issues/340.

Thank you for the re-direct Sebastien Bacher.

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

Title:
  Horizontal scroll doesn't honor Natural Scrolling preference

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

Bug description:
  It appears that the horizontal scroll setting is locked to only one
  direction and does not honor the natural scrolling preference.

  This has been posted on askubuntu.com
  (https://askubuntu.com/questions/1029128/inverted-horizontal-
  scrolling-ubuntu-18-04), but hasn't been reported as a bug yet (as per
  my searches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+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 1801540] Re: Microphone distorted sound on ALC892

2019-01-08 Thread Luca Mastromatteo

Seems to be the same problem as 
https://bugzilla.kernel.org/show_bug.cgi?id=195303
With ALC1220 codecs

The last comment was


 "I might have found the source of this problem at least for me. A while
ago I set my Pulseaudio sample rate to 44100 to reduce crackling in my
virtual machine audio but the sound card on my board runs at 48000.

What I did:
arecord --list-devices
arecord -f dat -r 6 -D hw:CARDIDHERE,DEVICEIDHERE -d 5 test.wav

arecord told me that it could not record of a rate of 6 and instead
got 48000. This means my card has a sample rate of 48000

So I ran:
arecord -f dat -r 48000 -D hw:1,0 -d 5 test.wav

And suddenly I had a clear recording! The only problem is I have changed
my sampling rate and alternate sample rate in /etc/pulse/daemon.conf
back to 48000 but it still seems to be defaulting to 44100 in all
programs.

If I run:
arecord -f cd -d 10 test-mic.wav
I observe it defaulting to 44100 and playing it back sounds awful again. Same 
with any other recording software, they are all still using 44100 for some 
reason which is causing the crackling."


This also applies to me, is there a temporary workaround for that I can
apply to ALSA or Pulseaudio?

** Bug watch added: Linux Kernel Bug Tracker #195303
   https://bugzilla.kernel.org/show_bug.cgi?id=195303

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1808796] Update Released

The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-settings-daemon FTBFS in cosmic-proposed due to circular
  relationship involving mutter

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

Bug description:
  [ Description ]

  Currently gnome-settings-daemon can't be built in cosmic-proposed for
  arm64 and armhf:

  The following packages have unmet dependencies:
   sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>= 
3.27.90) but it is not going to be installed

  analysing the situation with chdist shows:

  The following packages have unmet dependencies.
   mutter : Depends: gnome-settings-daemon but it is not going to be installed

  and then diving further:

  The following packages have unmet dependencies.
   gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed

  What has happened is that gnome-settings-daemon indirectly ends up
  Build-Depending on gnome-settings-daemon again:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d

  gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
  ${source:Version})". This in itself is correct, but when the arch:all
  gnome-settings-daemon-schemas is published before an arch-only build
  is picked up, we have skew that results in this failure. g-s-d-schemas
  3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the
  strict dependency means it is uninstallable.

  Presumably we'd gotten lucky up until now and never had a newer
  g-s-d-schemas published before all other arches at least started
  building.

  [ Fix ]

  Cut the arch:any part of the circular dependency. We make mutter
  Depend on gnome-settings-daemon-schemas instead, since it only needs
  the schemas and not running daemons. We still have a circular BD/D
  chain from g-s-d to itself, but now it looks like:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas

  ...importantly there are no strict version requirements any more, so
  this kind of skew isn't a problem. If mutter ever changes to have
  "Depends: gnome-settings-daemon-schemas (>= some-version)", this
  should also work - since the arch:all gnome-settings-daemon-schemas
  will be installable everywhere.

  [ QA ]

  I tested this in a bileto silo and it worked:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3567/+packages

  Once the fixed mutter is published, we should be able to retry the
  g-s-d builds.

  [ Regression potential ]

  mutter will no longer Depend on gnome-settings-daemon itself (the
  daemons). This might expose missing g-s-d dependencies from other
  packages. These could only be out-of-archive packages though:

  laney@raleigh> reverse-depends -r cosmic mutter
  Reverse-Depends
  ===
  * gnome-shell
  * vanilla-gnome-desktop

  and both of these depend on gnome-settings-daemon already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1808796/+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 1808796] Re: gnome-settings-daemon FTBFS in cosmic-proposed due to circular relationship involving mutter

This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.2

---
mutter (3.30.2-1~ubuntu18.10.2) cosmic; urgency=medium

  * Update gbp.conf and Vcs metadata for cosmic
  * control: Depend on g-s-d-schemas instead of g-s-d. We only need the
schemas. (LP: #1808796)

 -- Iain Lane   Mon, 17 Dec 2018 10:53:41 +

** Changed in: mutter (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-settings-daemon FTBFS in cosmic-proposed due to circular
  relationship involving mutter

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

Bug description:
  [ Description ]

  Currently gnome-settings-daemon can't be built in cosmic-proposed for
  arm64 and armhf:

  The following packages have unmet dependencies:
   sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>= 
3.27.90) but it is not going to be installed

  analysing the situation with chdist shows:

  The following packages have unmet dependencies.
   mutter : Depends: gnome-settings-daemon but it is not going to be installed

  and then diving further:

  The following packages have unmet dependencies.
   gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed

  What has happened is that gnome-settings-daemon indirectly ends up
  Build-Depending on gnome-settings-daemon again:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d

  gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
  ${source:Version})". This in itself is correct, but when the arch:all
  gnome-settings-daemon-schemas is published before an arch-only build
  is picked up, we have skew that results in this failure. g-s-d-schemas
  3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the
  strict dependency means it is uninstallable.

  Presumably we'd gotten lucky up until now and never had a newer
  g-s-d-schemas published before all other arches at least started
  building.

  [ Fix ]

  Cut the arch:any part of the circular dependency. We make mutter
  Depend on gnome-settings-daemon-schemas instead, since it only needs
  the schemas and not running daemons. We still have a circular BD/D
  chain from g-s-d to itself, but now it looks like:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas

  ...importantly there are no strict version requirements any more, so
  this kind of skew isn't a problem. If mutter ever changes to have
  "Depends: gnome-settings-daemon-schemas (>= some-version)", this
  should also work - since the arch:all gnome-settings-daemon-schemas
  will be installable everywhere.

  [ QA ]

  I tested this in a bileto silo and it worked:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3567/+packages

  Once the fixed mutter is published, we should be able to retry the
  g-s-d builds.

  [ Regression potential ]

  mutter will no longer Depend on gnome-settings-daemon itself (the
  daemons). This might expose missing g-s-d dependencies from other
  packages. These could only be out-of-archive packages though:

  laney@raleigh> reverse-depends -r cosmic mutter
  Reverse-Depends
  ===
  * gnome-shell
  * vanilla-gnome-desktop

  and both of these depend on gnome-settings-daemon already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1808796/+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 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

2019-01-08 Thread Andrea Azzarone

> I have this message each time i try to write a review for a snap
package

Are you on Bionic? Reviews should be disabled for snaps. How did you
manage to (try to) write a review for a snap?

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1808880/+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 1804744] Re: Restoring from new location does not find backup files

(seems also something worth SRUing to at least bionic)

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

Title:
  Restoring from new location does not find backup files

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

Bug description:
  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings 
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ethan-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ethan-laptop'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ethan-laptop'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ethan-laptop'
  org.gnome.DejaDup.Local folder '/media/ethan/porta_500gb/m1330'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ethan-laptop'
  org.gnome.DejaDup.Drive uuid '1919a422-d154-4e19-b551-f74b56cf1f0e'
  org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk 
drive'
  org.gnome.DejaDup.Drive folder 'm1330'
  org.gnome.DejaDup.Drive name 'porta_500gb'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ethan-laptop'
  org.gnome.DejaDup.GOA type 'google'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1804744/+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 1804744] Re: Restoring from new location does not find backup files

It was fixed in https://git.launchpad.net/deja-dup/commit/?id=96f3d9ed
and 38.2

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

Title:
  Restoring from new location does not find backup files

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

Bug description:
  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings 
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ethan-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ethan-laptop'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ethan-laptop'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ethan-laptop'
  org.gnome.DejaDup.Local folder '/media/ethan/porta_500gb/m1330'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ethan-laptop'
  org.gnome.DejaDup.Drive uuid '1919a422-d154-4e19-b551-f74b56cf1f0e'
  org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk 
drive'
  org.gnome.DejaDup.Drive folder 'm1330'
  org.gnome.DejaDup.Drive name 'porta_500gb'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ethan-laptop'
  org.gnome.DejaDup.GOA type 'google'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1804744/+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 1808576] Re: gnome-control-center segfaults when unit bolt.service is masked

The bug has been fixed upstream now

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  gnome-control-center segfaults when unit bolt.service is masked

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Fedora:
  Confirmed

Bug description:
  I don't have any Thunderbolt devices so I masked the unused the
  bolt.service. This causes problem with gnome-control-center.

  Steps to reproduce:

  1) launch gnome-control-center
  $ gnome-control-center

  2) navigate to Thunderbolt section
  go to Devices, then Thunderbolt and close gnome-control-center

  3) mask bold.service
  $ sudo systemctl stop bolt.service
  $ sudo systemctl mask bolt.service

  4) re-launch gnome-control-center
  $ gnome-control-center 

  (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: 
Could not create client: Error calling StartServiceByName for 
org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit 
bolt.service is masked.
  Segmentation fault (core dumped)

  Expected result: no segfault.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy gnome-control-center bolt
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.2
Candidate: 1:3.28.2-0ubuntu0.18.04.2
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  bolt:
Installed: 0.5-0ubuntu0.18.04.1
Candidate: 0.5-0ubuntu0.18.04.1
Version table:
   *** 0.5-0ubuntu0.18.04.1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 14 14:05:26 2018
  InstallationDate: Installed on 2018-07-15 (152 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
  ProcEnviron:
   LANG=en_CA.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1808576/+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 1734541] Re: encrypted home-directory is not unmounted on logout

2019-01-08 Thread Mikko Rantalainen

Still happens with Ubuntu LTS 18.04. I can provide additional info if
needed.

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

Title:
  encrypted home-directory is not unmounted on logout

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1734541/+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 1792511] Re: Unable to create a PPPoE connection in Ubuntu 18.04 LTS

Thank you for your bug report, that has been reported upstream also on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/216#note_345395

** Package changed: network-manager (Ubuntu) => gnome-control-center
(Ubuntu)

** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low

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

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

Title:
Unable to create a PPPoE connection in Ubuntu 18.04 LTS

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

Bug description:
My ISP provides PPPoE connection with username, password and service
name and binds my MAC Address. Since I have connected my router to
the WAN, the MAC Address of the router has been bound in their server
by them. Whereas the IP Address and Gateway are set to be
automatically obtained, and DNS addresses are manually given. My
Desktop has been connected to the router and the network is working
fine.

However, for the purpose of troubleshooting the network when it goes
down, I need to connect directly to the computer. Therefore, I need
to know how to configure a wired PPPoE connection directly in my
computer, which has only one NIC. The network settings GUI does not
allow setting up one.

Please guide me how to -

i) configure a PPPoE connection
ii) specify the username, password and service name, and
iii) clone my router's MAC address to my desktop

to be able to connect to the internet.The GUI provided in Ubuntu
18.04 Bionic Beaver (which is what I am using) does not provide for
creating a PPPoE connection. The GUI should also allow use of a
cloned MAC address for the PPPoE connection.

After referring to various community posts, I tried the following
command (though I am not quite conversant with Linux commands) :

nmcli connection add con-name "..." type pppoe username ... password
... service ... parent (iface name of the NIC) autoconnect no ifname
"*" save yes

The pppoe connection gets created but vanishes from the "Settings ->
Network" GUI under "Wired" category after some time and some times
gets listed under "Bluetooth" category (under Network Settings) before
vanishing.

Also, neither the command nor the GUI, allows me to specify a cloned
MAC address to the connection created using the above command.

Please get this issue addressed at the earliest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1792511/+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 1810660] Re: vpn static route

The issue seems similar to upstream https://gitlab.gnome.org/GNOME
/gnome-control-center/issues/138

** Package changed: network-manager (Ubuntu) => gnome-control-center
(Ubuntu)

** Summary changed:

- vpn static route
+ vpn configuration requires to enter a gateway

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

Title:
  vpn configuration requires to enter a gateway

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

Bug description:
  After upgrading to 18.04 I can no longer create a vpn with a static
  route unless a gateway is specified.

  Before (with 16.04) I could add 1 or more destination networks without
  a gateway for each. Once the VPN connection was established, all
  static routes defined would have a gateway the VPN device (e.g ppp0,
  tun0, etc), as below.

  192.168.xxx.0/24 is the local network
  10.0.xxx.0/24 are remote networks accessible through the VPN.

  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.xxx.254 0.0.0.0 UG20100  00 
enp0s25
  10.0.1.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.2.00.0.0.0 255.255.255.0   UH50 00 ppp0
  10.0.3.00.0.0.0 255.255.255.0   UH50 00 ppp0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810660/+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 1810705] Re: gnome-control-center disappeared when dock move to bottom

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

** This bug has been marked a duplicate of bug 1721637
   can't open  system settings(Ubuntu 17.10), icon is visible but  settings 
don't display

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

Title:
  gnome-control-center disappeared when dock move to bottom

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

Bug description:
  Package : gnome-control-center
  Package version : 1:3.28.2-0ubuntu0.18.04.2
  Ubuntu release 18.04
  Hardware : Processor sandybridge i3 2.2Ghz Memory 3GB Disk capacity 128GB

  I will move the dock position down. I open the gnome-control-center
  and select Dock and move the position down. It turns out that the
  settings window display disappears as minimized. I screenshot but it
  automatically captured on different workspace.

  I have reinstalled the package but it remains the same (window setting
  disappears)

  I also tried it from the live session mode and the same thing
  happened. But if I move the dock position to the right, the settings
  window still looks like it usually does.

  I've screen captured all of these experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810705/+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 1569877] Re: unity-control-center crashed with SIGSEGV in _cogl_context_get_gl_extensions()

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

** This bug has been marked a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used

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

Title:
  unity-control-center crashed with SIGSEGV in
  _cogl_context_get_gl_extensions()

Status in cogl package in Ubuntu:
  Confirmed

Bug description:
  Fresh install.  Nvidia Drivers and Chrome installed - nothing else.
  Unity control centre crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Apr 13 14:42:50 2016
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  ProcCmdline: unity-control-center
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: unity-control-center crashed with SIGSEGV in cogl_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1569877/+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 1565519] Re: unity-control-center crashed with SIGSEGV in _cogl_context_get_gl_extensions()

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

** This bug is no longer a duplicate of bug 1569877
   unity-control-center crashed with SIGSEGV in 
_cogl_context_get_gl_extensions()
** This bug has been marked a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used

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

Title:
  unity-control-center crashed with SIGSEGV in
  _cogl_context_get_gl_extensions()

Status in cogl package in Ubuntu:
  New

Bug description:
  Tried to launch the control-center app after a clean install of 16.04 beta 2.
  Application intermittently crashes with a SEGV during startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  3 18:57:30 2016
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-04-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: unity-control-center crashed with SIGSEGV in cogl_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1565519/+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 1574559] Re: /usr/bin/unity-control-center:11:_cogl_check_extension:_cogl_feature_check:update_base_winsys_features:_cogl_winsys_renderer_connect:cogl_renderer_connect

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

** This bug is no longer a duplicate of bug 1569877
   unity-control-center crashed with SIGSEGV in 
_cogl_context_get_gl_extensions()
** This bug has been marked a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used

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

Title:
  /usr/bin/unity-control-
  
center:11:_cogl_check_extension:_cogl_feature_check:update_base_winsys_features:_cogl_winsys_renderer_connect:cogl_renderer_connect

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-control-center.  This problem was most recently seen
  with version 15.04.0+16.04.20160413-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4e97da0d49ee665f0d6e0bc4888cd7e118a82226
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1574559/+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 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

@Michael, thx for testing, looks like the fix could be improved but if
the functional issue is resolved it should be good enough as a first
iteration

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Using an authentification certificate with a filename in its name is not 
possible

  * Test case
  - connect to a wpa wifi needing a certificate
  - name the certificate to include a space
  - try to use that said certificate

  it should be possible to use it

  * Regression potential
  the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not

  
  ***

  
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+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 1810022] Re: Totem does not play MOV file with x264 encoding

Upstream report is https://gitlab.gnome.org/GNOME/cogl/issues/1,
resolving the segfault wouldn't fix the problem that the xorg stack hits
errors though.

If the other bugs is hinting right, uninstalling the nvidia driver
should resolve the issue (why do you have those installed on an intel
system?)

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

Title:
  Totem does not play MOV file with x264 encoding

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device
  'default': No such file or directory

  (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver 
proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
  ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High 
Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, 
interlace-mode=(string)progressive, chroma-format=(string)4:2:0, 
bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder)
  ** Message: 14:48:03.811: PackageKit: xid = 18874384
  ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) 
decoder
  ** Message: 14:48:03.812: PackageKit: ignoring field named level
  ** Message: 14:48:03.812: PackageKit: ignoring field named profile
  ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode
  ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma
  ** Message: 14:48:03.812: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling 
StartServiceByName for org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.PackageKit exited with status 1
  ** Message: 14:48:03.864: No installation candidate for missing plugins found.

  
  The gstreamer1.0* packages are installed and ubuntu-restricted-extras. 

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  totem:
Installed: 3.26.0-0ubuntu6.1
Candidate: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+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 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

Hello Michael, or anyone else affected,

Accepted network-manager-applet into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/network-manager-applet/1.8.10-2ubuntu2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Using an authentification certificate with a filename in its name is not 
possible

  * Test case
  - connect to a wpa wifi needing a certificate
  - name the certificate to include a space
  - try to use that said certificate

  it should be possible to use it

  * Regression potential
  the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not

  
  ***

  
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+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 1810022] Re: Totem does not play MOV file with x264 encoding

The new report is a duplicate of bug #1730241 which seems to be cogl not
handling well the video drivers being in a buggy state

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

Title:
  Totem does not play MOV file with x264 encoding

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device
  'default': No such file or directory

  (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver 
proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
  ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High 
Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, 
interlace-mode=(string)progressive, chroma-format=(string)4:2:0, 
bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder)
  ** Message: 14:48:03.811: PackageKit: xid = 18874384
  ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) 
decoder
  ** Message: 14:48:03.812: PackageKit: ignoring field named level
  ** Message: 14:48:03.812: PackageKit: ignoring field named profile
  ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode
  ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma
  ** Message: 14:48:03.812: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling 
StartServiceByName for org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.PackageKit exited with status 1
  ** Message: 14:48:03.864: No installation candidate for missing plugins found.

  
  The gstreamer1.0* packages are installed and ubuntu-restricted-extras. 

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  totem:
Installed: 3.26.0-0ubuntu6.1
Candidate: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+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 1810929] Re: totem crashed with SIGSEGV

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

** This bug has been marked a duplicate of bug 1569877
   unity-control-center crashed with SIGSEGV in 
_cogl_context_get_gl_extensions()

** This bug is no longer a duplicate of bug 1569877
   unity-control-center crashed with SIGSEGV in 
_cogl_context_get_gl_extensions()
** This bug has been marked a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used

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

Title:
  totem crashed with SIGSEGV

Status in totem package in Ubuntu:
  New

Bug description:
  ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

  result of the  [Totem does not play MOV file with x264 encoding ]
  Bug # - 1810022

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 04:41:26 2019
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 154218
  InstallationDate: Installed on 2018-11-12 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 
IST. --
   -- No entries --
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcCmdline: totem DJI_0001.MOV
  ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

** Information type changed from Private to Public

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

Title:
  totem crashed with SIGSEGV

Status in totem package in Ubuntu:
  New

Bug description:
  ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

  result of the  [Totem does not play MOV file with x264 encoding ]
  Bug # - 1810022

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 04:41:26 2019
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 154218
  InstallationDate: Installed on 2018-11-12 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 
IST. --
   -- No entries --
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcCmdline: totem DJI_0001.MOV
  ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810929/+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 1754092] Re: firefox esr loading bookmark limbo

2019-01-08 Thread Galen Thurber

firefox 60.4.0 affected

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

Title:
  firefox esr loading bookmark limbo

Status in firefox package in Ubuntu:
  New

Bug description:
  on three computers I use Firefox ESR
  which all have the odd behaviour of not loading a bookmark.
  I'll select a bookmark ex: youtube.com and the tab icon will rotate but the 
page never loads & never times out. The limbo will happen with various 
bookmarks, cache has been cleared.
  To fix the limbo problem I'll hit enter once in the address bar.
  The limbo happens on 
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  and
  Ubuntu 14.04.5LTS
  and MX Linux 17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1754092/+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 1802225] Re: LightDM login doesn't display after screen lock

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

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

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

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

Title:
  LightDM login doesn't display after screen lock

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When locking the screen via the xfce menu or light-locker tool the
  screen sits at a blank/black screen. Moving the mouse or pressing a
  button on the keyboard does nothing. After searching I found I could
  just enter my password blindly and it would unlock the screen. Also
  going to a console tty and back to the graphical login would then show
  a login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  Uname: Linux 4.19.0-041900-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  8 13:29:14 2018
  InstallationDate: Installed on 2017-11-06 (366 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  LightdmConfig:
   [LightDM]
   logind-check-graphical=true
   display-setup-script=xrandr --output eDP-1 --primary
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1802225/+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 1809885] ProcCpuinfoMinimal.txt

2019-01-08 Thread sleeply4cat

apport information

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

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

Title:
  Gnome-shell onscreen keyboard performance issues

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Default gnome-shell keyboard is unresponsive on low-end hw. It have a big 
typing lag (200-300 ms) and periodically misses touches (especially the 
spacebar).
  Have this issue on ASUS M80TA tablet and just-installed Ubuntu 18.10, minimal 
installation, english locale.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-27 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.20.0-042000-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809885/+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 1809885] ProcEnviron.txt

2019-01-08 Thread sleeply4cat

apport information

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

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

Title:
  Gnome-shell onscreen keyboard performance issues

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Default gnome-shell keyboard is unresponsive on low-end hw. It have a big 
typing lag (200-300 ms) and periodically misses touches (especially the 
spacebar).
  Have this issue on ASUS M80TA tablet and just-installed Ubuntu 18.10, minimal 
installation, english locale.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-27 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.20.0-042000-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809885/+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 1809885] Re: Gnome-shell onscreen keyboard performance issues

2019-01-08 Thread sleeply4cat

apport information

** Tags added: apport-collected

** Description changed:

  Default gnome-shell keyboard is unresponsive on low-end hw. It have a big 
typing lag (200-300 ms) and periodically misses touches (especially the 
spacebar).
  Have this issue on ASUS M80TA tablet and just-installed Ubuntu 18.10, minimal 
installation, english locale.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ GsettingsChanges:
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ InstallationDate: Installed on 2018-12-27 (12 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
+ PackageArchitecture: amd64
+ Tags:  cosmic
+ Uname: Linux 4.20.0-042000-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Gnome-shell onscreen keyboard performance issues

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Default gnome-shell keyboard is unresponsive on low-end hw. It have a big 
typing lag (200-300 ms) and periodically misses touches (especially the 
spacebar).
  Have this issue on ASUS M80TA tablet and just-installed Ubuntu 18.10, minimal 
installation, english locale.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-27 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.20.0-042000-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809885/+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 1802569] Re: RM openssl1.0 from Ubuntu

2019-01-08 Thread Bug Watch Updater

** Changed in: qpid-proton (Debian)
   Status: New => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in cfengine2 package in Ubuntu:
  Confirmed
Status in ckermit package in Ubuntu:
  Confirmed
Status in conserver package in Ubuntu:
  Confirmed
Status in cqrlog package in Ubuntu:
  Confirmed
Status in freerdp package in Ubuntu:
  New
Status in libpam-ssh package in Ubuntu:
  New
Status in mailavenger package in Ubuntu:
  Confirmed
Status in moonshot-trust-router package in Ubuntu:
  Confirmed
Status in netkit-ftp-ssl package in Ubuntu:
  Confirmed
Status in netty-tcnative-1.1 package in Ubuntu:
  New
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in osslsigncode package in Ubuntu:
  New
Status in pam-ssh-agent-auth package in Ubuntu:
  New
Status in pidentd package in Ubuntu:
  New
Status in qpid-proton package in Ubuntu:
  New
Status in radsecproxy package in Ubuntu:
  New
Status in reconserver package in Ubuntu:
  Confirmed
Status in resiprocate package in Ubuntu:
  New
Status in ruby-eventmachine package in Ubuntu:
  New
Status in stunserver package in Ubuntu:
  New
Status in validns package in Ubuntu:
  New
Status in cfengine2 package in Debian:
  New
Status in ckermit package in Debian:
  New
Status in conserver package in Debian:
  New
Status in cqrlog package in Debian:
  New
Status in freerdp package in Debian:
  Fix Released
Status in libpam-ssh package in Debian:
  Fix Released
Status in mailavenger package in Debian:
  Fix Released
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in netty-tcnative-1.1 package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New
Status in osslsigncode package in Debian:
  Fix Released
Status in pam-ssh-agent-auth package in Debian:
  New
Status in pidentd package in Debian:
  New
Status in qpid-proton package in Debian:
  Fix Released
Status in radsecproxy package in Debian:
  Confirmed
Status in reconserver package in Debian:
  New
Status in resiprocate package in Debian:
  Confirmed
Status in ruby-eventmachine package in Debian:
  Fix Released
Status in stunserver package in Debian:
  Confirmed
Status in validns package in Debian:
  Confirmed

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

@Brian, description updated

** Changed in: network-manager-applet (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Description changed:

+ * Impact
+ Using an authentification certificate with a filename in its name is not 
possible
+ 
+ * Test case
+ - connect to a wpa wifi needing a certificate
+ - name the certificate to include a space
+ - try to use that said certificate
+ 
+ it should be possible to use it
+ 
+ * Regression potential
+ the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not
+ 
+ 
+ ***
+ 
+ 
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS
  
  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.
  
  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.
  
  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png
  
  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far as
  I can find no logs.
  
  If you move/rename the file, so there are no spaces in the filename, the
  problem is worked around.
  
  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.
  
  The problem was also not present on Ubuntu 16.04, and users who upgrade
  from 16.04 to 18.04 will find their connection keeps working. It is only
  when creating an entirely new connection (or after forgetting the
  connection and recreating it) that the problem dialog appears.

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Using an authentification certificate with a filename in its name is not 
possible

  * Test case
  - connect to a wpa wifi needing a certificate
  - name the certificate to include a space
  - try to use that said certificate

  it should be possible to use it

  * Regression potential
  the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not

  
  ***

  
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+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 1808796] Re: gnome-settings-daemon FTBFS in cosmic-proposed due to circular relationship involving mutter

2019-01-08 Thread Iain Lane

gnome-settings-daemon 3.30.1.2-1ubuntu3 built after being retried with
this mutter, and it's now in cosmic-updates.

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic

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

Title:
  gnome-settings-daemon FTBFS in cosmic-proposed due to circular
  relationship involving mutter

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [ Description ]

  Currently gnome-settings-daemon can't be built in cosmic-proposed for
  arm64 and armhf:

  The following packages have unmet dependencies:
   sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>= 
3.27.90) but it is not going to be installed

  analysing the situation with chdist shows:

  The following packages have unmet dependencies.
   mutter : Depends: gnome-settings-daemon but it is not going to be installed

  and then diving further:

  The following packages have unmet dependencies.
   gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed

  What has happened is that gnome-settings-daemon indirectly ends up
  Build-Depending on gnome-settings-daemon again:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d

  gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
  ${source:Version})". This in itself is correct, but when the arch:all
  gnome-settings-daemon-schemas is published before an arch-only build
  is picked up, we have skew that results in this failure. g-s-d-schemas
  3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the
  strict dependency means it is uninstallable.

  Presumably we'd gotten lucky up until now and never had a newer
  g-s-d-schemas published before all other arches at least started
  building.

  [ Fix ]

  Cut the arch:any part of the circular dependency. We make mutter
  Depend on gnome-settings-daemon-schemas instead, since it only needs
  the schemas and not running daemons. We still have a circular BD/D
  chain from g-s-d to itself, but now it looks like:

src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas

  ...importantly there are no strict version requirements any more, so
  this kind of skew isn't a problem. If mutter ever changes to have
  "Depends: gnome-settings-daemon-schemas (>= some-version)", this
  should also work - since the arch:all gnome-settings-daemon-schemas
  will be installable everywhere.

  [ QA ]

  I tested this in a bileto silo and it worked:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3567/+packages

  Once the fixed mutter is published, we should be able to retry the
  g-s-d builds.

  [ Regression potential ]

  mutter will no longer Depend on gnome-settings-daemon itself (the
  daemons). This might expose missing g-s-d dependencies from other
  packages. These could only be out-of-archive packages though:

  laney@raleigh> reverse-depends -r cosmic mutter
  Reverse-Depends
  ===
  * gnome-shell
  * vanilla-gnome-desktop

  and both of these depend on gnome-settings-daemon already.

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-01-08 Thread Olivier Tilloy

@Steve (sorry for the late reply): not sure how that relates to bug
#1726124, but in my limited understanding of the changes, they shouldn't
regress the split-DNS use case.

Some relevant pointers to better understand the fixes and their context:

 - https://bugzilla.gnome.org/show_bug.cgi?id=746422 (particularly
comments 8 and 26)

 - https://wiki.gnome.org/Projects/NetworkManager/DNS

 -
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  When using a VPN the DNS requests might still be sent to a DNS server
  outside the VPN when they should not

  * Test case

  Configure the system to send all the traffic to a VPN, do a name
  resolution, the request should not go to the public DNS server (to be
  checked by capturing the traffic by example with wireshark)

  
  * Regression potential

  The code change the handling of DNS servers when using a VPN, we
  should check that name resolution still work whne using a VPN in
  different configurations

  -

  
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1810941] [NEW] At boot, Zeigeist-datahub-vala triggers network mount

2019-01-08 Thread ALinuxUser

Public bug reported:

According to my system log, at boot time Zeigeist-datahub-vala triggers
mount requests for network shares. Given that some of these shares may
be offline, and given that the user and (to my knowledge) the system is
not yet trying to use these shares, this behaviour strikes me as
undesirable.

zeitgeist 1.0-0.1ubuntu1
Mint 19.1 x64 Cinnamon (based upon Ubuntu Bionic)

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

** Summary changed:

- Zeigeist-datahub-vala
+ At boot, Zeigeist-datahub-vala triggers network mount

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

Title:
  At boot, Zeigeist-datahub-vala triggers network mount

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  According to my system log, at boot time Zeigeist-datahub-vala
  triggers mount requests for network shares. Given that some of these
  shares may be offline, and given that the user and (to my knowledge)
  the system is not yet trying to use these shares, this behaviour
  strikes me as undesirable.

  zeitgeist 1.0-0.1ubuntu1
  Mint 19.1 x64 Cinnamon (based upon Ubuntu Bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1810941/+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 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

2019-01-08 Thread Ken VanDine

This will be fixed by the switch from Ubuntu Reviews to ODRS.

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1808880/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2019-01-08 Thread moreje

same behavior for me using Ubuntu 18.10

- Lockscreen shortcut (meta + L) requires two attempts to register.
- Activities button requires two attempts to register.
- Icons in dock resize by a few pixels when you put your cursor over them.

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  In Progress
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2019-01-08 Thread James M Knock

Sorry, this is so old that I've forgotten what it was about and the
circumstances. Also, I never understood the issues. I have since upgraded
to 18.04 and then to 18.04.1. I've also gotten out of the habit of
reporting such things. I will start reporting them again.
Jim

On Mon, Jan 7, 2019 at 8:55 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> James,
>
> I think this bug is fixed, and we just have too many spurious bug links
> pointing here due to similar stack traces. If you can share a link to
> one of your recent crash reports it would be most helpful.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1765886).
> https://bugs.launchpad.net/bugs/1748450
>
> Title:
>   gnome-shell crashed with SIGTRAP in _g_log_abort() from
>   g_log_default_handler() from default_log_handler(message="Connection
>   to xwayland lost") from g_logv() from g_log() from 
>
> Status in gnome-shell package in Ubuntu:
>   Invalid
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Bionic:
>   Invalid
> Status in mutter source package in Bionic:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   * Xwayland is failing frequently (not crashing), which triggers a
>   crash in gnome-shell because gnome-shell doesn't know how to survive
>   after Xwayland has reset itself.
>
>   * The frequent gnome-shell crashes create frequent problem reports and
>   annoying dialogs for users, after they log in to an apparently working
>   gnome-shell.
>
>   * This affects Xorg sessions too, because the gdm login screen itself
>   is a Wayland session. And Xorg users will see the problem dialog after
>   they have logged into a Xorg session.
>
>   * The fix simply converts the crash into a silent exit (as decided by
>   Gnome upstream). This avoids the mountain of crash reports and
>   annoying error dialogs at least. It does not fix the root causes that
>   remain in Xwayland, but this is considered acceptable because there
>   really isn't a bug in gnome-shell here other than it doesn't know how
>   to survive without a connection to Xwayland.
>
>   * For users of Xorg sessions, like bionic default, this is a full fix
>   as Xorg users will never get an Xwayland instance after logging in.
>   And hence the Xwayland bugs are irrelevant.
>
>   [Test Case]
>
>   * Just install bionic, use it lightly and reboot a few times.
>
>   * Observe crash files are left in /var/crash and problem report
>   dialogs after logging in.
>
>   [Regression Potential]
>
>   Medium. The fix does not really change the structure of the existing
>   error handling, only changes it from a core dump into a silent exit.
>   For Xorg users this should be invisible as the affected login screen
>   restarts automatically.
>
>   [Other Info]
>
>   This is a whole class of gnome-shell crash which includes bug 1505409,
> bug 1748450 and bug 1556601. All three should be considered the same crash
> for the sake of this SRU. Just don't mark them as duplicates of each other
>   because they are all still collecting duplicates of their own.
>
>   -
>
>   *** This is a duplicate of bug 1505409, but is being kept separate so
>   as to automatically collect duplicate reports since the stacktrace
>   signature has changed recently. Any resolution and discussion should
>   occur in bug 1505409. ***
>
>   See also:
>
> https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.26.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>   Uname: Linux 4.13.0-33-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: GNOME-Greeter:GNOME
>   Date: Thu Feb  8 23:50:23 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2016-03-21 (690 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160307)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/false
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5
>   UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>   UserGroups:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

[Desktop-packages] [Bug 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

2019-01-08 Thread Ken VanDine

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

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1808880/+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 1745990] Re: nautilus don't show all items in context menu "new document" and "scripts"

2019-01-08 Thread Paul White

** Tags removed: nautilus
** Tags added: bionic

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

Title:
  nautilus don't show all items in context menu "new document" and
  "scripts"

Status in nautilus package in Ubuntu:
  New

Bug description:
  ubuntu 17.10, nautilus 3.26.0

  action:
  - add many files (example 50) in folder ~/Templates (from terminal: for i in 
{1..50};do touch ~/Templates/file$i.txt; done)
  - in nautilus, right click in a folder (in empty space) and choose "New 
Document"
  - appear a list of the files in "Templates", but only the first 30, no way to 
view other files

  the same behavior for the list of nautilus script (right click >
  scripts), for the files copied in ~/.local/share/nautilus/scripts

  the problem for me is mainly for the scripts, I use many; I know that
  you can organize in folders, but 30 files are still few.

  in ubuntu-gnome 16.04/ nautilus 3.12.2 appear a list of the files in
  "Templates", with two arrows at top and bottom of the list for scroll
  the list

  tested in ubuntu 17.10, also in live usb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1745990/+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 1745990] Re: nautilus don't show all items in context menu "new document" and "scripts"

2019-01-08 Thread nukkio

same in Ubuntu 18.04.1 LTS

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

Title:
  nautilus don't show all items in context menu "new document" and
  "scripts"

Status in nautilus package in Ubuntu:
  New

Bug description:
  ubuntu 17.10, nautilus 3.26.0

  action:
  - add many files (example 50) in folder ~/Templates (from terminal: for i in 
{1..50};do touch ~/Templates/file$i.txt; done)
  - in nautilus, right click in a folder (in empty space) and choose "New 
Document"
  - appear a list of the files in "Templates", but only the first 30, no way to 
view other files

  the same behavior for the list of nautilus script (right click >
  scripts), for the files copied in ~/.local/share/nautilus/scripts

  the problem for me is mainly for the scripts, I use many; I know that
  you can organize in folders, but 30 files are still few.

  in ubuntu-gnome 16.04/ nautilus 3.12.2 appear a list of the files in
  "Templates", with two arrows at top and bottom of the list for scroll
  the list

  tested in ubuntu 17.10, also in live usb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1745990/+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 1810022] Re: Totem does not play MOV file with x264 encoding

2019-01-08 Thread preethi

The newly created private bug with crash information is

 #1810929 totem crashed with SIGSEGV

In spite of removing gstreamer1.0-vaapi, totem failed with the last error.
And yes - mpv plays the video and totem does not.

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

Title:
  Totem does not play MOV file with x264 encoding

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device
  'default': No such file or directory

  (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver 
proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
  ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High 
Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, 
interlace-mode=(string)progressive, chroma-format=(string)4:2:0, 
bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder)
  ** Message: 14:48:03.811: PackageKit: xid = 18874384
  ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) 
decoder
  ** Message: 14:48:03.812: PackageKit: ignoring field named level
  ** Message: 14:48:03.812: PackageKit: ignoring field named profile
  ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode
  ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma
  ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma
  ** Message: 14:48:03.812: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling 
StartServiceByName for org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.PackageKit exited with status 1
  ** Message: 14:48:03.864: No installation candidate for missing plugins found.

  
  The gstreamer1.0* packages are installed and ubuntu-restricted-extras. 

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  totem:
Installed: 3.26.0-0ubuntu6.1
Candidate: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+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 1803831] Re: Can't login to Ubuntu and unity desktop, screen loops up

It sounds like everything that uses Xorg is broken.

Are you saying that "Ubuntu on Wayland" still works?

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

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

** Changed in: mutter (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/1803831

Title:
  Can't login to Ubuntu and  unity desktop,screen loops up

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello,another problem has occurred...

  Can't login in to Ubuntu and Unity desktop with gdm3 except Ubuntu
  Wayland desktop environment..

  Whenever I am trying to login in to Ubuntu and Unity desktop, the
  login screen accepts password but it suddenly loops up..

  I have reinstall Ubuntu and unity desktop and reconfigured the gdm3,but no joy
  Lightdm is not working also..

  Please help me, thanks
  My version is Ubuntu 18.04.1LTS


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803831/+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 1803831] Re: Can't login to Ubuntu and unity desktop, screen loops up

Please also attach your /var/log/Xorg*.log files

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

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

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1803831

Title:
  Can't login to Ubuntu and  unity desktop,screen loops up

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello,another problem has occurred...

  Can't login in to Ubuntu and Unity desktop with gdm3 except Ubuntu
  Wayland desktop environment..

  Whenever I am trying to login in to Ubuntu and Unity desktop, the
  login screen accepts password but it suddenly loops up..

  I have reinstall Ubuntu and unity desktop and reconfigured the gdm3,but no joy
  Lightdm is not working also..

  Please help me, thanks
  My version is Ubuntu 18.04.1LTS


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803831/+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 1803831] Re: Can't login to Ubuntu and unity desktop, screen loops up

And do you find any crash files in /var/crash? If so then please run:

  ubuntu-bug /var/crash/YOURFILE.crash

and tell us the resulting bug ID(s).

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

Title:
  Can't login to Ubuntu and  unity desktop,screen loops up

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello,another problem has occurred...

  Can't login in to Ubuntu and Unity desktop with gdm3 except Ubuntu
  Wayland desktop environment..

  Whenever I am trying to login in to Ubuntu and Unity desktop, the
  login screen accepts password but it suddenly loops up..

  I have reinstall Ubuntu and unity desktop and reconfigured the gdm3,but no joy
  Lightdm is not working also..

  Please help me, thanks
  My version is Ubuntu 18.04.1LTS


  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: mutter
  PackageArchitecture: amd64
  Tags: bionic third-party-packages
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (61 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-05T20:33:54.035476

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803831/+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 1808233] Re: Update gtk to 3.24.2