[Desktop-packages] [Bug 1806226] Re: Dell C2665dnf gets broken installation

2018-12-04 Thread Jerry Quinn
I get the same issue.  Printing a test page on this queue gives me the
same PDL error.

What package should this bug be assigned to?

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

Title:
  Dell C2665dnf gets broken installation

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  My apologies if this is the wrong package to file this bug against...

  I just installed 18.04 on a new machine.  Very conveniently, it found
  my Dell C2665dnf printer and set up an ipp printer for it.
  Unfortunately, the printer configuration doesn't work.  Printing a
  test page gives 016-720 PDL error.

  I can install the Dell-created printer filter and PPD and create a
  printer that works fine, and I have this setup on another 18.04
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 01:28:28 2018
  InstallationDate: Installed on 2018-12-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat:
   device for Dell-C2665dnf-Color-MFP: 
dnssd://Dell%20C2665dnf%20Color%20MFP%20(D3%3A8E%3AA3)._pdl-datastream._tcp.local/?uuid=e72bf300-1dd2-11b2-ad7c-080037d38ea3
   device for Dell_C2665dnf_Color_MFP_D3_8E_A3_: 
ipp://Dell-C2665dnf-D38EA3.local:631/ipp/print
  MachineType: LENOVO 2344BPU
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Dell_C2665dnf_Color_MFP_D3_8E_A3_.ppd', 
'/etc/cups/ppd/Dell-C2665dnf-Color-MFP.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Dell_C2665dnf_Color_MFP_D3_8E_A3_.ppd: Permission denied
   grep: /etc/cups/ppd/Dell-C2665dnf-Color-MFP.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2344BPU
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn2344BPU:pvrThinkPadT430:rvnLENOVO:rn2344BPU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2344BPU
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1806817] Re: PKCS#7 signature not signed with a trusted key

2018-12-04 Thread Daniel van Vugt
Sounds like bug 1798863.

Please run this command to send us more system info:

  apport-collect 1806817

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Incomplete

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Incomplete

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

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

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

Title:
  PKCS#7 signature not signed with a trusted key

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Incomplete

Bug description:
  It's hard to report this bug on a laptop with this driver installed,
  so I'm reporting this with on my laptop with a much newer NVIDIA
  driver (but not recommended).

  My laptop, Lenovo Z40, has NVIDIA GeForce GT820M.  With nvidia-340
  driver installed it won't boot to SDDM (also tried with LightDM).
  Opening up another TTY is useless because the same message "PKCS#7
  signature not signed with a trusted key" keeps getting spammed.  I had
  to go to recovery to switch to Intel graphics.

  [CODE]
  $ lspci
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
  [/CODE]

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

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


[Desktop-packages] [Bug 1806165] Re: Ubuntu 18.10 I get logged off on resume from suspend - Unregistered Authentication Agent for unix-session

2018-12-04 Thread Daniel van Vugt
Do you have a password set? I'm wondering if bug 1803527 is related.

** Tags added: nvidia

** Summary changed:

- Ubuntu 18.10 I get logged off on resume from suspend - Unregistered 
Authentication Agent for unix-session
+ [nvidia] Ubuntu 18.10 I get logged off on resume from suspend - Unregistered 
Authentication Agent for unix-session

** Tags added: resume suspend-resume

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

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

Title:
  [nvidia] Ubuntu 18.10 I get logged off on resume from suspend -
  Unregistered Authentication Agent for unix-session

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is not a problem using only built in laptop screen however when I
  attach an external monitor and choose

  Setting->Display->Single Display

  then choose the external monitor to be the only active screen -> then
  when I suspend upon resume the external monitor lights up showing the
  password prompt which is good however after entering password all my
  launched applications are no longer running ... according to
  /var/log/auth.log I get logged out during this suspend/resume - this
  issue is repeatable

  getting same behaviour whether using nouveau or nvidia drivers ... its
  a fresh 18.10 install not an upgrade

  Here is a clip from /var/log/auth.log look closely at messages just
  after `Lid opened`

  -

  Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session opened for 
user root by (uid=0)
  Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session closed for 
user root
  Nov 30 21:20:18 nuem gnome-keyring-daemon[3057]: asked to register item 
/org/freedesktop/secrets/collection/login/863, but it's already registered
  Nov 30 21:20:19 nuem gnome-keyring-daemon[3057]: asked to register item 
/org/freedesktop/secrets/collection/login/862, but it's already registered
  Nov 30 21:40:36 nuem gnome-keyring-daemon[3057]: asked to register item 
/org/freedesktop/secrets/collection/login/1, but it's already registered
  Nov 30 21:40:39 nuem gnome-keyring-daemon[3057]: message repeated 2 times: [ 
asked to register item /org/freedesktop/secrets/collection/login/1, but it's 
already registered]
  Nov 30 21:49:25 nuem systemd-logind[523]: Lid closed.
  Nov 30 21:49:29 nuem systemd-logind[523]: Lid opened.
  Nov 30 21:49:51 nuem systemd-logind[523]: Operation 'sleep' finished.
  Nov 30 21:49:52 nuem polkitd(authority=local): Unregistered Authentication 
Agent for unix-session:2 (system bus name :1.376, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Nov 30 21:49:52 nuem gdm-password]: pam_unix(gdm-password:session): session 
closed for user upha
  Nov 30 21:49:52 nuem dbus-daemon[507]: [system] Rejected send message, 2 
matched rules; type="method_call", sender=":1.2100" (uid=1000 pid=31115 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error 
name="(unset)" requested_reply="0" destination="org.bluez" (bus)
  Nov 30 21:49:52 nuem systemd-logind[523]: Session 2 logged out. Waiting for 
processes to exit.
  Nov 30 21:49:53 nuem gdm-launch-environment]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
  Nov 30 21:49:53 nuem systemd-logind[523]: New session c2 of user gdm.
  Nov 30 21:49:53 nuem systemd: pam_unix(systemd-user:session): session opened 
for user gdm by (uid=0)
  Nov 30 21:49:55 nuem systemd-logind[523]: Removed session 2.
  Nov 30 21:49:56 nuem systemd: pam_unix(systemd-user:session): session closed 
for user upha
  Nov 30 21:49:57 nuem polkitd(authority=local): Registered Authentication 
Agent for unix-session:c2 (system bus name :1.2108 [/usr/bin/gnome-shell], 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Nov 30 21:50:07 nuem gdm-password]: pam_unix(gdm-password:session): session 
opened for user upha by (uid=0)
  Nov 30 21:50:07 nuem systemd-logind[523]: New session 37 of user upha.
  Nov 30 21:50:07 nuem systemd: pam_unix(systemd-user:session): session opened 
for user upha by (uid=0)
  Nov 30 21:50:17 nuem polkitd(authority=local): Registered Authentication 
