date:20190107

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

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

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

Title:
  Enable v4l2 hardware accelerated video decode

Status in chromium-browser package in Ubuntu:
  Confirmed

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 1810022] Re: Totem does not play MOV file with x264 encoding

And I don't mean to imply Seb's advice was bad. It was very good advice.
We still need to debug the crash...

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

Also since you get this after following Seb's advice:

  totem 1.MOV 
  double free or corruption (!prev)
  Aborted (core dumped)

we next need to get some information about that crash. Please follow
these instructions to find the crash details and send them to us:

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

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

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

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

-- 
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 1810728] Re: cups error - internal server error when adding a printer

2019-01-07 Thread asimsalam

Here is the content of /var/log/cups/error_log:

E [06/Jan/2019:21:05:26 -0800] [cups-deviced] PID 15777 (gutenprint52+usb) 
stopped with status 1!
E [06/Jan/2019:21:05:44 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats. 
E [06/Jan/2019:21:06:12 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:06:12 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:12 -0800] [Client 75] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:06:12 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:06:12 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:12 -0800] [Client 78] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:06:26 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:06:26 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:26 -0800] [Client 83] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:06:26 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:06:26 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:26 -0800] [Client 86] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:06:42 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats. 
E [06/Jan/2019:21:06:57 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:06:57 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:57 -0800] [Client 92] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:06:57 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats. 
E [06/Jan/2019:21:06:57 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:06:57 -0800] [Client 95] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/Canon-MG6320) from localhost
E [06/Jan/2019:21:55:53 -0800] [cups-deviced] PID 17639 (gutenprint52+usb) 
stopped with status 1!
E [06/Jan/2019:21:56:58 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:57:49 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:57:49 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:57:49 -0800] [Client 144] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/MG6320) from localhost
E [06/Jan/2019:21:57:50 -0800] [CGI] Unable to create PPD file: Printer does 
not support required IPP attributes or document formats.
E [06/Jan/2019:21:57:50 -0800] copy_model: empty PPD file
E [06/Jan/2019:21:57:50 -0800] [Client 147] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://localhost/printers/MG6320) from localhost
E [06/Jan/2019:22:05:13 -0800] [Job 2] The printer configuration is incorrect 
or the printer no longer exists.


** Tags added: cups

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

Title:
  cups error - internal server error when adding a printer

Status in cups package in Ubuntu:
  New

Bug description:
  Where
  -
  This is happening on a fresh Linux Mint Tessa whose upstream is bionic
   cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

  What
  
  The upstream package is provided by the upstream bionic
  sudo apt policy cups
  cups:
Installed: 2.2.7-1ubuntu2.2
Candidate: 2.2.7-1ubuntu2.2
Version table:
   *** 2.2.7-1ubuntu2.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Problem Synopsis
  
  I have problem(s) printing with adding or printing to both my printers, one 
Dell and the other a Canon.

  The Dell E525 was added automatically but when printing to it the queue 
reports there was a problem with printing

[Desktop-packages] [Bug 763868] Re: totem-video-thumbnailer assert failure: * glibc detected * /usr/bin/totem-video-thumbnailer: double free or corruption (!prev): 0xb0f0d570 ***

Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

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

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


** Information type changed from Private to Public

** Changed in: totem (Ubuntu)
   Status: New => Won't Fix

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

Title:
  totem-video-thumbnailer assert failure: *** glibc detected ***
  /usr/bin/totem-video-thumbnailer: double free or corruption (!prev):
  0xb0f0d570 ***

Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: totem

  Occurred while browsing through home folder under normal conditions.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: totem 2.32.0-0ubuntu10
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  AssertionMessage: *** glibc detected *** /usr/bin/totem-video-thumbnailer: 
double free or corruption (!prev): 0xb0f0d570 ***
  Date: Sun Apr 17 14:37:41 2011
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110329.1)
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 
file:///home/username/homeLink/STL.rm /tmp/.gnome_desktop_thumbnail.HRXOTV
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
  Title: totem-video-thumbnailer assert failure: *** glibc detected *** 
/usr/bin/totem-video-thumbnailer: double free or corruption (!prev): 0xb0f0d570 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/763868/+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

Also possibly related, but unlikely, is bug 1770725.

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

Thanks. It appears you have an Nvidia graphics driver installed, so that
prevents hardware-accelerated video decoding via VAAPI from working. :(

It looks like mpv did work, is that correct? If so then to get Totem
working please try this:

  sudo apt remove gstreamer1.0-vaapi:amd64

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

Re: [Desktop-packages] [Bug 1810022] Re: Totem does not play MOV file with x264 encoding

2019-01-07 Thread preethi

Also, the i965-va-driver is installed in Ubuntu.


Preethi R


On Tue, 8 Jan 2019 at 09:56, Preethi Rajasekaran 
wrote:

> Hi Sebastien and Daniel,
>
> PFA the output of the commands you requested.
>
> Regards,
> Preethi R
>
>
> On Tue, 8 Jan 2019 at 09:00, Daniel van Vugt <
> daniel.van.v...@canonical.com> wrote:
>
>> It appears you have a Sandy Bridge CPU and the required packages
>> installed for hardware video decoding
>> (
>> https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding
>> ).
>> So that should work. Maybe Seb has a point...
>>
>> Can you please also:
>>
>> 1. Run 'vainfo' and send us the output.
>>
>> 2. Try playing the video with 'mpv' and send us the output that 'mpv'
>> prints to the terminal when playing the video.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> 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
>>
>

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

Re: [Desktop-packages] [Bug 1810022] Re: Totem does not play MOV file with x264 encoding

2019-01-07 Thread preethi

Hi Sebastien and Daniel,

PFA the output of the commands you requested.

Regards,
Preethi R


On Tue, 8 Jan 2019 at 09:00, Daniel van Vugt 
wrote:

> It appears you have a Sandy Bridge CPU and the required packages
> installed for hardware video decoding
> (
> https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding
> ).
> So that should work. Maybe Seb has a point...
>
> Can you please also:
>
> 1. Run 'vainfo' and send us the output.
>
> 2. Try playing the video with 'mpv' and send us the output that 'mpv'
> prints to the terminal when playing the video.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>


** Attachment added: "output.txt"
   https://bugs.launchpad.net/bugs/1810022/+attachment/5227529/+files/output.txt

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

[Desktop-packages] [Bug 1802109] Re: cheese

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

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

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

Title:
  cheese

Status in cheese package in Ubuntu:
  Expired

Bug description:
   do not work in ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Nov  7 14:56:22 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:1094]
   NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0df7] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GF108M [GeForce GT 
520M] [1462:1094]
  InstallationDate: Installed on 2016-02-08 (1002 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: wortmann MS-1754
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=e21ffc21-d27c-4706-83fa-f2637d3d05cb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1754IMT.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1754
  dmi.board.vendor: Wortmann AG
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MS-1754
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1754IMT.10D:bd03/03/2011:svnwortmann:pnMS-1754:pvrREV1.0:rvnWortmannAG:rnMS-1754:rvrREV1.0:cvnMS-1754:ct10:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-1754
  dmi.product.version: REV:1.0
  dmi.sys.vendor: wortmann
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  7 09:28:02 2018
  xserver.configfile: default
  xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1802109/+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 1802349] Re: video is not playing in the default player and ear phone sound is not working

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

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

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

Title:
  video is not playing in the default player and ear phone sound is not
  working

Status in totem package in Ubuntu:
  Expired

Bug description:
  the video is not playing in the default video player and if I plug my
  earphone, the sound is not coming

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:57:31 2018
  InstallationDate: Installed on 2018-05-21 (170 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1802349/+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 1802243] Re: ubuntu 18.10 boots to black screen with blinking cursor

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

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

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

Title:
  ubuntu 18.10 boots to black screen with blinking cursor

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Software update center prompted me to reboot pc after installing
  updates.. After rebooting, it just shows a black screen with a
  blinking cursor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802243/+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 1810808] Re: blocchi continui pagine

Can you explain in more detail what you were doing when the machine
stops responding?

Next time it happens, please reboot, log in again and run:

  journalctl -b-1 > prevboot.txt

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


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

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

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

Title:
  blocchi continui pagine

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  aprendo le pagine il computer va in blocco e non risponde piu ai
  comandi

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jan  7 17:27:27 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
  InstallationDate: Installed on 2016-10-10 (819 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09CI.M060.20100401.JIP
  dmi.board.name: R519/R719
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09CI.M060.20100401.JIP:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R519/R719
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Oct  4 11:40:09 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1

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

Please run this command to send us more information about the system:

  apport-collect 1810861

** Summary changed:

- Speakers dont show or make audio
+ USB type C audio adapter (from a Pixel 3) doesn't produce any sound

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/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

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 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

** Tags removed: rls-dd-incoming
** Tags added: disco

-- 
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 network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Disco:
  Triaged

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/network-manager/+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 1810097] Re: HDMI is not recognized

Thanks. This means the kernel can't detect anything plugged into HDMI:

/sys/class/drm/card0-HDMI-A-1/enabled:disabled

So if not a kernel bug then most likely the cable isn't plugged in
properly, or the cable needs replacing. Please try a different HDMI
cable.

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

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

