date:20181106

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

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

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

Title:
  Firefox takes all available CPU power occasionally, and can't quit

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When this happens, I have to kill it by signal 1 to quit firefox processes.
  Closing tabs don't help when this happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 26.0+build2-0ubuntu0.13.10.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarno  1699 F panel-10-mixer
  BuildID: 20131206145143
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Channel: Unavailable
  Date: Mon Jan  6 18:25:25 2014
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-09-20 (108 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.0.254 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.101  
metric 9
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-b022607d-fa4c-4923-a0f0-a0cb42140101
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
  Profiles: Profile0 (Default) - LastVersion=26.0/20131206145143
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   google-talkplugin 4.9.1.0-1
   gecko-mediaplayer 1.0.8-4ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-b022607d-fa4c-4923-a0f0-a0cb42140101
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (80 days ago)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1099113] Re: Browsers hang after a few minutes max

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

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

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

Title:
  Browsers hang after a few minutes max

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Both Firefox and Chromium started hanging after upgrading to Raring.
  It quickly became clear that Firefox was getting stuck ona call to
  futex(..., FUTEX_WAIT_REQUEUE_PI_PRIVATE, ...) thanks to strace. I
  have now installed firefox:i386 as a test and am currently using it
  without issues...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  herve  2062 F pulseaudio
   /dev/snd/controlC0:  herve  2062 F pulseaudio
  BuildID: 20130108230423
  Channel: Unavailable
  Date: Sun Jan 13 14:46:48 2013
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-04-04 (649 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  IpRoute:
   default via 192.168.0.254 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.37  metric 
9
  MarkForUpload: True
  PrefSources:
   prefs.js
   
[Profile]/extensions/{5384767E-00D9-40E9-B72F-9CC39D655D6F}/defaults/preferences/defaults.js
   
[Profile]/extensions/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}/defaults/preferences/prefs-dwhelper.js
  Profiles: Profile0 (Default) - LastVersion=19.0/20130108230423 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to raring on 2012-12-16 (27 days ago)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1611
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.3A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd07/07/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058910252B0320100:rvnHewlett-Packard:rn1611:rvr96.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 058910252B0320100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1487709] Re: package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

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

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

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

Title:
  package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Error:BrokenCount>0

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: hplip-data 3.14.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Aug 12 10:41:45 2015
  DuplicateSignature: package:hplip-data:3.14.3-0ubuntu3:subprocess new 
pre-removal script returned error exit status 127
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2014-07-19 (398 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Fax:4: tpvmlp://Fax:4
   device for HP_Deskjet_F4200_series:3: tpvmlp://HP_Deskjet_F4200_series:3
   device for Microsoft_XPS_Document_Writer:2: 
tpvmlp://Microsoft_XPS_Document_Writer:2
   device for Send_To_OneNote_2013:1: tpvmlp://Send_To_OneNote_2013:1
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: VMware_Virtual_Printer: Generic PostScript Printer 
Foomatic/Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=90746b34-5434-4ac0-a58c-93933fc706ef ro quiet splash
  SourcePackage: hplip
  Title: package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1173058] Re: Firefox hangs with grey screen when download a file

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

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

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

Title:
  Firefox hangs with grey screen when download a file

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When I donwload a file Firefox becomes gray and hangs for 5/10
  seconds. Sometimes it happens also when browsing a page.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 20.0+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j0sh   1674 F pulseaudio
j0sh  31219 F pulseaudio
   /dev/snd/pcmC0D0p:   j0sh   1674 F...m pulseaudio
  BuildID: 20130417085609
  Channel: Unavailable
  Date: Fri Apr 26 08:48:47 2013
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-11 (14 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.9  metric 9
  MarkForUpload: True
  PrefSources:
   prefs.js
   
[Profile]/extensions/{6AC85730-7D0F-4de0-B3FA-21142DD85326}/defaults/preferences/colorzilla.js
  Profiles: Profile0 (Default) - LastVersion=20.0/20130417085609 (In use)
  RelatedPackageVersions:
   gnome-shell   3.6.3.1-0ubuntu6
   icedtea-6-plugin  1.3.2-1ubuntu1
   totem-mozilla 3.6.3-0ubuntu6
   rhythmbox-mozilla 2.98-0ubuntu5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to raring on 2013-04-19 (6 days ago)
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1480032] Re: python 3.4 vs python 2.7 ??? package hplip-data 3.14.3-0ubuntu3.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

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

Title:
  python 3.4 vs python 2.7 ??? package hplip-data 3.14.3-0ubuntu3.3
  failed to install/upgrade: subprocess new pre-removal script returned
  error exit status 1

Status in hplip package in Ubuntu:
  Expired

Bug description:
  I previously had problems loading software and the had to type the
  following to get it to work.

  
   setpython2.7  ! to revert default python 3.4 back to 2.7 

  ll /usr/bin/pyt*  ! test reversion worked then run the software update

  
  setpython3.4! return or reset to python 3.4 as default then test again to 