Agent for unix-session:37 (system bus name :1.2405 [/usr/bin/gnome-shell], 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Nov 30 21:50:19 nuem systemd-logind[523]: Session c2 logged out. Waiting for 
processes to exit.
  Nov 30 21:50:19 nuem polkitd(authority=local): Unregistered Authentication 
Agent for unix-session:c2 (system bus name :1.2108, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Nov 30 21:50:19 nuem 

[Desktop-packages] [Bug 1806817] Re: PKCS#7 signature not signed with a trusted key

2018-12-04 Thread Jonty Gamao
One thing I forgot to mention: nvidia-prime is also broken on
nvidia-340.  Even with Intel graphics in use instead of NVIDIA, the
laptop remains unusable.

It's fine for newer drivers, like nvidia-driver-415

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

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

Title:
  PKCS#7 signature not signed with a trusted key

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  It's hard to report this bug on a laptop with this driver installed,
  so I'm reporting this with on my laptop with a much newer NVIDIA
  driver (but not recommended).

  My laptop, Lenovo Z40, has NVIDIA GeForce GT820M.  With nvidia-340
  driver installed it won't boot to SDDM (also tried with LightDM).
  Opening up another TTY is useless because the same message "PKCS#7
  signature not signed with a trusted key" keeps getting spammed.  I had
  to go to recovery to switch to Intel graphics.

  [CODE]
  $ lspci
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
  [/CODE]

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

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


[Desktop-packages] [Bug 1806817] [NEW] PKCS#7 signature not signed with a trusted key

2018-12-04 Thread Jonty Gamao
Public bug reported:

It's hard to report this bug on a laptop with this driver installed, so
I'm reporting this with on my laptop with a much newer NVIDIA driver
(but not recommended).

My laptop, Lenovo Z40, has NVIDIA GeForce GT820M.  With nvidia-340
driver installed it won't boot to SDDM (also tried with LightDM).
Opening up another TTY is useless because the same message "PKCS#7
signature not signed with a trusted key" keeps getting spammed.  I had
to go to recovery to switch to Intel graphics.

[CODE]
$ lspci
03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / 
GT 620M/625M/630M/720M] (rev a1)
[/CODE]

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  PKCS#7 signature not signed with a trusted key

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  It's hard to report this bug on a laptop with this driver installed,
  so I'm reporting this with on my laptop with a much newer NVIDIA
  driver (but not recommended).

  My laptop, Lenovo Z40, has NVIDIA GeForce GT820M.  With nvidia-340
  driver installed it won't boot to SDDM (also tried with LightDM).
  Opening up another TTY is useless because the same message "PKCS#7
  signature not signed with a trusted key" keeps getting spammed.  I had
  to go to recovery to switch to Intel graphics.

  [CODE]
  $ lspci
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
  [/CODE]

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

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


[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault onb PDF using -dFirstPage and -dLastPage

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
http://bugs.ghostscript.com/show_bug.cgi?id=700315.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-03T16:49:41+00:00 Bheeshmar wrote:

We use ImageMagick to extract a the first page of a PDF as a thumbnail
and recently started getting exceptions with some PDFs. Traced it to the
call that ImageMagick was making:

gs  -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5
-dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4
-dGraphicsAlphaBits=4 '-r72x72' -dLastPage=1 -sOutputFile=1.png -f
Bloomfire-Security_and_Redundancy.pdf

When this is run with GS version 9.25, the thumbnail is extracted with no error.
When this is run with GS version 9.26, I see "Segmentation fault: 11"

I've attached a file that causes there error. Observed on both OSX and
Ubuntu Linux.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/1


On 2018-12-03T16:50:51+00:00 Bheeshmar wrote:

Created attachment 16470
Output of run with -dDEBUG

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/2


On 2018-12-03T16:51:24+00:00 Bheeshmar wrote:

Created attachment 16471
PDF example that causes the segfault

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/3


On 2018-12-04T00:47:14+00:00 Ken Sharp wrote:


*** This bug has been marked as a duplicate of bug 699815 ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/4


On 2018-12-04T21:05:41+00:00 Ken Sharp wrote:

*** Bug 700314 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/13


On 2018-12-04T21:10:10+00:00 Ken Sharp wrote:

*** Bug 700313 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/14


On 2018-12-04T21:32:36+00:00 Ken Sharp wrote:

Fixed in commit fae21f1668d2b44b18b84cf0923a1d5f3008a696

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517/comments/15


** Changed in: gs-gpl
   Status: Unknown => Fix Released

** Changed in: gs-gpl
   Importance: Unknown => Medium

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This 

[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault onb PDF using -dFirstPage and -dLastPage

2018-12-04 Thread Laurent Dinclaux
I have changed the upstream related bug which has been resolved (patch
available)

** No longer affects: gs-gpl

** Bug watch added: Ghostscript (AFPL) Bugzilla #700315
   http://bugs.ghostscript.com/show_bug.cgi?id=700315

** Also affects: gs-gpl via
   http://bugs.ghostscript.com/show_bug.cgi?id=700315
   Importance: Unknown
   Status: Unknown

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

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

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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


[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location

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

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

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in cinnamon-desktop-environment package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Mint 17.3 Cinnamon 64bit.

  Steps to reproduce:
   * Do a fresh install.
   * Run mintupdate and update all packages.
   * Run firefox. 
   * Start right clicking on the page to open the context menu. Resize the 
window and perhaps move it around the screen a couple of times. Right click 
some more. 
   * Observer that, eventually, the context menu will start to appear in 
incorrect locations on the screen. The same also happens with the search bar, 
text fields and any other dropdown box.

  In the worst embodiment of the bug, the menu opens underneath the
  pointer and treats the release of the mouse button as a click, and so
  does things the user does not want to do.

  I believe the root cause is the following bug in GTK+ 3.10.8. Firefox
  switched over to using GTK+3 in version 46 which is when this bug
  appeared and has been there ever since.

  https://bugzilla.gnome.org/show_bug.cgi?id=758609
  https://bugzilla.mozilla.org/show_bug.cgi?id=1022241

  Mozilla aren't going to fix it because it's a GTK bug. GTK have
  already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not
  have the patch.

  Please roll out the patch for us 17.3 users who cannot upgrade. I can
  confirm that the problem is solved in Mint 18.

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

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


[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location

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

** Changed in: cinnamon-desktop-environment (Ubuntu)
   Status: New => Confirmed

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in cinnamon-desktop-environment package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Mint 17.3 Cinnamon 64bit.

  Steps to reproduce:
   * Do a fresh install.
   * Run mintupdate and update all packages.
   * Run firefox. 
   * Start right clicking on the page to open the context menu. Resize the 
window and perhaps move it around the screen a couple of times. Right click 
some more. 
   * Observer that, eventually, the context menu will start to appear in 
incorrect locations on the screen. The same also happens with the search bar, 
text fields and any other dropdown box.

  In the worst embodiment of the bug, the menu opens underneath the
  pointer and treats the release of the mouse button as a click, and so
  does things the user does not want to do.

  I believe the root cause is the following bug in GTK+ 3.10.8. Firefox
  switched over to using GTK+3 in version 46 which is when this bug
  appeared and has been there ever since.

  https://bugzilla.gnome.org/show_bug.cgi?id=758609
  https://bugzilla.mozilla.org/show_bug.cgi?id=1022241

  Mozilla aren't going to fix it because it's a GTK bug. GTK have
  already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not
  have the patch.

  Please roll out the patch for us 17.3 users who cannot upgrade. I can
  confirm that the problem is solved in Mint 18.

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

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


[Desktop-packages] [Bug 1767552] Re: screen rotates if laptop tilts

2018-12-04 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  screen rotates if laptop tilts

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I have ran windows 7, 10, ubuntu 16.04, linux mint and maybe others
  and i can't recall it doing this before. it is hp 450 g2 laptop. it is
  not a 2in1 tablet/laptop. i looked for info in forums but had no luck.
  i also checked in settings because i thought it may have had a tablet
  setting i could turn off.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 21:58:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:2248]
 Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d0b638ce-09f3-4d54-a78f-b7aeebaef22f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.09
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.09:bd01/21/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3009DD10303:rvnHewlett-Packard:rn2248:rvrKBCVersion59.21:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G2
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic

2018-12-04 Thread hugh chao
seems not only one oem platform can reproduced this issue due to Bug
539477

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

Title:
  different behaviors for switch display mode between xenial and bionic

Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  When the "Fn lock" is enabled, we can switch the video mode by one key: 
video-key (Fn+F8).
  But, the key event is too frequent. It's hard to select the wanted video mode.

  Reproduce steps: Press down the Video-out hotkey

  Expected results: User can select Video mode precisely by Video-out hotkey
  Actual results: The speed of switch video mode is too fast makes can not 
select Video mode precisely

  Notebook: XPS 13

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

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


[Desktop-packages] [Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic

2018-12-04 Thread hugh chao
** Tags added: stella

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

Title:
  different behaviors for switch display mode between xenial and bionic

Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  When the "Fn lock" is enabled, we can switch the video mode by one key: 
video-key (Fn+F8).
  But, the key event is too frequent. It's hard to select the wanted video mode.

  Reproduce steps: Press down the Video-out hotkey

  Expected results: User can select Video mode precisely by Video-out hotkey
  Actual results: The speed of switch video mode is too fast makes can not 
select Video mode precisely

  Notebook: XPS 13

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

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


[Desktop-packages] [Bug 1806797] Re: Frozen (black) screen on resume/unlock

2018-12-04 Thread Daniel van Vugt
Please test "Ubuntu on Wayland" so that we can see if the problem is in
code that's common to both.

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

Title:
  Frozen (black) screen on resume/unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a monitor to which I connect using an HDMI cable.
  While connected, I have 2 displays and I can use both fine.
  When I disconnect, it is also fine, until I close the laptop or it goes to 
sleep.
  When it wakes up, I get the unlock/login screen, and I can login fine as 
anyone but myself.
  When I login as myself (i.e., unlock the screen rather than login), I get a 
completely black screen.
  I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an 
attempt to unlock with the same result - black screen.
  My only options appears to be reboot or kill the X server from the console 
(Ctrl-Alt-F2, login and kill).
  This started to happen recently (a month?)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 21:18:19 2018
  DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: 
installed
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  MachineType: System76, Inc. Gazelle Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.04SB.01RSY5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Gazelle Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: gazp9c
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 14 23:40:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault onb PDF using -dFirstPage and -dLastPage

2018-12-04 Thread Bug Watch Updater
** Changed in: gs-gpl
   Status: New => Invalid

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

Status in GS-GPL:
  Invalid
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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


[Desktop-packages] [Bug 1806804] Re: /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package 'libglvnd-dev' being installed

2018-12-04 Thread Daniel van Vugt
Workaround:

sudo apt install --reinstall libglvnd-dev

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

Title:
  /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package
  'libglvnd-dev' being installed

Status in libglvnd package in Ubuntu:
  New

Bug description:
  /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package
  'libglvnd-dev' being installed.

  $ dpkg -L libglvnd-dev
  /.
  /usr
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/share
  /usr/share/bug
  /usr/share/bug/libglvnd-dev
  /usr/share/bug/libglvnd-dev/control
  /usr/share/doc
  /usr/share/doc/libglvnd-dev
  /usr/share/doc/libglvnd-dev/copyright
  /usr/lib/x86_64-linux-gnu/libEGL.so
  /usr/lib/x86_64-linux-gnu/libGL.so
  /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so
  /usr/lib/x86_64-linux-gnu/libGLESv2.so
  /usr/lib/x86_64-linux-gnu/libGLX.so
  /usr/lib/x86_64-linux-gnu/libGLdispatch.so
  /usr/lib/x86_64-linux-gnu/libOpenGL.so
  /usr/share/doc/libglvnd-dev/changelog.Debian.gz

  $ ls -ld `dpkg -L libglvnd-dev`
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or 
directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or 
directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so': No such file 
or directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or 
directory
  drwxr-xr-x   20 root root  4096 Dec  4 11:42 /.
  drwxr-xr-x   14 root root  4096 Dec  3 15:40 /usr
  drwxr-xr-x  156 root root  4096 Dec  5 10:49 /usr/lib
  drwxr-xr-x  100 root root 94208 Dec  5 11:15 /usr/lib/x86_64-linux-gnu
  lrwxrwxrwx1 root root22 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0
  lrwxrwxrwx1 root root15 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLX.so -> libGLX.so.0.0.0
  lrwxrwxrwx1 root root18 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libOpenGL.so -> libOpenGL.so.0.0.0
  drwxr-xr-x  284 root root 12288 Dec  5 10:49 /usr/share
  drwxr-xr-x  105 root root  4096 Dec  4 12:11 /usr/share/bug
  drwxr-xr-x2 root root  4096 Dec  4 12:11 /usr/share/bug/libglvnd-dev
  -rw-r--r--1 root root38 Aug 10 19:13 
/usr/share/bug/libglvnd-dev/control
  drwxr-xr-x 1957 root root 69632 Dec  5 11:15 /usr/share/doc
  drwxr-xr-x2 root root  4096 Dec  4 12:11 /usr/share/doc/libglvnd-dev
  lrwxrwxrwx1 root root32 Aug 10 19:50 
/usr/share/doc/libglvnd-dev/changelog.Debian.gz -> 
../libglvnd0/changelog.Debian.gz
  -rw-r--r--1 root root  4697 Aug 10 19:13 
/usr/share/doc/libglvnd-dev/copyright

  I think this was probably triggered by me installing and removing both
  nvidia-390 and nvidia-340 yesterday. So maybe it's a bug related to
  those.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libglvnd-dev 1.1.0-1
  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
  Date: Wed Dec  5 11:21:38 2018
  InstallationDate: Installed on 2018-12-04 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: libglvnd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806517]

2018-12-04 Thread Laurent Dinclaux
I have the same issue on multiple servers running ubuntu 16.04 or 18.04
since the 9.26 upgrade. In order to convert a PDF file in PNG I use the
command:

» convert "myfile.pdf[0]" test.png

Which gives this error:

convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER 
-dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

So I tried using ghostscript directly:

» ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4
-dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1
'-sOutputFile=test.png' '-fmyfile.pdf'

Which gives an error:

GPL Ghostscript 9.26 (2018-11-20)
Copyright (C) 2018 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
[1] 10954 segmentation fault (core dumped) ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

If I omit -dFirstPage=1 -dLastPage=1 it works properly:

» ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
GPL Ghostscript 9.26 (2018-11-20)
Copyright (C) 2018 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 2.
Page 1
Page 2

Please note that it also affects imagemagick convert command and PHP
readimage command.

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

Status in GS-GPL:
  Invalid
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

[Desktop-packages] [Bug 1806517]

2018-12-04 Thread Ken Sharp
*** This bug has been marked as a duplicate of bug 700315 ***

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

Status in GS-GPL:
  Invalid
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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


[Desktop-packages] [Bug 1806804] [NEW] /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package 'libglvnd-dev' being installed

2018-12-04 Thread Daniel van Vugt
Public bug reported:

/usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package
'libglvnd-dev' being installed.

$ dpkg -L libglvnd-dev
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/share
/usr/share/bug
/usr/share/bug/libglvnd-dev
/usr/share/bug/libglvnd-dev/control
/usr/share/doc
/usr/share/doc/libglvnd-dev
/usr/share/doc/libglvnd-dev/copyright
/usr/lib/x86_64-linux-gnu/libEGL.so
/usr/lib/x86_64-linux-gnu/libGL.so
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so
/usr/lib/x86_64-linux-gnu/libGLESv2.so
/usr/lib/x86_64-linux-gnu/libGLX.so
/usr/lib/x86_64-linux-gnu/libGLdispatch.so
/usr/lib/x86_64-linux-gnu/libOpenGL.so
/usr/share/doc/libglvnd-dev/changelog.Debian.gz

$ ls -ld `dpkg -L libglvnd-dev`
ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or 
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or 
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so': No such file or 
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or 
directory
drwxr-xr-x   20 root root  4096 Dec  4 11:42 /.
drwxr-xr-x   14 root root  4096 Dec  3 15:40 /usr
drwxr-xr-x  156 root root  4096 Dec  5 10:49 /usr/lib
drwxr-xr-x  100 root root 94208 Dec  5 11:15 /usr/lib/x86_64-linux-gnu
lrwxrwxrwx1 root root22 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0
lrwxrwxrwx1 root root15 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLX.so -> libGLX.so.0.0.0
lrwxrwxrwx1 root root18 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libOpenGL.so -> libOpenGL.so.0.0.0
drwxr-xr-x  284 root root 12288 Dec  5 10:49 /usr/share
drwxr-xr-x  105 root root  4096 Dec  4 12:11 /usr/share/bug
drwxr-xr-x2 root root  4096 Dec  4 12:11 /usr/share/bug/libglvnd-dev
-rw-r--r--1 root root38 Aug 10 19:13 /usr/share/bug/libglvnd-dev/control
drwxr-xr-x 1957 root root 69632 Dec  5 11:15 /usr/share/doc
drwxr-xr-x2 root root  4096 Dec  4 12:11 /usr/share/doc/libglvnd-dev
lrwxrwxrwx1 root root32 Aug 10 19:50 
/usr/share/doc/libglvnd-dev/changelog.Debian.gz -> 
../libglvnd0/changelog.Debian.gz
-rw-r--r--1 root root  4697 Aug 10 19:13 
/usr/share/doc/libglvnd-dev/copyright

I think this was probably triggered by me installing and removing both
nvidia-390 and nvidia-340 yesterday. So maybe it's a bug related to
those.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libglvnd-dev 1.1.0-1
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
Date: Wed Dec  5 11:21:38 2018
InstallationDate: Installed on 2018-12-04 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package
  'libglvnd-dev' being installed

Status in libglvnd package in Ubuntu:
  New

Bug description:
  /usr/lib/x86_64-linux-gnu/lib*GL.so are missing despite package
  'libglvnd-dev' being installed.

  $ dpkg -L libglvnd-dev
  /.
  /usr
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/share
  /usr/share/bug
  /usr/share/bug/libglvnd-dev
  /usr/share/bug/libglvnd-dev/control
  /usr/share/doc
  /usr/share/doc/libglvnd-dev
  /usr/share/doc/libglvnd-dev/copyright
  /usr/lib/x86_64-linux-gnu/libEGL.so
  /usr/lib/x86_64-linux-gnu/libGL.so
  /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so
  /usr/lib/x86_64-linux-gnu/libGLESv2.so
  /usr/lib/x86_64-linux-gnu/libGLX.so
  /usr/lib/x86_64-linux-gnu/libGLdispatch.so
  /usr/lib/x86_64-linux-gnu/libOpenGL.so
  /usr/share/doc/libglvnd-dev/changelog.Debian.gz

  $ ls -ld `dpkg -L libglvnd-dev`
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or 
directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or 
directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so': No such file 
or directory
  ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or 
directory
  drwxr-xr-x   20 root root  4096 Dec  4 11:42 /.
  drwxr-xr-x   14 root root  4096 Dec  3 15:40 /usr
  drwxr-xr-x  156 root root  4096 Dec  5 10:49 /usr/lib
  drwxr-xr-x  100 root root 94208 Dec  5 11:15 /usr/lib/x86_64-linux-gnu
  lrwxrwxrwx1 root root22 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0
  lrwxrwxrwx1 root root15 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libGLX.so -> libGLX.so.0.0.0
  lrwxrwxrwx1 root root18 Aug 10 19:50 
/usr/lib/x86_64-linux-gnu/libOpenGL.so -> libOpenGL.so.0.0.0
  drwxr-xr-x  284 root root 12288 Dec  5 10:49 /usr/share
  drwxr-xr-x  

[Desktop-packages] [Bug 1806797] Re: Frozen (black) screen on resume/unlock

2018-12-04 Thread sds
I don't use Wayland.

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

Title:
  Frozen (black) screen on resume/unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a monitor to which I connect using an HDMI cable.
  While connected, I have 2 displays and I can use both fine.
  When I disconnect, it is also fine, until I close the laptop or it goes to 
sleep.
  When it wakes up, I get the unlock/login screen, and I can login fine as 
anyone but myself.
  When I login as myself (i.e., unlock the screen rather than login), I get a 
completely black screen.
  I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an 
attempt to unlock with the same result - black screen.
  My only options appears to be reboot or kill the X server from the console 
(Ctrl-Alt-F2, login and kill).
  This started to happen recently (a month?)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 21:18:19 2018
  DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: 
installed
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  MachineType: System76, Inc. Gazelle Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.04SB.01RSY5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Gazelle Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: gazp9c
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 14 23:40:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start

2018-12-04 Thread Anup Khanal
** Changed in: hundredpapercuts
   Status: Incomplete => Confirmed

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

Title:
  NetworkManager does not start / fails to start

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]:   monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]:   keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1")
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]:   urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   wpa_supplicant running
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ModemManager available in 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ofono is now available
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemAdded' is invalid for instance
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemRemoved' is invalid for instan
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed
  Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a 
sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000]
  Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, 