Title:
  HDMI is not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8159.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  with friendly greetings from Germany
  Heinz Köhler

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Dec 30 17:27:38 2018
  DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2014-12-09 (1482 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97-HD3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 21 14:19:34 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

It appears you have a Sandy Bridge CPU and the required packages
installed for hardware video decoding
(https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding).
So that should work. Maybe Seb has a point...

Can you please also:

1. Run 'vainfo' and send us the output.

2. Try playing the video with 'mpv' and send us the output that 'mpv'
prints to the terminal when playing the video.

-- 
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 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

2019-01-07 Thread Michael Terry

I'll take this bug as the first part. That's just been fixed in master.

The second part... I think we already have another bug for that.

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Changed in: deja-dup
   Status: New => Fix Committed

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

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

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

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1371613/+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 1809692] Re: distorted lines when using google chrome browser

Thanks. That's either a bug in the web browser, graphics driver, or even
in the web page.

I would first assume it's a bug in the web browser, but unfortunately
Google Chrome is not part of Ubuntu so we can't handle that here. So to
help us reassign this bug without closing it, can you please confirm the
same bug exists in chromium-browser?


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

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

Title:
  distorted lines when using google chrome browser

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I get dynamically changing distorted lines when using google chrome
  browser, I suppose it is due to my graphics card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 25 04:18:51 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07d0]
  InstallationDate: Installed on 2018-04-12 (256 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0c45:6717 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5480
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed 
root=UUID=72a3879f-b71f-40a0-b09b-ceb983af1dbf ro acpi_rev_override quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0D0XXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0D0XXK:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.name: Latitude 5480
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Dec 24 22:28:33 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1368 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809692/+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 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

2019-01-07 Thread Bug Watch Updater

** Changed in: libreoffice-dictionaries (Debian)
   Status: Won't Fix => Fix Released

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  Won't Fix
Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix
Status in scowl package in Ubuntu:
  Fix Released
Status in hunspell-en-us package in Debian:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Fix Released
Status in scowl package in Debian:
  Fix Released

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+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 1809517] Re: OS freezes after screen turns off and I return to account

I did interpret "I have disabled Ubuntu from requiring my password after
the screen turns off" as automatic login/no password. Maybe that's
incorrect.

So a few questions:

1. Does your login have a password and/or is it configured for automatic
login?

2. Is the dock ("taskbar") visible on the "landing page"?

3. Does re-locking (Super+L) and re-unlocking the system get around the
problem?

4. Please run 'apport-collect 1809517' to send us more information about
the system.

** This bug is no longer a duplicate of bug 1740792
   Automatic login still requires user password after suspend/hibernate

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

** Tags added: cosmic

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

Title:
  OS freezes after screen turns off and I return to account

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded to the newest 18.10 I have disabled Ubuntu from
  requiring my password after the screen turns off due to inactivity but
  I'm still taken to the landing page as if I needed to unlock my
  computer. After sliding up or hitting enter the screen stays purple
  with the taskbar visible. I can click the application shortcuts on the
  taskbar but nothing happens afterwards.It doesn't happen every time,
  only once out of every 5 to 10 times.

  I'm using a Dell Inspiron 5559 64bit, graphics card is Intel HD
  Graphics 520 (Skylake GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809517/+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 1771031] Re: Please remove libgnome from Ubuntu

** No longer affects: gnome-translate (Ubuntu)

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

** Description changed:

  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.
  
  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030
- 
- The libgnome removal in turn blocks these other removals:
- gnome-vfs LP: #1771035
- libgnome-keyring LP: #1771036

** Also affects: libgnome-keyring (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Please remove libgnome from Ubuntu
+ Please remove libgnome and friends from Ubuntu

** Description changed:

  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.
  
+ resapplet and winefish are unmaintained and aren't in Debian.
+ 
+ linsmith is in Debian and will be either ported to gtk3 or removed
+ eventually, but I don't think Ubuntu needs to wait for that.
+ 
  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnome-keyring package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  New
Status in linsmith package in Ubuntu:
  New
Status in orbit2 package in Ubuntu:
  New
Status in resapplet package in Ubuntu:
  New
Status in winefish package in Ubuntu:
  New

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771031/+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 1771036] Re: Please remove libgnome-keyring from Ubuntu

** Changed in: libgnome-keyring (Ubuntu)
   Status: New => Invalid

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

Title:
  Please remove libgnome-keyring from Ubuntu

Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in mysql-workbench package in Ubuntu:
  Invalid

Bug description:
  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same.
  Users who are hurt by these removals can keep using Ubuntu 18.04 LTS
  for a few years.

  This bug depends on the libgnome removal LP: #1771031

  ukui-power-manager is a blocker LP: #1767165 (but mate-power-manager
  was done)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1771036/+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 1771035] Re: Please remove gnome-vfs from Ubuntu

** No longer affects: gnome-raw-thumbnailer (Ubuntu)

** Changed in: gnome-vfs (Ubuntu)
   Status: New => Invalid

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

Title:
  Please remove gnome-vfs from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid

Bug description:
  gnome-vfs has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same. If
  we do it now, maybe some projects will do the needed porting work away
  from libgnome (porting to gtk3 is probably needed) in time for Ubuntu
  20.04 LTS or Debian 10. Users who are hurt by these removals can keep
  using Ubuntu 18.04 LTS for a few years.

  This bug depends on the libgnome removal LP: #1771031

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771035/+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 1795342] Re: High Power Consumption

Did you confirm the power usage is still too high before sending
allprocs.txt?

Even that second file doesn't seem to show any long term execution. So
maybe forget about leaving the machine idle. Just leave it on for
multiple hours/days, use it, and then please send another allprocs.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/1795342

Title:
  High Power Consumption

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-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-power-consumption/+bug/1795342/+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

> Perhaps I need to enable more aggressive crash capturing somehow?

Yes, please follow step 3 in comment 1 to do that.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 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() from

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 a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
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

-- 
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 1262201] Re: System freezes on resume/unlock

Devon,

This bug is over 5 years old so if you have any problems in current
versions it would be most helpful if you logged a new one by running:

  ubuntu-bug gnome-shell

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

Title:
  System freezes on resume/unlock

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After suspend the session the system freezes. This happens when I try to 
resume the
   session, in the login screen.

   To make it happen:

    1- Suspend the session from the user menu
    2- Resume the session

Expected: The session resumes
Observed: The system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-shell 3.8.4-0ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: i386
  Date: Wed Dec 18 10:42:22 2013
  DisplayManager: gdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2013-12-17 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20131216)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  gdmSessionLog:
   /etc/gdm/Xsession: Beginning session setup...
   localuser:nando being added to access control list
   localuser:nando being added to access control list
   Script para cjkv iniciada en run_im.
   Script para default iniciada en run_im.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1262201/+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 1744584] Re: Exclude Snap .cache from Dejadup backups

2019-01-07 Thread Michael Terry

** Changed in: deja-dup (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Exclude Snap .cache from Dejadup backups

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

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1744584/+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 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss

Not myself, no. That was just to cover duplicate bug 1809856. If that's
incorrect, feel free to remove it.

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

Title:
  Dell XPS 13 9350, 9360 and 9370 headphone  audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 124406] Re: Keyboard keys get stuck and repeat

2019-01-07 Thread Felipe Butcher

wow! see this was opened in 2007. just googled this from the future (i
am in 2018) and found this.

using ubuntu 18. found that what was causing it in my case was a
clipboard manager i use here. closing the clipboard manager stopped the
bleeding.

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/124406/+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 1792835] Re: Bash completion for Inkscape does not work

This bug was fixed in the package cowdancer - 0.88

---
cowdancer (0.88) unstable; urgency=medium

  [ Mattia Rizzolo ]
  * Fix bash completion to work with a dynamic _have() instead of the static
have().  LP: #1792835
  * Bump debhelper compat level to 12, using the new debhelper-compat.
+ Move from the deprecated dh_install --fail-missing to dh_missing.
  * Bump Standards-Version to 4.3.0, no changes needed.

  [ James Clarke ]
  * Fix FTBFS with glibc 2.28.  Closes: #916062

 -- Mattia Rizzolo   Mon, 07 Jan 2019 14:43:20 +0100

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

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

Title:
  Bash completion for Inkscape does not work

Status in apt-xapian-index package in Ubuntu:
  New
Status in cowdancer package in Ubuntu:
  Fix Released
Status in dpatch package in Ubuntu:
  New
Status in inkscape package in Ubuntu:
  Fix Released
Status in jackd2 package in Ubuntu:
  New

Bug description:
  Bash completion for Inkscape does not work in Ubuntu 18.04. It will
  for example suggest non-svg files.

  The reason seems to be that /usr/share/bash-
  completion/completions/inkscape uses the have() function, which is
  temporarily defined in /usr/share/bash-completion/bash_completion, but
  then unset at the end of that file.

  Workaround: Copy /usr/share/bash-completion/completions/inkscape to
  ~/.local/share/bash-completion/completions/inkscape and remove the
  uses of "have".

  The bash completion for some other commands seem to use have() too,
  e.g. jackd, ufw, cowbuilder, dpatch_edit_patch, and axi-cache, so bash
  completion for these commands will presumably not work either.


  From /usr/share/bash-completion/bash_completion:
  -
  # Backwards compatibility for compat completions that use have().
  # @deprecated should no longer be used; generally not needed with dynamically
  # loaded completions, and _have is suitable for runtime use.
  have()
  {
  unset -v have
  _have $1 && have=yes
  }
  [...]
  unset -f have
  unset have
  -

  From /usr/share/bash-completion/completions/inkscape:
  -
  [...]
  have inkscape &&
  _inkscape()
  {
[...]
  }
  [ "${have:-}" ] && complete -F _inkscape $filenames inkscape
  -


  System information:

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

  $ apt-cache policy inkscape
  inkscape:
Installed: 0.92.3-1
Candidate: 0.92.3-1
Version table:
   *** 0.92.3-1 500
  500 http://no.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1792835/+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 1801757] Re: all app indicators disappear

2019-01-07 Thread Frank Quinn

I have been living with this issue for some time now, finally annoyed me
enough to Google and found this bug (thanks for reporting :)). Alt-f2 r
also fixes for me which is a new workaround that I'm very grateful for.
In my case it seems to be related to extensions which manipulate the top
bar (e.g. todo.txt / system monitor). If I disable all extensions, and
reboot the box, its fine. If I enable one of the extensions after
rebooting and logging, it looks fine but after reboot, no application
icons will be there. Previously I had just assumed they were broken
extensions but seems to happen with quite a few of them and i have seen
with many different combinations of extensions.

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

Title:
all app indicators disappear

Status in gnome-shell-extension-appindicator package in Ubuntu:
Confirmed

Bug description:
Occasionally all of my app indicators just disappear. Right now, for
example the only icons in my top bar are the wifi icon, the volume
icon, and the battery charge icon. Everything else is gone. The
applications associated with the missing indicators, e.g., Dropbox,
Cloud Station Drive, Pritunl, Shutter, are still running, but their
app indicators are no longer there.

The only way I've found to get them back is to log out and log back
in.

I have no idea what provokes this behavior.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 5 11:37:47 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-27 (39 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+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] [NEW] Speakers dont show or make audio

2019-01-07 Thread Nicholas Johnson

Public bug reported:

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

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

** Attachment added: "my config.htm file for my pc"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227497/+files/config.htm

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

Title:
  Speakers dont show or make audio

Status in alsa-driver package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+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 1262201] Re: System freezes on resume/unlock

2019-01-07 Thread Devon

Still a problem in Ubuntu 18.10 on Acer Swift 3. With screen blanked, on
resume, it occasionally hangs to leave a blank screen and the side bar.

To recover from it, I switched to another tty (Ctrl-Alt-F3 for example)
then ran "killall gnome-shell" and gnome-shell would restart by itself.
However now for some reason I need to do "export DISPLAY=:0; gnome-shell
-r &"

The side bar is then missing and the display blanks after 15 seconds.

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

Title:
  System freezes on resume/unlock

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After suspend the session the system freezes. This happens when I try to 
resume the
   session, in the login screen.

   To make it happen:

    1- Suspend the session from the user menu
    2- Resume the session

Expected: The session resumes
Observed: The system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-shell 3.8.4-0ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: i386
  Date: Wed Dec 18 10:42:22 2013
  DisplayManager: gdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2013-12-17 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20131216)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  gdmSessionLog:
   /etc/gdm/Xsession: Beginning session setup...
   localuser:nando being added to access control list
   localuser:nando being added to access control list
   Script para cjkv iniciada en run_im.
   Script para default iniciada en run_im.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1262201/+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 1780310] Re: Option 'finishings' has value '3' and cannot be edited

This bug was fixed in the package system-config-printer -
1.5.11-2ubuntu2

---
system-config-printer (1.5.11-2ubuntu2) disco; urgency=low

  * 40_temporary-fix-for-error-pop-up-window-for-ipp-2.x-attributes.patch:
Temporary fix for error pop-up window for IPP2.0+ attributes backported
from upstream (Upstream issue #122, LP: #1780310, LP: #1766107).

 -- Till Kamppeter   Mon,  7 Jan 2019 20:01:12
+0100

** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Option 'finishings' has value '3' and cannot be edited

Status in System Config Printer:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Whenever I open the print queue for my local printer, I get a dialog
  box with the message:

  Option 'finishings' has value '3' and cannot be edited

  I can dismiss the dialog box and everything seems to work normally,
  but it is annoying.  However, it's possible that some obscure printer
  feature does not work for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: system-config-printer 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 12:30:50 2018
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2018-07-03 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  Lpstat: device for Ricoh-Aficio-MP-C3500: 
lpd://hqnvprint02.nvidia.com/secureprint
  MachineType: ASUS X299-A
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=d418cc23-14fc-41cf-b75f-29644c2a16be ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnASUS:pnX299-A:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X299-A
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1780310/+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 1766107] Re: 'orientation-requested' and 'print-quality' has value '0'

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

This bug was fixed in the package system-config-printer -
1.5.11-2ubuntu2

---
system-config-printer (1.5.11-2ubuntu2) disco; urgency=low

  * 40_temporary-fix-for-error-pop-up-window-for-ipp-2.x-attributes.patch:
Temporary fix for error pop-up window for IPP2.0+ attributes backported
from upstream (Upstream issue #122, LP: #1780310, LP: #1766107).

 -- Till Kamppeter   Mon,  7 Jan 2019 20:01:12
+0100

** Changed in: system-config-printer (Ubuntu)
   Status: New => Fix Released

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

Title:
  'orientation-requested' and 'print-quality' has value '0'

Status in System Config Printer:
  Unknown
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  CUPS stopped working suddenly. So I opened the settings of my printer
  in the system-config-printer utility which welcomes me with two error
  messages.

  First dialog:
  > Option 'orientation-requested' has value '0' and cannot be edited.

  Second dialog:
  > Option 'print-quality' has value '0' and cannot be edited.

  After clicking OK two times Apport reported an error in
  > /usr/share/system-config-printer/system-config-printer.py

  because of
  > system-config-printer.py crashed with TypeError in __init__(): debugprint() 
takes 1 positional argument but 2 were given

  CupsErrorLog:
  > [cups-deviced] PID 19691 (gutenprint52+usb) stopped with status 1!
  > Unable to create "/etc/cups/subscriptions.conf.N": No such file or directory

  
  Any ideas to fix this?

  Regards,
  Atalanttore
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CupsErrorLog:
   E [21/Apr/2018:21:26:10 +0200] [cups-deviced] PID 19691 (gutenprint52+usb) 
stopped with status 1!
   E [22/Apr/2018:19:11:12 +0200] Unable to create 
"/etc/cups/subscriptions.conf.N": No such file or directory
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lpstat: device for Samsung_SCX_3400_Series_SEC001599E7B363_: 
ipp://SEC001599E7B363.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 5986:055c Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RZ
  Package: system-config-printer 1.5.9+20170825-0ubuntu1
  PackageArchitecture: all
  Papersize: a4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash 
acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Tags: third-party-packages artful
  Uname: Linux 4.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.09
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_W67RZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1766107/+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 1804685] Re: Icon View Captions display in the wrong positions

This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu7.1

---
nautilus (1:3.26.4-0ubuntu7.1) cosmic; urgency=medium

  * debian/patches/git_captions_order.patch
- 'preferences-window: Fix icon views captions order'
  (lp: #1804685)

 -- Sebastien Bacher   Mon, 17 Dec 2018 15:34:36
+0100

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

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

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Released
Status in nautilus source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+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 1804685] Update Released

2019-01-07 Thread Brian Murray

The verification of the Stable Release Update for nautilus 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1804685

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Released
Status in nautilus source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+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 1804685] Re: Icon View Captions display in the wrong positions

This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.3

---
nautilus (1:3.26.4-0~ubuntu18.04.3) bionic; urgency=medium

  * debian/patches/git_captions_order.patch