confirm

  That worked before and I stopped doing it when for several updates it
  did not appear to be necessary.

  Hope this helps.

  ddw

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: hplip-data 3.14.3-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  CupsErrorLog:
   W [30/Jul/2015:21:55:32 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'HP-Officejet-Pro-8500-A910-2-Gray..' already exists
   W [30/Jul/2015:21:55:32 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'HP-Officejet-Pro-8500-A910-2-RGB..' already exists
   W [30/Jul/2015:21:55:32 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'HP-Officejet-Pro-8600-Gray..' already exists
   W [30/Jul/2015:21:55:32 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'HP-Officejet-Pro-8600-RGB..' already exists
  Date: Thu Jul 30 21:55:00 2015
  DuplicateSignature: package:hplip-data:3.14.3-0ubuntu3.3:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-17 (804 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Lpstat:
   device for HP-Officejet-Pro-8500-A910-2: 
hp:/net/Officejet_Pro_8500_A910?zc=dhcppc2
   device for HP-Officejet-Pro-8600: hp:/net/Officejet_Pro_8600?zc=HPB60CCE
  MachineType: LENOVO 6457W56
  PackageArchitecture: all
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles:
   HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.14.3
   HP-Officejet-Pro-8500-A910-2: HP Officejet Pro 8500 a910, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=360a51bb-40c0-4908-8298-cfa12de90710 ro quiet splash
  SourcePackage: hplip
  Title: package hplip-data 3.14.3-0ubuntu3.3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC7WW (2.27 )
  dmi.board.name: 6457W56
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn6457W56:pvrThinkPadT61p:rvnLENOVO:rn6457W56:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6457W56
  dmi.product.version: ThinkPad T61p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1499389] Re: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen

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

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

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

Title:
  HP Photosmart D5460 prints text in gray instead of black when A4
  borderless is chosen

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hello,

  if I print black text on my HP Photosmart D5460, the output is grey
  instead of black when choose "A4 borderless" as media size.

  Steps to reproduce:

  1. Start LibreOffice Writer, write some text
  2. Click "File -> Print"
  3. In the print dialogue, check "Use only paper size from printer settings" 
(under the "Options"-tab)
  4. On the "General"-tab, select the printer and click on properties
  5. In the properties dialogue, select "A4 borderless" as paper size 
(optionally set print quality to "draft" and output mode to "black only 
grayscale", my preferred settings)
  6. Start the print.

  Now the printed text is grey instead of black, I have attached a photo
  of how the output looks compared to normal output (when media size is
  set to "A4" non-borderless).

  I have also attached the file (printout) with the data that would go
  to the printer when printing on "A4 borderless" according to the guide
  on
  
https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer

  Kind regards;
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Sep 24 15:57:48 2015
  InstallationDate: Installed on 2015-09-17 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150916)
  Lpstat:
   device for Photosmart-D5400-series: 
hp:/usb/Photosmart_D5400_series?serial=MY95A990G204V3
   device for test: /tmp/printout
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Photosmart-D5400-series.ppd', '/etc/cups/ppd/test.ppd'] failed 
with exit code 2: grep: /etc/cups/ppd/Photosmart-D5400-series.ppd: Permission 
denied
   grep: /etc/cups/ppd/test.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz root=/dev/mapper/internal--hdd-test1 
ro rootflags=subvol=@ quiet splash vt.handoff=7
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1506323] Re: hplip 3.15.2 recognizes ez-ipupdate as running package manager

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

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

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

Title:
  hplip 3.15.2 recognizes ez-ipupdate as running package manager

Status in hplip package in Ubuntu:
  Expired

Bug description:
  The message `A package manager '/usr/sbin/ez-ipupdate -d' appears to
  be running. Please quit the package manager and press enter to
  continue (i=ignore, r=retry*, f=force, q=quit) :r` is misleading
  because `ez-ipupdate` is a DDNS updater, not a package manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip (not installed)
  Uname: Linux 4.2.3-040203-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 15 07:56:05 2015
  InstallationDate: Installed on 2015-09-14 (30 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1570955] Re: hp-scan stops working if I run hp-info (several printer models)

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

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

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

Title:
  hp-scan stops working if I run hp-info (several printer models)

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  I have:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  I downloaded hplip-3.16.3.run and executed it and it installed hplip. I add a 
USB printer (HP Photosmart B210), and then I run hp-scan and it scans properly. 
I can run hp-scan any number of times with no problem. Each time I run it  I 
get this on dmesg:
  [101238.781550] Did not find alt setting 1 for intf 0, config 1

  Then I run hp-info -i , I get all the printer info, 3 dmesg errors get 
generated:
  [101290.777189] Did not find alt setting 1 for intf 0, config 1
  [101290.777686] Did not find alt setting 1 for intf 0, config 1
  [101290.778184] Did not find alt setting 1 for intf 0, config 1

  And after that, all subsequent calls to hp-scan fail. The first time I type 
hp-scan after having ran hp-info -i , it shows an error:
  Using device hpaio:/usb/Photosmart_Plus_B210_series?serial=CN09F1P57X05J9
  Opening connection to device...
  error: SANE: Error during device I/O (code=9)

  And dmesg also prints:
  [101355.572440] Did not find alt setting 1 for intf 0, config 1

  All the subsequent calls to hp-scan will hang up for ever opening connection 
to device.
  and it prints the dmesg error: [101355.572440] Did not find alt setting 1 for 
intf 0, config 1

  At this point I can only kill the process (hp-scan).
  The only way to make it work again is disconnecting the USB cable, and 
connecting it back in. But as soon as I run hp-info it goes bad again.

  The problem does not happen over network. Over network I can always
  scan and also run hp-info (even at the same time).

  I tested with 3.15.11 and 3.15.9 and got the same issue. I will go
  back a little bit more to bisect and post the results later on.

  I got reports on the exact same problems on a Laserjet m1212 (over USB).
  I originally got a report from two deskjet 2132 with the same problems, but I 
got a brand new 2130 and it works so I would assume the 2132 should work too 
and it might be a different problem.

  They all print the dmesg error each time hp-info or hp-scan is
  executed.

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

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

[Desktop-packages] [Bug 1507356] Re: drivers impresora hp envy 4500 series

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

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

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

Title:
  drivers impresora hp envy 4500 series

Status in hplip package in Ubuntu:
  Expired

Bug description:
  
   Ubuntu 15.04 does not recognize my scanner printer the HP ENVY 4500 series 
(all in one), I installed the latest version of HPLIP-3.15.9 and still not 
recognize the scanner, the printer works perfectly, showing the error is " hp: 
/ usb / serial ENVY_4500_series = CN57V351MY05X4 ", to run diagnostics on the 
terminal with HPLIP out the following" Checking for HP Properitery Plugin's 
  No plug-in printers are configured. ".

  Please could help me ?. Thank you

  HP Linux Imaging and Printing System (ver. 3.15.9)
  Diagnse Self Healing Utility Utility and see. 1.0

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software Comes With ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  Certain conditions under. See COPYING file for more details.

  hp-doctor

  HP Linux Imaging and Printing System (ver. 3.15.9)
  Diagnse Self Healing Utility Utility and see. 1.0

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software Comes With ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  Certain conditions under. See COPYING file for more details.


  Checking for Deprecated items 
  No items are found Deprecated

  
  HPLIP checking for updates 

  HP Linux Imaging and Printing System (ver. 3.15.9)
  Upgrade version latest HPLIP see. 1.0

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software Comes With ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  Certain conditions under. See COPYING file for more details.

  Latest version of HPLIP is already installed.

  
  Checking for Dependencies 

  ---
  | INFO SYSTEM |
  ---

   Kernel: 3.19.0-30-generic # 34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 GNU / 
Linux
   Host: TANTALO-2
   Proc: 3.19.0-30-generic # 34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 GNU / 
Linux
   Distribution: ubuntu 15.04
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: 3.15.9 HPLIP
  HPLIP-Home: / usr / share / hplip
  HPLIP-Installation: Auto installation is supported for ubuntu distro version 
15.04

  Current contents of '/etc/hp/hplip.conf' file:
  # Hplip.conf. Generated from hplip.conf.in by configure.

  [Hplip]
  version = 3.15.9

  [Dirs]
  home = / usr / share / hplip
  run = / var / run
  ppd = / usr / share / ppd / HP
  ppdbase = / usr / share / ppd
  doc = / usr / share / doc / hplip-3.15.9
  html = / usr / share / doc / hplip-3.15.9
  icon = / usr / share / applications
  cupsbackend = / usr / lib / cups / backend
  cupsFilter = / usr / lib / cups / filter
  DRV = / usr / share / cups / drv / hp
  bin = / usr / bin

  # Following are determined to values at set time and can not be changed.
  [Set]
  network-build = yes
  libusb01-build = no
  pp-build = no
  gui-build = yes
  scanner-build = yes
  fax-build = yes
  dbus-build = yes
  cups11-build = no
  doc-build = yes
  shadow-build = no
  hpijs-install = no
  foomatic-DRV-install = no
  foomatic-ppd-install = no
  foomatic-rip-hplip-install = no
  hpcups-install = yes
  cups-DRV-install = yes
  cups-ppd-install = no
  internal-tag = 3.15.9
  restricted-build = no
  ui-toolkit = qt4
  qt3 = no
  qt4 = yes
  policy-kit = no
  lite-build = no
  udev_sysfs_rules = no
  hpcups-only-build = no
  hpijs-only-build = no

  
  Current contents of '/var/lib/hp/hplip.state' file:
  Plugins are not installed. Could not access file: No such file or directory

  Current contents of '~ / .hplip / hplip.conf' file:
  [Upgrade]
  notify_upgrade = true
  last_upgraded_time = 1445011499
  pending_upgrade_time = 0
  latest_available_version = 3.15.9

  [Settings]
  systray_visible = 0
  systray_messages = 0

  [Last_used]
  device_uri = "hp: / usb / serial ENVY_4500_series = CN57V351MY05X4?"
  printer_name =
  WORKING_DIR =.

  [Commands]
  scan = / usr / bin / xsane SANE_URI% -V%

  [Refresh]
  rate = 30
  enable = false
  type = 1

  [Polling]
  enable = false
  interval = 5
  device_list =

  [Fax]
  voice_phone =
  email_address =

  [Installation]
  date_time = 10/18/15 20:11:42
  version = 3.15.9

  
   
  

  --
  | External Dependencies |
  --

   gs Ghostscript - PostScript and PDF language interpreter and previewer 
REQUIRED 7.05 9.15 OK -
   scanimage scanimage - Shell scanning program 1.0.24 1.0 OPTIONAL OK -
   xsane xsane - scanner frontend for SANE Graphical 0.9 0.998 OPTIONAL

[Desktop-packages] [Bug 1506019] Re: Network interface logical name = rename2 after installtion

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

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

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

Title:
  Network interface logical name = rename2 after installtion

Status in hplip package in Ubuntu:
  Expired

Bug description:
  I've a machine with 4 network interfaces.

  When installing ubuntu will not be able to set the correct name for
  one of them, and it will call it rename2.

  I did use Ubuntu 15.10 Server daily 2015-10-09

  lshw -class network
  WARNING: you should run this program as super-user.
*-network:0 DISABLED
 description: Ethernet interface
 product: I350 Gigabit Network Connection
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:01:00.0
 logical name: rename2
 version: 01
 serial: 2c:60:0c:7a:43:c9
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=igb 
driverversion=5.2.18-k firmware=1.63, 0x89fa latency=0 link=no 
multicast=yes port=twisted pair
 resources: irq:24 memory:c7e2-c7e3 ioport:6020(size=32) 
memory:c7e44000-c7e47fff memory:c6e6-c6e7 memory:c6e4-c6e5
*-network:1 DISABLED
 description: Ethernet interface
 product: I350 Gigabit Network Connection
 vendor: Intel Corporation
 physical id: 0.1
 bus info: pci@:01:00.1
 logical name: eno1
 version: 01
 serial: 2c:60:0c:7a:43:ca
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=igb 
driverversion=5.2.18-k firmware=1.63, 0x89fa latency=0 link=no 
multicast=yes port=twisted pair
 resources: irq:46 memory:c7e0-c7e1 ioport:6000(size=32) 
memory:c7e4-c7e43fff memory:c6e2-c6e3 memory:c6e0-c6e1
*-network:0
 description: Ethernet interface
 product: Ethernet Controller 10-Gigabit X540-AT2
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0f0
 version: 01
 serial: a0:36:9f:6e:36:08
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list rom ethernet physical tp 100bt-fd 
1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=ixgbe 
driverversion=4.0.1-k firmware=0x8389 latency=0 link=no multicast=yes 
port=twisted pair
 resources: irq:56 memory:c6a0-c6bf memory:c6c04000-c6c07fff 
memory:c798-c79f memory:c7d0-c7df memory:c7c0-c7cf
*-network:1
 description: Ethernet interface
 product: Ethernet Controller 10-Gigabit X540-AT2
 vendor: Intel Corporation
 physical id: 0.1
 bus info: pci@:04:00.1
 logical name: enp4s0f1
 version: 01
 serial: a0:36:9f:6e:36:0a
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list rom ethernet physical tp 100bt-fd 
1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=ixgbe 
driverversion=4.0.1-k duplex=full firmware=0x8389 ip=192.168.69.153 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:100 memory:c680-c69f memory:c6c0-c6c03fff 
memory:c790-c797 memory:c7b0-c7bf memory:c7a0-c7af

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

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

[Desktop-packages] [Bug 1562516] Re: Missing /usr/share/hplip

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

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

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

Title:
  Missing /usr/share/hplip

Status in hplip package in Ubuntu:
  Expired

Bug description:
  The /usr/share/hplip folder is missing.

  Probably everyone uses who upgraded package is still using
  /usr/share/hplip from old version.

  Some commands:

  $  dpkg -x hplip_3.15.7-0ubuntu4_amd64.deb /tmp/out/

  $ ls -l /tmp/out/usr/bin/hp-setup 
  lrwxrwxrwx 1 wieczyk wieczyk 23 wrz 18  2015 /tmp/out/usr/bin/hp-setup -> 
../share/hplip/setup.py

  $ find /tmp/out/ -name setup.py | wc -l
  0

  $ dpkg -c hplip_3.15.7-0ubuntu4_amd64.deb | grep setup
  -rw-r--r-- root/root  1764 2015-09-18 02:38 
./usr/share/man/man1/hp-setup.1.gz
  lrwxrwxrwx root/root 0 2015-09-18 02:38 ./usr/bin/hp-setup -> 
../share/hplip/setup.py

  As you can see there is no setup.py

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

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

[Desktop-packages] [Bug 1519765] Re: package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

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

Title:
  package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in hplip package in Ubuntu:
  Expired

Bug description:
  package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: hplip-data 3.14.3-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CupsErrorLog:
   
  Date: Wed Nov 25 02:55:21 2015
  DuplicateSignature: package:hplip-data:3.14.3-0ubuntu3:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-11-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=94cd1ef0-9387-47a2-aed0-bf9e6a3e6fd2 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: hplip
  Title: package hplip-data 3.14.3-0ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1506230] Re: package hplip-data 3.14.3-0ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101

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

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

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

Title:
  package hplip-data 3.14.3-0ubuntu3.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 101

Status in hplip package in Ubuntu:
  Expired

Bug description:
  IDK

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: hplip-data 3.14.3-0ubuntu3.5
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Oct 14 16:41:15 2015
  DuplicateSignature: package:hplip-data:3.14.3-0ubuntu3.5:subprocess installed 
post-installation script returned error exit status 101
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 101
  InstallationDate: Installed on 2015-09-30 (14 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron 1501
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: hplip
  Title: package hplip-data 3.14.3-0ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 101
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.1
  dmi.board.name: 0UW744
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 1501
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1496994] Re: failure of proprietary plugin installation doesn't provide any reasons

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

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

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

Title:
  failure of proprietary plugin installation doesn't provide any reasons

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  After the installation displays a dialog `Plug-in installation
  successful` it display another dialog

  Failed to install Plug-in.
  Either you have chosen to skip the Plug-in installation  or entered 
incorrect Password.

  which doesn't make any sense (both the sequence of dialogs and the
  possibility of an incorrect password (the installation dialog doesn't
  allow those)). The user is left without any ideas what went wrong. The
  precise reason and instructions or tips how to fix them should be
  provided.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Sep 17 22:04:43 2015
  InstallationDate: Installed on 2015-09-14 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat:
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn: 
hp:/net/HP_Color_LaserJet_MFP_M476dn?ip=192.168.178.41
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB): 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
   device for Hewlett-Packard-hp-LaserJet-4200: 