code=dumped, status=11/SEGV
  Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: 

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

2018-12-04 Thread Anup Khanal
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1791283] Re: Cannot open files in required application with double click or open with in ftp Nautilus

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

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

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

Title:
  Cannot open files in required application with double click or open
  with in ftp Nautilus

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  For more information, see https://askubuntu.com/questions/964747
  /cannot-open-text-editor-with-double-click-in-ftp-
  nautilus/1067423#1067423

  When an FTP server is open in Nautilus and a file is either double
  clicked or right clicked and opened with (and app chosen from the
  menu), it always downloads the files with the default browser, rather
  than open in the requested application.

  One of the times this becomes a massive issue is when you are
  connected to an ftp web server and want to test changes in code live.
  This means you now have to download the file, open it, edit it, and
  re-upload. In the past for minor changes or in a test environment, it
  has been WAY faster to open the file directly in a txt editor, then
  just save and see the changes instantly.

  This is still working in Ubuntu 16.04. I have it failing in 18.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 20:57:42 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+217+129'"
  InstallationDate: Installed on 2018-08-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1806797] Re: Xorg freeze

2018-12-04 Thread Daniel van Vugt
Does the problem only occur in Xorg sessions (the "Ubuntu" login
option)? Or does it also occur in "Ubuntu on Wayland" sessions?

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

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

** Summary changed:

- Xorg freeze
+ Frozen (black) screen on resume/unlock

** Tags added: black-screen resume suspend-resume

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

Title:
  Frozen (black) screen on resume/unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a monitor to which I connect using an HDMI cable.
  While connected, I have 2 displays and I can use both fine.
  When I disconnect, it is also fine, until I close the laptop or it goes to 
sleep.
  When it wakes up, I get the unlock/login screen, and I can login fine as 
anyone but myself.
  When I login as myself (i.e., unlock the screen rather than login), I get a 
completely black screen.
  I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an 
attempt to unlock with the same result - black screen.
  My only options appears to be reboot or kill the X server from the console 
(Ctrl-Alt-F2, login and kill).
  This started to happen recently (a month?)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 21:18:19 2018
  DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: 
installed
   system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  MachineType: System76, Inc. Gazelle Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.04SB.01RSY5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Gazelle Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: gazp9c
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 14 23:40:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1806797] [NEW] Xorg freeze

2018-12-04 Thread sds
Public bug reported:

I have a monitor to which I connect using an HDMI cable.
While connected, I have 2 displays and I can use both fine.
When I disconnect, it is also fine, until I close the laptop or it goes to 
sleep.
When it wakes up, I get the unlock/login screen, and I can login fine as anyone 
but myself.
When I login as myself (i.e., unlock the screen rather than login), I get a 
completely black screen.
I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an attempt 
to unlock with the same result - black screen.
My only options appears to be reboot or kill the X server from the console 
(Ctrl-Alt-F2, login and kill).
This started to happen recently (a month?)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec  4 21:18:19 2018
DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: 
installed
 system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: 
installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
MachineType: System76, Inc. Gazelle Pro
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago)
dmi.bios.date: 06/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.04SB.01RSY5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Gazelle Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp9c
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Gazelle Pro
dmi.product.sku: Not Applicable
dmi.product.version: gazp9c
dmi.sys.vendor: System76, Inc.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Sat Oct 14 23:40:31 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug cosmic freeze third-party-packages 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/1806797

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a monitor to which I connect using an HDMI cable.
  While connected, I have 2 displays and I can use both fine.
  When I disconnect, it is also fine, until I close the laptop or it goes to 
sleep.
  When it wakes up, I get the unlock/login screen, and I can login fine as 
anyone but myself.
  When I login as myself (i.e., unlock the screen rather than login), I get a 
completely black screen.
  I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an 
attempt to unlock with the same result - black screen.
  My only options appears to be reboot or kill the X server from the console 
(Ctrl-Alt-F2, login and kill).
  This started to happen recently (a month?)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  

[Desktop-packages] [Bug 1806448] Re: Dragging a window to the edge of the screen does not tile/semi-maximize it (for some apps)

2018-12-04 Thread Daniel van Vugt
Thanks.

I can't reproduce the bug myself. Are you using multiple monitors?

** Summary changed:

- dragging a window to the edge of the screen does not produce the desired 
effect
+ Dragging a window to the edge of the screen does not tile/semi-maximize it 
(for some apps)

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

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

Title:
  Dragging a window to the edge of the screen does not tile/semi-
  maximize it (for some apps)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Have a relatively fresh installation of Ubuntu 18.10. Unfortunately, I just 
had to realize that dragging windows to the left or right edge unfortunately 
does not have the desired effect in a number of cases that they fill half the 
screen. This applies to the following apps, among others:
  - LibreOffice
  - Nautilus
  - Gnome Calendar
  - Gnome Tasks
  - Settings
  Seems to be the same in a wayland and X Session. Especially the problem with 
LibreOffice makes working almost impossible for me. 

  Should not necessarily be part of a bug report, but I'm thinking about
  switching back to Unity or another desktop environment, as the Gnome
  desktop doesn't seem to be mature for a long time (I've already
  reported well over 10 bugs now).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 18:09:43 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-30 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806795] [NEW] Inkscape "space between lines" changes by itself.

2018-12-04 Thread Joe Crollard
Public bug reported:

This is a really strange bug, so it's hard to explain. I recorded a
video to make it easier to understand, but when I select some text, and
click something like "change space between letters" a few times.. it
just keeps going and going. The numbers keep increasing without me
clicking anything. If I click on a separate object of text it continues.
I'm running Kubuntu 18.10. Inkscape is installed from the main repos.

I installed the flatpak version of Inkscake and this bug does not occcur
with it.

Video is attached.

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

** Attachment added: "Screencast 2018-12-04 17:51:00.mp4"
   
https://bugs.launchpad.net/bugs/1806795/+attachment/5219198/+files/Screencast%202018-12-04%2017%3A51%3A00.mp4

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

Title:
  Inkscape "space between lines" changes by itself.

Status in inkscape package in Ubuntu:
  New

Bug description:
  This is a really strange bug, so it's hard to explain. I recorded a
  video to make it easier to understand, but when I select some text,
  and click something like "change space between letters" a few times..
  it just keeps going and going. The numbers keep increasing without me
  clicking anything. If I click on a separate object of text it
  continues. I'm running Kubuntu 18.10. Inkscape is installed from the
  main repos.

  I installed the flatpak version of Inkscake and this bug does not
  occcur with it.

  Video is attached.

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

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

2018-12-04 Thread Daniel van Vugt
It looks like you're also running skypeforlinux, slack and more. Please
try with all apps closed (just log out and log in again). Is the power
usage still high with zero apps?

-- 
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 1802569] Re: RM openssl1.0 from Ubuntu

2018-12-04 Thread Bug Watch Updater
** Changed in: ruby-eventmachine (Debian)
   Status: Unknown => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

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

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

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

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


[Desktop-packages] [Bug 1797381] Re: In tablet mode, step "Who are you" OSK hides when the passwordd field is focused

2018-12-04 Thread Daniel van Vugt
Maybe merge with bug 1760399?

** Tags added: osk

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

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

Title:
  In tablet mode, step "Who are you" OSK hides when the passwordd field
  is focused

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Test Case:
  1. On a 2 in 1 in tablet mode, launch the installer and proceed to the user 
setup step (Who are you)
  2. With the OSK, enter the username, login, hostname and password then 
proceed zith the rest of the installation

  Actual result
  The OSK hides when the password field has the focus and the user cannot enter 