- 'preferences-window: Fix icon views captions order'
  (lp: #1804685)

 -- Sebastien Bacher   Mon, 17 Dec 2018 15:40:36
+0100

** Changed in: nautilus (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Released
Status in nautilus source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2019-01-07 Thread Samuel thibault

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

Is there really any reason why keyboard-configuration.postinst passes
--force to setupcon?

In Debian we do this in the Debian installer because it is running
within a bterm and thus can't detect it's running on the Linux console.
But we never do this for an installed system. Apparently Ubuntu took
that code snipped and dropped the check for being running within the
Debian installer, and thus erroneously run with --force when DISPLAY is
empty (typically from unattended upgrades and such), with the resulting
observed effects of this bug report.

I guess Ubuntu wants to apply the attached patch

** Attachment added: "proposed fix"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+attachment/5227479/+files/patch

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+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 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start

2019-01-07 Thread Filip Roland

Dear Daniel!

I did what you wrote and that worked!

The problem is solved permanently!

Thank you very much!

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

Title:
ASPEED AST2400 graphics failure on normal start but work on recovery
start

Status in mutter package in Ubuntu:
Incomplete

Bug description:
I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA
chipset.
With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well.
Once when I updated (but before the actual version) it went wrong.

To be truth it not really the xresver...-ast's problem because this
earlier not installed automatically and the poroblem was the same.
When i found it on synaptic as uninstalled i hoped that this will
solve the problem and i had installed it but it not worked at all...

The issue:
When I boot normally the login window load slowly and keybord and mouse very
slow too but work.
I can login. But after i login the screen not show the desktop it show
diagonal stripes. (see the attachment)
This stripes made from original screen but unrecognisable the things. But the
items work if you can click the right places. (for example i can click on the
main switch button if i have luck and Crl+Alt+Del log out me.)
After i log out the login screen corrupted on the same diagonal stripe way.
But also work I can re login.

How it work:
If I start the recovery mode and on the recovery window choose continue start
normally (and nothing else needed) it works without problem. Evrithing is fine.

I tried to install ASPEED driver but on the Softwares and Updates menu
Another driver don't found it.

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

ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log'
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 28 00:28:01 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9]
InstallationDate: Installed on 2017-11-20 (402 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 062a: Creative Labs Optical mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. P10S-I Series
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=hu_HU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P10S-I Series
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: Server
dmi.product.name: P10S-I Series
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Dec 28 00:17:45 2018
xserver.configfile: default
xserver.devices:
inputPower Button KEYBOARD, id 6
inputPower Button KEYBOARD, id 7
inputSleep Button

Re: [Desktop-packages] [Bug 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start

2019-01-07 Thread Filip Roland

Dear Daniel!
I did what you wrote and that worked!
The problem solved permanently!
Thank you very much!

Saját Samsung Galaxy okostelefonról küldve.
Eredeti üzenet Feladó: Daniel van Vugt
Dátum: 2019. 01. 07. 10:43 (GMT+01:00)
Címzett: registrat...@filiproland.hu Tárgy: [Bug 1809940] Re: ASPEED AST2400
graphics failure on normal start but
work on recovery start
Can you please try editing /etc/gdm3/custom.conf and uncommenting this
line:

#WaylandEnable=false

Then reboot, but make sure you're not rebooting into recovery mode
again.. Does that fix it?

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

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

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

Title:
ASPEED AST2400 graphics failure on normal start but work on recovery
start

Status in mutter package in Ubuntu:
Incomplete

How it work:
If I start the recovery mode and on the recovery window choose continue start
normally (and nothing else needed) it works without problem. Evrithing is fine.

I tried to install ASPEED driver but on the Softwares and Updates menu
Another driver don't found it.

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

[Desktop-packages] [Bug 651586] Re: Mozilla Thunderbird and Firefox spellcheck has too many languages

2019-01-07 Thread Mattia Rizzolo

We just had another package that likes and wants more symlinks, and I'm
going to approve that and add more symlinks.  I don't think removing
them is the way to go atm, rather firefox and thunderbird could do
something to deduplicate them (but it needs to be clever, as not
necessarily all en_* (or whatever) are the same).

** Changed in: libreoffice-dictionaries (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Mozilla Thunderbird and Firefox spellcheck has too many languages

Status in firefox package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Triaged
Status in libreoffice package in Ubuntu:
  Confirmed
Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  Mozilla Thunderbird and Firefox spellcheck has too many languages. It
  does not follow the Ubuntu Language Support Standard (gnome-language-
  selector).

  Language Support (gnome-language-selector) has a feature which allows
  you to gray out languages you are not interested in seeing and black
  in the languages you would like to see. Mozilla apps should follow
  this or should at least offer a workaround allowing a user to disable
  certain languages.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.8+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Wed Sep 29 17:49:00 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 
(20100419.1)
  ProcEnviron:
   LANGUAGE=en_US:en_CA:en
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/651586/+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 218687] [Review update] R3.2

2019-01-07 Thread OpenContrail Admin

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

Review in progress for https://review.opencontrail.org/48530 
Submitter: Nagendra Prasath (npchand...@juniper.net)

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

Title:
  applet.py crashed with IPPError in collect_printer_state_reasons()

Status in Juniper Openstack:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  Binary package hint: system-config-printer

  I just connect the hp deskjet F380 all-in-one and crashed at
  recognition

  ProblemType: Crash
  Architecture: amd64
  Date: Thu Apr 17 09:28:45 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/share/system-config-printer/applet.py
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: nvidia
  Package: system-config-printer-gnome 0.7.81+svn1976-0ubuntu7
  PackageArchitecture: all
  ProcCmdline: python /usr/share/system-config-printer/applet.py
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/system-config-printer/applet.py']
  SourcePackage: system-config-printer
  Title: applet.py crashed with IPPError in collect_printer_state_reasons()
  Uname: Linux 2.6.24-15-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv 
plugdev video

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/218687/+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 218687] [Review update] R3.2

2019-01-07 Thread OpenContrail Admin

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

Review in progress for https://review.opencontrail.org/48530 
Submitter: Nagendra Prasath (npchand...@juniper.net)

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

Title:
  applet.py crashed with IPPError in collect_printer_state_reasons()

Status in Juniper Openstack:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  Binary package hint: system-config-printer

  I just connect the hp deskjet F380 all-in-one and crashed at
  recognition

  ProblemType: Crash
  Architecture: amd64
  Date: Thu Apr 17 09:28:45 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/share/system-config-printer/applet.py
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: nvidia
  Package: system-config-printer-gnome 0.7.81+svn1976-0ubuntu7
  PackageArchitecture: all
  ProcCmdline: python /usr/share/system-config-printer/applet.py
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/system-config-printer/applet.py']
  SourcePackage: system-config-printer
  Title: applet.py crashed with IPPError in collect_printer_state_reasons()
  Uname: Linux 2.6.24-15-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv 
plugdev video

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/218687/+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 1795342] Re: High Power Consumption

2019-01-07 Thread Irfan

Please ignore the previous output file, took that too soon after system
boot.

Consider the attachment with this comment, the power usage is still same
and high. I left the machine completely idle for longer.

** Attachment added: "allprocs.txt"
   
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+attachment/5227474/+files/allprocs.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/1795342

Title:
  High Power Consumption

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-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-power-consumption/+bug/1795342/+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-07 Thread John

bump

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

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 org.gnome.Shell.desktop[16220]: Fatal server 
error:
  Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]:

[Desktop-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

2019-01-07 Thread Iain Lane

I did some more poking this morning and followed up to the thread. A
change in 2.80 has made this start happening. I'm hoping that someone
upstream will understand what's going on enough to propose a fix.

-- 
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 network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Disco:
  Triaged

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/network-manager/+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 1513801] Re: 1002:4a49 Scrambled screen and mouse pointer on first boot all ubuntu versions

2019-01-07 Thread lotuspsychje

this was only on this hardware, i never been able to reproduce on other machines
so closing the bug invalid, as the computer mainboard broken

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  1002:4a49 Scrambled screen and mouse pointer on first boot all ubuntu
  versions

Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I have this bug haunting me on 12.04,14.04,15.10 and 16.04

  First boot the screen and mouse pointer are disformed,
  after second boot it gets fixxed and i can't reproduce it anymore on next 
reboots

  the day after first boot, screen is disformed again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.5.0+git20150819-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  6 11:54:51 2015
  DistUpgraded: 2015-10-28 14:50:53,632 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] R420 [Radeon X800 PRO/GTO AGP] 
[1002:4a49] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0002]
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0003]
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  SourcePackage: xserver-xorg-video-ati
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151019-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov  6 11:51:46 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu10
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1513801/+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 814473] Re: gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()

there has been no new report/activity for years, closing as deprecated


** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  This comes up after a graphical lock-up. The event is just like a
  Suspend action and needs to press the power button to resume.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.1.3-0ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
  Uname: Linux 3.0.0-6-generic x86_64
  Architecture: amd64
  Date: Fri Jul 22 16:25:23 2011
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1c158c0db7:mov0x10(%rbx),%ecx
   PC (0x7f1c158c0db7) ok
   source "0x10(%rbx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/libgdk-3.so.0
   ?? () from /usr/lib/libgdk-3.so.0
   ?? () from /usr/lib/libgdk-3.so.0
   ?? () from /usr/lib/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/libgdk-3.so.0
  Title: gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/814473/+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 1029412] Re: Bring back the old 'compact' format, coz the latest one is (a) not compact and (b) not compact and (c) has a teenie zoom level

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

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

Title:
  Bring back the old 'compact' format, coz the latest one is (a) not
  compact and (b) not compact and (c) has a teenie zoom level

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  If you don't want to replace the current 'Compact' (Ctrl-3), then
  (re-)create a new (or improved) 'Really Compact' and use Ctrl-4.

  Secondly, the zoom size on Ctrl-3 is tiny.  The older 'Really Compact'
  format used to zoom to the same level as Ctrl-1.

  Please feel free to contact me should you have any questions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1029412/+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 996158] Re: Unity or Ubuntu dock launcher with auto-hide using mouse is unreliable

The bug here is about unity, please open a new ticket if you have
similar issues in newer versions not using Unity

** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu)

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

Title:
  Unity or Ubuntu dock launcher with auto-hide using mouse is unreliable

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-2d package in Ubuntu:
  Invalid

Bug description:
  Using mouse with unity-panel auto-hide mode makes the mouse to shift
  left while pointer stays in place (at the left edge). The effect is
  your mouse is shifting (every time you acces launcher) to the left
  until there is no space on the table and you have to put it up and
  move to the right. This is very inconvinient and makes usage of the
  unity launcher unreliable. The issue was introduced with the new
  launcher reveal mechanizm when you have to "push" the pointer do the
  left edge to make launcher re-appear. It happened after upgrade from
  Ubuntu 11.10 to 12.04. The bug affects unity and unity-2d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/996158/+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 996167] Re: Unable to use Unity launcher with auto-hide mode using graphics tablet after upgrade to 12.04

** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu)

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

Title:
  Unable to use Unity launcher with auto-hide mode using graphics tablet
  after upgrade to 12.04

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-2d package in Ubuntu:
  Invalid

Bug description:
  After upgrade from 10.10 to 12.04 unity-2d launcher with auto-hide
  mode never reveals using graphics tablet as input device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/996167/+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 1272030] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_unix64()

there has been no new report/activity for years, closing as deprecated

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  ffi_call_unix64()

Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  I just booted.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Jan 23 20:19:30 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2014-01-22 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f0e152da7f7:mov(%rax),%rdi
   PC (0x7f0e152da7f7) ok
   source "(%rax)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1272030/+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 1810675] Re: Bug 950843 not fixed in any distro.

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

** This bug has been marked a duplicate of bug 950843
   simple scan fails to scan. "unable to start scan" change scan ner gives no 
options

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

Title:
  Bug 950843 not fixed in any distro.

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Hi guys, in relationship with this closed post:
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/950843, I
  have the same problem than John and Miles over different Epson Wifi
  Scanners or combis (printer + scanner). After searching a lot, many
  other Linux Distributions have the same problem in their latest
  versions with the scanner drivers well installed and the conection to
  the equipment working. Using the program what you want, the scanner
  starts (you can see the process on the scanner screen) to do his work
  and then all fails.

  The most worrisome situation is that anyone of this forums don't give
  any solution and it looks like a big problem. To nornmal users and
  institutional or educational ines, this type of problems are very
  important to select a good OS, and it's crazy that in 2019 we have
  problems to work propperly with a modern scan in Linux, no to mention
  that many manufacturers like Epson still do not give direct support...

  I'm using Ubuntu 18.04 LTS and usually an Epson XP-530.

  Greetings from Spain,
  Pablo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1810675/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS, 18.10 and 19.04

Ubuntu MATE 19.04 (disco) is affected too.

** Summary changed:

- HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 
LTS and 18.10
+ HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 
LTS, 18.10 and 19.04

** Tags added: disco

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS, 18.10 and 19.04

Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1809783] Re: Bluetooth always on when power on my laptop

The bluetooth status should be store/restored by the bluez init scripts

** No longer affects: gnome-shell (Ubuntu)

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

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

Title:
  Bluetooth always on when power on my laptop

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth works properly but it's always turned on on startup and I
  have to turn it off manually

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.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
  CurrentDesktop: Budgie:GNOME
  Date: Wed Dec 26 09:16:08 2018
  InstallationDate: Installed on 2018-12-07 (18 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE C50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 5.10
  dmi.board.asset.tag: *
  dmi.board.name: ZBWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: SATELLITE C50-B
  dmi.product.version: PSCMLE-02N01VIT
  dmi.sys.vendor: TOSHIBA
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1809783/+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

Thank you for your bug report. What screen resolution are you using?
Could it be that there is not enough vertical space to fit the settings
dialog when the dock is at the bottom?

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

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

-- 
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 1810022] Re: Totem does not play MOV file with x264 encoding

Does it work if you move away the ~/.cache/gstreamer-1.0 directory?
(similar to https://askubuntu.com/questions/300645/cant-play-videos-in-
totem-error-says-that-were-missing-plugins-that-should-n)

-- 
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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS and 18.10

Ubuntu MATE 18.10 (cosmic) is affected too.

** Summary changed:

- HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 
LTS
+ HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 
LTS and 18.10

** Tags removed: amd64
** Tags added: cosmic

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS and 18.10

Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1810050] Re: screen glitch in dock

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  screen glitch in dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  i found a glitch in the dock when closing out of the screen switch
  menu down by the activities button. it changes back to the normal
  colour when the mouse cursor hovers over it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 29 15:37:21 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:fce0]
  InstallationDate: Installed on 2018-12-29 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181225)
  MachineType: TOSHIBA Satellite C650
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=22135462-7795-4371-b6e5-dbb5a4541789 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.00:bd04/01/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-00M001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C650
  dmi.product.sku: PSC2EC-00M001
  dmi.product.version: PSC2EC-00M001
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1810050/+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 1772498] Re: Command "X -configure" segmentation fault

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

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

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

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

Title:
  Command "X -configure" segmentation fault

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Was searching for a method to disable DPMS via a custom
  /etc/X11/xorg.conf file and discovered this bug. Under a fresh Ubuntu
  18.04 minimal desktop installation, after stopping gdm3 and executing
  "sudo X -configure" in /etc/X11 subdirectory to create an xorg.conf
  file, this happens:

  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu
  Current Operating System: Linux {hostname} 4.15.0-20-generic #21-Ubuntu SMP 
Tue Apr 24 06:16:15 UTC 2018 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=562f17d1-d033-4aa0-ba91-f8a04e7510a6 ro quiet splash vt.handoff=1
  Build Date: 13 April 2018  08:07:36PM
  xorg-server 2:1.19.6-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.34.0
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 21 11:26:02 2018
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x564f083b08ad]
  (EE) 1: /usr/lib/xorg/Xorg (0x564f081f8000+0x1bc649) [0x564f083b4649]
  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb92b9ca000+0x12890) 
[0x7fb92b9dc890]
  (EE) 3: /usr/lib/xorg/Xorg (0x564f081f8000+0xb2294) [0x564f082aa294]
  (EE) 4: /usr/lib/xorg/Xorg (xf86BusProbe+0x9) [0x564f08282229]
  (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0x7f1) [0x564f08290e51]
  (EE) 6: /usr/lib/xorg/Xorg (0x564f081f8000+0x56cd3) [0x564f0824ecd3]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7fb92b5fab97]
  (EE) 8: /usr/lib/xorg/Xorg (_start+0x2a) [0x564f08238b8a]
  (EE)
  (EE) Segmentation fault at address 0x50
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)
  (EE)
  Please consult the The X.Org Foundation support
  at http://wiki.x.org
  for help.
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE)
  (EE) Server terminated with error (1). Closing log file.

  lsb_release -rd

  Description: Ubuntu 18.04 LTS
  Release: 18.04

  apt-cache policy xorg

  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expected:

I expected "X -configure" to write a default xorg.conf file in
  /etc/X11

  What happened instead:

X binary crashed

  Personal Note:

Will create ugly hack to solve my problem while this bug gets fixed.
  Not holding my breathe, please add "you don't need an xorg.conf file"
  comments below. :D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1772498/+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 1810808] [NEW] blocchi continui pagine

2019-01-07 Thread mastrototaro leonardo

Public bug reported:

aprendo le pagine il computer va in blocco e non risponde piu ai comandi

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Mon Jan  7 17:27:27 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
InstallationDate: Installed on 2016-10-10 (819 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09CI.M060.20100401.JIP
dmi.board.name: R519/R719
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09CI.M060.20100401.JIP:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: R519/R719
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Oct  4 11:40:09 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  blocchi continui pagine

Status in xorg package in Ubuntu:
  New

Bug description:
  aprendo le pagine il computer va in blocco e non risponde piu ai
  comandi

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jan  7 17:27:27 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
  InstallationDate: Installed on 2016-10-10 (819 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09CI.M060.20100401.JIP
  dmi.board.name: R519/R719
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias:

Re: [Desktop-packages] [Bug 1809517] Re: OS freezes after screen turns off and I return to account

2019-01-07 Thread Matthew

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

I'm not completely sure how its the same. It is related to the login 
from suspended but that's about it. That's like saying a flat tire is 
the same as bad wheel bearings on a vehicle because they're both on the 
wheel.

On 1/7/19 12:14 AM, Daniel van Vugt wrote:
> *** This bug is a duplicate of bug 1740792 ***
>  https://bugs.launchpad.net/bugs/1740792
>
> Sounds like bug 1740792, or bug 1803527.
>
> ** This bug has been marked a duplicate of bug 1740792
> Automatic login still requires user password after suspend/hibernate
>

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

Title:
  OS freezes after screen turns off and I return to account

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I recently upgraded to the newest 18.10 I have disabled Ubuntu from
  requiring my password after the screen turns off due to inactivity but
  I'm still taken to the landing page as if I needed to unlock my
  computer. After sliding up or hitting enter the screen stays purple
  with the taskbar visible. I can click the application shortcuts on the
  taskbar but nothing happens afterwards.It doesn't happen every time,
  only once out of every 5 to 10 times.

  I'm using a Dell Inspiron 5559 64bit, graphics card is Intel HD
  Graphics 520 (Skylake GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809517/+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 1800043] Re: nautilus cannot write on nfs file share

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

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

Title:
  nautilus cannot write on nfs file share

Status in nautilus package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this 
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) 
Nautilus is not able to perform any write access to it (write, delete, make new 
directory,...). I can do all of this operations by using shell commands (touch, 
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if 
I start it with root privileges.
  Even stranger is the following: even though nautilus cannot write into the 
mounted shares it is able to write into its subfolders. This bug seems to 
affect others as well: 
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

  Ubuntu version: 18.04.1 LTS - amd64
  Nautilus version: 1:3.26.4-0~ubuntu18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+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 292205] Re: Printer Canon PIXMA MP110 doesn't work in Linux

2019-01-07 Thread valeria Victoria

Hello,.,.,.
Download Driver in https://canon-driver.org/canon-pixma-mp110-driver/

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

Title:
  Printer Canon PIXMA MP110 doesn't work in Linux

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I tried to install my multifunctional printer on Linux, but there isn't any 
compatible driver for it.
  So I searched the net and found, that PIXMA MP110 is almost compatible with 
the iP1500 driver.
  However, neither this driver is listed in the Ubuntu printers driver list.

  I found some .deb packages (converted from .rpms), that would work as iP1500 
drivers.
  I installed them through dpkg, with the `--force-all` parameter and restarted 
cupsd.

  Now, I can see the iP1500 driver in the driver list, but after chosing
  this one as my MP110 printer's driver, I can create print jobs, but my
  printer seems to not react (printer does nothing and no action occurs
  on the printer's display).

  I'll attach the two .deb packages, I installed.
  I use Ubuntu Intrepid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/292205/+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 1809692] Re: distorted lines when using google chrome browser

2019-01-07 Thread Mushegh Rafayelyan

Thanks!

see attached the screenshot with distorted lines at two different places of
the screen. I am not totally sure but it seems that such a problem is
arising when the screen content is getting changed dynamically, for
example, when I write text (see the second attachment).

Best regards,

Mushegh Rafayelyan
Postdoctoral researcher at Kastler-Brossel Laboratory
(ENS, Sorbonne U., CNRS, Collège de France)
http://www.lkb.upmc.fr/opticalimaging/


On Mon, 7 Jan 2019 at 10:31, Daniel van Vugt 
wrote:

> Can you please attach a screenshot or photo of the problem?
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1809692
>
> Title:
>   distorted lines when using google chrome browser
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I get dynamically changing distorted lines when using google chrome
>   browser, I suppose it is due to my graphics card.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3.1
>   ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
>   Uname: Linux 4.4.0-140-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Tue Dec 25 04:18:51 2018
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-20160624-2
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:07d0]
>   InstallationDate: Installed on 2018-04-12 (256 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20160624-10:47
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 8087:0a2b Intel Corp.
>Bus 001 Device 003: ID 0c45:6717 Microdia
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Latitude 5480
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed
> root=UUID=72a3879f-b71f-40a0-b09b-ceb983af1dbf ro acpi_rev_override quiet
> splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/30/2018
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.8.2
>   dmi.board.name: 0D0XXK
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A02
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0D0XXK:rvrA02:cvnDellInc.:ct10:cvr:
>   dmi.product.name: Latitude 5480
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.91-2~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Dec 24 22:28:33 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1368
>vendor LGD
>   xserver.version: 2:1.18.4-0ubuntu0.8
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1809692/+subscriptions
>


** Attachment added: "Screenshot from 2019-01-07 16-57-09.png"
   
https://bugs.launchpad.net/bugs/1809692/+attachment/5227434/+files/Screenshot%20from%202019-01-07%2016-57-09.png

** Attachment added: "Screenshot from 2019-01-07 17-05-46.png"
   
https://bugs.launchpad.net/bugs/1809692/+attachment/5227435/+files/Screenshot%20from%202019-01-07%2017-05-46.png

-- 
You received this bug notification because you are a member of Desktop
Packages,

[Desktop-packages] [Bug 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS

2019-01-07 Thread nmaxx

Same problem here - the hplip version is 3.17.10+repack0-5,m btw. (not
exactly recent, it could really use an SRU to the latest upstream
release).

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS

Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS

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

** Changed in: mate-panel (Ubuntu)
   Status: New => Confirmed

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS

Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS

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

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

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS

Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1810097] Re: HDMI is not recognized

2019-01-07 Thread Heinz Köhler

Hallo!

heinzub@heinz-Z97-D3H:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-VGA-1/enabled:enabled
heinzub@heinz-Z97-D3H:~$

Mit freundlichen Grüßen


Heinz Köhler
Feldkamp 6 b, Ofen
26160 Bad Zwischenahn
Telefon:  +49 441 69241
Fax:  +49 441 30449608
Mobile:   +49 160 952 134 77
E-Mail:   he...@hkzwahn.de

Am 07.01.19 um 11:25 schrieb Daniel van Vugt:
> grep ./sys/class/drm/*/enabled

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

Title:
  HDMI is not recognized

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8159.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  with friendly greetings from Germany
  Heinz Köhler

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Dec 30 17:27:38 2018
  DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2014-12-09 (1482 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97-HD3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 21 14:19:34 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1810097/+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 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss

2019-01-07 Thread Kai-Heng Feng

Daniel,

Do you observe this on 9370?

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

Title:
  Dell XPS 13 9350, 9360 and 9370 headphone  audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1762726] Re: Context menu does not show on passwords fields

2019-01-07 Thread Olivier Tilloy

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

Thanks for the confirmation. The update that fixed the issue is gnome-
shell 3.28.3-0ubuntu0.18.04.4. I am therefore marking this bug as a
duplicate of bug #1765304.

** This bug has been marked a duplicate of bug 1765304
   Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & 
raising window whenever they're focused)

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

Title:
  Context menu does not show on passwords fields

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  As many people I use a password manager in order to manage my logins.
  For that I simply copy/paste the username and password in the
  respective fields from another application.  Given some webpages block
  this by JavaScript, I have the following about:config preference:

  dom.event.clipboardevents.enabled=false

  This mostly as an information, because it doesn't seem to affect the
  problem.

  Take a login page (I tried AliExpress - https://login.aliexpress.com/), and 
right click in the username field.  A context menu is shown, containing 
-amongst others- "Paste".
  Click right in the password field, and the context menu is not shown.  I 
would expect it to be shown.

  Using Ctrl-V does work.

  I tried a recreated profile in order to exclude profile-based issues.
  The same happens.

  This does not happen on Ubuntu 16.04LTS
  (59.0.2+build1-0ubuntu0.16.04.3) with equivalent version Firefox
  (59.0.2)

  I am not 100% sure this is a firefox issue.  Perhaps this is Gnome
  related, because I use the default interface on each installation:
  Unity on 16.04LTS and Gnome3 on 18.04LTS.

  

  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy firefox
  firefox:
Installed: 59.0.2+build1-0ubuntu1
Candidate: 59.0.2+build1-0ubuntu1
Version table:
   *** 59.0.2+build1-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+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 1795111] Re: gsd-housekeepin spams syslog with Failed to enumerate children of /tmp/systemd-private.. Error opening directory '/tmp/systemd-private..

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

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

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

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

Title:
  gsd-housekeepin spams syslog with Failed to enumerate children of /tmp
  /systemd-private.. Error opening directory '/tmp/systemd-private..

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  The fan and cpu is very active during this event, thousands of errors
  reported. Syslog case attached. The desktop becomes unresponsive
  during this event (for instance cant close windows).

  lsb_release -rd
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.2
Candidate: 3.28.3-0ubuntu0.18.04.2
Version table:
   *** 3.28.3-0ubuntu0.18.04.2 500
  500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages

  uname -a
  Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  gnome-shell --version
  GNOME Shell 3.28.3

  NOTE: syslog package name is incorrect it seems

  apt-cache policy gsd-housekeepin
  N: Unable to locate package gsd-housekeepin

  apt-cache policy gsd-housekeeping
  N: Unable to locate package gsd-housekeeping

  Sample:

  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-HcUyZY:
 Error opening directory 
'/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-HcUyZY':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-iinX30: 
Error opening directory 
'/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-iinX30': 
Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-wgHcsA:
 Error opening directory 
'/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-wgHcsA':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-1vLCpk:
 Error opening directory 
'/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-1vLCpk':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-M2su41: 
Error opening directory 
'/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-M2su41': 
Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-zPlm2z:
 Error opening directory 
'/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-zPlm2z':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-nn8vHs:
 Error opening directory 
'/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-nn8vHs':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-4y9y5r: 
Error opening directory 
'/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-4y9y5r':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-gW3soH:
 Error opening directory 
'/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-gW3soH':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of 
/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-ZGaNqX:
 Error opening directory 
'/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-ZGaNqX':
 Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children 
of /var/tmp/mkinitramfs_FJNyyu/var/cache/ldconfig: Error opening directory 
'/var/tmp/mkinitramfs_FJNyyu/var/cache/ldconfig': Permission denied 
  Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to

[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() from

2019-01-07 Thread James P Michels III

Not sure if you will find this useful, but for me this bug occurs
regularly with a very common pattern.

I use a VPN to access my companies network when working remotely. I also
regularly use Nautilus to sftp mount remote servers in my companies data
centers. I use vscode as an IDE to edit C++ code files on the remote
servers and run build scripts there as I develop. Local development,
while possible, would be a significant hassle.

Eventually, the gnome-shell will crash taking the gvfs sftp mount with
it. For me around 1-2 times per work day. Recovery is trivial, I just
click on a bookmark in Nautilus to restart the mount.

This crash has been happening for years now. Wayland or X-Org.

This crash does not occur when I use the same workflow from my company's
office. IE, private network without VPN.

I've always assumed this was a result of intermittent poor connectivity
with my ISP.

Again, sorry if this comment is just noise.

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

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:

[Desktop-packages] [Bug 428817] Re: Print Dialog does not allow editing of page parameters

2019-01-07 Thread Jonathan Kamens

I was having this problem on Ubuntu 18.10 (WOW, THIS PROBLEM HAS BEEN
AROUND FOR A VERY LONG TIME) with my HP LaserJet 500 color M551 printer.
When I tried to install it, the driver that kept getting selected was
"HP LaserJet 500 color M551, driverless, cups-filters 1.21.3". This,
despite the fact that I have "hpijs-ppds", "hplip", and "hplip-data"
installed.

I solved the problem by downloading the current version of HPLIP
directly from HP (https://sourceforge.net/projects/hplip/ or
https://developers.hp.com/hp-linux-imaging-and-printing), unpacking it,
locating the PPD for my printer in the source code ("hp-
laserjet_500_color_m551-ps.ppd"), and changing the configured driver of
the printer installed in Linux to specify that PPD directly rather than
using the recommended driver.

I think the problem here, or at least one of the problems here, is not
nearly all of the HP printer drivers are being installed by Ubuntu. In
particular, while I can't say for certain, it looks to me like the
hpijs-ppds package is only installing a few fax drivers, not the full
array of drivers available in HP's HPLIP package. I have no idea why
that's the case.

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

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

Title:
  Print Dialog does not allow editing of page parameters

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in hplip package in Ubuntu:
  New

Bug description:
  Binary package hint: cups-pdf

  In Ubuntu-jaunty amd64,

  Cups PDF driver does not allow us to change the paper size,
  orientation, or anything.  I would like to print my images from GIMP
  to pdf, but they are wider than an A4 page, and so I cannot print them
  to a whole pdf!  I know PDF format can support multiple sizes.  And
  the options are there, just greyed out.

  This is non-application specific.  Firefox print dialog behaves the
  same.  OOo Print dialog doesn't even show the Cups PDF driver.

  If those options are there, but are just greyed out, I would consider
  this a problem.  If the options have not been implemented, perhaps put
  up a notice on that tab saying that they don't exist?

  I hope whoever fixes this gets paid for it!  Thanks for the awesome
  work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/428817/+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 428817] Re: Print Dialog does not allow editing of page parameters

2019-01-07 Thread Jonathan Kamens

Added hplip to the affects list for this bug because hpijs-ppds appears
to only be installing a few fax PPDs, not the full array of available
HPLIP PPDs.


** Tags added: cosmic

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

Title:
  Print Dialog does not allow editing of page parameters

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in hplip package in Ubuntu:
  New

Bug description:
  Binary package hint: cups-pdf

  In Ubuntu-jaunty amd64,

  Cups PDF driver does not allow us to change the paper size,
  orientation, or anything.  I would like to print my images from GIMP
  to pdf, but they are wider than an A4 page, and so I cannot print them
  to a whole pdf!  I know PDF format can support multiple sizes.  And
  the options are there, just greyed out.

  This is non-application specific.  Firefox print dialog behaves the
  same.  OOo Print dialog doesn't even show the Cups PDF driver.

  If those options are there, but are just greyed out, I would consider
  this a problem.  If the options have not been implemented, perhaps put
  up a notice on that tab saying that they don't exist?

  I hope whoever fixes this gets paid for it!  Thanks for the awesome
  work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/428817/+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 1800043] Re: nautilus cannot write on nfs file share

2019-01-07 Thread Jens Gollasch

I have the same problem, can't write to the 1st directory of nfs share in GUI.
Searched a day until found this thread here.
Coming from 14.04 to 16.04 and nemo 3.6.5 instead of nautilus (mint cinnamon
17.3->18.3). The same problem also consists with thunar.
So it should be a common bug.
Maybe a follow failure from another (gnome?)package, because with a fresh usb
stick (in my case mint 18.03) it works!

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

Title:
nautilus cannot write on nfs file share

Status in nautilus package in Ubuntu:
Incomplete

Bug description:
I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418)
Nautilus is not able to perform any write access to it (write, delete, make new
directory,...). I can do all of this operations by using shell commands (touch,
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if
I start it with root privileges.
Even stranger is the following: even though nautilus cannot write into the
mounted shares it is able to write into its subfolders. This bug seems to
affect others as well:
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

Ubuntu version: 18.04.1 LTS - amd64
Nautilus version: 1:3.26.4-0~ubuntu18.04.1

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

[Desktop-packages] [Bug 1762726] Re: Context menu does not show on passwords fields

2019-01-07 Thread Jawtheshark

Hello, I confirm that my current 18.04 installation, with Firefox 64.0,
the issue is gone.

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

Title:
  Context menu does not show on passwords fields

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  As many people I use a password manager in order to manage my logins.
  For that I simply copy/paste the username and password in the
  respective fields from another application.  Given some webpages block
  this by JavaScript, I have the following about:config preference:

  dom.event.clipboardevents.enabled=false

  This mostly as an information, because it doesn't seem to affect the
  problem.

  Take a login page (I tried AliExpress - https://login.aliexpress.com/), and 
right click in the username field.  A context menu is shown, containing 
-amongst others- "Paste".
  Click right in the password field, and the context menu is not shown.  I 
would expect it to be shown.

  Using Ctrl-V does work.

  I tried a recreated profile in order to exclude profile-based issues.
  The same happens.

  This does not happen on Ubuntu 16.04LTS
  (59.0.2+build1-0ubuntu0.16.04.3) with equivalent version Firefox
  (59.0.2)

  I am not 100% sure this is a firefox issue.  Perhaps this is Gnome
  related, because I use the default interface on each installation:
  Unity on 16.04LTS and Gnome3 on 18.04LTS.

  

  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy firefox
  firefox:
Installed: 59.0.2+build1-0ubuntu1
Candidate: 59.0.2+build1-0ubuntu1
Version table:
   *** 59.0.2+build1-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+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 1638395] Re: Unable to locate remote printer when printing

2019-01-07 Thread Brother Printer Support

Hi We are brother printer technical support provider who provide best
Brother Printer Customer Service For Usa brother Printer customer. Dial
1800-436-0509 to help or Visit>> https://www.printertollfreenumber.com
/brother-printer-support

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638395/+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 1762726] Re: Context menu does not show on passwords fields

2019-01-07 Thread Harald H.

A update to Ubuntu received today seems to have fixed the issue.

---

$ less /var/log/apt/history.log

Upgrade: gedit:amd64 (3.28.1-1ubuntu1, 3.28.1-1ubuntu1.1),
libgweather-3-15:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1),
gir1.2-gweather-3.0:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1), gnome-
shell-common:amd64 (3.28.3-0ubuntu0.18.04.3, 3.28.3-0ubuntu0.18.04.4),
gedit-common:amd64 (3.28.1-1ubuntu1, 3.28.1-1ubuntu1.1), gnome-
shell:amd64 (3.28.3-0ubuntu0.18.04.3, 3.28.3-0ubuntu0.18.04.4),
libgweather-common:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1)

---

I'm no longer able to reproduce the issue.

It seems to have been fixed by this patch:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304

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

Title:
  Context menu does not show on passwords fields

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  As many people I use a password manager in order to manage my logins.
  For that I simply copy/paste the username and password in the
  respective fields from another application.  Given some webpages block
  this by JavaScript, I have the following about:config preference:

  dom.event.clipboardevents.enabled=false

  This mostly as an information, because it doesn't seem to affect the
  problem.

  Take a login page (I tried AliExpress - https://login.aliexpress.com/), and 
right click in the username field.  A context menu is shown, containing 
-amongst others- "Paste".
  Click right in the password field, and the context menu is not shown.  I 
would expect it to be shown.

  Using Ctrl-V does work.

  I tried a recreated profile in order to exclude profile-based issues.
  The same happens.

  This does not happen on Ubuntu 16.04LTS
  (59.0.2+build1-0ubuntu0.16.04.3) with equivalent version Firefox
  (59.0.2)

  I am not 100% sure this is a firefox issue.  Perhaps this is Gnome
  related, because I use the default interface on each installation:
  Unity on 16.04LTS and Gnome3 on 18.04LTS.

  

  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy firefox
  firefox:
Installed: 59.0.2+build1-0ubuntu1
Candidate: 59.0.2+build1-0ubuntu1
Version table:
   *** 59.0.2+build1-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+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 1773700] Re: [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling sound no matter what sound I play

2019-01-07 Thread Jule Marcoueille

And I do not know if it changes something but I have this workaround
active too: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html

Plus, I have tried the fixes in your first post with no more luck for the 
crackling sound.
* `options snd-hda-intel position_fix=1` in `/etc/modprobe.d/alsa-base.conf` - 
KO
* `options snd-hda-intel position_fix=2` in `/etc/modprobe.d/alsa-base.conf` - 
KO
* `load-module module-udev-detect tsched=0` in `/etc/pulse/default.pa` - KO

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

Title:
  [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling
  sound no matter what sound I play

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

Bug description:
  I just installed ubuntu, and immediately had problems of very loud and 
crackling sound no matter what sound I played.
  I tried the three solutions listed here 
https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in 
no sound at all, and now even if I revert back everything, I can't get any 
sound out from the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 22:37:20 2018
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX390UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX390UAK
  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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX390UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-07 Thread preethi

PFA the requested output files.

Thank you for your help.

Regards,
Preethi R


On Mon, 7 Jan 2019 at 16:20, Daniel van Vugt 
wrote:

> I can't seem to reproduce this bug on 18.04 after installing ubuntu-
> restricted-extras.
>
> 1. What model of CPU do you have? (run lscpu)
>
> 2. Please run:  dpkg -l > allpackages.txt
>and attach the resulting file 'allpackages.txt'.
>
> ** Changed in: totem (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>


** Attachment added: "lscpu.txt"
   https://bugs.launchpad.net/bugs/1810022/+attachment/5227409/+files/lscpu.txt

** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/bugs/1810022/+attachment/5227410/+files/allpackages.txt

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

[Desktop-packages] [Bug 1773700] Re: [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling sound no matter what sound I play

2019-01-07 Thread Jule Marcoueille

For me the steps from this tutorial https://era86.github.io/2017/10/03
/asus-zenbook-3-volume-controls.html have done the trick in order to
control the internal speaker volume. But unfortunately it is more a
workaround than a real fix since I still have crackling sound... :'(

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

Title:
  [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling
  sound no matter what sound I play

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

Bug description:
  I just installed ubuntu, and immediately had problems of very loud and 
crackling sound no matter what sound I played.
  I tried the three solutions listed here 
https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in 
no sound at all, and now even if I revert back everything, I can't get any 
sound out from the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 22:37:20 2018
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX390UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX390UAK
  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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX390UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773700/+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 1810039] Re: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]

2019-01-07 Thread Jule Marcoueille

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

@vanvugt: the gif is relevant in order to understand well the bug I
think, I mean it may show the correct way of handling some devices but
as I said in my case changing PCM volume is the only way to get volume
react normally since Master volume does nothing at all. I guess it can
help devs understand where the bug is coming from.

And indeed this is a duplicate of
https://bugs.launchpad.net/bugs/1773700. I did not find him before,
sorry for this one.

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

Title:
  Volume noisy and loud with no level control [HDA Intel PCH / Realtek
  ALC295]

Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  What I expect:
  When I use slider volume or when I use volume up button of my laptop, I 
expect that the volume goes up slightly.

  What happens:
  From the mute state, one press on volume up do graphically well but in 
reality the volume is loud and noisy from the first step. And all other up 
steps do not change the volume.
  Doing this with `alsamixer` started show me what you can see in 
volume-issue.gif attached file.
  Indeed when I press volume up PCM volume is maxed to 100 instantly and then 
Speaker volume and then Master volume.

  In my case manually changing the PCM volume in `alsamixer` is the only
  way to change the actual volume of my laptop. Even changing Master
  volume has no effect!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jule   1680 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 29 16:04:58 2018
  InstallationDate: Installed on 2018-12-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX390UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX390UAK
  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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX390UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810039/+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 1808959] Re: [snap] core18-based snap fails to start on Solus

2019-01-07 Thread Henrik Steen

I'm also trying to run the Chromium snap on Solus, I get the same error.

I don't think the solution to use core 16 is right, due to the old
Chromium version that comes with it.

Is it possible to maintain the core 16 version of Chromium as well?

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

Title:
  [snap] core18-based snap fails to start on Solus

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After installation of chromium and I try to start it I get this error
  inside my terminal.

  fredu  ~  chromium 
  execv failed: No such file or directory

  System:
  Description:Solus
  Release:3.

  Chromium:   stable
  snapd:  2.36.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1808959/+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 1730071] Re: Application icons appear stretched when using scaling

2019-01-07 Thread MN

+1, Ubuntu 18.10

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

Title:
  Application icons appear stretched when using scaling

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  The appindicator gnome extension shows the "system tray icons" in the
  upper right corner of the screen. However the icons appear vertically
  stretched. The problem appears to be purely visual, as they still work
  as expected.

  > lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  > apt-cache policy gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
Installed: 17.10.1
Candidate: 17.10.1
Version table:
   *** 17.10.1 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+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 1810770] Re: package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinst

2019-01-07 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 freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1810770

Title:
  package libfreerdp2-2:amd64
  2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  found during upgdate

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1
  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
  Date: Mon Jan  7 10:54:57 2019
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-08-20 (139 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  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.6
  SourcePackage: freerdp2
  Title: package libfreerdp2-2:amd64 
2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1810770/+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 1810772] Re: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative

2019-01-07 Thread Gianfranco Costamagna

Olivier, can you please have a look?
firefox with the switch does build everywhere except armhf ppc64el s390x
while the current thunderbird in the archive is ftbfs even without changes.

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

Title:
  firefox/thunderbird: please drop llvm-4.0 and switch to versionless
  alternative

Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  As said, we want to remove llvm-toolchain-4.0 from the archive, and
  firefox/thunderbird are the two last blockers.

  Debian has already switched to the versionless alternative.

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+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 1810772] [NEW] firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative

2019-01-07 Thread Gianfranco Costamagna

Public bug reported:

As said, we want to remove llvm-toolchain-4.0 from the archive, and
firefox/thunderbird are the two last blockers.

Debian has already switched to the versionless alternative.

thanks

** Affects: firefox (Ubuntu)
 Importance: High
 Status: New

** Affects: thunderbird (Ubuntu)
 Importance: High
 Status: New

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

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

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

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

Title:
  firefox/thunderbird: please drop llvm-4.0 and switch to versionless
  alternative

Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  As said, we want to remove llvm-toolchain-4.0 from the archive, and
  firefox/thunderbird are the two last blockers.

  Debian has already switched to the versionless alternative.

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+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 1810770] [NEW] package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should rein

2019-01-07 Thread Phil Hedges

Public bug reported:

found during upgdate

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1
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
Date: Mon Jan  7 10:54:57 2019
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-08-20 (139 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
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.6
SourcePackage: freerdp2
Title: package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libfreerdp2-2:amd64
  2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  found during upgdate

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1
  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
  Date: Mon Jan  7 10:54:57 2019
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-08-20 (139 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  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.6
  SourcePackage: freerdp2
  Title: package libfreerdp2-2:amd64 
2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1810770/+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 1810771] [NEW] HPLIP hp-systray tray icon does not show dropdown menu in Unity Panel on 18.04 LTS

Public bug reported:

Steps to reproduce:
1. Install Ubuntu 18.04 LTS with `ubuntu-unity-desktop`  all updates
2. Install HPLIP into it with `sudo apt install hplip-gui`
3. Log out.

Expected results:
* HPLIP shows hp-systray icon and its fully functional

Actual results:
* HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: hplip-gui 3.17.10+repack0-5
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
CupsErrorLog:
 W [14/Aug/2018:13:47:13 +0300] Notifier for subscription 25 (dbus://) went 
away, retrying!
 W [07/Jan/2019:13:51:06 +0300] Notifier for subscription 39 (dbus://) went 
away, retrying!
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Jan  7 14:00:31 2019
InstallationDate: Installed on 2018-04-28 (253 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b7cab74d-ae3c-460b-95fe-5f8e8a45ff56 ro quiet splash
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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

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


** Tags: apport-bug bionic

** Attachment added: "hp-systray - dropdown menu malfunction on Unity"
   
https://bugs.launchpad.net/bugs/1810771/+attachment/5227386/+files/hplip1804-unity.png

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

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in Unity Panel
  on 18.04 LTS

Status in hplip package in Ubuntu:
  New
Status in ubuntu-unity-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS with `ubuntu-unity-desktop`  all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: hplip-gui 3.17.10+repack0-5
  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
  CupsErrorLog:
   W [14/Aug/2018:13:47:13 +0300] Notifier for subscription 25 (dbus://) went 
away, retrying!
   W [07/Jan/2019:13:51:06 +0300] Notifier for subscription 39 (dbus://) went 
away, retrying!
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan  7 14:00:31 2019
  InstallationDate: Installed on 2018-04-28 (253 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b7cab74d-ae3c-460b-95fe-5f8e8a45ff56 ro quiet splash
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS

** Summary changed:

- HPLIP hp-systray does not show dropdown menu in MATE Panel on 18.04 LTS
+ HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 
LTS

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

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS

Status in hplip package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  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: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1810745/+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 1810016] Re: Graphics does not support

I'm not sure if it's related but you seem to have an Nvidia driver
installed, despite only having an Intel GPU...

DkmsStatus:
 nvidia, 390.87, 4.15.0-42-generic, x86_64: installed
 nvidia, 390.87, 4.15.0-43-generic, x86_64: installed

Can you please explain in more detail what problem you see?

** Changed in: xorg (Ubuntu)
 Assignee: SHELVY S (sshelvys) => (unassigned)

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

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

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

Title:
  Graphics does not support

Status in Ubuntu:
  Incomplete

Bug description:
  It is showing that the display is unknown

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 29 10:35:12 2018
  DistUpgraded: 2018-11-22 15:13:57,824 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.15.0-42-generic, x86_64: installed
   nvidia, 390.87, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0493]
  InstallationDate: Installed on 2017-07-22 (524 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=65ea9fa8-00d1-4bde-8e46-490e91f42ca2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (36 days ago)
  dmi.bios.date: 08/12/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M2610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd08/12/2011:svnAcer:pnAspireSeries:pvr:rvnAcer:rnVeritonM2610:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire Series
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov 22 11:24:31 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1405 
   vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.8

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