hp:/net/hp_LaserJet_4200?ip=141.20.27.45
   device for HP-Color-LaserJet-MFP-M476dn: 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'Hewlett-Packard-hp-LaserJet-4200.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn.ppd', 
'/etc/cups/ppd/HP-Color-LaserJet-MFP-M476dn.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB).ppd'] failed 
with exit code 2: /etc/cups/ppd/Hewlett-Packard-hp-LaserJet-4200: HP LaserJet 
4200 Series Postscript (recommended)
   Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn: HP Color LaserJet Pro MFP M476 
Postscript (recommended)
   grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M476dn.ppd: Keine Berechtigung
   Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn(USB): HP Color LaserJet Pro MFP 
M476 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-29-generic 
root=UUID=ca5b3a35-462e-4adb-90e2-d00e286062ae ro rootflags=subvol=@
  SourcePackage: hplip
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1177236] Re: Deformed image in Firefox while scrolling

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

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

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

Title:
  Deformed image in Firefox while scrolling

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Since upgrading from Kubuntu 12.10 to 13.04, scrolling in Firefox
  sometimes shows glitches. Most of the time too short lived to make a
  screendump, but I managed once. The glitching appears while scrolling
  but is intermittent.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  € lsb_release -rd
  Description:Ubuntu 13.04
  Release:13.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  € apt-cache policy firefox
  firefox:
Installed: 20.0+build1-0ubuntu2
Candidate: 20.0+build1-0ubuntu2
Version table:
   *** 20.0+build1-0ubuntu2 0
  500 http://nl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  lspci sniplett:
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)
  00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated 
Graphics Controller (rev 03)

  3) What you expected to happen and 4) What happened instead
  Related screenshots are here: 
http://meta.electronics.stackexchange.com/questions/2909/stackexchange-circuitlab-bug-or-linux-firefox-bug

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

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

[Desktop-packages] [Bug 1595566] Re: HP OfficeJet Pro 8740 is not listed in the printers database (lpinfo -m)

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

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

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

Title:
  HP OfficeJet Pro 8740 is not listed in the printers database (lpinfo
  -m)

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hi.

  According to http://hplipopensource.com/hplip-
  web/models/officejet/hp_officejet_pro_8740.html HP 8740 should be
  supported with HPLIP 3.16.5. I've installed HPLIP 3.16.5 from Yaketty
  in Xenial by recompiling it to build a native package with native
  Xenial dependencies. I've installed the following resulting packages:
  hplip, hplip-data, hplip-gui, libhpmud0, libsane-hpaio, printer-
  driver-hpcups, printer-driver-postscript-hp. However, lpinfo -m
  doesn't list HP 8740:

  $ lpinfo -m | grep 8740
  gutenprint.5.2://bjc-PIXMA-iP8740/expert Canon PIXMA iP8740 - CUPS+Gutenprint 
v5.2.11
  foomatic:Canon-PIXMA-iP8740-gutenprint-ijs-simplified.5.2.ppd Canon 
PIXMA-iP8740 Foomatic/gutenprint-ijs-simplified.5.2
  foomatic:Canon-PIXMA-iP8740-gutenprint-ijs.5.2.ppd Canon PIXMA-iP8740 
Foomatic/gutenprint-ijs.5.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hplip (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CupsErrorLog:
   
  CurrentDesktop: KDE
  Date: Thu Jun 23 17:03:01 2016
  InstallationDate: Installed on 2016-04-26 (58 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: a4
  PpdFiles: VMware_Virtual_Printer: Generic PostScript Printer 
Foomatic/Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=c483951c-bc3a-4801-9797-c40b89d25faa ro quiet splash
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1791029] Re: cannot print pdf

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

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

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

Title:
  cannot print pdf

Status in cups package in Ubuntu:
  Expired

Bug description:
  I cannot print pdfs on any printer. The file is processed in the
  printer dialogue and then disappears. without printing. I can print
  odf files on the same printer without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.5
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Sep  6 11:10:50 2018
  InstallationDate: Installed on 2018-02-01 (216 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n: 
hp:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.2
   device for Hewlett-Packard-HP-LaserJet-400-M401dne: 
hp:/net/HP_LaserJet_400_M401dne?zc=NPI13B8A2
  MachineType: LENOVO 20281
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd: 
Permission denied
   grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=18dad62c-a203-45d8-a228-4a2dfc8af342 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J6ET58WW (2.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20281  QB0
  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:bvrJ6ET58WW(2.03):bd01/17/2014:svnLENOVO:pn20281:pvrM5400:rvnLENOVO:rn20281QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: M5400
  dmi.product.name: 20281
  dmi.product.version: M5400
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)

2018-11-06 Thread Benjamin Li

I am so so so sorry for I made a mistake of selecting the wrong kernel
with the wrong architecture to install, which lead to all those error
messages during boot in v4.19. (My laptop should install the kernel with
architecture amd64 but I installed i386, I am so sorry for making things
more complicated, SORRY!!!)

Anyway, I "apt purge" the wrong kernel (4.19 with architecture i386) and
just installed the proper one(architecture amd64).

However! The issue in the v4.17 remain in the 4.19! I don't see anything
improve in my situation, I still can't get in the system, getting stuck
in the black screen after the Ubuntu logo during the boot, I can only
access the system in recovery mode; the brightness of my display can't
be adjusted; the setting for my display still says "Unknown Display",
and the laptop can't get back if I put the whole system into sleep
mode(by turn off the display)

Any idea? Please help Thanks in advance!

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

Title:
  Xorg freeze (black screen after ubuntu logo during boot)

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

Bug description:
  I experienced this bug ever since I have upgraded my laptop from
  16.04. But it got resolved in my last update after I reported the bug.
  However, I forgot to go back to Launchpad to mark it as resolved and
  now the problem comes again after I just updated the system.

  So, as the title stated, I can't get in the system due to the infinite
  black screen I am facing. I am only able to report this bug under the
  recovery mode.

  Besides, there's something wrong with the lock screen too. I can't get
  back to the system if I just put the system into "sleep mode". Black
  screen again!

  What's worst, the brightness of my display can't be adjusted as well!
  I feel like being blind at night! Please help!!! Thank you!

  And I think there might be the compatibility problem between my laptop
  and the new desktop -- Gnome, which is the default in 18.04.

  What should do? I really love using Ubuntu, as I really learned a lot
  in these days I used it as my study os for CS.

  Any help is appreciated, thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.17.0-041700rc3-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 19:49:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd]
  InstallationDate: Installed on 2018-04-04 (215 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: ASUSTeK COMPUTER INC. T300FA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic 
root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T300FA.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T300FA
  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.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T300FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Nov  6 03:47:33 2018
  xserver.configfile: default
  xser

[Desktop-packages] [Bug 1801410] Re: Icons.keep.flashing

Can you please provide a photo or video of the problem "icons keep
flashing"?

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

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

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

Title:
  Icons.keep.flashing

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  lost.use.of.space.key
  very.slow.internet.connection
  Icons.keep.flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  2 09:56:43 2018
  DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller (ThinkPad T520) [17aa:21cf]
  InstallationDate: Installed on 2017-09-21 (407 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 42424WU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a4b8720-cf83-49dd-b18a-63b77499e529 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET55WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42424WU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET55WW(1.35):bd11/24/2011:svnLENOVO:pn42424WU:pvrThinkPadT520:rvnLENOVO:rn42424WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 42424WU
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  1 10:46:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1724901] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

2018-11-06 Thread Ramesh

This bug reports says "Launching 17.10" so I guess its present in ubuntu
17.10 but my system is Ubuntu 16.04.5 and I have the same problem.

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

Title:
  Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Launching ubuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 19 13:43:23 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0504]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M] [1025:0505]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Aspire 5750G
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=65719b3f-c720-46a5-8489-b9a337a5bd78 ro quiet splash vt.handoff=7
  Renderer: Software
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   RRProviderAutoConfigGpuScreen ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x55bf0e466af0, argc=12, argv=0x7ffd8d73d578, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd8d73d568) at ../csu/libc-start.c:308
   _start ()
  Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750G:pvrV1.21:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1801976] Re: Display does not work correctly

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1801976

Title:
  Display does not work correctly

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

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P09ABI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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/linux/+bug/1801976/+subscriptions

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

[Desktop-packages] [Bug 1801747] Status changed to Confirmed

2018-11-06 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/gdm3/+bug/1801747/+subscriptions

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

[Desktop-packages] [Bug 1801976] Re: Display does not work correctly