a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 15:15:14 2018
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  InstallationDate: Installed on 2018-10-11 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797377] Re: In tablet mode, OSK is not displayed in the WiFi network auth dialog

2018-12-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1760399 ***
https://bugs.launchpad.net/bugs/1760399

I think we should use bug 1760399.

** Tags added: osk

** This bug has been marked a duplicate of bug 1760399
   New On-screen keyboard does not appear automatically when selecting some 
text fields

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

Title:
  In tablet mode, OSK is not displayed in the WiFi network auth dialog

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Test Case:
  1. On a 2 in 1 laptop, use it in table mode
  2. Start the installer and proceed to the WiFi step
  3. Connect to an authenticated network
  4. Type the password and authenticate

  Actual result
  The OSK is not displayed and the user cannot enter his password

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 15:10:11 2018
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  InstallationDate: Installed on 2018-10-11 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1768786] Re: Desktop is displayed when resuming from suspend

2018-12-04 Thread Daniel van Vugt
Removed the uncompleted tasks. Please use bug 1532508 instead.

** No longer affects: budgie-desktop (Ubuntu)

** No longer affects: ubuntu-unity-meta (Ubuntu)

** No longer affects: budgie-desktop (Ubuntu Bionic)

** No longer affects: ubuntu-unity-meta (Ubuntu Bionic)

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

Title:
  Desktop is displayed when resuming from suspend

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Failing to trigger lockscreen before suspend compromises user privacy. 

  [Test case]
  1.  Open Settings -> Privacy and make sure that "Automatic screen lock" is 
OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Make sure that the lockscreen is shown on resume and that you can't see 
the desktop

  [Regression Potential]
  System fails to lock before suspend when "Automatic screen lock" is ON.

  [Original Bug]

  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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


[Desktop-packages] [Bug 1428307] Re: when screen is locked and I open my laptop, a past screen is flashed

2018-12-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1768786 ***
https://bugs.launchpad.net/bugs/1768786

This bug report got missed because it was logged in the wrong category.
Graphical issues relating to the login and lock screens are still gnome-
shell issues.

The problem was mainly discussed in bug 1532508. Then bug 1768786 was
opened and it was declared fixed for gnome-shell version
3.28.2-0ubuntu0.18.04.1. Please comment in one of those bugs if you feel
the fix isn't working.


** This bug has been marked a duplicate of bug 1768786
   Desktop is displayed when resuming from suspend

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

Title:
  when screen is locked and I open my laptop, a past screen is flashed