Also, please run these commands and send the output:

  sudo apt install edid-decode
  for e in /sys/class/drm/*/edid ; do edid-decode $e ; done


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

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

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

Title:
  Display does not work correctly

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P09ABI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1801976] Re: Display does not work correctly

That sounds unusual. Can you please attach a photo of the display when
it is "milky and too large" ?

** Tags added: hybrid nouveau

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

Title:
  Display does not work correctly

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P09ABI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV

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

** Package changed: linux (Ubuntu) => upower (Ubuntu)

** Changed in: upower (Ubuntu)
   Status: Fix Released => Confirmed

** This bug has been marked a duplicate of bug 1796550
   [regression] Keyboard brightness control keys (down/up) don't work in cosmic 
(upower 0.99.8)

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

Title:
  Keyboard backlight control doesn't work on Asus N550JV

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase
  or decrease keyboard backlight brightness, respectively) doesn't do
  anything, the keyboard backlight stays off. Other key combinations,
  like adjusting display brightness or audio volume, do work.

  Keyboard backlight control worked in Kubuntu 18.04 on the same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   2820 F pulseaudio
   /dev/snd/controlC1:  lastique   2820 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Oct 26 17:40:24 2018
  InstallationDate: Installed on 2013-10-11 (1840 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.sku: ASUS-NotebookSKU
  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/upower/+bug/1800164/+subscriptions

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

[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

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

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

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

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/gdm3/+bug/1801747/+subscriptions

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

[Desktop-packages] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug

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

  apport-collect 1801898

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

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

** Tags added: cosmic multimonitor

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Desktop-packages] [Bug 1799947] Re: Application windows in 18.04.01 go black but launcher is still visible

In that case, please manually attach the output from running each of
these commands:

  * lspci -k
  * cat /proc/cpuinfo
  * dpkg -l
  * xrandr
  * journalctl -b


** Tags added: bionic

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

Title:
  Application windows in 18.04.01 go black but launcher is still visible

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

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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

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

[Desktop-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

OK. Next we probably want to get an idea of what gdm is doing.

Please reproduce the problem, then reboot and collect the system log of
the previous boot where the problem occured:

  journalctl -b-1 > prev_boot.txt

and attach prev_boot.txt.

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu)

** No longer affects: linux (Ubuntu)

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.versio

[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery

I don't know where it's written, but it does make sense. Although I
think I overstated the requirement because really I can only see a
justification to get all fixes into the _next_ release before
backporting.

You don't want to declare a bug fixed in the latest LTS only to find
months or years later that the fix is missing in newer releases. So we
must ensure every fix exists in the _next_ release before it is put into
any previous release.

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

Title:
  totem silently fails to create screenshot gallery

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  New
Status in totem source package in Cosmic:
  Fix Released

Bug description:
  *Impact

  The gallery plugin/menu option doesn't work

  * Test case

  - open a video
  - open the menu and click on the gallery option
  - validate making a gallery with the default options

  -> the picked filename should exist and be a gallery if pictures from
  the video

  * Regression potential

  The changes are restricted to the screenshot plugin, so make sure that
  one works

  --

  https://gitlab.gnome.org/GNOME/totem/issues/268

  ---

  https://gitlab.gnome.org/GNOME/totem/merge_requests/18/

  ---

  Package totem 3.26.0-0ubuntu6

  totem 3.26.0 running on Ubuntu 18.04 silently fails to create
  screenshot gallery. I'm assuming that this has something to do with
  totem-video-thumbnailer.

  Steps to reproduce:

  totem-video-thumbnailer -g 20 inputvideo outputpng

  I can reproduce this result with both HEVC and AVC encoded videos. I
  haven't been able to test other codecs, but the error indicates the
  codec isn't the problem.

  totem 3.18.1 under Ubuntu 16.04 does not have this problem.

  Any further information required I will be happy to produce within my 
abilities.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-19 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1800164] [NEW] Keyboard backlight control doesn't work on Asus N550JV

You have been subscribed to a public bug:

Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase or
decrease keyboard backlight brightness, respectively) doesn't do
anything, the keyboard backlight stays off. Other key combinations, like
adjusting display brightness or audio volume, do work.

Keyboard backlight control worked in Kubuntu 18.04 on the same machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lastique   2820 F pulseaudio
 /dev/snd/controlC1:  lastique   2820 F pulseaudio
CurrentDesktop: KDE
Date: Fri Oct 26 17:40:24 2018
InstallationDate: Installed on 2013-10-11 (1840 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. N550JV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago)
WifiSyslog:
 
dmi.bios.date: 11/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N550JV.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N550JV
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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N550JV
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: upower (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-bug cosmic kernel-bug-exists-upstream 
kernel-fixed-upstream
-- 
Keyboard backlight control doesn't work on Asus N550JV
https://bugs.launchpad.net/bugs/1800164
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to upower 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 1571206] Re: org.gtk.vfs.Daemon[1025]: A connection to the bus can't be made

2018-11-06 Thread Tejeev Patel

I see it too on xubuntu 16.04
4.15.0-38-generic #41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  org.gtk.vfs.Daemon[1025]: A connection to the bus can't be made

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged on a fresh xenial 64 install, with a gnome-shell
  session

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6
  Uname: Linux 4.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 16 17:31:03 2016
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-06 Thread Chris Guiver

When the files hit my mirror, i installed

guiverc@dx6120lu:~$ dpkg -l |grep libreoffice |grep "1.1"
ii  libreoffice-common   1:6.1.2-0ubuntu1.1 
all  office productivity suite -- arch-independent files
ii  libreoffice-java-common  1:6.1.2-0ubuntu1.1 
all  office productivity suite -- arch-independent Java 
support files
ii  libreoffice-style-breeze 1:6.1.2-0ubuntu1.1 
all  office productivity suite -- Breeze symbol style
ii  libreoffice-style-colibre1:6.1.2-0ubuntu1.1 
all  office productivity suite -- colibre symbol style
ii  libreoffice-style-tango  1:6.1.2-0ubuntu1.1 
all  office productivity suite -- Tango symbol style

after which I logged out & back in. I then re-tested libreoffice...

Simon, I'm not sure what the issue was (and I'm no good with
aesthetics), but I SEE NO CHANGE.

When this lp.bug hit my inbox I looked for what your issue was, and the
only thing I saw was black boxes kept being drawn when you hovered over
buttons, eg. if I went into print-preview, if you move the mouse over
'close preview' a dark box starts flashing slightly-low-left over the
close-preview button and makes it hard to read.  I assumed this was what
this bug was about, as it occurs elsewhere too. This 'flaw' (or issue)
appears to have not been altered.

I could be complete wrong - feel free [as always] to ping me (irc, etc).
I saw no adverse effects, but it didn't fix what I hoped it would (which
could be a different thing...)  ps: if what I've described is something
else & needs a lp.bug raised - just tell me.

** Attachment added: "main screen when [libreoffice] opened"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+attachment/5209778/+files/libreoffice_2018-11-07_main_screen.jpg

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

Title:
  Theming does not work on LXQt

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

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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

[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-06 Thread Chris Guiver

my appearance settings if needed  (uploaded this as only place where I
saw breeze)

My LXQt theme is "Lubuntu Arc"

ps: i've taken quite a few screenshots before & after change so I could
look for differences, I can upload if desired, but I didn't see anything
of value.

** Attachment added: "if LXQt appearance settings used in my testing"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+attachment/5209779/+files/libreoffice_2018-11-07_appearance_settings.jpg

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

Title:
  Theming does not work on LXQt

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

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

-- 
Mailing list: https://launchpad.net/~desktop-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-11-06 Thread William.Yeung

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

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

Title:
  Printing job in 16.04 is slower than in 14.04

Status in Ubuntu:
  New

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/+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 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()

2018-11-06 Thread Treviño

Please also include this change when backporting
https://gitlab.gnome.org/GNOME/gjs/merge_requests/240

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

Title:
  [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in
  GetPropertyOperation() from Interpret() from js::RunScript()

Status in gjs package in Ubuntu:
  In Progress
Status in mozjs60 package in Ubuntu:
  Invalid
Status in gjs source package in Cosmic:
  In Progress
Status in mozjs60 source package in Cosmic:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/f64145b51a9d0fd20bfff57836b8f743e56c50ba
  https://gitlab.gnome.org/GNOME/gjs/issues/212

  ---

  mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52 which
  was still the latest yesterday)

  Steps to reproduce:

  1. Start gnome-shell (master)
  2. Super+A to show applications
  3. Alt+F2 and type "debugexit" to exit cleanly.

  Backtrace:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=...,
  pc=, script=..., fp=, cx=)
  at ./js/src/vm/JSContext.h:161
  161   ./js/src/vm/JSContext.h: No such file or directory.
  [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))]
  (gdb) bt
  #0  0x7f3bf4033a4e in GetPropertyOperation
  (vp=..., lval=..., pc=, script=..., fp=, 
cx=) at ./js/src/vm/JSContext.h:161
  #1  0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&)
  (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834
  #2  0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&)
  (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418
  #3  0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct)
  (cx=0x55d07921beb0, args=..., construct=)
  at ./js/src/vm/Interpreter.cpp:490
  #4  0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, 
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
  (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=...,
  thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536
  #5  0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, 
JS::Handle, JS::Handle, JS::HandleValueArray const&, 
JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., 
rval=...)
  at ./debian/build/dist/include/js/RootingAPI.h:1128
  #6  0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0
  #7  0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0
  #8  0x7f3bf7625573 in  () at /usr/lib/libgjs.so.0
  #9  0x7f3bf7f65b6d in g_closure_invoke ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x7f3bf7f788f3 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7f3bf7f81882 in g_signal_emit_valist ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x7f3bf7f81ecf in g_signal_emit ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0)
  at clutter-actor.c:5932
  #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0)
  at ../src/st/st-widget.c:354
  #15 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0)
  at ../src/st/st-bin.c:188
  #16 0x7f3bf7f6c448 in g_object_run_dispose ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #17 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0)
  at clutter-actor.c:8615
  #18 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0)
  at clutter-actor.c:19002
  #19 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0)
  at clutter-actor.c:6264
  #20 0x7f3bf7f65b6d in g_closure_invoke ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #21 0x7f3bf7f78c4a in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #22 0x7f3bf7f81882 in g_signal_emit_valist ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #23 0x7f3bf7f81ecf in g_signal_emit ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795a9ba0)
  at clutter-actor.c:5932
  #25 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795a9ba0)
  at ../src/st/st-widget.c:354
  #26 0x7f3bf7f6c448 in g_object_run_dispose ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795a9ba0)
  at clutter-actor.c:8615
  #28 0x7f3bf7025cf5 in st_bin_dispose (gobject=0x55d0795a8260)
  at ../src/st/st-bin.c:185
  #29 0x7f3bf7f6ac13 in g_object_unref ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #30 0x7f3bf7610f5e in ObjectInstance::release_native_object() ()
  at /usr/lib/libgjs.so.0
  #31 0x7f3bf7618496 in ObjectInstance::disassociate_js_gobject(

[Desktop-packages] [Bug 1801410] Re: Icons.keep.flashing

2018-11-06 Thread Seth Arnold

Ow, this looks painful:

[[0;32m  OK  [0m] Started Disk Manager.
 Starting Firmware update daemon...
[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) A start job is running for 
Firmware update daemon (2s / 1min 30s)
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) A start job is running for 
Daily apt download activities (45s / no limit)
[K[[0;32m  OK  [0m] Started Firmware update daemon.
[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 6s / no limit)
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 7s / no limit)
[K[[0;1;31m*[0m[0;31m*[0m] (2 of 2) A start job is running for Daily 
apt download activities (51s / no limit)
[K[[0m[0;31m* [0m] (2 of 2) A start job is running for Daily apt 
download activities (51s / no limit)
[K[[0;1;31m*[0m[0;31m*[0m] (2 of 2) A start job is running for Daily 
apt download activities (52s / no limit)
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 9s / no limit)

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

Title:
  Icons.keep.flashing

Status in xorg package in Ubuntu:
  New

Bug description:
  lost.use.of.space.key
  very.slow.internet.connection
  Icons.keep.flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  2 09:56:43 2018
  DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller (ThinkPad T520) [17aa:21cf]
  InstallationDate: Installed on 2017-09-21 (407 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 42424WU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a4b8720-cf83-49dd-b18a-63b77499e529 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET55WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42424WU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET55WW(1.35):bd11/24/2011:svnLENOVO:pn42424WU:pvrThinkPadT520:rvnLENOVO:rn42424WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 42424WU
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  1 10:46:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1790876] Re: SRU 3.28.2 to bionic

2018-11-06 Thread Treviño

Verified as per SRU exception
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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

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

Title:
  SRU 3.28.2 to bionic

Status in gnome-calculator package in Ubuntu:
  In Progress
Status in gnome-calculator 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 work normally with various
  setups

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

  [ Regresison potential ]

  Currency names might be different than used to be, no translation
  implied though.

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

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

[Desktop-packages] [Bug 1802007] [NEW] package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.sv

2018-11-06 Thread Tomasz Dudziak

Public bug reported:

asdf

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
Uname: Linux 4.15.0-1018-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct 31 23:53:13 2018
DuplicateSignature:
 package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
 Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
  unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2018-08-30 (68 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: ubuntu-themes
Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1802007

Title:
  package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to
  install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-
  light/status/22/gnome-netstatus-rx.svg.dpkg-new': Operation not
  permitted

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  asdf

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
  Uname: Linux 4.15.0-1018-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 23:53:13 2018
  DuplicateSignature:
   package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
   Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-08-30 (68 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: ubuntu-themes
  Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

2018-11-06 Thread Theo Linkspfeifer

Your suggestion in comment #8 looks like something that is worth to
forward to the Xfce bug tracker (Xfce Core -> Xfce4-settings).

https://bugzilla.xfce.org/

The new key could be added to the xsettings.xml, and maybe even be
exposed in the keyboard settings dialog too.

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

Title:
  org.gnome.desktop.interface.cursor-blink-timeout not honored

Status in vte2.91 package in Ubuntu:
  New
Status in xfconf package in Ubuntu:
  New

Bug description:
  Xubuntu desktop 18.04.1

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

  gnome-terminal: 3.28.2-1ubuntu1~18.04.1
  libgtk-3-0: 3.22.30-1ubuntu1
  dconf-editor: 3.28.0-1

  Per workaround instructions in comment #8 on bug 838381 (of which this is not 
a duplicate), I set /org/gnome/desktop/interface/cursor-blink-timeout to a 
large value, less than the stated maximum of 2^31 - 1.
  I saved the change, exited dconf-editor and restarted the computer.

  What I expected to happen:
  Cursor in GTK-based terminal emulators will no longer stop blinking after 10 
seconds.

  What happens instead:
  Cursor in GTK-based terminal emulators continues to stop blinking after 10 
seconds.

  Of note, the cursor-blink-time *is* honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1798481/+subscriptions

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

[Desktop-packages] [Bug 1790876] Re: SRU 3.28.2 to bionic

Hello Marco, or anyone else affected,

Accepted gnome-calculator into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
calculator/1: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: gnome-calculator (Ubuntu Bionic)
   Status: New => 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 gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1790876

Title:
  SRU 3.28.2 to bionic

Status in gnome-calculator package in Ubuntu:
  In Progress
Status in gnome-calculator 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 work normally with various
  setups

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

  [ Regresison potential ]

  Currency names might be different than used to be, no translation
  implied though.

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

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

[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

Hello PJSingh5000, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2 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: mutter (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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730211

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Unable to type capital letters using onscreen keyboard:

  [Test Case]
  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  [Regression Potential]
  Please make sure that osk correctly revert to lower case. Also make sure
  the physical keyboard correctly works after using the osk.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

Hello Traumflug, or anyone else affected,

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

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

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

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

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

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

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

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

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

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

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

  ---

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

  ---

  Workaround:

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

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

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

  Expected to happen:

  Desktop appears.

  Actually happening:

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

  Partial diagnosis:

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

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

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

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-06 Thread Andrew Lendrum

UPDATE: I found the packages in bionic-updates.

After setting prime-select nvidia and logging out, I got the attached
/var/log/gpu-manager.log.

It says that nvidia is not loaded, and my laptop still runs hot.

When I set prime-select intel, log out, and back in, nvidia is still not
loaded (according to the log) and my laptop still runs hot.

Any suggestings?

** Attachment added: "/var/log/gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5209748/+files/gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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

[Desktop-packages] [Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

2018-11-06 Thread Steve Stevenson

I really don't have much experience reporting bugs with large open
projects. I tried asking in what I thought was the correct venue but
didn't get a response. As long as people who were in my situation can
discover the solution via finding this report or the answer I posted to
the related question on askubuntu.com then I'm satisfied and I don't
mind this report being closed ("invalid" I guess, not sure what statuses
are available). I'd close it myself but I can't find an affordance for
doing that.

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

Title:
  org.gnome.desktop.interface.cursor-blink-timeout not honored

Status in vte2.91 package in Ubuntu:
  New
Status in xfconf package in Ubuntu:
  New

Bug description:
  Xubuntu desktop 18.04.1

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

  gnome-terminal: 3.28.2-1ubuntu1~18.04.1
  libgtk-3-0: 3.22.30-1ubuntu1
  dconf-editor: 3.28.0-1

  Per workaround instructions in comment #8 on bug 838381 (of which this is not 
a duplicate), I set /org/gnome/desktop/interface/cursor-blink-timeout to a 
large value, less than the stated maximum of 2^31 - 1.
  I saved the change, exited dconf-editor and restarted the computer.

  What I expected to happen:
  Cursor in GTK-based terminal emulators will no longer stop blinking after 10 
seconds.

  What happens instead:
  Cursor in GTK-based terminal emulators continues to stop blinking after 10 
seconds.

  Of note, the cursor-blink-time *is* honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1798481/+subscriptions

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-06 Thread Mario Vukelic

To be clear, the above debugging output is with xkb-data
2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of
airplane mode by the dedicated key being broken

$ aptitude show xkb-data
Package: xkb-data
Version: 2.23.1-1ubuntu1.18.10.1
State: installed

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-06 Thread Mario Vukelic

@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a
regression with xkb-data 2.23.1-1ubuntu1.18.10.1.

On this machine, the airplane mode key worked perfectly out-of-the-box
(i.e., the key enabled AND disabled the airplane mode) with the
development version of  Cosmic, using xkb-data 2.23. See my comment #13
further up in this bug.

Here's the debug output for gnome-settings-daemon:

[*** Airplane mode is off, Wifi and BT are on ***]

/usr/lib/gnome-settings-daemon/gsd-rfkill -v
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'WLAN' (idx=1): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'BLUETOOTH' (idx=11): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.185: Registered client at 
path /org/gnome/SessionManager/Client29
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.187: Opened rfkill-input 
inhibitor.

[*** Here I am pressing the airplane mode key to enable Airplane mode >
Wifi/BT goes off ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.352: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.353: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing the airplane mode key again to DISable Airplane
mode > Wifi/BT should go back on. This fails and the airplane mode re-
engages immediately as described ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing DISabling Airplane mode from the Gnome panel
menu > Wifi/BT goes back on. This works ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed Bluetooth rfkill 
with ID 11

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1725312] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed() from st_scroll_view_style_changed()

2018-11-06 Thread Iain Lane

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_style_changed() from
  st_scroll_view_style_changed()

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

Bug description:
  [ Impact ]

  gnome-shell randomly crashes

  [ Test case ]

  There's not a real case for this crash, while it's the most recorded in e.u.c 
for bionic, there's no a known way to reproduce this.
  So, monitoring e.u.c results is the easiest way to check if this fixes the 
issue

  [ Regression potential ]

  Gnome-shell has invalid theme for scrolled views

  ---

  https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a
  Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/467
  Upstream fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/190

  ---

  I was restoring a backup when this occurred.  I was not interacting
  with the system at the time.

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
   PC (0x7f840ef624f1) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!SegvReason: writing unknown VMASignal: 
11SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery

2018-11-06 Thread George

Daniel That's interesting. I wasn't aware that it was required to fix a
bug reported on an LTS release on development release first. I find this
curious. It begs the question required by whom? And perhaps more
interesting, why?

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

Title:
  totem silently fails to create screenshot gallery

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  New
Status in totem source package in Cosmic:
  Fix Released

Bug description:
  *Impact

  The gallery plugin/menu option doesn't work

  * Test case

  - open a video
  - open the menu and click on the gallery option
  - validate making a gallery with the default options

  -> the picked filename should exist and be a gallery if pictures from
  the video

  * Regression potential

  The changes are restricted to the screenshot plugin, so make sure that
  one works

  --

  https://gitlab.gnome.org/GNOME/totem/issues/268

  ---

  https://gitlab.gnome.org/GNOME/totem/merge_requests/18/

  ---

  Package totem 3.26.0-0ubuntu6

  totem 3.26.0 running on Ubuntu 18.04 silently fails to create
  screenshot gallery. I'm assuming that this has something to do with
  totem-video-thumbnailer.

  Steps to reproduce:

  totem-video-thumbnailer -g 20 inputvideo outputpng

  I can reproduce this result with both HEVC and AVC encoded videos. I
  haven't been able to test other codecs, but the error indicates the
  codec isn't the problem.

  totem 3.18.1 under Ubuntu 16.04 does not have this problem.

  Any further information required I will be happy to produce within my 
abilities.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-19 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

2018-11-06 Thread Dash

Ubuntu 18.10 does have the same problem, Ubuntu 16.04.2 has *NO*
problem. From where could I get an 4.4 kernel for 18.04 for testing
purpose ?

Other infos: when I check in systems, it show me 3 display despite the
fact that only 2 are connected:

1. internal display
2. unknown display with resolution 1024 x 768 (4:3) 800 x 600 (4:3) 848 x 480 
(16:9) !
3. external display with correct informations (Brand, model, )

I also discover that starting the laptop with the display connected,
shows me the splash image on both displays as it should. Problem arise
on greeting image. From here I see "No input signal" and the external
display goes black.

Daniel

PS: perhaps bug 1723025? could be identical but from my side, I can
start with or without external display, it's only when I use the fn
switch key that problem arise.

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

Title:
  External display not recognized, internal one goes to black

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

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/gdm3/+bug/1801747/+subscriptions

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

[Desktop-packages] [Bug 1801976] [NEW] Display does not work correctly

2018-11-06 Thread HeinzDiedrichsen

Public bug reported:

Initially everything was fine. Then came an update and now the display
is milky and too large. I dont know what to do. What would be the proper
BIOS Setting or how can the issue be settled?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Tue Nov  6 18:07:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 620M/630M/635M/640M 
LE] [144d:c0d1]
InstallationDate: Installed on 2018-11-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABI.026.141024.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550P7C-T0ADE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG SENS
dmi.product.name: 550P5C/550P7C
dmi.product.version: P09ABI
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 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/1801976

Title:
  Display does not work correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD

[Desktop-packages] [Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver

2018-11-06 Thread Mateusz Mikuła

Another workaround is adding `nvidia-drm.modeset=1` to the kernel
command line.

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

Title:
  Ubuntu 18.10 login screen never appears when using the Nvidia driver

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1768271] Re: sudo update-desktop-database results in "font/ttf" is an invalid MIME type ("font" is an unregistered media type)

** Description changed:

- When running:
+ * Impact
  
- $ sudo update-desktop-database
+ The "update-desktop-database" command outputs some "invalid MIME type"
+ warnings
  
- I get this:
+ * Test case
  
+ - install gnome-font-viewer if it's not installed
+ - $ sudo update-desktop-database
+ 
+ you should not get warnings like those
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)
  
+ * Regression potential
  
- I think this is the same bug as this one: 
https://bugzilla.redhat.com/show_bug.cgi?id=1564650
+ Check that fonts files can still be opened from nautilus and preview
+ (browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
+ from there)
+ 
+ --
+ 
+ I think this is the same bug as this one:
+ https://bugzilla.redhat.com/show_bug.cgi?id=1564650
  
  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
-   Installed: 0.23-1ubuntu3
-   Candidate: 0.23-1ubuntu3
-   Version table:
-  *** 0.23-1ubuntu3 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 0.23-1ubuntu3
+   Candidate: 0.23-1ubuntu3
+   Version table:
+  *** 0.23-1ubuntu3 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: desktop-file-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: desktop-file-utils (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  sudo update-desktop-database results in "font/ttf" is an invalid MIME
  type ("font" is an unregistered media type)

Status in desktop-file-utils package in Ubuntu:
  Fix Committed
Status in desktop-file-utils source package in Bionic:
  Triaged

Bug description:
  * Impact

  The "update-desktop-database" command outputs some "invalid MIME type"
  warnings

  * Test case

  - install gnome-font-viewer if it's not installed
  - $ sudo update-desktop-database

  you should not get warnings like those
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

  * Regression potential

  Check that fonts files can still be opened from nautilus and preview
  (browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
  from there)

  --

  I think this is the same bug as this one:
  https://bugzilla.redhat.com/show_bug.cgi?id=1564650

  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
    Installed: 0.23-1ubuntu3
    Candidate: 0.23-1ubuntu3
    Version table:
   *** 0.23-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  Installation

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-06 Thread Andrew Lendrum

@Alberto

This is my first time on launchpad, so please forgive any noob errors.

I followed the instructions to the letter:
I enabled bionic-proposed with: sudo add-apt-repository "deb 
http://archive.ubuntu.com/ubuntu/ $(lsb_release -sc)-proposed restricted main 
universe"
I created /etc/apt/preferences.d/proposed-updates with the specified content
I updated.
Then when I tried to install the packages I saw:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Release 'bionic-proposed' for 'nvidia-driver-390' was not found
E: Release 'bionic-proposed' for 'gdm3' was not found
E: Release 'bionic-proposed' for 'nvidia-settings' was not found
E: Release 'bionic-proposed' for 'libnvidia-gl-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-compute-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-decode-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-encode-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-ifr1-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-fbc1-390' was not found


Am I missing something?

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

--

[Desktop-packages] [Bug 1796361] Re: autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed

Hello Olivier, or anyone else affected,

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

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

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

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

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

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: New => Fix Committed

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

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

Title:
  autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  libreoffice 6.1.2 autopkgtests pass with openjdk 10.0.2+13-1ubuntu1
  that's currently in cosmic. When upgrading openjdk to 11~28-3ubuntu1
  in cosmic-proposed, the test called odk-build-examples reliably fails.
  I'm attaching the log of the failed test, ran separately in an up-to-
  date amd64 cosmic VM with cosmic-proposed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 17:55:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (824 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (21 days ago)

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

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

[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

Hello Simon, or anyone else affected,

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

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

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

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

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

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

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

Title:
  Theming does not work on LXQt

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

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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

[Desktop-packages] [Bug 1791936] Re: GNOME system-monitor cpu graph color does not update or persist

** Changed in: gnome-system-monitor (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GNOME system-monitor cpu graph color does not update or persist

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  1. Description:   Ubuntu 18.04.1 LTS
 Release:   18.04

  2. gnome-system-monitor:
Installed: (none)
Candidate: 3.28.2-0ubuntu1
Version table:
   3.28.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3. I expect the colors to update in the graph and persist across
  application exit.

  4. When I choose a different color for my cpu graphs the color does
  not update in the actual graph.  Also when I close the app and open it
  again the colors seem to reset to default.

  
  Screenshot attached.

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

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

Thanks for the data Mario, seems like it's not the backend then but that there 
is a bug in the key handling. Unsure we can describe it as "regression" though, 
the feature was not working at all, now it's half working.
Or was it something that is currently working on cosmic and which isn't now?

The log doesn't have informations on gnome-settings-daemon though which
would be useful to have (but unsure what's the easiest way to put in
debug mode, maybe restart it manually with --debug?)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1800863] Re: gnome-system-monitor colour pick bug

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

** This bug has been marked a duplicate of bug 1791936
GNOME system-monitor cpu graph color does not update or persist

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

Title:
gnome-system-monitor colour pick bug

Status in gnome-system-monitor package in Ubuntu:
New

Bug description:
In the System Monitor 3.30.0, when changing the colours for the CPUs,
they do not all save. There are cases when they do or perhaps only one
may save. I first realised this when I change the last two core to
custom colours. I also realised that the colours after being changed,
will show in the squares but are not represented by the lines as the
lines display the previous colours. If I then change, say CPU 0, that
colour will show. If I replace CPU1, CPU0's colour will revert on the
graph and the colour for CPU1 will be fine. After a while of closing
and opening the app, all of the colours have finally saved.

I upgraded from Ubuntu 18.04 to 18.10.

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

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

[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack

** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: llvm-toolchain-7 (Ubuntu Bionic)
 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/1798597

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  New
Status in llvm-toolchain-7 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

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

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

[Desktop-packages] [Bug 1768271] Re: sudo update-desktop-database results in "font/ttf" is an invalid MIME type ("font" is an unregistered media type)

** Changed in: desktop-file-utils (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: desktop-file-utils (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  sudo update-desktop-database results in "font/ttf" is an invalid MIME
  type ("font" is an unregistered media type)

Status in desktop-file-utils package in Ubuntu:
  In Progress
Status in desktop-file-utils source package in Bionic:
  Triaged

Bug description:
  When running:

  $ sudo update-desktop-database

  I get this:

  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

  
  I think this is the same bug as this one: 
https://bugzilla.redhat.com/show_bug.cgi?id=1564650

  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
Installed: 0.23-1ubuntu3
Candidate: 0.23-1ubuntu3
Version table:
   *** 0.23-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: desktop-file-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+subscriptions

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

[Desktop-packages] [Bug 1743216] Re: perl crashed with SIGABRT in _dbus_abort()

2018-11-06 Thread Hans Deragon

I confirm that since I installed xdg-utils 1.1.2-1ubuntu2.3 from
Ubuntu:18.04/bionic-proposed, I have not gotten any crashes.

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Bionic:
  Fix Committed
Status in xdg-utils source package in Cosmic:
  Fix Released
Status in xdg-utils package in Debian:
  Unknown

Bug description:
  [ Description ]

  When xdg-screensaver suspend  refers to a window with invalid
  UTF-8 in its title, it will spawn a perl process that crashes with an
  assertion:

    dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
    This is normally a bug in some application using the D-Bus library.

  [ Fix ]

  Use decode() from the Encode module to replace invalid character
  sequences with U+FFFD, the replacement symbol. This is not a new
  dependency as Encode has been a perl core module since 5.8.

  [ QA ]

  I don't know how to get a window with such a title, so we can do two
  things.

  1)

  1. $ sudo -e $(which xdg-screensaver) # hack the script
  2. Find the line "# Inhibit idle detection (flags = 8) with window name and 
ID."
  3. Find the } on its own above that.  Insert a new line afterwards and set 
the window name to be the same as the one in this bug, by pasting the code
    $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News 
Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox";
  4. Save and exit
  5. $ xwininfo
  6. click some window, and copy the "Window id", which will be 0x
  7. $ xdg-screensaver suspend 

  In the bad case (before this bug is fixed) it should crash, and in the
  good case it should work.

  8. Undo what you just did by running $ xdg-screensaver resume 

  2)

  Observe that the error bucket

  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  has a reduction in report rate with the new versions.

  [ Regression potential ]

  If the code is bad then the window name passed to Inhibit() could be
  wrong. That shouldn't matter too much.

  If it is really bad then the program might crash for everybody and
  we'll see an increase in errors.

  [ Original description ]

  Errors Bucket
  -
  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  crashed after launching the software updater

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-4
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 14 13:30:52 2018
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2017-12-28 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201)
  Signal: 6SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1795169] Re: Focus switches constantly between username and password fields

** Changed in: firefox (Ubuntu Bionic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

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

Title:
  Focus switches constantly between username and password fields

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Bionic:
  Confirmed

Bug description:
  https://www.bbva.es/particulares/index.jsp

  If you click on "Entrar"(Log in) the pop-up window that opens allows you to 
enter a username when you click in "usuario"(user) but when you click on "clave 
de acceso"(password) the selection cursor changes continuously between "user" 
and " password ", preventing the introduction of the password.
  Ubuntu 16.04 with firefox 62.0 work fine, when update to ubuntu 18.04.1 LTS 
with firefox 62.0 fail.
  The 18.04 with Chromium 69.0.3497.81, also works well.
  I have the same problem in two computers.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  firefox:
Instalados: 62.0+build2-0ubuntu0.18.04.5
Candidato:  62.0+build2-0ubuntu0.18.04.5
Tabla de versión:
   *** 62.0+build2-0ubuntu0.18.04.5 500
  500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

tagging as rls-cc-notfixing, while good to fix it impacts a non default
plugin and we don't think it's important enough to be actively tracked
by desktop

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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1799614] Re: Use new media API

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

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  In Progress
Status in gnome-software source package in Cosmic:
  New

Bug description:
  snapd now provides 'media' which replaces the old 'screenshots' data.
  We need to migrate to this as the old screenshot data will be removed
  in the future.

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

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

[Desktop-packages] [Bug 1799217] Re: [SRU] Really don't ship Yaru-dark

2018-11-06 Thread Didier Roche

Setting it as Won't fix then for cosmic.

** Changed in: yaru-theme (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  [SRU] Really don't ship Yaru-dark

Status in yaru-theme package in Ubuntu:
  Triaged
Status in yaru-theme source package in Cosmic:
  Won't Fix

Bug description:
  [Impact] 
  We thought we disabled separate dark theme in the package explicitely as long 
as GTK2 part of the dark theme isn't complete.
  Currently, people enabling dark theme have:
  - GTK3 apps with dark theme
  - GTK2 apps with Adwaita theme

  A typo order in package (we remove the dark theme directory AFTER
  dh_install) made it still shipping it. Do it in the correct order
  right now

  [Test Case]
  * Install the new package version from propsoed
  * ls /usr/share/themes/Yaru-dark/
  -> should be empty

  [Regression Potential]
  People who set Yaru Dark theme in Tweaks will default to Adwaita after the 
update. They can set it back to Yaru after the update with the same (unshipped 
by default) tools. We expect them to be technical enough as they changed the 
default.

  
  --

  yaru-theme package for Cosmic Cuttlefish includes 'Yaru-dark', which
  is not complete (it lacks of gtk2 folder).

  Note, as discussed on IRC, in order to support applications that
  prefer dark variant, /usr/share/themes/Yaru/gtk-3.0/gtk-dark.css is
  enough

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

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

[Desktop-packages] [Bug 1776595] Re: No bookmarks in the sidebar of the file manager

2018-11-06 Thread Gunnar Hjalmarsson

This is a misconception. The window menu is opened if you click the icon
with three horizontal bars.

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

** Changed in: gnome-user-docs (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No bookmarks in the sidebar of the file manager

Status in gnome-user-docs package in Ubuntu:
  Invalid

Bug description:
  https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-
  edit.html

  The file manager has been stripped of a lot of (imo useful)
  functionalities, since my first Ubuntu install (12.04). Now, the
  toption to bookmark locations seems to have been removed as well.

  1. Ubuntu Version: Ubuntu 18.04

  2. package: nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4

  3. I expected to get the "window" menu, and in it the option to
  "Bookmark this Location"

  4. But the menu only has one item left, called "files"

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

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

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2018-11-06 Thread bmaupin

In Xubuntu this may be fixable by removing the indicator-application
package:

sudo apt remove indicator-application
xfce4-panel -r

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  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/network-manager-applet/+bug/1761606/+subscriptions

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

[Desktop-packages] [Bug 1776595] [NEW] No bookmarks in the sidebar of the file manager

You have been subscribed to a public bug:

https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-edit.html

The file manager has been stripped of a lot of (imo useful)
functionalities, since my first Ubuntu install (12.04). Now, the toption
to bookmark locations seems to have been removed as well.

1. Ubuntu Version: Ubuntu 18.04

2. package: nautilus:
  Installed: 1:3.26.3-0ubuntu4
  Candidate: 1:3.26.3-0ubuntu4

3. I expected to get the "window" menu, and in it the option to
"Bookmark this Location"

4. But the menu only has one item left, called "files"

** Affects: gnome-user-docs (Ubuntu)
 Importance: Undecided
 Status: Invalid

-- 
No bookmarks in the sidebar of the file manager
https://bugs.launchpad.net/bugs/1776595
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

2018-11-06 Thread Steven Maddox

Have updated the patch to work with 18.04, here are the instructions I
just used to build it (personally I builds like this in a VM)...
ultimately you get the file 'network-manager-
gnome_1.8.10-2ubuntu1_amd64.deb' and that is the only thing you need to
install on normal 18.04 system where you want the fix...

sudo sed -i 's/^# \(deb-src \)/\1/' /etc/apt/sources.list
sudo apt-get update
sudo apt-get build-dep network-manager-applet
wget 
http://archive.ubuntu.com/ubuntu/pool/main/n/network-manager-applet/network-manager-applet_{1.8.10.orig,1.8.10-2ubuntu1.debian}.tar.xz
tar xf network-manager-applet_*.orig.tar.xz
cd network-manager-applet-*/
tar xf ../network-manager-applet_*.debian.tar.xz
wget -P debian/patches 
http://gist.github.com/Lantizia/2f32f0ca8193a61ceefb0c8c95e92bcc/raw/hide_unmanaged_interfaces.patch
sed -i '1s/^/hide_unmanaged_interfaces.patch\n/' debian/patches/series
sudo dpkg-buildpackage -b
# Ignore the bit about not being able to sign it
# Only need to install 'network-manager-gnome_1.8.10-2ubuntu1_amd64.deb'

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

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

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1799947] Re: Application windows in 18.04.01 go black but launcher is still visible

2018-11-06 Thread Paul Chambre

OK. I apparently had to chmod permissions on .cache/apport to allow it
to write the credentials file.

Now I get: "You are not the reporter or subscriber of this problem
report, or the report is a duplicate or already closed."

On the bright side, I haven't seen a black window in a couple of days.

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

Title:
  Application windows in 18.04.01 go black but launcher is still visible

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

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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

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

[Desktop-packages] [Bug 1028267] Re: thunderbird license change not reflected in /usr/share/doc/thunderbird/copyright

2018-11-06 Thread gf

Bug control team: please change this bug to "Low" importance.
Thanks
G

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

Title:
  thunderbird license change not reflected in
  /usr/share/doc/thunderbird/copyright

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

Bug description:
  Now that thunderbird (and firefox, see
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1028266) have
  switched from the MPLv1/GPL/LGPL tri-license to MPL 2.0,
  /usr/share/doc/thunderbird/copyright should reflect this. Also,
  /usr/share/doc/thunderbird/MPL.gz should be updated, or removed if the
  MPL 2.0 would be included in /usr/share/doc/thunderbird/copyright.

  Also, based on a quick look, the license list in this file seem to
  lack quite a few of the licenses in the list one can see at
  about:license (help -> about thunderbird -> licensing information).

  This is for thunderbird 14.0 in Ubuntu 10.04 and 12.04.

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

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