Status in gdm package in Ubuntu:
  New
Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  I close my laptop, which locks the screen. I then open the laptop.
  Sometimes I must hit the power button to get the screen to unlock. But
  before I see the password prompt, I see something else.

  I see a past random screen. It goes by quickly, in less than a second.
  But this is still not acceptable. The screen should not show _any_
  information before the user has logged in.

  It would not be bad if I could somehow determine what this screen is,
  because then I would make sure it is blank. But it seems random.
  Sometimes it seems to be the screen I had visible when I closed up the
  laptop. Sometimes it seems to be the screen I had visible at one of
  the last several times I closed the laptop. It does not seem very
  deterministic. It is hard to know which screen it is going to flash at
  me before the password prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:30:51 2015
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: 1: AppId = gedit, Flags = 1, Reason = There are 
unsaved documents
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-01-31 (397 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (202 days ago)

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

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


[Desktop-packages] [Bug 1576859] Re: Graphics corruption when resuming from suspend

2018-12-04 Thread Daniel van Vugt
** Summary changed:

- Graphical glitches when resuming from suspend
+ Graphics corruption when resuming from suspend

** Summary changed:

- Graphics corruption when resuming from suspend
+ [nvidia] Graphics corruption when resuming from suspend

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

Title:
  [nvidia] Graphics corruption when resuming from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Resuming from suspend results in graphical glitches. These glitches,
  at least on the cover screen(shows date/time) go away when the Hard
  Drive spins back up. Additional corruption can occur in overview on
  currently active applications(Such as Chromium).

  Description:   Ubuntu 16.04 LTS
  Release:  16.04

  gnome-shell:
Installed: 3.18.4-0ubuntu3
Candidate: 3.18.4-0ubuntu3
Version table:
   *** 3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 29 15:56:14 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-23 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

2018-12-04 Thread Dimitri John Ledkov
** No longer affects: ekiga (Debian)

** No longer affects: opal (Debian)

** No longer affects: ptlib (Debian)

** No longer affects: t38modem (Debian)

** Also affects: ruby-eventmachine (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: Debian Bug tracker #900160
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900160

** Also affects: ruby-eventmachine (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900160
   Importance: Unknown
   Status: Unknown

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

Title:
  RM openssl1.0 from Ubuntu

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

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

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

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


[Desktop-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04

2018-12-04 Thread William.Yeung
Dear Till,
  I'am very sorry to bother you again.
We are still working hard to looking for cause why Ubuntu 16.04 printing 
performance slowdown.
  We figure out that there are many cause may slowdown the print job.
The other cause than OS may slowdown the print job, and we are working on those 
cause’s investigation.
Here are some slowdown point about OS issues that we can't investigation 
deeper, we hope that you(or your team) can offer a help for the investigation.

  The phenomenon that print jobs slower in 16.04 is more obvious when 
printing many single page jobs in the same time. 
We use a printing manual to simulate the continuous printing. The printing 
result shows that Ubuntu 16.04 is slower than 14.04.

Below is the printing time:

Ubuntu 14.04:
Round 1: 12.86(s)
Round 2: 12.56(s)
Aver: 12.73(s)

Ubuntu 16.04:
Round 1: 14.09(s)
Round 2: 13.98(s)
Aver: 14.29(s)




Attach file introduction:

Test log:

\PS_Driver_log\PS_Driver_log\Log\error_log20181204_14.04Origin_A4_7ods_job47_53

\PS_Driver_log\PS_Driver_log\Log\error_log20181204_16.04Origin_A4_7ods_job83_89

Test Driver:
\PS_Driver_log\PS_Driver\Ricoh-Basic-PS-PPDv1.12.1.tar.gz

Test file:
\PS_Driver_log\Testfile\testlinux.ods

Printing manual:
\PS_Driver_log.zip\TestManualOfContinuousPrinting.docx


By the way, the printing performance is unstable, some times the
slowdown of Ubuntu 16.04 is obvious. But what we can confirm is that
Ubuntu 16.04 is slower all the time.

We appreciate that you can do we a favor on the investigation why
16.04's printing performance slowdown.

Best Regards,


** Attachment added: "PS_Driver_log.zip"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+attachment/5219187/+files/PS_Driver_log.zip

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

Title:
  Printing job in 16.04 is slower than in 14.04

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04LTS
  OS Version:   16.04.5
  CUPS Version: 2.1.3
  Ghostscript Version:  9.25 (2018-09-13)

  Printing job in 16.04 is slower than in 14.04

  We(RICOH printer driver developer) are report a problem from our printer 
users:
  I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

  But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
  print the same file with the same driver is slow(326 Seconds).

  I figure out that all the print jobs is much slower on Ubuntu 16.04.

  I view the "CUPS Error Log",   it shows that there are three points
  which maybe the reasons that makes the print job slowly.

  
  FIRST:
  
  By counting the time from "Starting renderer" to "renderer exited with status 
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
  So we assuming that:"renderer" is one of the key process that makes the print 
job slowly.

  "Starting renderer with command: \"printf \'\\033%%-12345X@PJL 
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\  @PJL 
EOJ\\012\\033%%-12345X\'\""
  .
  renderer exited with status 0"
  


  SECOND:
  
  On 16.04, a print job outputs lots of logs as below:
  "[Job xxx] Removing document files."

  This step(“Removing document files”)does not exsit on 14.04.
  

  
  The phenomenon that print jobs slower in 16.04 is more obvious when printing 
many jobs in the same time.

  THIRD
  We tried drivers form other company(HP,Brother…), the printings also slow 
down in Ubuntu 16.04 than 14.04.

  Our question is:
  1. Do you have any plan to improve the performance of printing on Ubuntu 
16.04?
  2. Do you have any workaround before this problems fixed?

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

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


[Desktop-packages] [Bug 1806788] Re: ubuntu-geoip-provider crashed with SIGSEGV in raise()

2018-12-04 Thread Apport retracing service
*** This bug is a duplicate of bug 1302358 ***
https://bugs.launchpad.net/bugs/1302358

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ubuntu-geoip-provider crashed with SIGSEGV in raise()

Status in ubuntu-geoip package in Ubuntu:
  New

Bug description:
  This just happened immediately on resume from hibernation and desktop
  login.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: geoclue-ubuntu-geoip 1.0.2+14.04.20131125-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  3 23:03:12 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/ubuntu-geoip-provider
  InstallationDate: Installed on 2018-02-13 (294 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/ubuntu-geoip-provider
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe79b33f7c9:mov0x4(%rdi),%edi
   PC (0x7fe79b33f7c9) ok
   source "0x4(%rdi)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: ubuntu-geoip
  StacktraceTop:
   raise (sig=15) at ../sysdeps/unix/sysv/linux/pt-raise.c:35
   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_va () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ubuntu-geoip-provider crashed with SIGSEGV in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1771151] Re: Xorg crashed with SIGSEGV in miPointerSetPosition() from positionSprite() from positionSprite() from fill_pointer_events() from GetPointerEvents() from QueuePointe

2018-12-04 Thread flo schneider
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.

possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190

As master is also outdated, you will need to add at least this patch:
https://github.com/thjaeger/easystroke/pull/6

"This fixes a serious bug that can lead to system instability. Without
this patch, if a 'Command' action is commonly used, it will lead to so
many zombie processes that the OS will be unable to launch additional
processes."

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

Title:
  Xorg crashed with SIGSEGV in miPointerSetPosition() from
  positionSprite() from positionSprite() from fill_pointer_events() from
  GetPointerEvents() from QueuePointerEvents()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  after today's updates

  I don't know if this is related but for some time now, possibly since
  17.04, I have had a weird situation where I cannot get windows to
  raise to focus on click so I have had to use sloppy focus.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 17:09:45 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-19-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.12, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  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: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05a4]
  InstallationDate: Installed on 2014-08-13 (1369 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  MachineType: Dell Inc. OptiPlex 9020
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x55d18c672fe0 : mov
(%rbx),%r15
   PC (0x55d18c672fe0) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r15" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   miPointerSetPosition ()
   ()
   ()
   GetPointerEvents ()
   QueuePointerEvents ()
  Title: Xorg crashed with SIGSEGV in miPointerSetPosition()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd02/01/2018:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.2-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Sep 12 12:13:51 2017
  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.version: 2:1.19.3-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1778233] Re: Xorg crash when using mouse

2018-12-04 Thread flo schneider
*** This bug is a duplicate of bug 1771151 ***
https://bugs.launchpad.net/bugs/1771151

It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.

possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190

As master is also outdated, you will need to add at least this patch:
https://github.com/thjaeger/easystroke/pull/6

"This fixes a serious bug that can lead to system instability. Without
this patch, if a 'Command' action is commonly used, it will lead to so
many zombie processes that the OS will be unable to launch additional
processes."

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

Title:
  Xorg crash when using mouse

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Sometimes when moving mouse Xorg crashes.

  I have a Logitech mouse with free spinning scroll wheel (MX Master).
  100% sure way to reproduce the problem is put the wheel is free spin
  mode and scroll as fast as possible for a few seconds.

  Also the crash happens randomly every couple of days during normal use
  when moving mouse normally.

  I have tried both Nouveau and Nvidia proprietary GPU drivers. Same
  behavior on both.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  xserver-xorg-core:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  Date: Fri Jun 22 16:09:44 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
  InstallationDate: Installed on 2018-06-05 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Intel Corporation S2600CW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=09005743-f23a-4610-8ea7-102ba625db6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0024.021320181901
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H12881-251
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0024.021320181901:bd02/13/2018:svnIntelCorporation:pnS2600CW:pvr:rvnIntelCorporation:rnS2600CW:rvrH12881-251:cvn..:ct17:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600CW
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1806292] Re: Minimum window width doesn't fit on screen in portrait mode

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=121911.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T19:37:25+00:00 Alexander Kallenbach wrote:

Description:
I've turned my screen around to work in portrait mode. Sadly LibreOffice which 
has been maximized came out of this mode. I'm not able to use LibreOffice in a 
maximized window. The window didn't fit into the screen and therefore it isn't 
possible to work with LibreOffice in portrait mode. I'll attach a screenshot to 
clarify what I mean.

I'm on a machine running Ubuntu 18.10. My screen has a resolution set to
2550*1440, scaling is set to 200% (sadly it isn't possible to set
scaling to 150%).

I've already created a bugreport on launchpad:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806292?comments=all

Steps to Reproduce:
1. Open LibreOffice
2. Turn your laptop to use it in portrait mode

Actual Results:
Maximized window isn't possible. Window doesn't fit to screen. Effective 
working not possible.

Expected Results:
Maximizing is possible even in portrait mode.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806292/comments/5


On 2018-12-04T19:38:44+00:00 Alexander Kallenbach wrote:

Created attachment 147290
screenshot

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806292/comments/6


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

** Changed in: df-libreoffice
   Importance: Unknown => Medium

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

Title:
  Minimum window width doesn't fit on screen in portrait mode

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

Bug description:
  As described above. I've turned my screen around to work in portrait
  mode. Sadly LibreOffice came out of the full screen mode. Full screen
  mode seems not to be possible on portrait mode. The window didn't fit
  into the screen and therefore it isn't possible to work with
  LibreOffice in portrait mode. I'll attach a screenshot to clarify what
  I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer 1:6.1.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:52:10 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1806292/+subscriptions

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


[Desktop-packages] [Bug 1801470] Re: [radeon] Double password to login after screen locked

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

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

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

Title:
  [radeon] Double password to login after screen locked

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After every the screen is blocked, I have to write twice the password.
  The first time the top bar is available but the user as seen on the
  blocked screen still on. Then, I have to "cancel" the process which
  drop down the "curtain" and then I have to enter the password yet
  again.

  That happens since the update from 18.04 to 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  2 22:44:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-08 (148 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (3 days ago)

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

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


[Desktop-packages] [Bug 1801470] Re: [radeon] Double password to login after screen locked

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

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

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

Title:
  [radeon] Double password to login after screen locked

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After every the screen is blocked, I have to write twice the password.
  The first time the top bar is available but the user as seen on the
  blocked screen still on. Then, I have to "cancel" the process which
  drop down the "curtain" and then I have to enter the password yet
  again.

  That happens since the update from 18.04 to 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  2 22:44:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-08 (148 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (3 days ago)

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

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


[Desktop-packages] [Bug 1801470] Re: [radeon] Double password to login after screen locked

2018-12-04 Thread porl
I also have this issue (though I notice it is tagged with [radeon]  and
I have nvidia). I am not positive but I believe it started when I did
the in-place upgrade to 18.10 from 18.04. SDDM does not have the same
issue so it appears to be GDM specific.

Output from lspci -k for reference as requested of the original poster
above:


 lspci -k 

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor Host Bridge/DRAM Registers (rev 07)
Subsystem: Dell XPS 15 9550
Kernel driver in use: skl_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
Subsystem: Dell XPS 15 9550
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Thermal Subsystem (rev 07)
Subsystem: Dell XPS 15 9550
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family 
USB 3.0 xHCI Controller (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series 
Chipset Family Thermal Subsystem (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series 
Chipset Family Serial IO I2C Controller #0 (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series 
Chipset Family Serial IO I2C Controller #1 (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series 
Chipset Family MEI Controller #1 (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller 
[AHCI Mode] (rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #1 (rev f1)
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #2 (rev f1)
Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #9 (rev f1)
Kernel driver in use: pcieport
00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #13 (rev f1)
Kernel driver in use: pcieport
00:1d.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #15 (rev f1)
Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation HM170 Chipset LPC/eSPI Controller (rev 31)
Subsystem: Dell XPS 15 9550
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset 
Family Power Management Controller (rev 31)
Subsystem: Dell XPS 15 9550
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family 
HD Audio Controller (rev 31)
Subsystem: Dell Sunrise Point-H HD Audio
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus 
(rev 31)
Subsystem: Dell XPS 15 9550
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
Subsystem: Dell XPS 15 9550
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac 
Wireless LAN SoC (rev 01)
Subsystem: Dell BCM43602 802.11ac Wireless LAN SoC
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
Subsystem: Dell XPS 15 9550
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
04:00.0 Non-Volatile memory controller: Toshiba America Info Systems NVMe 
Controller (rev 01)
Subsystem: Toshiba America Info Systems NVMe Controller
Kernel driver in use: nvme
Kernel modules: nvme

 end of lspci -k output 

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

[Desktop-packages] [Bug 1428307] Re: when screen is locked and I open my laptop, a past screen is flashed

2018-12-04 Thread spm2011
Still an issue on Ubuntu 18.04 GNOME

This has been happening for a long time, I'm astounded this issue hasn't
received more attention.

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

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

Title:
  when screen is locked and I open my laptop, a past screen is flashed

Status in gdm package in Ubuntu:
  New
Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  I close my laptop, which locks the screen. I then open the laptop.
  Sometimes I must hit the power button to get the screen to unlock. But
  before I see the password prompt, I see something else.

  I see a past random screen. It goes by quickly, in less than a second.
  But this is still not acceptable. The screen should not show _any_
  information before the user has logged in.

  It would not be bad if I could somehow determine what this screen is,
  because then I would make sure it is blank. But it seems random.
  Sometimes it seems to be the screen I had visible when I closed up the
  laptop. Sometimes it seems to be the screen I had visible at one of
  the last several times I closed the laptop. It does not seem very
  deterministic. It is hard to know which screen it is going to flash at
  me before the password prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:30:51 2015
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: 1: AppId = gedit, Flags = 1, Reason = There are 
unsaved documents
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-01-31 (397 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (202 days ago)

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

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


[Desktop-packages] [Bug 1428307] Re: when screen is locked and I open my laptop, a past screen is flashed

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

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

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

Title:
  when screen is locked and I open my laptop, a past screen is flashed

Status in gdm package in Ubuntu:
  New
Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  I close my laptop, which locks the screen. I then open the laptop.
  Sometimes I must hit the power button to get the screen to unlock. But
  before I see the password prompt, I see something else.

  I see a past random screen. It goes by quickly, in less than a second.
  But this is still not acceptable. The screen should not show _any_
  information before the user has logged in.

  It would not be bad if I could somehow determine what this screen is,
  because then I would make sure it is blank. But it seems random.
  Sometimes it seems to be the screen I had visible when I closed up the
  laptop. Sometimes it seems to be the screen I had visible at one of
  the last several times I closed the laptop. It does not seem very
  deterministic. It is hard to know which screen it is going to flash at
  me before the password prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:30:51 2015
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: 1: AppId = gedit, Flags = 1, Reason = There are 
unsaved documents
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-01-31 (397 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (202 days ago)

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

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


[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-12-04 Thread Martin Wildam
I would have expected something in dmesg. After test, check timestamps
of other logfiles in /var/log - maybe you then find a log which contains
useful information.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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


[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2018-12-04 Thread Theo Linkspfeifer
It is a library for keyboard layout handling. The Ubuntu package used to
include a patch which apparently fixes the problem with xfce4-keyboard-
settings.

Old upstream report:
https://bugs.freedesktop.org/show_bug.cgi?id=47671

** Bug watch added: freedesktop.org Bugzilla #47671
   https://bugs.freedesktop.org/show_bug.cgi?id=47671

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1806292] Re: Working not possible in portrait mode

2018-12-04 Thread Olivier Tilloy
Thank you Alexander.

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=121911
   Importance: Unknown
   Status: Unknown

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

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

** Summary changed:

- Working not possible in portrait mode
+ Minimum window width doesn't fit on screen in portrait mode

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

Title:
  Minimum window width doesn't fit on screen in portrait mode

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

Bug description:
  As described above. I've turned my screen around to work in portrait
  mode. Sadly LibreOffice came out of the full screen mode. Full screen
  mode seems not to be possible on portrait mode. The window didn't fit
  into the screen and therefore it isn't possible to work with
  LibreOffice in portrait mode. I'll attach a screenshot to clarify what
  I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer 1:6.1.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:52:10 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1806292/+subscriptions

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


[Desktop-packages] [Bug 1806514] Re: [snap] Cannot use PyUno connector

2018-12-04 Thread Olivier Tilloy
** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

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

Title:
  [snap] Cannot use PyUno connector

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  It's not possible to use pyoo, which uses the Uno connector to
  Libreoffice, on a machine where the Libreoffice Snap is installed. The
  pyoo/Uno connector works fine with the libreoffice Apt packages.

  To reproduce run this script:
  #!/usr/bin/env python3
  import pyoo
  import subprocess
  import time
  import shlex

  # PyOO needs a running Libreoffice process to do its work
  lo_proc = subprocess.Popen(shlex.split("soffice 
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo 
--nodefault"))
  time.sleep(3) # give Libreoffice time to actually start before trying to 
connect to it
  lo_instance = pyoo.Desktop('localhost', 2002)
  lo_instance.create_spreadsheet()

  Expected results (seen with the Libreoffice DEB-packages from Ubuntu):
  A new Calc window opens up showing a spreadsheet

  Actual results:
  $ ./test.py 
  Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in 
_get_remote_context
  return resolver.resolve(url)
  uno.NoConnectException: Connector : couldn't connect to socket (Success)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "./test.py", line 10, in 
  lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in 
__init__
  self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in 
_get_remote_context
  raise IOError(resolver, url)
  OSError: [Errno pyuno object 
(com.sun.star.uno.XInterface)0x1ff9450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
 supportedServices={com.sun.star.bridge.UnoUrlResolver}, 
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
 uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext

  
  Actual results if you specify the path to the soffice binary:
  lo_proc = subprocess.Popen(shlex.split("soffice 
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo 
--nodefault"))

  $ ./test.py 
  /snap/libreoffice/90/lib/libreoffice/program/soffice.bin: error while loading 
shared libraries: libicuuc.so.55: cannot open shared object file: No such file 
or directory
  Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in 
_get_remote_context
  return resolver.resolve(url)
  uno.NoConnectException: Connector : couldn't connect to socket (Success)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "./test.py", line 10, in 
  lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in 
__init__
  self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in 
_get_remote_context
  raise IOError(resolver, url)
  OSError: [Errno pyuno object 
(com.sun.star.uno.XInterface)0x1b11450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
 supportedServices={com.sun.star.bridge.UnoUrlResolver}, 
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
 uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext

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

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


[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-04 Thread VanVan
Yes, I can confirm that bluetooth works well, but I hope we can find a
way to use internal sound, it's a good quality speaker for a small
laptop :)

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/1784485/+subscriptions

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


[Desktop-packages] [Bug 1805715] Re: password exposed in calculator input box

2018-12-04 Thread peterzay
The problem has just occurred in a Chrome browser gmail window while
composing a new mail.

In mid composition, I left my computer to attend to other matters.

When I came back, the screen was locked.

Typing the password clearly revealed the plain text in the body of the
email, minus the first character.

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

Title:
  password exposed in calculator input box

Status in gnome-screensaver package in Ubuntu:
  Incomplete

Bug description:
  Plain text Linux user id password exposed in calculator input box.

  The first character of the password is dropped.

  This is reproducible as follows:

  1. allow screen saver to kick in or invoke it manually with ctrl+alt+l
  2. type in password
  3. hit enter
  4. view password in input box of calculator (less first character)

  Note the calculator window has the desktop focus and the input box is
  empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 28 16:37:44 2018
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2018-11-14 (13 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-04 Thread aditya lele
The only workaround that I have found till now is using a bluetooth
headset. It works perfectly well.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/1784485/+subscriptions

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


[Desktop-packages] [Bug 1805715] Re: password exposed in calculator input box

2018-12-04 Thread peterzay
Cannot reproduce this problem since reporting it.

That said, it has been festering for a while.

Please leave this open for others, just in case, given the seriousness.

By the way, the screensaver does not always kick in.

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

Title:
  password exposed in calculator input box

Status in gnome-screensaver package in Ubuntu:
  Incomplete

Bug description:
  Plain text Linux user id password exposed in calculator input box.

  The first character of the password is dropped.

  This is reproducible as follows:

  1. allow screen saver to kick in or invoke it manually with ctrl+alt+l
  2. type in password
  3. hit enter
  4. view password in input box of calculator (less first character)

  Note the calculator window has the desktop focus and the input box is
  empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 28 16:37:44 2018
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2018-11-14 (13 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806292] Re: Working not possible in portrait mode

2018-12-04 Thread Alexander Kallenbach
Upstream bugreport:
https://bugs.documentfoundation.org/show_bug.cgi?id=121911

** Bug watch added: Document Foundation Bugzilla #121911
   https://bugs.documentfoundation.org/show_bug.cgi?id=121911

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

Title:
  Working not possible in portrait mode

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  As described above. I've turned my screen around to work in portrait
  mode. Sadly LibreOffice came out of the full screen mode. Full screen
  mode seems not to be possible on portrait mode. The window didn't fit
  into the screen and therefore it isn't possible to work with
  LibreOffice in portrait mode. I'll attach a screenshot to clarify what
  I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer 1:6.1.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:52:10 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1805715] Re: password exposed in calculator input box

2018-12-04 Thread Eduardo dos Santos Barretto
Hi Peter,
are you still experiencing this issue?


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

** Changed in: gnome-screensaver (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  password exposed in calculator input box

Status in gnome-screensaver package in Ubuntu:
  Incomplete

Bug description:
  Plain text Linux user id password exposed in calculator input box.

  The first character of the password is dropped.

  This is reproducible as follows:

  1. allow screen saver to kick in or invoke it manually with ctrl+alt+l
  2. type in password
  3. hit enter
  4. view password in input box of calculator (less first character)

  Note the calculator window has the desktop focus and the input box is
  empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 28 16:37:44 2018
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2018-11-14 (13 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806750] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

2018-12-04 Thread Desmo75TS
Solved!
Thank you very much

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problemi con le dipendenze - lasciato non configurato

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know the shown error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec  4 19:27:27 2018
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2018-11-10 (24 days ago)
  InstallationMedia: Xubuntu 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: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions

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


[Desktop-packages] [Bug 1806292] Re: Working not possible in portrait mode

2018-12-04 Thread Alexander Kallenbach
I meant maximized window. There other applications which are affected as
well. My screen has a resolution set to 2550*1440, scaling is set to
200% (sadly it isn't possible to set scaling to 150%).

I will create a bugreport upstream as well.

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

Title:
  Working not possible in portrait mode

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  As described above. I've turned my screen around to work in portrait
  mode. Sadly LibreOffice came out of the full screen mode. Full screen
  mode seems not to be possible on portrait mode. The window didn't fit
  into the screen and therefore it isn't possible to work with
  LibreOffice in portrait mode. I'll attach a screenshot to clarify what
  I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer 1:6.1.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:52:10 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

2018-12-04 Thread Lukas
ups - my bad - I forgot that on Debian the lightning-l10n... packages
exist for translation...

So we are just missing some additions l10n packages on ubuntu...

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

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


[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

2018-12-04 Thread Lukas
As far as my Debian (testing) installations go, there is no issue with
the locale of lightning so this may only be just an Ubuntu packaging
Problem? Maybe a switch to debian "stock" version would help?

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

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


[Desktop-packages] [Bug 1806727] Re: KDE: Eqonomize doesn't appear in the K-Menu

2018-12-04 Thread Juhani Numminen
** Package changed: xorg (Ubuntu) => eqonomize (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/1806727

Title:
  KDE: Eqonomize doesn't appear in the K-Menu

Status in eqonomize package in Ubuntu:
  New

Bug description:
  This fixes it:

  sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop
  /usr/share/applications

  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 x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Dec  4 17:46:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1043:0471]
  InstallationDate: Installed on 2018-10-05 (60 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1806750] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

2018-12-04 Thread Juhani Numminen
Some users at the Linux Mint forums have that problem because of HP
Printer drivers downloaded directly from HP.
(https://forums.linuxmint.com/viewtopic.php?f=18=273104=40)

Please open the terminal and run this command:

sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate

Then try the update again.

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problemi con le dipendenze - lasciato non configurato

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know the shown error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec  4 19:27:27 2018
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2018-11-10 (24 days ago)
  InstallationMedia: Xubuntu 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: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions

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


[Desktop-packages] [Bug 1780247] Re: Gedit misrecognises encoding on plain ASCII file

2018-12-04 Thread spm2011
Looks fine for me in gedit 3.28.1 on Ubuntu 18.04

Are you sure the file wasn't overwritten with binary data by another
program ?

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

Title:
  Gedit misrecognises encoding on plain ASCII file

Status in gedit package in Ubuntu:
  New

Bug description:
  On opening the attached file, gedit recognises it incorrectly as some
  asian-specific encoding, even though the file is plain ASCII.

  Ubuntu version:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Gedit package version:
  gedit:
Installed: 3.18.3-0ubuntu4
Candidate: 3.18.3-0ubuntu4
Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1800650] Re: gedit highlights indexes of multidimensional arrays as comments in Perl mode

2018-12-04 Thread spm2011
** Package changed: gedit (Ubuntu) => gtksourceview (Ubuntu)

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

Title:
  gedit highlights indexes of multidimensional arrays as comments in
  Perl mode

Status in gtksourceview package in Ubuntu:
  New

Bug description:
  In gedit's Perl highlight mode, variables of all kinds ($var, %hash,
  @array etc.) are highlighted in dark green. The same usually works for
  the last index of an array as well ($#array) but only if the array is
  one-dimensional. With multidimensional arrays, the proper syntax is
  more complicated: $#{$array[0]} should give the last index of the
  first element of an array of arrays. Here gedit however interprets the
  number sign (#) as the mark of a comment and highlights the rest of
  the line in blue. The expected behavior would be to highlight
  $#{$array[0]} in dark green like all other variables. See the attached
  screenshot.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gedit:
Installed: 3.28.1-1ubuntu1
Candidate: 3.28.1-1ubuntu1
Version table:
   *** 3.28.1-1ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1
  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: Tue Oct 30 12:27:38 2018
  InstallationDate: Installed on 2017-02-13 (624 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago)

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

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


[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-12-04 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted gnome-desktop3 into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.8.4-0ubuntu3.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

** Changed in: hwdata (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed
Status in hwdata source package in Trusty:
  Fix Committed
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Desktop-packages] [Bug 1802653] Re: [HDA-Intel - HDA ATI HDMI, playback] No sound at all

2018-12-04 Thread Eduardo dos Santos Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [HDA-Intel - HDA ATI HDMI, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  v

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  betab  2401 F pulseaudio
   /dev/snd/pcmC1D1p:   betab  2401 F...m pulseaudio
   /dev/snd/controlC0:  betab  2401 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 14:46:54 2018
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  betab  2401 F pulseaudio
   /dev/snd/pcmC1D1p:   betab  2401 F...m pulseaudio
   /dev/snd/controlC0:  betab  2401 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA ATI HDMI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-DS2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438518-007
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/05/2017:svnNOVATECHLTD:pnBB-95004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-DS2-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: BB-95004
  dmi.product.sku: BB-95004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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


[Desktop-packages] [Bug 1755490] Please test proposed package

2018-12-04 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted hwdata into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/hwdata/0.249-1ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed
Status in hwdata source package in Trusty:
  Fix Committed
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Desktop-packages] [Bug 1806750] [NEW] package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

2018-12-04 Thread Desmo75TS
Public bug reported:

I don't know the shown error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 linux-libc-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Dec  4 19:27:27 2018
ErrorMessage: problemi con le dipendenze - lasciato non configurato
InstallationDate: Installed on 2018-11-10 (24 days ago)
InstallationMedia: Xubuntu 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: glib2.0
Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1806750

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problemi con le dipendenze - lasciato non configurato

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know the shown error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec  4 19:27:27 2018
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2018-11-10 (24 days ago)
  InstallationMedia: Xubuntu 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: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions

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


[Desktop-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix

2018-12-04 Thread Brian Murray
Hello errors.ubuntu.com, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  gnome-shell crashes with SIGSEGV in
  gweather_location_common_deserialize →
  gweather_location_format_two_deserialize →
  gweather_location_deserialize → ffi_call_unix64 → ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in libgweather source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 3.28 series.

  [ QA ]

  Run Ubuntu session, expect the shell to show weather information and
  not to crash on timezone changes

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

  [ Regresison potential ]

  Weather location might be leaked. However this is very safe as
  upstream fix comes with proper testing.

  ---

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

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

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


[Desktop-packages] [Bug 1806744] [NEW] "New Document" opens a new window

2018-12-04 Thread spm2011
Public bug reported:

To reproduce:

  - Open file(s) in Gedit
  - Right click dock icon -> "New Document"

Expected: gedit opens a new tab in the existing window for the new document.
This is the default behaviour, observed on Fedora.

Actual:
Ubuntu gedit opens a new window for the new document.
Possibly related to 
https://askubuntu.com/questions/75671/why-does-gedit-keep-randomly-opening-new-instances-when-opening-files-from-nauti

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1
ProcVersionSignature: User Name 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec  4 12:55:02 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-12 (82 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: Upgraded to bionic on 2018-09-28 (66 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "gedit_menu_new.png"
   
https://bugs.launchpad.net/bugs/1806744/+attachment/5219079/+files/gedit_menu_new.png

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

Title:
  "New Document" opens a new window

Status in gedit package in Ubuntu:
  New

Bug description:
  To reproduce:

- Open file(s) in Gedit
- Right click dock icon -> "New Document"

  Expected: gedit opens a new tab in the existing window for the new document.
  This is the default behaviour, observed on Fedora.

  Actual:
  Ubuntu gedit opens a new window for the new document.
  Possibly related to 
https://askubuntu.com/questions/75671/why-does-gedit-keep-randomly-opening-new-instances-when-opening-files-from-nauti

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1
  ProcVersionSignature: User Name 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 12:55:02 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (82 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (66 days ago)

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

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


[Desktop-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

2018-12-04 Thread Timo Aaltonen
excellent, I'll prepare the sru for cosmic

bionic will get 1.20.3 as part of 18.04.2 HWE stack

** Changed in: mesa (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu Cosmic)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu Disco)
   Status: Confirmed => Invalid

** Changed in: xorg-server (Ubuntu Disco)
   Status: Incomplete => Fix Released

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

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Invalid
Status in xorg-server source package in Bionic:
  Confirmed
Status in mesa source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Triaged
Status in mesa source package in Disco:
  Invalid
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  

[Desktop-packages] [Bug 1788150] Re: Shebang should point to Python 2

2018-12-04 Thread Sebastien Bacher
Looking a bit the issue seems fixed in 18.10

** Changed in: duplicity (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Shebang should point to Python 2

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  I think we should change the shebang line to ensure Python 2 usage, as
  I have 3 set as default. This will produce and error as the statvfs
  package is deprecated, but available, in 2 and removed in 3. The error
  this produces in Deja Dup is "could not understgand duplicity
  version".

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

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


[Desktop-packages] [Bug 1806514] Re: [snap] Cannot use PyUno connector

2018-12-04 Thread Olivier Tilloy
** Summary changed:

- Cannot use PyUno connector with Libreoffice snap
+ [snap] Cannot use PyUno connector

** Tags added: snap

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

Title:
  [snap] Cannot use PyUno connector

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It's not possible to use pyoo, which uses the Uno connector to
  Libreoffice, on a machine where the Libreoffice Snap is installed. The
  pyoo/Uno connector works fine with the libreoffice Apt packages.

  To reproduce run this script:
  #!/usr/bin/env python3
  import pyoo
  import subprocess
  import time
  import shlex

  # PyOO needs a running Libreoffice process to do its work
  lo_proc = subprocess.Popen(shlex.split("soffice 
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo 
--nodefault"))
  time.sleep(3) # give Libreoffice time to actually start before trying to 
connect to it
  lo_instance = pyoo.Desktop('localhost', 2002)
  lo_instance.create_spreadsheet()

  Expected results (seen with the Libreoffice DEB-packages from Ubuntu):
  A new Calc window opens up showing a spreadsheet

  Actual results:
  $ ./test.py 
  Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in 
_get_remote_context
  return resolver.resolve(url)
  uno.NoConnectException: Connector : couldn't connect to socket (Success)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "./test.py", line 10, in 
  lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in 
__init__
  self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in 
_get_remote_context
  raise IOError(resolver, url)
  OSError: [Errno pyuno object 
(com.sun.star.uno.XInterface)0x1ff9450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
 supportedServices={com.sun.star.bridge.UnoUrlResolver}, 
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
 uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext

  
  Actual results if you specify the path to the soffice binary:
  lo_proc = subprocess.Popen(shlex.split("soffice 
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo 
--nodefault"))

  $ ./test.py 
  /snap/libreoffice/90/lib/libreoffice/program/soffice.bin: error while loading 
shared libraries: libicuuc.so.55: cannot open shared object file: No such file 
or directory
  Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in 
_get_remote_context
  return resolver.resolve(url)
  uno.NoConnectException: Connector : couldn't connect to socket (Success)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "./test.py", line 10, in 
  lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in 
__init__
  self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in 
_get_remote_context
  raise IOError(resolver, url)
  OSError: [Errno pyuno object 
(com.sun.star.uno.XInterface)0x1b11450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
 supportedServices={com.sun.star.bridge.UnoUrlResolver}, 
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
 uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext

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

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


[Desktop-packages] [Bug 1770929] Re: backup fails on ubuntu 18.4

2018-12-04 Thread Sebastien Bacher
Similar to what is described also on
https://bugzilla.redhat.com/show_bug.cgi?id=1470873

** Bug watch added: Red Hat Bugzilla #1470873
   https://bugzilla.redhat.com/show_bug.cgi?id=1470873

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

Title:
  backup fails on ubuntu 18.4

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault onb PDF using -dFirstPage and -dLastPage

2018-12-04 Thread Clemens Fuchslocher
I can confirm this problem on Ubuntu 16.04 and ghostscript
9.26~dfsg+0-0ubuntu0.16.04.1:

$ gs --version
9.26
$ convert "confidential.pdf[0]" confidential.png
convert: FailedToExecuteCommand `"gs" -q -dQUIET -dSAFER -dBATCH -dNOPAUSE 
-dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 
"-sDEVICE=pngalpha" -dTextAlphaBits=4 -dGraphicsAlphaBits=4 "-r72x72" 
-dFirstPage=1 -dLastPage=1 "-sOutputFile=/tmp/magick-12412a591aAW0c1rp%d" 
"-f/tmp/magick-12412pbD9WU9tgyvz" "-f/tmp/magick-12412_OoIhBmXubzJ"' (-1) @ 
error/delegate.c/ExternalDelegateCommand/461.
convert: no images defined `confidential.png' @ 
error/convert.c/ConvertImageCommand/3210.

The problem doesn't happen with ghostscript
9.25~dfsg+1-0ubuntu0.16.04.3:

$ dpkg --install libgs9_9.25~dfsg+1-0ubuntu0.16.04.3_amd64.deb 
libgs9-common_9.25~dfsg+1-0ubuntu0.16.04.3_all.deb 
ghostscript_9.25~dfsg+1-0ubuntu0.16.04.3_amd64.deb 
ghostscript-x_9.25~dfsg+1-0ubuntu0.16.04.3_amd64.deb
$ gs --version
9.25
$ convert "confidential.pdf[0]" confidential.png
$ identify confidential.png
confidential.png PNG 595x842 595x842+0+0 8-bit sRGB 22.5KB 0.000u 0:00.000

Not every PDF is affected by this problem.

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

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

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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


[Desktop-packages] [Bug 1806727] [NEW] KDE: Eqonomize doesn't appear in the K-Menu

2018-12-04 Thread Volker Wysk
Public bug reported:

This fixes it:

sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop
/usr/share/applications

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 x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Dec  4 17:46:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1043:0471]
InstallationDate: Installed on 2018-10-05 (60 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic kubuntu 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/1806727

Title:
  KDE: Eqonomize doesn't appear in the K-Menu

Status in xorg package in Ubuntu:
  New

Bug description:
  This fixes it:

  sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop
  /usr/share/applications

  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 x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Dec  4 17:46:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1043:0471]
  InstallationDate: Installed on 2018-10-05 (60 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  

[Desktop-packages] [Bug 1788150] Re: Shebang should point to Python 2

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

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

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

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

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

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

Title:
  Shebang should point to Python 2

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  I think we should change the shebang line to ensure Python 2 usage, as
  I have 3 set as default. This will produce and error as the statvfs
  package is deprecated, but available, in 2 and removed in 3. The error
  this produces in Deja Dup is "could not understgand duplicity
  version".

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

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


[Desktop-packages] [Bug 1778504] Re: duplicity failed with UnicodeDecodeError

2018-12-04 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1770929 ***
https://bugs.launchpad.net/bugs/1770929

** This bug has been marked a duplicate of bug 1770929
   backup fails on ubuntu 18.4

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

Title:
  duplicity failed with UnicodeDecodeError

Status in duplicity package in Ubuntu:
  New

Bug description:
  For a couple of weeks, my weekly backup (deja-dup+duplicity, ubuntu
  18.04) fails with:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
  full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 19: 
ordinal not in range(128)

  It looks like this Unicode error repeatedly arises, whatever the version of 
duplicity. Mine is:
  Package: duplicity
  Version: 0.7.17-0ubuntu1
  Priority: optional
  Section: utils
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Alexander Zangerl 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 1 090 kB
  Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python (<< 2.8), python (>= 
2.7~), python-fasteners, python:any (<< 2.8), python:any (>= 2.7.5-5~), 
python-lockfile (>> 1:0.9), gnupg | gnupg1
  Suggests: rsync, python-paramiko, python-pexpect, python-urllib3, 
python-oauthlib, python-boto, ncftp, python-cloudfiles, lftp, python-gdata, 
tahoe-lafs, python-swiftclient
  Homepage: http://duplicity.nongnu.org/
  Task: ubuntu-mate-desktop
  Supported: 5y
  Download-Size: 183 kB
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  If this is a problem with some files encoding, how can I locate which
  one(s) is faulty?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 13:18:38 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-02-07 (137 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (38 days ago)

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

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


[Desktop-packages] [Bug 1795142] Re: Allow for a custom period of inactivity before going to sleep to be selected

2018-12-04 Thread Efthimios Chaskaris
** Description changed:

  The times of inactivity you are allowed to set your computer to sleep
  after are predetermined. I would like to be able to define these times,
  preferably in minutes. I know I am probably able to change the value
  through text files and the command line, but Ubuntu should be as user-
- friendly as it can be. Having to use a command line doesn't help with
- that.
+ friendly as it can be. Having to use a command line for simple things
+ doesn't help with that.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 29 17:26:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Allow for a custom period of inactivity before going to sleep to be
  selected

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

Bug description:
  The times of inactivity you are allowed to set your computer to sleep
  after are predetermined. I would like to be able to define these
  times, preferably in minutes. I know I am probably able to change the
  value through text files and the command line, but Ubuntu should be as
  user-friendly as it can be. Having to use a command line for simple
  things doesn't help with that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 29 17:26:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797376] Re: Don't merge with Debian 2018.20180907.48586-2 for cosmic

2018-12-04 Thread Sebastien Bacher
** Changed in: texlive-bin (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Don't merge with Debian 2018.20180907.48586-2 for cosmic

Status in texlive-bin package in Ubuntu:
  Fix Released

Bug description:
  The changes are non trivial for cosmic

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

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


[Desktop-packages] [Bug 1797377] Re: In tablet mode, OSK is not displayed in the WiFi network auth dialog

2018-12-04 Thread Sebastien Bacher
** Package changed: ubiquity (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  In tablet mode, OSK is not displayed in the WiFi network auth dialog

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Test Case:
  1. On a 2 in 1 laptop, use it in table mode
  2. Start the installer and proceed to the WiFi step
  3. Connect to an authenticated network
  4. Type the password and authenticate

  Actual result
  The OSK is not displayed and the user cannot enter his password

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 15:10:11 2018
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  InstallationDate: Installed on 2018-10-11 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1799230] Re: [SRU] libreoffice 6.0.7 for bionic

2018-12-04 Thread Olivier Tilloy
Override updated at https://code.launchpad.net/~osomon/britney/hints-
ubuntu-bionic-libreoffice/+merge/360073

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

Title:
  [SRU] libreoffice 6.0.7 for bionic

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice-l10n package in Ubuntu:
  Triaged
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.0.7 is the seventh bugfix release of the still 6.0 line. 
Version 6.0.6 is currently in bionic.
     For a list of fixed bugs compared to 6.0.6 see the list of bugs fixed in 
the three release candidates:
   https://wiki.documentfoundation.org/Releases/6.0.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.7/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.7/RC3#List_of_fixed_bugs
     (that's a total of 66 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 66 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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


[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault onb PDF using -dFirstPage and -dLastPage

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

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

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

Title:
  Ghostscript segmentation fault onb PDF using -dFirstPage and
  -dLastPage

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

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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


[Desktop-packages] [Bug 1393688] Re: open *.ppt file in libreoffice Impress is abnormal

2018-12-04 Thread Olivier Tilloy
Tested on cosmic, version 6.1.2.1 (deb), and the file opens in impress
by default, and indeed there's only one slide in it.

Tested libreoffice 6.1.3.2 upstream build (debs), and the same is
observed. So that may be an upstream problem (if the file is not
corrupted in some way).

@shijing: if you're still tracking this bug, would you mind filing an
upstream bug report at
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided
and sharing the link to that report here? Thanks!

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

Title:
  open *.ppt file in libreoffice Impress is abnormal

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I have a  *.ppt  fromat file , use other office software is correct, but open 
with libreoffice impress is abnormal.
  the ppt file has thirty pages in it , but in libreoffice impress show one 
page, and the content is uncomplete.

  OS: Ubuntu  /Ubuntu Kylin 14.10 and Ubuntu Kylin 15.04

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

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


[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

2018-12-04 Thread Efthimios Chaskaris
I did, however, manage to change one other permission(the home folder
access) before changing the removable drives one. That's why I thought
it was specific to the removable drives permission.

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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


[Desktop-packages] [Bug 1797377] [NEW] In tablet mode, OSK is not displayed in the WiFi network auth dialog

2018-12-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Test Case:
1. On a 2 in 1 laptop, use it in table mode
2. Start the installer and proceed to the WiFi step
3. Connect to an authenticated network
4. Type the password and authenticate

Actual result
The OSK is not displayed and the user cannot enter his password

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 11 15:10:11 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2018-10-11 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic rls-dd-incoming ubiquity-18.10.9
-- 
In tablet mode, OSK is not displayed in the WiFi network auth dialog
https://bugs.launchpad.net/bugs/1797377
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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


[Desktop-packages] [Bug 1806385] Re: [snap] Creating new slide by double click not working correctly

2018-12-04 Thread Olivier Tilloy
This is not a snap-specific issue, indeed. Would you mind filing an
upstream bug report at
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided
and sharing the link to that bug report here? Thanks!

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

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

** Summary changed:

- [snap] Creating new slide by double click not working correctly
+ Creating a new slide by double click not working correctly

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

Title:
  Creating a new slide by double click not working correctly

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Version: 6.1.3.2
  Build-ID: libreoffice-6.1.3.2-snap1

  You can create new slides in impress by double clicking on the empty
  part of the slides pane (below the existing slide). However, this
  works only as expected while the slides pane actually has empty space
  at the bottom.

  As soon as I have created a few slides, the slides pane is completely
  filled, and two things happen:

  (1) Improvement: It is very hard to double click on the thin white
  space at the bottom of the filled slides pane. This could be improved
  by always letting a few pixels at the bottom to click on.

  (2) Bug: You can actually manage to double click there and this
  creates a new slide. However, this new slide is not filed at the end
  of slides (as it should) but appears at a strange location somewhere
  in the middle of slides. This is definitely wrong.

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

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


[Desktop-packages] [Bug 1806292] Re: Working not possible in portrait mode

2018-12-04 Thread Olivier Tilloy
Do you mean fullscreen, or maximized window?

Note that this likely not specific to libreoffice. The application just
happens to enforce a minimum window width that appears to be larger than
the width of your screen when in portrait orientation. That would
affects similarly other applications that enforce a minimum width for
their windows.

Regardless, would you mind filing an upstream bug report at
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided,
to get upstream's take on the problem? Please share the link to that bug
report here. Thanks!

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

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

Title:
  Working not possible in portrait mode

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  As described above. I've turned my screen around to work in portrait
  mode. Sadly LibreOffice came out of the full screen mode. Full screen
  mode seems not to be possible on portrait mode. The window didn't fit
  into the screen and therefore it isn't possible to work with
  LibreOffice in portrait mode. I'll attach a screenshot to clarify what
  I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer 1:6.1.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:52:10 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1806288] Re: Deactivation of night mode until tomorrow does not work

2018-12-04 Thread Sebastien Bacher
Right, there is no storage of that configuration so it's currently
"until tomorrow or reboot", I've reported it upstream now on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/119

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

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

Title:
  Deactivation of night mode until tomorrow does not work

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

Bug description:
  As described above. I've deactivated the night mode until tomorrow
  ("Bis morgen deaktivieren"). After I've rebooted my laptop night mode
  has been activated again. Either the function should be renamed or
  fulfil what it promises.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:31:37 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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-settings-daemon/+bug/1806288/+subscriptions

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


[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

2018-12-04 Thread Efthimios Chaskaris
I did, however, manage to change one other permission earlier. That's
why I thought it was specific to this permission.

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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


[Desktop-packages] [Bug 1799974] Re: [MIR] gupnp

2018-12-04 Thread Sebastien Bacher
Same as gssdp, the doc/depends issue is fixed in 1.0.3-2 in Debian/going
to be autosynced. The tests are not integration tests so unsure there is
much value having them as autopkgtests?

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

Title:
  [MIR] gupnp

Status in gupnp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries

  * Security

  There is an old CVE recorded/fixed
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is used during build

  * Dependendies

  The package uses standard desktop libraries that are already in main

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 4.2, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

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

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


[Desktop-packages] [Bug 1806697] Re: Chromium snap "Removable storage devices" permission fails to enable

2018-12-04 Thread Olivier Tilloy
I can observe the problem in an up-to-date cosmic VM. The interface is
correctly connected, but gnome-software fails to display the switch in
the correct state. Killing gnome-software "fixes" the problem. So it
looks like the status of the permissions are cached in the running
instance of gnome-software, and not properly updated when changing them
from the UI.

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

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

** Summary changed:

- Chromium snap "Removable storage devices" permission fails to enable
+ Status of interface connections not properly updated in the UI

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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


[Desktop-packages] [Bug 1806379] Re: [MIR] gnome-shell-extension-desktop-icons

2018-12-04 Thread Mathieu Trudel-Lapierre
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  [MIR] gnome-shell-extension-desktop-icons

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Availability
  

  Currently in binNEW - synced from experimental.

  This is an arch:all package (no compilation; all JS), successfully
  built.

  Rationale
  =
  The desktop team would like to include Nautilus 3.30 in disco. However, 
Nautilus as of 3.28 - Ubuntu currently has 3.26 - drops support for having 
icons on the desktop. We'd like to keep this.

  The upstream team have provided a GNOME Shell extension to replace
  this functionality, which we want to ship. It is not "1.0" yet - we
  are working with upstream on iterating it.

  This package is a GNOME Shell extension written for 'gjs', i.e. in
  Javascript with GObject/GNOME support. It uses the standard GNOME
  libraries.

  Our intention is to work with upstream improve this extension over
  'disco' and following cycles up to the next LTS; to that end we would
  like to include it in Ubuntu Desktop fairly early on, to identify and
  shake out any problems.

  Security
  
  No known security issues, but this is a relatively new piece of software.

  
https://security-tracker.debian.org/tracker/source-package/gnome-shell-extension-desktop-icons
  (once accepted): 
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+cve

  Quality assurance
  =
  Desktop is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gnome-shell-extension-desktop-icons
  https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues

  Dependencies
  
  No binary universe dependencies

  Standards compliance
  
  4.2.1, compat 11, dh rules

  Maintenance
  ===
  We've packaged this as part of the Debian GNOME team, and we'll maintain it 
there.

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

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


[Desktop-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

2018-12-04 Thread Ken VanDine
I can confirm with the PPA enabled I no longer see classic snaps crash
when running wayland on cosmic.  I tested vscode and slack.

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in mesa source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Incomplete
Status in mesa source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-12-04 Thread Moses Moore
"turn off FXAA" workaround works here too.
Ubuntu 18.10, Nvidia driver 390.87-0ubuntu1

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in xfce4 package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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


[Desktop-packages] [Bug 1806712] [NEW] [MIR] fonts-yrsa-rasa

2018-12-04 Thread Sebastien Bacher
Public bug reported:

* Availability

Currently version builds fine and is in sync from Debian
https://launchpad.net/ubuntu/+source/fonts-gujr/2:1.3
(it's a font and arch all so only amd64 build)

* Rationale

It's a new depends from fonts-gujr

* Security

No CVE/known security issue

* Quality assurance

- the desktop-packages team is subscribed to the package
- the package is in sync with Debian
- there are no open bugs on debian or launchpad

* Dependendies

The package has no depends

* Standards compliance

the package is using standard packaging (dh11) and the current the
standards-version, it is in sync from Debian

* Maintainance

The package is maintained in Debian by the fonts team, the desktop team
is going to look at issues on the Ubuntu side if requires

** Affects: fonts-yrsa-rasa (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] fonts-yrsa-rasa

Status in fonts-yrsa-rasa package in Ubuntu:
  New

Bug description:
  * Availability

  Currently version builds fine and is in sync from Debian
  https://launchpad.net/ubuntu/+source/fonts-gujr/2:1.3
  (it's a font and arch all so only amd64 build)

  * Rationale

  It's a new depends from fonts-gujr

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the package is in sync with Debian
  - there are no open bugs on debian or launchpad

  * Dependendies

  The package has no depends

  * Standards compliance

  the package is using standard packaging (dh11) and the current the
  standards-version, it is in sync from Debian

  * Maintainance

  The package is maintained in Debian by the fonts team, the desktop
  team is going to look at issues on the Ubuntu side if requires

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-yrsa-rasa/+bug/1806712/+subscriptions

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


[Desktop-packages] [Bug 1198880] Re: Uninterrupted processes after Screen Lock

2018-12-04 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu?

Please let us know if you do. Alternatively, this bug report can be left
to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.related

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  Uninterrupted processes after Screen Lock

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  After installing Ubuntu 12.04.2 LTS on VirtualBox virtual x64 machine.
  I noticed, that this bug after opening Gedit and waiting until screen
  will automatically locks. After I login back - some processes appears
  to be in Uninterrupted state.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14
  Uname: Linux 3.5.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Mon Jul  8 13:31:15 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749672] Re: [MIR] xdg-desktop-portal

2018-12-04 Thread Ken VanDine
** Changed in: xdg-desktop-portal (Ubuntu Xenial)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: xdg-desktop-portal (Ubuntu Bionic)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: xdg-desktop-portal (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: xdg-desktop-portal (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: xdg-desktop-portal (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: xdg-desktop-portal (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  [MIR] xdg-desktop-portal

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Triaged
Status in xdg-desktop-portal source package in Bionic:
  Triaged

Bug description:
  Availability
  
  In sync with Debian.

  Built for all supported architectures.

  Rationale
  =
  Required for snaps.

  Security
  
  No known security issues, but due to the nature of this package, a security 
review is probably needed.

  https://security-tracker.debian.org/tracker/source-package/xdg-desktop-portal
  https://launchpad.net/xdg-desktop-portal/+cve

  Quality assurance
  =
  - The Desktop Packages bug team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-desktop-portal
  https://github.com/flatpak/xdg-desktop-portal/issues

  Upstream build tests (new) are run with dh_auto_test (failure would
  fail the build).

  autopkgtests are passing
  https://autopkgtest.ubuntu.com/packages/xdg-desktop-portal
  https://ci.debian.net/packages/x/xdg-desktop-portal/unstable/amd64/

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.3

  debhelper compat 11, dh 7 style simple rules

  Maintenance
  ===
  - Actively developed upstream. Last release was 0.10 yesterday
  https://github.com/flatpak/xdg-desktop-portal/commits/master

  Well-maintained in Debian by Simon McVittie (Debian's Flatpak maintainer). 
Team-maintained.
  https://salsa.debian.org/debian/xdg-desktop-portal

  Background information
  ==
  xdg-desktop-portal was originally created to allow Flatpak apps to request 
access outside the sandbox. It's useful technology that can be used by Snap 
too, which simplifies work for app developers to support both next generation 
packaging formats. For instance, see 
https://blogs.gnome.org/alexl/2018/02/14/moving-a-portal/

  See also the MIR xdg-desktop-portal-gtk LP: #1750069.

  Presumably, we'll want to backport these packages to be snap
  dependencies in 16.04 LTS (maybe 14.04 LTS too).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672/+subscriptions

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


[Desktop-packages] [Bug 1797381] Re: In tablet mode, step "Who are you" OSK hides when the passwordd field is focused

2018-12-04 Thread Sebastien Bacher
** Package changed: ubiquity (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  In tablet mode, step "Who are you" OSK hides when the passwordd field
  is focused

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Test Case:
  1. On a 2 in 1 in tablet mode, launch the installer and proceed to the user 
setup step (Who are you)
  2. With the OSK, enter the username, login, hostname and password then 
proceed zith the rest of the installation

  Actual result
  The OSK hides when the password field has the focus and the user cannot enter 
a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 15:15:14 2018
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  InstallationDate: Installed on 2018-10-11 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-12-04 Thread Iain Lane
** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: gtk+3.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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


[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2018-12-04 Thread Sebastien Bacher
** Changed in: mesa (Ubuntu Cosmic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

2018-12-04 Thread Will Cooke
** Also affects: network-manager (Ubuntu Disco)
   Importance: High
   Status: Triaged

** Changed in: network-manager (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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


  1   2   >