[Desktop-packages] [Bug 1074286] Re: system-config-printer/applet.py should be implemented with a binary executable

2018-11-06 Thread gf

Thanks for updating the status and importance for me, C!
:)
G

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

Title:
  system-config-printer/applet.py  should be implemented with a binary
  executable

Status in system-config-printer package in Ubuntu:
  Triaged

Bug description:
  After loging into XFCE environment, I see with "top" that /usr/share
  /system-config-printer/applet.py consumes 22MB of physical memory,
  just behind X.

  Most of the time, the printer applet does nothing and thus wastes
  memory.

  I think that this applet should be implemented with a compiler which
  create a binary executable instead of writing a python script or
  python byte code which will never reach the performances of a binary
  executable (speed and memory).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: system-config-printer-gnome 1.3.11+20120807-0ubuntu10
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CurrentDmesg: [  913.672003] mtrr: no MTRR for e000,100 found
  Date: Fri Nov  2 10:32:45 2012
  InstallationDate: Installed on 2012-10-20 (12 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=cd43b074-5f0e-46e5-8362-13424056d921 ro quiet splash vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission non accordée: 
'/var/log/cups/error_log'
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6430
  Package: system-config-printer (not installed)
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic 
root=UUID=19fbf7a9-ba26-43ce-9f73-2ffc42922043 ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
  Tags:  xenial
  Uname: Linux 4.4.0-137-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2017-09-02 (398 days ago)
  UserGroups: audio cdrom fuse plugdev sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 08R94K
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn08R94K:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1074286/+subscriptions

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

The update is fine for the disco serie now

** Tags removed: version-blocked-ff

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

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 1797224] Re: Stay on 2.0 for cosmic, update next cycle

** Tags removed: version-blocked-ff

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  The new version requires the MIR situation to be sorted out

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

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

[Desktop-packages] [Bug 1797060] Re: Update to 2.8.1 next cycle

** Tags removed: version-blocked-ff

** Summary changed:

- Update to 2.8.1 next cycle
+ Update to 2.8.1

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

Title:
  Update to 2.8.1

Status in udisks2 package in Ubuntu:
  New

Bug description:
  The new version is not bugfix only, it's for next cycle

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

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

[Desktop-packages] [Bug 1789489] Re: update to 0.3.12

** Summary changed:

- update to 0.3.12 next cycle
+ update to 0.3.12

** Tags removed: version-blocked-ff

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

Title:
  update to 0.3.12

Status in volume-key package in Ubuntu:
  New

Bug description:
  The update is not done in Debian yet because it fails to build,
  waiting for the next update

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

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

[Desktop-packages] [Bug 1801912] [NEW] ctrl-f doesn't open the search box

2018-11-06 Thread Will Cooke

Public bug reported:

In Cosmic if you hit ctrl-f the search bar appears for a second and then
vanishes again.

On Bionic ctrl-f doesn't do anything, which could be preferred.

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

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

Title:
  ctrl-f doesn't open the search box

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In Cosmic if you hit ctrl-f the search bar appears for a second and
  then vanishes again.

  On Bionic ctrl-f doesn't do anything, which could be preferred.

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

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

[Desktop-packages] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug

2018-11-06 Thread Andreas Vinsander

I am not using wayland.

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Desktop-packages] [Bug 1796717] Re: Update to 0.69.0

** Summary changed:

- Update to 0.69.0 next cycle
+ Update to 0.69.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 0.69.0

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  The new version has new features and poppler updates require
  transition due to soname changes, that's for next cycle

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

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

[Desktop-packages] [Bug 1797059] Re: Update to 1.9.0

** Summary changed:

- Update to 1.9.0 next cycle
+ Update to 1.9.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 1.9.0

Status in harfbuzz package in Ubuntu:
  Triaged

Bug description:
  The new version has changes that are not trivial, let's delay to next
  cycle

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

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

[Desktop-packages] [Bug 1789502] Re: Update to 0.6.50

The disco cycle is starting so that's unblocked now

** Tags removed: version-blocked-ff

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  In Progress

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

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

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

[Desktop-packages] [Bug 1792360] Re: Update to 0.18.0

** Summary changed:

- Update to 0.18.0 (next cycle or ffe)
+ Update to 0.18.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 0.18.0

Status in spice-vdagent package in Ubuntu:
  Triaged
Status in spice-vdagent package in Debian:
  New

Bug description:
  The new version is not in Debian yet and includes features (new gtk
  backend, systemd socket activation, ...), marked as blocked by
  feature-freeze

  Update request in Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=905771

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

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

[Desktop-packages] [Bug 1797064] Re: Update to 2.9.8

** Summary changed:

- Update to 2.9.8 next cycle
+ Update to 2.9.8

** Tags removed: version-blocked-ff

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

Title:
  Update to 2.9.8

Status in libxml2 package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian experimental but it's late to update on
  Ubuntu this cycle, especially with a non trivial update on a component
  like that, the update is for next cycle

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

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

[Desktop-packages] [Bug 1797222] Re: Update to 2.13.1 on next cycle

The disco cycle is starting so that's unblocked now

** Tags removed: version-blocked-ff

** Summary changed:

- Update to 2.13.1 on next cycle
+ Update to 2.13.1

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

Title:
  Update to 2.13.1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Updating is not risk free and there is no reason to do that now,
  that's for next cycle

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

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

[Desktop-packages] [Bug 1795924] Re: Update to 7.1-1

** Summary changed:

- Update to 7.1-1 next cycle
+ Update to 7.1-1

** Tags removed: version-blocked-ff

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

Title:
  Update to 7.1-1

Status in fonts-smc-anjalioldlipi package in Ubuntu:
  Triaged

Bug description:
  The changes in the new version are non trivial enough to land now in
  cosmic, that's for next cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-smc-anjalioldlipi/+bug/1795924/+subscriptions

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

[Desktop-packages] [Bug 1792893] Re: Update to 3.7.0

The disco cycle is starting so that's unblocked now

** Summary changed:

- Update to 3.7.0 for next cycle?
+ Update to 3.7.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 3.7.0

Status in liblouis package in Ubuntu:
  Triaged

Bug description:
  Debian updated but the NEWS suggest that update would require a ffe

  "* Noteworthy changes in release 3.7.0 (2018-09-03)
  This release implements major improvements for back-translation thanks
  to concerted efforts by Bue Vester-Andersen, Bert Frees, Timothy Lee
  and others. In particular the input/output positions are now correct
  also for back-translation. There are new and improved Chinese Braille
  tables and some long awaited improvements to UEB. The release also has
  some code cleanups and documentation improvements."

  I'm unsure how to properly test those changes so unless someone steps
  up and request a ffe with testing steps then it's for next cycle

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

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

[Desktop-packages] [Bug 1801898] [NEW] Only one of two external (displayport) displays is working without hotplug

2018-11-06 Thread Andreas Vinsander

Public bug reported:

After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of my 
two external displays will not be activated without hotplugging the other 
external display.
The display settings app shows the second display as inactive, and when trying 
to activate the settings app states that some hardware limitation stops it from 
being possible to apply the change.
The laptop lid is closed, the internal laptop display is not active.

Hotplugging the other external display solves the problem - after
hotplug both external displays are active. This makes the bug annoying
but workaroundable.

I am not sure if this bug belongs to the Xorg package or the linux
package.

Hardware:
Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

$ sudo lspci -v
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu8
  Candidate: 1:7.7+19ubuntu8
  Version table:
 *** 1:7.7+19ubuntu8 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy linux-image-4.18.0-10-generic
linux-image-4.18.0-10-generic:
  Installed: 4.18.0-10.11
  Candidate: 4.18.0-10.11
  Version table:
 *** 4.18.0-10.11 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

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

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-

[Desktop-packages] [Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

2018-11-06 Thread knb

Here : https://bugs.freedesktop.org/show_bug.cgi?id=96312 some people
said this is caused by a "slow compositor" . In my case, it seems to me,
these log entries are probably caused by  a Xorg process running with
100% cpu blocking the UI for ~ 1 minute. This happens after animations
played (e.g. progressbars), window resizing, scrolling, when I have many
GUI apps open. I am still investigating.

My system: nvidia driver, 2 old GPUs, 18.04 with gdm3+Xorg

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

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

Status in libinput:
  Invalid
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have just recently looked in my syslog and discovered that the
  following message shows up a lot daily so I thought I should report
  it:

  /usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset
  negative

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libinput10 1.2.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  1 18:39:08 2016
  InstallationDate: Installed on 2016-05-15 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: libinput
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1743216] Re: perl crashed with SIGABRT in _dbus_abort()

2018-11-06 Thread Jean-Baptiste Lallement

Actually I did a mistake when I updated xdg-screensaver. with $window_name set 
at the right location there is no more crash with the version from proposed.
Marking as verification-done

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

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Bionic:
  Fix Committed
Status in xdg-utils source package in Cosmic:
  Fix Released
Status in xdg-utils package in Debian:
  Unknown

Bug description:
  [ Description ]

  When xdg-screensaver suspend  refers to a window with invalid
  UTF-8 in its title, it will spawn a perl process that crashes with an
  assertion:

    dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
    This is normally a bug in some application using the D-Bus library.

  [ Fix ]

  Use decode() from the Encode module to replace invalid character
  sequences with U+FFFD, the replacement symbol. This is not a new
  dependency as Encode has been a perl core module since 5.8.

  [ QA ]

  I don't know how to get a window with such a title, so we can do two
  things.

  1)

  1. $ sudo -e $(which xdg-screensaver) # hack the script
  2. Find the line "# Inhibit idle detection (flags = 8) with window name and 
ID."
  3. Find the } on its own above that.  Insert a new line afterwards and set 
the window name to be the same as the one in this bug, by pasting the code
    $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News 
Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox";
  4. Save and exit
  5. $ xwininfo
  6. click some window, and copy the "Window id", which will be 0x
  7. $ xdg-screensaver suspend 

  In the bad case (before this bug is fixed) it should crash, and in the
  good case it should work.

  8. Undo what you just did by running $ xdg-screensaver resume 

  2)

  Observe that the error bucket

  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  has a reduction in report rate with the new versions.

  [ Regression potential ]

  If the code is bad then the window name passed to Inhibit() could be
  wrong. That shouldn't matter too much.

  If it is really bad then the program might crash for everybody and
  we'll see an increase in errors.

  [ Original description ]

  Errors Bucket
  -
  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  crashed after launching the software updater

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-4
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 14 13:30:52 2018
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2017-12-28 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201)
  Signal: 6SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1790609] Re: Update evince to 3.28.4

2018-11-06 Thread Jean-Baptiste Lallement

I verified evince 3.28.4-0ubuntu1 from bionic-proposed with a broad
range of PDF and PS documents, some very simple, some complex with
thousands of pages and a variety of fonts and graphics and didn't find
any issue.

Marking as verification-done.

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

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

Title:
  Update evince to 3.28.4

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

Bug description:
  [Impact]
  New release in the stable 3.28 series.

  https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28
  https://gitlab.gnome.org/GNOME/evince/blob/gnome-3-28/NEWS

  [Test Case]
  1. Install new evince version
  2. try opening multiple pdf and ps files, ensure no obvious regression is 
visible.

  [Regression Potential] 
  The visible regression potential is the enable-ps (see comment below), 
otherwise, the new evince upstream release has been released a while ago with 
no post-release fixes: https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28

  [Other Info]
  Please add --enable-ps to the build options since this version disables 
viewing Postscript files as a workaround for security issues in Ghostscript. We 
should fix Ghostscript instead.

  See https://gitlab.gnome.org/GNOME/evince/issues/967

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

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

[Desktop-packages] [Bug 1801896] [NEW] package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kerne

2018-11-06 Thread Vitaliy

Public bug reported:

sudo apt-get install nvidia-340 nvidia-settings
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Уже установлен пакет nvidia-settings самой новой версии 
(396.51-0ubuntu0~gpu16.04.1).
nvidia-settings установлен вручную.
Следующие пакеты устанавливались автоматически и больше не требуются:
  libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 
libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libffi6:i386 
libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386
  libglx-mesa0:i386 libglx0:i386 libllvm6.0:i386 libnvidia-common-390 
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libwayland-client0:i386 
libwayland-server0:i386 libx11-xcb1:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 
libxcb-sync1:i386 libxshmfence1:i386 libxxf86vm1:i386 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime
  nvidia-utils-390
Для их удаления используйте «sudo apt autoremove».
Будут установлены следующие дополнительные пакеты:
  lib32gcc1 libc6-i386 ocl-icd-libopencl1
Рекомендуемые пакеты:
  libcuda1-340 nvidia-opencl-icd-340
Пакеты, которые будут УДАЛЕНЫ:
  libnvidia-cfg1-390 libnvidia-compute-390:i386 libnvidia-decode-390 
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390
  libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 nvidia-375 
nvidia-384 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 
nvidia-headless-no-dkms-390
  xserver-xorg-video-nvidia-390
НОВЫЕ пакеты, которые будут установлены:
  lib32gcc1 libc6-i386 nvidia-340 ocl-icd-libopencl1
Обновлено 0 пакетов, установлено 4 новых пакетов, для удаления отмечено 19 
пакетов, и 19 пакетов не обновлено.
Необходимо скачать 54,7 MB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 37,0 
MB.
Хотите продолжить? [Д/н] 
Пол:1 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 libc6-i386 amd64 
2.27-3ubuntu1 [2 651 kB]
Пол:2 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 lib32gcc1 
amd64 1:8.2.0-1ubuntu2~18.04 [47,9 kB]
Пол:3 http://ru.archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 
nvidia-340 amd64 340.107-0ubuntu0.18.04.1 [51,9 MB]
Пол:4 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 ocl-icd-libopencl1 
amd64 2.2.11-1ubuntu1 [30,3 kB]
Получено 54,7 MB за 5с (10,8 MB/s) 
(Чтение базы данных … на данный момент установлено 202937 файлов и каталогов.)
Удаляется nvidia-375 (384.130-0ubuntu0.16.04.1) …
Удаляется nvidia-384 (390.77-0ubuntu0.18.04.1) …
Удаляется nvidia-driver-390 (390.77-0ubuntu0.18.04.1) …
Удаляется xserver-xorg-video-nvidia-390 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-cfg1-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-encode-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-decode-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-compute-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-encode-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-decode-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-fbc1-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-fbc1-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-ifr1-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-gl-390:i386 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-ifr1-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется libnvidia-gl-390:amd64 (390.77-0ubuntu0.18.04.1) …
Удаляется nvidia-headless-no-dkms-390 (390.77-0ubuntu0.18.04.1) …
Удаляется nvidia-compute-utils-390 (390.77-0ubuntu0.18.04.1) …
Удаляется nvidia-dkms-390 (390.77-0ubuntu0.18.04.1) …
Removing all DKMS Modules
Done.
INFO:Disable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
update-initramfs: deferring update (trigger activated)
Выбор ранее не выбранного пакета libc6-i386.
(Чтение базы данных … на данный момент установлено 202719 файлов и каталогов.)
Подготовка к распаковке …/libc6-i386_2.27-3ubuntu1_amd64.deb …
Распаковывается libc6-i386 (2.27-3ubuntu1) …
Заменено файлами из установленного пакета libc6:i386 (2.27-3ubuntu1) …
Выбор ранее не выбранного пакета lib32gcc1.
Подготовка к распаковке …/lib32gcc1_1%3a8.2.0-1ubuntu2~18.04_amd64.deb …
Распаковывается lib32gcc1 (1:8.2.0-1ubuntu2~18.04) …
Выбор ранее не выбранного пакета nvidia-340.
Подготовка к распаковке …/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb …
Добавляется «отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 в 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib из-за nvidia-340»
Добавляется «отклонение /usr/lib/i386-linux-gnu/libGL.so.1 в 
/usr/lib/i386-linux-gnu/libGL.so.1.distrib из-за nvidia-340»
Добавляется «отклонение /usr/lib/x86_64-linux-gnu/libGL.so в 
/usr/lib/x86_64-linux-gnu/libGL.so.distrib из-

[Desktop-packages] [Bug 1801757] Re: all app indicators disappear