date:20190620

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

** This bug has been marked a duplicate of bug 1832000
   NVidia fails everytime a new kernel update is released : nvidia-340 
340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build

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

Title:
  nvidia kernel module fails to build each kernel update.

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

Bug description:
  nvidia kernel module fails to build each kernel update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.107-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-150.176-generic 4.4.179
  Uname: Linux 4.4.0-150-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.4.0-151-generic
  Date: Wed Jun 19 22:11:11 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2015-11-14 (1313 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: HP-Pavilion AY600AA-ABA HPE-127c
  PackageVersion: 340.107-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-150-generic 
root=UUID=55fcadff-651e-d101-002c-a5ff651ed101 ro quiet splash nomodeset 
usbcore.autosuspend=-1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.07
  dmi.board.name: IONA
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnAY600AA-ABAHPE-127c:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: AY600AA-ABA HPE-127c
  dmi.sys.vendor: HP-Pavilion
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jun 19 21:38:53 2019
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1833617] Re: screen freeze after suspend

Please reproduce the freeze again, then reboot and run:

  journalctl -b-1 > prevboot.txt

and send us the file 'prevboot.txt'.


** Tags added: amdgpu

** Summary changed:

- screen freeze after suspend
+ [amdgpu] screen freeze after suspend

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Changed in: xserver-xorg-video-amdgpu (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/1833617

Title:
  [amdgpu] screen freeze after suspend

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1833617/+subscriptions

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

[Desktop-packages] [Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from

It appears there's only one caller of this function in gnome-shell:

js/ui/osdMonitorLabeler.js:let monitor =
this._monitorManager.get_monitor_for_connector(connector);


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

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Bug description:
  https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f

  gnome shell crashes when I go to Settings -> Devices -> Displays

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 11:01:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (1146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f49b8116bf0 
:mov0x18(%rax),%eax
   PC (0x7f49b8116bf0) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_get_monitor_for_connector () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector()

Tracking in:
https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f

** Description changed:

+ https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
+ 
  gnome shell crashes when I go to Settings -> Devices -> Displays
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 11:01:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (1146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f49b8116bf0 
:mov0x18(%rax),%eax
   PC (0x7f49b8116bf0) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_get_monitor_for_connector () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
+ gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector() from 

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

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

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

Bug description:
  https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f

  gnome shell crashes when I go to Settings -> Devices -> Displays

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 11:01:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (1146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f49b8116bf0 
:mov0x18(%rax),%eax
   PC (0x7f49b8116bf0) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_get_monitor_for_connector () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1833642] Re: /usr/bin/gnome-shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

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

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

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1833534] Re: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

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

** This bug has been marked a duplicate of bug 1833527
   in gnome settings audio section does not see any sound card

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

Title:
  [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 13:01:11 2019
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833534/+subscriptions

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

[Desktop-packages] [Bug 1833642] [NEW] /usr/bin/gnome-shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

2019-06-20 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: artful bionic cosmic disco

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

It's good if you can't reproduce a bug any more. Although your
AlsaInfo.txt shows the main problem was that pulseaudio wasn't running
at all:

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

Let us know if you wish to investigate that problem again.


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

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833527/+subscriptions

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

[Desktop-packages] [Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

gnome-shell!587 only says it fixes gnome-shell#1325. If you think it
also fixes gnome-shell#1370 then you should probably add a comment here:

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587

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

Title:
  App-switcher icons too small with hidpi (3000x2000) monitor

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1370), but given that this is an important part of the
  Ubuntu desktop and that you're providing some patches for improving
  the X11 experience with hidpi monitors, I'm notifying about the issue
  here too.

  It could be related to my previous similar report for fractional
  scaling resolutions: https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1831161. But I'm not sure. Besides, fractional scaling is
  an experimental feature while 2x is not.

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

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

** This bug has been marked a duplicate of bug 1793640
   Pulseaudio fails to detect sound card, while timidity is installed

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => Opinion

** No longer affects: mutter (Ubuntu)

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)

I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about Xorg, not Wayland.

> So it looks like a gdm3 bug.

Yes I understand that's how it looks, but we have established the root
cause of this bug is in the Nvidia driver. Maybe we will be able to work
around it with some gdm3 change, but that's not where the root cause of
the problem is.

Other display managers are managing to work around the Nvidia driver bug
here because they run as root. gdm3 does not run as root because it is
trying to be more secure and avoid running as root. Calling this a gdm3
bug is probably wrong. I can reproduce the bug without gdm3.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

Re: [Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson

I think his point was to isolate the problem as being gdm3's wayland code.
If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)

my point was that you marked this as invalid, but the only way to avoid
this bug is to avoid using gdm3. You don't have to change anything else. So
it looks like a gdm3 bug.

On Fri, 21 Jun 2019 at 11:50, Daniel van Vugt 
wrote:

> Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
> of pointless. It's pointless because the most common reason for using
> nvidia-drm.modeset=1 is to get Wayland support. I know there are other
> reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
> PRIME setups. But mostly if people use modeset=1 it is to get Wayland
> support.
>
> If we can't get a fix from Nvidia then some kind of workaround that runs
> Xorg as root (like comment #26) is probably the next best option.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1716857
>
> Title:
>   nvidia-drm.modeset=1 results in no monitors detected by Xorg
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions
>

-- 
Tim Richardson

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1813471] Re: Thunderbird crashes with GTK_USE_PORTAL environment variable.

2019-06-20 Thread Bug Watch Updater

** Changed in: thunderbird
   Status: New => Confirmed

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

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

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups. But mostly if people use modeset=1 it is to get Wayland
support.

If we can't get a fix from Nvidia then some kind of workaround that runs
Xorg as root (like comment #26) is probably the next best option.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1813471]

2019-06-20 Thread Y-benjamin

Here are the crash reports generated using the beta

bp-b5718f8c-7977-46a4-84b8-d190b0190618 <-- with 'GTK_USE_PORTAL=0
thunderbird'

bp-0fd780e4-9d38-4b70-b887-208e50190618 <-- with 'GTK_USE_PORTAL=1
thunderbird'

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

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

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

2019-06-20 Thread Y-benjamin

I've tested 6.70.0, 6.70.1, 68.0b1, and the daily on Ubuntu 19.04, all
crash after all dialogs are closed and it seems (still needs a little
more testing) at least one email account is setup.

Whats odd is that unless you explicitly set GTK_USE_PORTAL = 1 in the
string to launch TB (i.e.  'GTK_USE_PORTAL=1 thunderbird') the bug is
not triggered.

It also happens regardless to the value you give GTK_USE_PORTAL as
'GTK_USE_PORTAL=0 thunderbird'

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

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

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

[Impact]

With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in white at the bottom, nothing
else.

The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using
the wrong clock. This would lead us to wait forever (or at least 49 years)
before rendering the next frame. There's no decisive way to know this kernel
bug is going to happen before it does so just detect timestamps which are
obviously going to cause freezes and ignore them.

[Test case]

1) Use Virtualbox or VMware ESxi (if you have the infra)
1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA'
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm
with 'lspci -nnvv' command.
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
4) apt-get dist-upgrade
5) Reboot

with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround

[Potential regression]

Low, it should fix vmwgfx and stop using the wrong clock.

A test kernel (pre-sru) has been made available to impact users for them
to test and conclude it works. It does work as expected, and no
regression has been found during the pre-sru testing phase.

It can't be worse than actual situation where the login never appears.
+
+ As per commit description:
+
+ "
+ This should be transparent to to user space, as long as it doesn't
+ compare the time against the result of gettimeofday().
+ "

[Other informations]

upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

[Original description]

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I've been running this Ubuntu 18.04.2 VM without problem for many months
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the
system hangs immediately after displaying the splash screen. I never see a
login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

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

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sun Jun 9 12:38:37 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-05-06 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
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:bd04/13/2018: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.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Ok, including my own testing we got 4 positive feedback. 
With that being said, I have just submitted the patch to our kernel team a few 
minutes ago.

This will be part of the next cycle 01-July through 21-July.

Thanks for the pre-SRU testing, we will need you guys one more time
during the testing phase of bionic-proposed in a couple of weeks.

- Eric


** Tags added: sts

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  It can't be worse than actual situation where the login never appears.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson

"gdm3 compile without wayland", I meant

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson

What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.

we know that gdm3 sessions with external monitors work with root
permissions.

we know that gdm3 compiled with wayland also works (according to the
gentoo user generix).

And neither gnome developers nor nvidia acknowledge a bug. If you make a
venn diagram of all of this, gdm3 is the intersection of every
observation.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

[Impact]

[Test case]

with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround

[Potential regression]

- Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it
- can't be worse than actual situation where the login doesn't appears at
- all.
+ Low, it should fix vmwgfx and stop using the wrong clock.
+
+ A test kernel (pre-sru) has been made available to impact users for them
+ to test and conclude it works. It does work as expected, and no
+ regression has been found during the pre-sru testing phase.
+
+ It can't be worse than actual situation where the login never appears.

[Other informations]

upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

[Original description]

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel Gutierrez

Additional confirmation...

Looks like this updated kernel fixes the issue on the affected test VM I
created.

Using the detailed directions in comment #75, I was able to install the
new test kernel and reboot.

Verified the expected version value with uname and then installed the
packages that were previously hanging from the copies I archived with
the test VM and rebooted.

Login showed up and functioned as normal.  This appears to be the ideal
fix.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  It can't be worse than actual situation where the login never appears.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic

[Desktop-packages] [Bug 1833624] [NEW] [Inspiron 3521, Realtek ALC3221, Black Headphone Out, Front] No sound at all

2019-06-20 Thread Mercedes Alonso

Public bug reported:

Ubuntu 19.04
Processor Intel® Core™ i5-3337U CPU @ 1.80GHz × 4 
Gnome 3.32.1
OS: 64-bit

My speakers are recognized by the system however no sound comes out of them. 
This happens wither plugging them to my laptop or to my projector which is 
connected via HDMI. This is how it used to work with windows 7-
When I perform the sound test, no sound is manifested.
The speakers test does however produce a sound, so it appears that even though 
the Jack connection is detected, no sound comes out.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  redcandy   1633 F pulseaudio
 /dev/snd/pcmC0D0c:   redcandy   1633 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 23:54:53 2019
InstallationDate: Installed on 2019-06-19 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  redcandy   1633 F pulseaudio
 /dev/snd/pcmC0D0c:   redcandy   1633 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Inspiron 3521, Realtek ALC3221, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0010T1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron3521:pvrA08:rvnDellInc.:rn0010T1:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 3521
dmi.product.sku: Inspiron 3521
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot from 2019-06-21 00-11-02.png"
   
https://bugs.launchpad.net/bugs/1833624/+attachment/5271935/+files/Screenshot%20from%202019-06-21%2000-11-02.png

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

Title:
  [Inspiron 3521, Realtek ALC3221, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04
  Processor Intel® Core™ i5-3337U CPU @ 1.80GHz × 4 
  Gnome 3.32.1
  OS: 64-bit

  My speakers are recognized by the system however no sound comes out of them. 
This happens wither plugging them to my laptop or to my projector which is 
connected via HDMI. This is how it used to work with windows 7-
  When I perform the sound test, no sound is manifested.
  The speakers test does however produce a sound, so it appears that even 
though the Jack connection is detected, no sound comes out.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redcandy   1633 F pulseaudio
   /dev/snd/pcmC0D0c:   redcandy   1633 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 23:54:53 2019
  InstallationDate: Installed on 2019-06-19 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redcandy   1633 F pulseaudio
   /dev/snd/pcmC0D0c:   redcandy   1633 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 3521, Realtek ALC3221, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0010T1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron3521:pvrA08:rvnDellInc.:rn0010T1:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 103C_5335KV
  dmi.product.name:

[Desktop-packages] [Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling

2019-06-20 Thread Carlos Pita

There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587

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

Title:
  App-switcher icons too small with hidpi monitor and 1.25 scaling

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is a bug upstream but since Ubuntu has its own fractional scaling
  patch for x11 you might be interested in working together with the
  gnome shell team.  I refer you to my detailed description and some
  preliminary analysis of the cause of the problem in gnome gitlab
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1325.

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

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

[Desktop-packages] [Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-20 Thread Carlos Pita

There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587

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

Title:
  App-switcher icons too small with hidpi (3000x2000) monitor

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1370), but given that this is an important part of the
  Ubuntu desktop and that you're providing some patches for improving
  the X11 experience with hidpi monitors, I'm notifying about the issue
  here too.

  It could be related to my previous similar report for fractional
  scaling resolutions: https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1831161. But I'm not sure. Besides, fractional scaling is
  an experimental feature while 2x is not.

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

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

[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-06-20 Thread Joseph Yasi

** Description changed:

  After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
  in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
+ plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is
  enabled by default in /etc/alsa/conf.d/50-jack.conf.
  
  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.
  
- When enumering the ALSA jack plugin device, it tries to connect to
+ When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again in
  it's cleanup code. Since it's closing the same file descriptor twice, it
  interacts with other threads that have potentially opened file
  descriptors, and causes the crash.
  
- This same bug could potentially affect other multithreaded programs that
- enumerate ALSA devices.
+ This same bug could potentially affect other multi-threaded programs
+ that enumerate ALSA devices.
  
  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  New
Status in jackd2 package in Debian:
  New

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

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

[Desktop-packages] [Bug 1833617] [NEW] screen freeze after suspend

2019-06-20 Thread Meir Levi

Public bug reported:

It's most likely amdgup driver needs an upgrade. Problem occurs since
kernel upgrade to 5.0

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
Uname: Linux 5.0.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompositorRunning: None
Date: Thu Jun 20 13:46:46 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
   Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
InstallationDate: Installed on 2019-06-06 (14 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Dell Inc. Inspiron 3180
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0918N8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3180
dmi.product.sku: 087E
dmi.product.version: 1.3.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug disco 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/1833617

Title:
  screen freeze after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Gary Filipski

Additional confirmation...

Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:

Having performed the workaround of uncommenting the
WaylandEnable=false...

   - Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen

   - Using your ppa, installed the test kernel.

   - Rebooted.

Login proceeded normally: Linux linuxTest 4.15.0-53-generic
#57+hf231164v20190620b11-Ubuntu SMP Thu Jun 20 13:18:41 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux

Thank you!

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze

[Desktop-packages] [Bug 1833611] Re: [snap] mouse pointer on Ubuntu flavours is retro-looking when hovering over links

2019-06-20 Thread Paul White

** Summary changed:

- [snap] mouse pointer on Ubuntu flavours is retro-looking
+ [snap] mouse pointer on Ubuntu flavours is retro-looking when hovering over 
links

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

Title:
  [snap] mouse pointer on Ubuntu flavours is retro-looking when hovering
  over links

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This is a follow-up to Community Hub post:
  
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/52?u=paulw2u

  The installation of the deb to snap transition (for all major Ubuntu
  flavours) was in a live environment using ISOs dated 20190618 or
  20190620. This installed Chromium 75.0.3770.80 or 75.0.3770.90
  depending on the date of the test.

  In Ubuntu and Ubuntu Budgie the mouse pointer, when hovering over a
  link, appears as an upward pointing black hand which is as expected.

  But in Ubuntu MATE, Kubuntu, Lubuntu and Xubuntu the mouse pointer
  appears as a retro looking left pointing white hand.

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Great for the quick feedback.

I have until June 26th to submit the patch for the next cycle[0]

It's giving me a couple of more days to get other impacted users
feedback.

[0] - https://kernel.ubuntu.com/

- Eric

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Pat

Eric,
your new test kernel works for... and screen-resizing works this time too.

To confirm, I am running the correct kernel build;

uname -a

Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP
Thu Jun 20 13:18:41 UTC 2019 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel

[Desktop-packages] [Bug 1833611] [NEW] [snap] mouse pointer on Ubuntu flavours is retro-looking

2019-06-20 Thread Paul White

Public bug reported:

This is a follow-up to Community Hub post:
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/52?u=paulw2u

The installation of the deb to snap transition (for all major Ubuntu
flavours) was in a live environment using ISOs dated 20190618 or
20190620. This installed Chromium 75.0.3770.80 or 75.0.3770.90 depending
on the date of the test.

In Ubuntu and Ubuntu Budgie the mouse pointer, when hovering over a
link, appears as an upward pointing black hand which is as expected.

But in Ubuntu MATE, Kubuntu, Lubuntu and Xubuntu the mouse pointer
appears as a retro looking left pointing white hand.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: eoan snap

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

Title:
  [snap] mouse pointer on Ubuntu flavours is retro-looking

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This is a follow-up to Community Hub post:
  
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/52?u=paulw2u

  The installation of the deb to snap transition (for all major Ubuntu
  flavours) was in a live environment using ISOs dated 20190618 or
  20190620. This installed Chromium 75.0.3770.80 or 75.0.3770.90
  depending on the date of the test.

  In Ubuntu and Ubuntu Budgie the mouse pointer, when hovering over a
  link, appears as an upward pointing black hand which is as expected.

  But in Ubuntu MATE, Kubuntu, Lubuntu and Xubuntu the mouse pointer
  appears as a retro looking left pointing white hand.

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Bionic)
   Importance: Critical => High

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Detailled instructions on how to use my ppa :

$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic 
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic

then reboot, and once login you can confirm if you run my test kernel
with "uname -a" which should report "4.15.0-53.57+hf231164v20190620b11"

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix

[Desktop-packages] [Bug 1828275] Re: [snap] chromium generates a lot of Apparmor noise

2019-06-20 Thread Jamie Strandboge

You can 'sudo snap connect chromium:mount-observe' for /etc/fstab.
/run/mount/utab is more complicated and you can read about it here:
https://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-
libmount/5987

For the /run/udev/data accesses, can you paste the output of:

$ cat /run/udev/data/b230\:*

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

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

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

Title:
  [snap] chromium generates a lot of Apparmor noise

Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Running Chromium's snap result in a lot of Apparmor noise like this:

  audit: type=1400 audit(0): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/mount/utab" pid=0 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(0): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/b230:0" pid=0 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  The above and the attached log was collected with:

  journalctl -o cat -k | grep -F ' apparmor="DENIED" ' | grep -F
  snap.chromium.chromium | sed 's/ audit([0-9.:]\+): / audit(0): /; s/
  pid=[0-9]\+ / pid=0 /' | sort


  Additional information:

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: edge
  refresh-date: 11 days ago, at 12:08 EDT
  channels:
stable:74.0.3729.131 2019-05-02 (705) 162MB -
candidate: 74.0.3729.131 2019-05-01 (705) 162MB -
beta:  74.0.3729.61  2019-04-06 (688) 162MB -
edge:  75.0.3770.9   2019-04-27 (703) 163MB -
  installed:   75.0.3770.9  (703) 163MB -

  $ snap interfaces chromium
  SlotPlug
  :browser-supportchromium:browser-sandbox
  :camera chromium
  :desktopchromium
  :gsettings  chromium
  :home   chromium
  :networkchromium
  :network-bind   chromium
  :opengl chromium
  :personal-files chromium:chromium-config
  :pulseaudio chromium
  :screen-inhibit-control chromium
  :u2f-deviceschromium
  :unity7 chromium
  :upower-observe chromium
  :x11chromium
  gtk-common-themes:gtk-3-themes  chromium
  gtk-common-themes:icon-themes   chromium
  gtk-common-themes:sound-themes  chromium
  -   chromium:cups-control
  -   chromium:mount-observe
  -   chromium:network-manager
  -   chromium:password-manager-service
  -   chromium:removable-media

  $ apt-cache policy snapd
  snapd:
Installed: 2.38+18.04
Candidate: 2.38+18.04
Version table:
   *** 2.38+18.04 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.37.4+18.04.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.32.5+18.04 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

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

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
libbonobo 2.32.1-3 in eoan
libbonobo2-0 2.32.1-3 in eoan amd64
libbonobo2-0 2.32.1-3 in eoan arm64
libbonobo2-0 2.32.1-3 in eoan armhf
libbonobo2-0 2.32.1-3 in eoan i386
libbonobo2-0 2.32.1-3 in eoan ppc64el
libbonobo2-0 2.32.1-3 in eoan s390x
libbonobo2-bin 2.32.1-3 in eoan amd64
libbonobo2-bin 2.32.1-3 in eoan arm64
libbonobo2-bin 2.32.1-3 in eoan armhf
libbonobo2-bin 2.32.1-3 in eoan i386
libbonobo2-bin 2.32.1-3 in eoan ppc64el
libbonobo2-bin 2.32.1-3 in eoan s390x
libbonobo2-common 2.32.1-3 in eoan amd64
libbonobo2-common 2.32.1-3 in eoan arm64
libbonobo2-common 2.32.1-3 in eoan armhf
libbonobo2-common 2.32.1-3 in eoan i386
libbonobo2-common 2.32.1-3 in eoan ppc64el
libbonobo2-common 2.32.1-3 in eoan s390x
libbonobo2-dev 2.32.1-3 in eoan amd64
libbonobo2-dev 2.32.1-3 in eoan arm64
libbonobo2-dev 2.32.1-3 in eoan armhf
libbonobo2-dev 2.32.1-3 in eoan i386
libbonobo2-dev 2.32.1-3 in eoan ppc64el
libbonobo2-dev 2.32.1-3 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #885770
1 package successfully removed.


** Changed in: libbonobo (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo (for liborbit2-dev)

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

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

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
libbonoboui 2.24.5-4 in eoan
libbonoboui2-0 2.24.5-4 in eoan amd64
libbonoboui2-0 2.24.5-4 in eoan arm64
libbonoboui2-0 2.24.5-4 in eoan armhf
libbonoboui2-0 2.24.5-4 in eoan i386
libbonoboui2-0 2.24.5-4 in eoan ppc64el
libbonoboui2-0 2.24.5-4 in eoan s390x
libbonoboui2-bin 2.24.5-4 in eoan amd64
libbonoboui2-bin 2.24.5-4 in eoan arm64
libbonoboui2-bin 2.24.5-4 in eoan armhf
libbonoboui2-bin 2.24.5-4 in eoan i386
libbonoboui2-bin 2.24.5-4 in eoan ppc64el
libbonoboui2-bin 2.24.5-4 in eoan s390x
libbonoboui2-common 2.24.5-4 in eoan amd64
libbonoboui2-common 2.24.5-4 in eoan arm64
libbonoboui2-common 2.24.5-4 in eoan armhf
libbonoboui2-common 2.24.5-4 in eoan i386
libbonoboui2-common 2.24.5-4 in eoan ppc64el
libbonoboui2-common 2.24.5-4 in eoan s390x
libbonoboui2-dev 2.24.5-4 in eoan amd64
libbonoboui2-dev 2.24.5-4 in eoan arm64
libbonoboui2-dev 2.24.5-4 in eoan armhf
libbonoboui2-dev 2.24.5-4 in eoan i386
libbonoboui2-dev 2.24.5-4 in eoan ppc64el
libbonoboui2-dev 2.24.5-4 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #885769
1 package successfully removed.


** Changed in: libbonoboui (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo (for liborbit2-dev)

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

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

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan s390x
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan s390x
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan s390x
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan s390x
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan s390x
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan i386
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan ppc64el
libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #893922
1 package successfully removed.


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

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
orbit2 1:2.14.19-4 in eoan
liborbit-2-0 1:2.14.19-4 in eoan amd64
liborbit-2-0 1:2.14.19-4 in eoan arm64
liborbit-2-0 1:2.14.19-4 in eoan armhf
liborbit-2-0 1:2.14.19-4 in eoan i386
liborbit-2-0 1:2.14.19-4 in eoan ppc64el
liborbit-2-0 1:2.14.19-4 in eoan s390x
liborbit2 1:2.14.19-4 in eoan amd64
liborbit2 1:2.14.19-4 in eoan arm64
liborbit2 1:2.14.19-4 in eoan armhf
liborbit2 1:2.14.19-4 in eoan i386
liborbit2 1:2.14.19-4 in eoan ppc64el
liborbit2 1:2.14.19-4 in eoan s390x
liborbit2-dev 1:2.14.19-4 in eoan amd64
liborbit2-dev 1:2.14.19-4 in eoan arm64
liborbit2-dev 1:2.14.19-4 in eoan armhf
liborbit2-dev 1:2.14.19-4 in eoan i386
liborbit2-dev 1:2.14.19-4 in eoan ppc64el
liborbit2-dev 1:2.14.19-4 in eoan s390x
orbit2 1:2.14.19-4 in eoan amd64
orbit2 1:2.14.19-4 in eoan arm64
orbit2 1:2.14.19-4 in eoan armhf
orbit2 1:2.14.19-4 in eoan i386
orbit2 1:2.14.19-4 in eoan ppc64el
orbit2 1:2.14.19-4 in eoan s390x
orbit2-nameserver 1:2.14.19-4 in eoan amd64
orbit2-nameserver 1:2.14.19-4 in eoan arm64
orbit2-nameserver 1:2.14.19-4 in eoan armhf
orbit2-nameserver 1:2.14.19-4 in eoan i386
orbit2-nameserver 1:2.14.19-4 in eoan ppc64el
orbit2-nameserver 1:2.14.19-4 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #890459
1 package successfully removed.


** Changed in: orbit2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo (for liborbit2-dev)

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

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

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
libgnome 2.32.1-6 in eoan
libgnome-2-0 2.32.1-6 in eoan amd64
libgnome-2-0 2.32.1-6 in eoan arm64
libgnome-2-0 2.32.1-6 in eoan armhf
libgnome-2-0 2.32.1-6 in eoan i386
libgnome-2-0 2.32.1-6 in eoan ppc64el
libgnome-2-0 2.32.1-6 in eoan s390x
libgnome2-0 2.32.1-6 in eoan amd64
libgnome2-0 2.32.1-6 in eoan arm64
libgnome2-0 2.32.1-6 in eoan armhf
libgnome2-0 2.32.1-6 in eoan i386
libgnome2-0 2.32.1-6 in eoan ppc64el
libgnome2-0 2.32.1-6 in eoan s390x
libgnome2-bin 2.32.1-6 in eoan amd64
libgnome2-bin 2.32.1-6 in eoan arm64
libgnome2-bin 2.32.1-6 in eoan armhf
libgnome2-bin 2.32.1-6 in eoan i386
libgnome2-bin 2.32.1-6 in eoan ppc64el
libgnome2-bin 2.32.1-6 in eoan s390x
libgnome2-common 2.32.1-6 in eoan amd64
libgnome2-common 2.32.1-6 in eoan arm64
libgnome2-common 2.32.1-6 in eoan armhf
libgnome2-common 2.32.1-6 in eoan i386
libgnome2-common 2.32.1-6 in eoan ppc64el
libgnome2-common 2.32.1-6 in eoan s390x
libgnome2-dev 2.32.1-6 in eoan amd64
libgnome2-dev 2.32.1-6 in eoan arm64
libgnome2-dev 2.32.1-6 in eoan armhf
libgnome2-dev 2.32.1-6 in eoan i386
libgnome2-dev 2.32.1-6 in eoan ppc64el
libgnome2-dev 2.32.1-6 in eoan s390x
libgnome2-doc 2.32.1-6 in eoan amd64
libgnome2-doc 2.32.1-6 in eoan arm64
libgnome2-doc 2.32.1-6 in eoan armhf
libgnome2-doc 2.32.1-6 in eoan i386
libgnome2-doc 2.32.1-6 in eoan ppc64el
libgnome2-doc 2.32.1-6 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #885768
1 package successfully removed.


** Changed in: libgnome (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo (for liborbit2-dev)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

Removing packages from eoan:
libgnome-keyring 3.12.0-1build1 in eoan
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan i386
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan ppc64el
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan s390x
libgnome-keyring-common 3.12.0-1build1 in eoan amd64
libgnome-keyring-common 3.12.0-1build1 in eoan arm64
libgnome-keyring-common 3.12.0-1build1 in eoan armhf
libgnome-keyring-common 3.12.0-1build1 in eoan i386
libgnome-keyring-common 3.12.0-1build1 in eoan ppc64el
libgnome-keyring-common 3.12.0-1build1 in eoan s390x
libgnome-keyring-dev 3.12.0-1build1 in eoan amd64
libgnome-keyring-dev 3.12.0-1build1 in eoan arm64
libgnome-keyring-dev 3.12.0-1build1 in eoan armhf
libgnome-keyring-dev 3.12.0-1build1 in eoan i386
libgnome-keyring-dev 3.12.0-1build1 in eoan ppc64el
libgnome-keyring-dev 3.12.0-1build1 in eoan s390x
libgnome-keyring0 3.12.0-1build1 in eoan amd64
libgnome-keyring0 3.12.0-1build1 in eoan arm64
libgnome-keyring0 3.12.0-1build1 in eoan armhf
libgnome-keyring0 3.12.0-1build1 in eoan i386
libgnome-keyring0 3.12.0-1build1 in eoan ppc64el
libgnome-keyring0 3.12.0-1build1 in eoan s390x
libgnome-keyring0-dbg 3.12.0-1build1 in eoan amd64
libgnome-keyring0-dbg 3.12.0-1build1 in eoan arm64
libgnome-keyring0-dbg 3.12.0-1build1 in eoan armhf
libgnome-keyring0-dbg 3.12.0-1build1 in eoan i386
libgnome-keyring0-dbg 3.12.0-1build1 in eoan ppc64el
libgnome-keyring0-dbg 3.12.0-1build1 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #892359
1 package successfully removed.


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

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  Fix Released
Status in libbonobo package in Ubuntu:
  Fix Released
Status in libbonoboui package in Ubuntu:
  Fix Released
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome-keyring package in Ubuntu:
  Fix Released
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo

[Desktop-packages] [Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting

2019-06-20 Thread Treviño

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

** Tags added: fixed-in-3.33.3 fixed-upstream

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

Title:
  Xwayland not using XAUTHORITY, prevents root applications from
  connecting

Status in gdm:
  Expired
Status in GParted:
  Fix Released
Status in Mutter:
  Unknown
Status in Ubuntu GNOME:
  Invalid
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gparted package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  When running wayland, GDM fails to set up an XAUTHORITY file and instead
  relies on the process UID for authentication.  This prevents
  applications run as root, like gparted or synaptic from connecting to
  the server.  GDM needs to set up the XAUTHORITY file when running
  Xwayland just like it does when it runs the conventional Xorg.

  A large list of applications broken by this can be found here:

  https://codesearch.debian.net/search?q=Exec%3Dsu-to-
  root+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1

  openSUSE handles this issue with this patch (from the changelog, it looks 
like they implemented this for their YaST settings app):
  
https://build.opensuse.org/package/view_file/GNOME:Factory/mutter/mutter-xwayland-create-xauthority.patch?expand=1

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

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

[Desktop-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

Ok I managed to fix it

rm -rf ~/.config/chrome-remote-desktop/pulse*

Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833527/+subscriptions

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

[Desktop-packages] [Bug 1833534] Re: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

Ok I managed to fix it

rm -rf ~/.config/chrome-remote-desktop/pulse*

Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/

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

Title:
  [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 13:01:11 2019
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833534/+subscriptions

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel Gutierrez

Here is the last of the output after running the first test repo update
command in comment #73 on the Bug1832138VM.zip VM I built.

I'm guessing either there is an integrity issue upstream or more likely
there is a missing step so that a system that has been using the default
repo settings is superseded by the test repo for the updated package(s).
If I ignore these errors and upgrade after update I get the 49 year hang
on reboot.

E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/Packages.xz
  File has unexpected size (543836 != 543620). Mirror sync in progress? [IP: 
91.189.91.23 80]
   Hashes of expected file:
- Filesize:543620 [weak]
- SHA256:3b6cc1e3be5322bc0c88e8dbeecee75d75ed68460ef281d94e9d59ed432224bb
- SHA1:022b402b91b0d22d1e2c321c2417c875a2ee8428 [weak]
- MD5Sum:a3e4b55f39d2645601f31ea6835092ad [weak]
   Release file created at: Thu, 20 Jun 2019 17:41:04 +
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/Packages.xz
  
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/dep11/icons-64x64.tar.gz
  
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock. Sure thing,
  it can't be worse than actual situation where the login doesn't
  appears at all.

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

** Description changed:

+ [Impact]
+ 
+ With most recent version of mutter installed. 
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive) 
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at the bottom, nothing else.
+ 
+ The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
+ before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.
+ 
+ [Test case]
+ 
+ 1) Use Virtualbox or VMware ESxi (if you have the infra)
+  - [vbox] Make sure in the VM setting that the display uses 'VMSVGA' which 
will force the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 
'lspci -nnvv' command.
+ 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
+ 4) apt-get dist-upgrade
+ 5) Reboot
+ 
+ with 4.15 it will fails
+ with hwe kernel 4.18 it will work as expected.
+ 
+ [Potential regression]
+ 
+ Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it
+ can't be worst than current situation where the login doesn't appears at
+ all.
+ 
+ [Other informations]
+ 
+ upstream fix:
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f
+ 
+ [Original description]
+ 
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
  Pro.
  
  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.
  
  I can SSH into the system however.
  
  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false
  
  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.
  
  After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
  shown in this 'uname -a' output;
  
  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
  2019 x86_64 x86_64 x86_64 GNU/Linux
  
  lsb_release -a output;
  
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
-  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
-Subsystem: VMware SVGA II Adapter [15ad:0405]
+  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
+    Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

After building and testing:

"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"

the above seems to do the trick ^ which will make the SRU easier (only one 
commit).
I just don't know why the kernel git bisect testing found another commit, but 
anyway.

Anybody impacted want to test this testpkg to double-check before I
submit the patch to the kernel team ?

sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update

Version: 4.15.0-53.57+hf231164v20190620b11

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to

[Desktop-packages] [Bug 1833471] Re: Can not enable Wifi Hotspot

2019-06-20 Thread Marcel Beerli

Here the journalctl info
I tested the Hotspot option with or without docking station.
Let me know if you need anything else

** Attachment added: "journal.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+attachment/5271861/+files/journal.zip

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

Title:
  Can not enable Wifi Hotspot

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

Bug description:
  Ubuntu 19.04 fresh upgrade
  Hotspot was working on Elitebook 740G2 on Ubuntu 16.04
  was no longer working on Ubuntu 18.04

  When Wifi is enabled, I can connect to wifi router. So wifi works
  When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to 
Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it 
clears the "Visible Networks" box, a few seconds later is shows available 
networks again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 23:07:45 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-07-19 (1431 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1800260] Re: [snap] with CSD, minimize and maximize buttons are invisible until hovered

2019-06-20 Thread Olivier Tilloy

Preliminary investigation: the code in chromium responsible for looking
up the theme color for the header bar is there:
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/gtk_ui.cc?type=cs=864.

Outside of the snap confinement, the query for "#headerbar.header-
bar.titlebar" returns the expected RGB value (for Yaru) of (43,43,41).
But within the snap confinement the computed value is (242,242,242).

I suspect the version of Yaru that's in gtk-common-themes has something
to do with this, but I need to write a minimal reproducer to verify
that.

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

Title:
  [snap] with CSD, minimize and maximize buttons are invisible until
  hovered

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Channel:Stable
  Version:70.0.3538.67
  Updated:10/19/2018
  License:Free
  Developer:  Canonical
  Source: Snap Store
  Installed Size: 148.2 MB

  Settings -> Appearance: "Use system title bar and borders" was turned
  off. Close, minimize, maximize buttons became oval (more of stretched
  down) instead of circle. Turned back it on, buttons went back to
  normal shape (circle). It's a repeatable action.

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-06-20 Thread Adrian Mariano

I finally posted on the pulseaudio list and someone referred me to this
bug:

https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640

I uninstalled timidity and that seems to have fixed the problem.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1829377] Re: Remove this package

cdebconf-terminal also build-depends on libvte-dev, this should be
resolved first before we do an Ubuntu-specific removal.

** Also affects: cdebconf-terminal (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove this package

Status in cdebconf-terminal package in Ubuntu:
  New
Status in vte package in Ubuntu:
  New
Status in vte package in Debian:
  New

Bug description:
  Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
  Eoan.

  Upstream version has been unmaintained for about 8 years, development
  continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).

  Geany is the only package referring to it, and it also does
  incorrectly since it already uses GTK3, see bug 1829375.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libvte9 1:0.28.2-6
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 16 13:41:04 2019
  InstallationDate: Installed on 2016-11-09 (917 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: vte
  UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)

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

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

[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory

2019-06-20 Thread Brian Murray

** Tags removed: rls-ee-incoming

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

Title:
  jackdbus fails to start: cannot allocate memory

Status in systemd:
  Fix Released
Status in jackd2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in jackd2 source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  The `.log/jack/jackdbus.log` shows the following after trying to
  start/restart jack using "Ubuntu Studio Controls" (also tried using
  `jack_control start`):

  ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
  memory)

  This is a fresh install of Ubuntu Studio 19.04, installed via USB. The
  first thing I did after installing was check to see if jack was
  running, but unfortunately it's not working. The error would seem to
  indicate that I'm not in the `audio` group, however checking `groups`
  shows that I am in the audio group.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: jackd2 1.9.12~dfsg-2build1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
  Uname: Linux 5.0.0-13-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 12 18:13:25 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 
(20190416)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory

2019-06-20 Thread Dimitri John Ledkov

** Also affects: systemd (Ubuntu Eoan)
   Importance: High
   Status: Confirmed

** Also affects: jackd2 (Ubuntu Eoan)
   Importance: Undecided
   Status: Invalid

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

Title:
  jackdbus fails to start: cannot allocate memory

Status in systemd:
  Fix Released
Status in jackd2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in jackd2 source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  The `.log/jack/jackdbus.log` shows the following after trying to
  start/restart jack using "Ubuntu Studio Controls" (also tried using
  `jack_control start`):

  ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
  memory)

  This is a fresh install of Ubuntu Studio 19.04, installed via USB. The
  first thing I did after installing was check to see if jack was
  running, but unfortunately it's not working. The error would seem to
  indicate that I'm not in the `audio` group, however checking `groups`
  shows that I am in the audio group.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: jackd2 1.9.12~dfsg-2build1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
  Uname: Linux 5.0.0-13-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 12 18:13:25 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 
(20190416)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

I already did that test ^  using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.

But based on last duflu update, I as I said I will now give a try again
but this time using Ubuntu kernel as follow:

9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57

Let's see what will be the outcome in a couple of hours.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to :

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

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

[Desktop-packages] [Bug 1833555] [NEW] Add OEM->Family

2019-06-20 Thread Jean-Baptiste Lallement

Public bug reported:

Some OEM store the commercial name of the product into the Family field
of the system information record of smbios.

Please add this fied to ubuntu-report.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-report 1.5.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 14:49:35 2019
Dependencies:
 gcc-9-base 9.1.0-4ubuntu1
 libc6 2.29-0ubuntu2
 libgcc1 1:9.1.0-4ubuntu1
 libidn2-0 2.0.5-1
 libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2014-07-15 (1801 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubuntu-report
UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

** Affects: ubuntu-report (Ubuntu)
 Importance: Undecided
 Assignee: Jean-Baptiste Lallement (jibel)
 Status: New


** Tags: amd64 apport-bug eoan

** Changed in: ubuntu-report (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

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

Title:
  Add OEM->Family

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  Some OEM store the commercial name of the product into the Family
  field of the system information record of smbios.

  Please add this fied to ubuntu-report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-report 1.5.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:49:35 2019
  Dependencies:
   gcc-9-base 9.1.0-4ubuntu1
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-4ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2014-07-15 (1801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2019-06-20 Thread Launchpad Bug Tracker

This bug was fixed in the package gnome-settings-daemon -
3.32.1-1ubuntu2

---
gnome-settings-daemon (3.32.1-1ubuntu2) eoan; urgency=medium

* debian/patches/ubuntu_ibus_configs.patch:
- Always call add_ibus_sources_from_locale() during the first run
of g-s-d. This ensures that an IBus method is included in "live
sessions" when applicable (LP: #1786344).

-- Gunnar Hjalmarsson Thu, 20 Jun 2019 11:57:11
+0100

** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress => Fix Released

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Bionic:
Confirmed

Bug description:
[Impact]

If you

* start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

* wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

* select a language which requires an input method for typing

* click the "Try Ubuntu" button

no IBus method is made easily available via the input source indicator
in the session you enter. If you for instance select zh_CN as language
and "Try Ubuntu", you would expect to enter a session with the
"Intelligent Pinyin" method included among the available input
sources.

The proposed fix should ensure that an IBus method is always available
in "live sessions" in languages which are prepared for it.

[Test Case]

1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
not included among your available input sources.

2. Generate the Chinese locale:

sudo locale-gen zh_CN.UTF-8

3. Add to ~/.profile this line:

export LC_CTYPE=zh_CN.UTF-8

4. Remove the gnome-settings-daemon stamp file:

rm ~/.local/share/gnome-settings-daemon/input-sources-converted

5. Log out and log in again.

=> Find that the "Intelligent Pinyin" method was not added (since the
sources already in the list prevented it from being added).

6. Install gnome-settings-daemon from bionic-proposed.

7. Repeat step 4 and 5.

=> Find that the "Intelligent Pinyin" method was added.

[Regression Potential]

The proposed upload includes a small change which specifically
addresses the issue as described above. I find that the risk for
adverse side effects is low.

[Original description]

Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1781049] Re: WiFi hard blocked after resuming laptop from suspend

2019-06-20 Thread Dexter

Apologies for the delay, was busy with college work. I recall having
this bug on Ubuntu 16.04 and 17.04 too. I will have to install and see.
Also, this bug exists on Kubuntu (not surprising) Fedora, Manjaro (both
latest kernels and updates) . I tried digging up more info on hp-wmi
etc. but nothing worked out.

Can I use a live-CD and check with the Ubuntu version that ships with
this kernel or do I have to install it on the system?

Thank you for your time and help!

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

Title:
  WiFi hard blocked after resuming laptop from suspend

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

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  1a9d81bf-e7f5-4f8a-956f-96180dc493e1  wifi  1531450229  Thu 
12 Jul 2018 09:50:29 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlo1activated

[Desktop-packages] [Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height

2019-06-20 Thread Dmytro

In the .H files of the libappindicator I have found 2 authors' e-mails:
Ted Gould  and Cody Russell
. I have written email and received the
email-daemon answer that this e-mails are not valid. I see the problem
and want to know who can help me to find the decision.

Could you be so kind to direct me in the right way and say the real
email or website where I can ask how to resolve the problem?

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

Title:
  Shell boxpointer menus don't have scroll buttons when they exceed the
  screen height

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

Bug description:
  I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
  consist of constant items and many dynamically added items. If the
  screen pixel resolution is not so good as it must be then the last
  menu items are not visible. Ubuntu 16.04 automatically add top and
  bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
  is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
  scrolling bars are not appearing.

  On the other hand menu scrolling is working fine anywhere into usual
  GTK window with menu bar (without using appindicator). Ubuntu 16.04
  and Ubuntu 18.04 use the same 12.10.1 libappindicator version.

  Here is the test c program which illustrates the issue. It works fine
  in Linux Ubuntu 16.04 and has the described above problem in Linux
  18.04:

  #include 
  #include 

  #define LOGO_PNG "/home/super/my-project/menu-test/logo.png"

  AppIndicator* c_indicator;
  GtkWidget* c_menu;

  void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
  {
  gtk_main_quit();
  }

  int main(int argc, char *argv[])
  {
  gtk_init(, );

  int i;
  GtkWidget* item;
  char title[128];

  c_menu = gtk_menu_new();

  item = gtk_menu_item_new_with_label("Quit");
  g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
  gtk_widget_show(item);

  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
  gtk_separator_menu_item_new());

  for (i = 1; i <= 100; ++i) {
  snprintf(title, sizeof(title), "Item #%03u", i);
  item = gtk_menu_item_new_with_label(title);
  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
  gtk_widget_show(item);
  }

  //

  c_indicator = app_indicator_new("Menu Test", LOGO_PNG, 
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
  app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
  app_indicator_set_icon(c_indicator, LOGO_PNG);
  app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));

  gtk_main();

  return 0;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 21:15:59 2019
  InstallationDate: Installed on 2018-07-03 (325 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libappindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

2019-06-20 Thread Rüdiger Kupper

For the record: Upstream bug is at
https://bugs.launchpad.net/hplip/+bug/1036236. But projects are linked.

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

Title:
hpcups and hpijs driver use different rasterization

Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Won't Fix

Bug description:
HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
- hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
- hp-color_laserjet_cp1515n-pcl3.ppd

The new hpcups shall replace the old hpijs, however, it produces very
different rasterization results, resulting in a radically different
visual impression. Differences are especially prominent for greyscale
prints.

Hpcups produces "amplitude modulation" halftones (dots of different
sizes at fixed locations). When resolution is set to "Normal", the
size of these dots is so large that contours cannot be reproduced with
reasonable detail. Heavy aliasing can be easily seen in the circle
contours on the Ubuntu Printer test page. Printing photographs in
greyscale mode yields badly rasterized images like those known from
low-quality newspaper prints (dot pattern is so prominent it dominates
image contours). Artifacts are reduced, but still visible at
resolution "Best".

In contrast, hpijs produces "frequency modulation" halftones with
stochastic dithering (small-sized dots placed at varying densities).
At resolution "Normal", it produces evenly colored areas with
reasonably sharp edges. Circle contours on the Ubuntu Printer test
page appear continuous. Photographs are reproduced at a a much higher
fidelity as with the hpcups driver.

Questions:
1. Why do the two drivers use different rasterization?
2. Why is the result of rasterization so bad in the hpcups driver, set at
resolution "Normal, Greyscale"?

Note:
Both drivers produce acceptable color prints with much fewer artifacts
visible, even at resolution "Normal".

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: hplip 3.12.2-1ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
CurrentDmesg: [ 63.368304] init: plymouth-stop pre-start process (1700)
terminated with status 1
Date: Mon Aug 13 16:38:16 2012
Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
MachineType: exone D156200
Papersize: letter
PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
dmi.bios.date: 04/23/2004
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 4.06 Rev. 1.09.1562
dmi.board.name: D1562
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D1562
dmi.chassis.type: 6
dmi.chassis.vendor: exone
dmi.modalias:
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
dmi.product.name: D156200
dmi.sys.vendor: exone

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

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

2019-06-20 Thread Rüdiger Kupper

Hello J T,
thanks for reporting that this is still a problem. I had originally filed this
report in 2012, but since it never moved forward I just resigned and kept using
the HPIJS driver, which produces much better (in terms of visually accurate)
output. However, Till Kamppeter says that Ubuntu is actively phasing out the
HPIJS driver. This means that the HPCUPS driver needs to be improved/fixed.

This bug is (upstream) assigned to Suma Byrappa, so he/she should be the
person to contact.

@Suma Byrappa:
Can you confirm that hpcups uses different halftoning algorithms (amplitude vs.
frequency modulation). Why is this? Why does it mainly concern greyscale
prints, not color? How about adding an option of selecting the algorithm in the
officially maintained driver (which is hpcups, as I understand)?

Thanks for your support!

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

Title:
hpcups and hpijs driver use different rasterization

Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Won't Fix

Bug description:
HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
- hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
- hp-color_laserjet_cp1515n-pcl3.ppd

Questions:
1. Why do the two drivers use different rasterization?
2. Why is the result of rasterization so bad in the hpcups driver, set at
resolution "Normal, Greyscale"?

Note:
Both drivers produce acceptable color prints with much fewer artifacts
visible, even at resolution "Normal".

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

[Desktop-packages] [Bug 1833534] Re: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

i only see chrome device as output device after manually running
pulseaudio -D and pulseaudio --check

** Attachment added: "Screenshot from 2019-06-20 12-58-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+attachment/5271795/+files/Screenshot%20from%202019-06-20%2012-58-29.png

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

Title:
  [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 13:01:11 2019
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833534/+subscriptions

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

[Desktop-packages] [Bug 1833534] [NEW] [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

Public bug reported:

in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.

I have excatly same problem on PC where configuration is completely
different than my laptops one.

All the problems started recently, after upgrading to 19.04 some time
later one of the updates destroyed all sound

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 13:01:11 2019
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550GEX.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550GEX
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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook Pro
dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug disco

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

Title:
  [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 13:01:11 2019
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833534/+subscriptions

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

[Desktop-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

** Attachment added: "after run pulseaudio -D and pulseaudio --check"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271788/+files/Screenshot%20from%202019-06-20%2012-58-29.png

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833527/+subscriptions

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

[Desktop-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

More info after i run pulseaudio --check i can see an output device but
its not my sound card, another screenshot attached

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833527/+subscriptions

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

[Desktop-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

** Attachment added: "Screenshot from 2019-06-20 12-46-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271783/+files/Screenshot%20from%202019-06-20%2012-46-32.png

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  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/pulseaudio/+bug/1833527/+subscriptions

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

[Desktop-packages] [Bug 1833527] [NEW] in gnome settings audio section does not see any sound card

Public bug reported:

in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.

I have excatly same problem on PC where configuration is completely
different than my laptops one.

All the problems started recently, after upgrading to 19.04 some time
later one of the updates destroyed all sound

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 12:28:49 2019
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550GEX.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550GEX
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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook Pro
dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug disco

** Description changed:

  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.
  
  I have excatly same problem on PC where configuration is completely
- different than my laptops one
+ different than my laptops one.
+ 
+ All the problems started recently, after upgrading to 19.04 some time
+ later one of the updates destroyed all sound
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

2019-06-20 Thread Till Kamppeter

J T, you are posting your auto-generated bug data here but do not post a
comment telling what is exactly your observation.

Note that in HPLIP upstream HPIJS is still contained but not further
developed. We also do not explicitly support it any more in Ubuntu, we
encourage users to switch to hpcups and do even automatic migration.

If you observe any output quality advantage in HPIJS, please report a
new bug to HPLIP upstream (https://bugs.launchpad.net/hplip/), so that
they can compare and improve the hpcups driver.

Nothing of Ubuntu and its packaging is involved here. So I am closing
this bug.

** Changed in: hplip (Ubuntu)
Status: Incomplete => Won't Fix

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

Title:
hpcups and hpijs driver use different rasterization

Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Won't Fix

Bug description:
HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
- hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
- hp-color_laserjet_cp1515n-pcl3.ppd

Questions:
1. Why do the two drivers use different rasterization?
2. Why is the result of rasterization so bad in the hpcups driver, set at
resolution "Normal, Greyscale"?

Note:
Both drivers produce acceptable color prints with much fewer artifacts
visible, even at resolution "Normal".

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

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

Hello gf.

I am not Rüdiger, the original submitter of this bug, but I am affected
by it. Since Rüdiger has not posted to this bug report in over 7 years,
I am posting to it to let you know that:

1) It *is* still a problem,
2) I *am* still interested in finding a solution to this bug,
and
3) I would like you to *not* close the ticket.

Is there a better place for me to report this bug? (HP's FAQ at
https://developers.hp.com/hp-linux-imaging-and-printing/faqs suggests
reporting it here, but this bug doesn't seem to have had any work done
on it since Suma Byrappa (suma-byrappa) became an assignee in December
2013).

Thanks.

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

Title:
hpcups and hpijs driver use different rasterization

Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Won't Fix

Bug description:
HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
- hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
- hp-color_laserjet_cp1515n-pcl3.ppd

Questions:
1. Why do the two drivers use different rasterization?
2. Why is the result of rasterization so bad in the hpcups driver, set at
resolution "Normal, Greyscale"?

Note:
Both drivers produce acceptable color prints with much fewer artifacts
visible, even at resolution "Normal".

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

[Desktop-packages] [Bug 1036236] UdevDb.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] ProcModules.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] ProcInterrupts.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] ProcEnviron.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] Locale.txt

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1036236/+attachment/5271750/+files/Locale.txt

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1036236/+attachment/5271754/+files/ProcCpuinfo.txt

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] Lsusb.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] Dependencies.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] CurrentDmesg.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] Lspci.txt

apport information

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

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] PrintingPackages.txt

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1036236/+attachment/5271753/+files/PrintingPackages.txt

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CupsErrorLog:
 W [20/Jun/2019:09:16:39 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'serverLaser.hpijs-Gray..\' already exists
 W [20/Jun/2019:09:16:39 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'serverLaser.hpijs-RGB..\' already exists
 W [20/Jun/2019:09:17:31 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'serverLaser.hpcups-Gray..\' already exists
 W [20/Jun/2019:09:17:31 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'serverLaser.hpcups-RGB..\' already exists
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Lpstat:
 device for serverLaser.hpcups: parallel:/dev/usb/lp0
 device for serverLaser.hpijs: parallel:/dev/usb/lp0
MachineType: Hewlett-Packard HP EliteBook 8560p
Package: hplip 3.19.1+dfsg0-1
PackageArchitecture: amd64
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/serverLaser.hpcups.ppd', '/etc/cups/ppd/serverLaser.hpijs.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/serverLaser.hpcups.ppd: Permission 
denied
 grep: /etc/cups/ppd/serverLaser.hpijs.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=e119eace-ded7-4a54-b62d-d08677374c7c ro splash quiet vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Tags:  disco
Uname: Linux 5.0.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/13/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.67
dmi.board.name: 1618
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.4E
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.67:bd02/13/2018:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8560p
dmi.product.sku: WX787AV
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard


** Tags added: apport-collected disco

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

Title:
  hpcups and hpijs driver use different rasterization

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

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

Workaround for mutter proposed here:

https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

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

[Desktop-packages] [Bug 1833514] Re: System shutting down

Please:

  1. Wait till the problem happens again and let the system shut down.

  2. Power up the system and then run:

 journalctl -b-1 > prevboot.txt

  3. Attach the file 'prevboot.txt' to this bug.

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

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

Title:
  System shutting down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the system shuts down automatically withouot  any warnings. using sony
  vaio laptop with only ubuntu installed on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:27:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:90a8]
  InstallationDate: Installed on 2019-05-30 (20 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVT13113ENS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=6918c007-6332-40ec-bbb1-a5d8ff4c287a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0190E4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0190E4:bd04/30/2012:svnSonyCorporation:pnSVT13113ENS:pvrC903CUWG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVT13113ENS
  dmi.product.sku: N/A
  dmi.product.version: C903CUWG
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1832457] Re: [SRU] 2.60.4

2019-06-20 Thread Launchpad Bug Tracker

This bug was fixed in the package glib2.0 - 2.60.4-1

---
glib2.0 (2.60.4-1) experimental; urgency=medium

  * New upstream release (LP: #1832457)
  +  Fixes to improved network status detection with NetworkManager (#1788)
  + Leak fixes to some `glib-genmarshal` generated code
  + Further fixes to the Happy Eyeballs (RFC 8305) implementation
  + File system permissions fix to clamp down permissions in a small time window
when copying files (CVE-2019-12450)
  + Bugs fixed:
   - Please revert #535 gmacros: Try to use the standard __func__ first in
 G_STRFUNC
  * gfile-Limit-access-to-files-when-copying.patch: Drop. It's in this version
upstream.
  * d/p/*: Refresh through gbp pq

 -- Iain Lane   Wed, 12 Jun 2019 09:15:11 +0100

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12450

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS

[Desktop-packages] [Bug 1833514] [NEW] System shutting down

2019-06-20 Thread Atul Tyagi

Public bug reported:

the system shuts down automatically withouot  any warnings. using sony
vaio laptop with only ubuntu installed on it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 14:27:14 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [104d:90a8]
InstallationDate: Installed on 2019-05-30 (20 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Sony Corporation SVT13113ENS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=6918c007-6332-40ec-bbb1-a5d8ff4c287a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0190E4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0190E4:bd04/30/2012:svnSonyCorporation:pnSVT13113ENS:pvrC903CUWG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVT13113ENS
dmi.product.sku: N/A
dmi.product.version: C903CUWG
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  System shutting down

Status in xorg package in Ubuntu:
  New

Bug description:
  the system shuts down automatically withouot  any warnings. using sony
  vaio laptop with only ubuntu installed on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:27:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:90a8]
  InstallationDate: Installed on 2019-05-30 (20 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVT13113ENS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=6918c007-6332-40ec-bbb1-a5d8ff4c287a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0190E4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0190E4:bd04/30/2012:svnSonyCorporation:pnSVT13113ENS:pvrC903CUWG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVT13113ENS
  dmi.product.sku: N/A
  dmi.product.version: C903CUWG
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

I'll see if I can hack around it, but the simplicity of the mistake in
the vmwgfx kernel code makes me think we should be preferring a kernel
fix still.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

I am now able to reproduce and debug the problem. Indeed it is what I
said in comment #31.

The vmwgfx driver in this old kernel is telling lies. It says the next
screen refresh is in 49 years from now. It should be within 16.6
milliseconds.


** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it
+ Login screen never appears on vmwgfx using bionic kernel 4.15

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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/1832138/+subscriptions

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

[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2019-06-20 Thread accnetdev

Hi,

I use Linux from about 1996 and Windows from the very first version 2.x
Both OS have become more reliable and powerfull.

For Ubuntu the worst weaknesses are related to multimedia and conflicts
between devs : Graphics cards, sound issues and many other boring things
are really where Canonical and the linux community have to work a lot.

In too much cases, we have to reinstall the whole system (backing up and
reinstalling all our specific configurations and apps) to fix these kind
of issues, to retrieve a clean Ubuntu OS.

This is what I am going to do one more time now, and it is a time
consuming activity, that I would appreciate not to have to do...

I rarely experience this on Windows or MacOS PCs, in these OS
uninstalling drivers or apps, cleaning and reinstalling fixes most often
these kind of multimedia issues.

On most of my PCs, I use Kubuntu 18.04 as KDE is my favourite Desktop
Environment.

Thanks for reading.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1833498] Re: Upgrading evince always breaks djvu support

UPDATE: No, removing djvulibre-desktop solved the problem only for the
_multipage_ DjVu files, but not for the single-page ones. So, for a
single-page djvu files I still get the above-mentioned error message,
unless I manually add "image/vnd.djvu" to the end of MimeTypes in
/usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument.evince-backend
file.

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

Title:
  Upgrading evince always breaks djvu support

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Every time I upgrade evince (as part of "sudo apt update; sudo apt
  upgrade") I have to remember to edit the file /usr/lib/x86_64-linux-
  gnu/evince/4/backends/djvudocument.evince-backend and add
  "image/vnd.djvu" to the end of MimeType list. If I don't do this then
  evince is unable to view djvu files. Please add "image/vnd.djvu" to
  MimeType in the official version of this file so that I (and
  presumably all other millions of Ubuntu Linux users, who are too lazy
  to open a bugreport for it) don't have to edit it manually. Thank you.

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

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

[Desktop-packages] [Bug 1832374] Re: Media keys stop working due to missing service file

2019-06-20 Thread Sebastien Bacher

** Description changed:

+ * Impact 
+ Sometime multimedia keys stop working
+ 
+ * Test case
+ - start playing an audio file in VLC/totem/smplayer
+ - pause
+ - open a video in another player
+ - exit the other player
+ - try to resume the music play from the first one using the play key
+ 
+ -> it should work
+ 
+ * Regression potential
+ Make sure that multimedia play/pause keys keep working
+ 
+ --
+ 
  Over the last two releases I've noticed that if you have an audio player
  such as Clementine running, pause the audio playback and watch a video
  via VLC or SMPlayer and then close the video player and try to use the
  media keys again, the following is logged to journald:
  
  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service files.
  
  From what I can see is that a service file is created for the media keys
  for SMPlayer, when SMPlayer is closed that service file is removed and
  then media keys are still bound to that service.
  
  I get the above output for previous track, stop, play, pause and next
  track media keys.
  
  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:
  
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list
  
  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages still
  get logged. Closing SMPlayer again does not restore media keys so that
  Clementine can handle them. I had SMPlayer running ~17 hours ago.
  
  Doing a shell reload doesn't seem to fix this either.
  
  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.
  
  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320
  
  If you need any other information let me know.
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-settings-daemon 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 11 17:36:07 2019
  InstallationDate: Installed on 2019-02-01 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20181202)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

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

Title:
  Media keys stop working due to missing service file

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

Bug description:
  * Impact 
  Sometime multimedia keys stop working

  * Test case
  - start playing an audio file in VLC/totem/smplayer
  - pause
  - open a video in another player
  - exit the other player
  - try to resume the music play from the first one using the play key

  -> it should work

  * Regression potential
  Make sure that multimedia play/pause keys keep working

  --

  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode

[Desktop-packages] [Bug 1833498] Re: Upgrading evince always breaks djvu support

Oops, typo in the previous comment: I wrote "evince filename,djvu" but
of course I meant "evince filename.djvu", i.e. with dot "." rather than
comma ",".

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

** Bug watch added: Red Hat Bugzilla #1507305
   https://bugzilla.redhat.com/show_bug.cgi?id=1507305

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

Title:
  Upgrading evince always breaks djvu support

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Every time I upgrade evince (as part of "sudo apt update; sudo apt
  upgrade") I have to remember to edit the file /usr/lib/x86_64-linux-
  gnu/evince/4/backends/djvudocument.evince-backend and add
  "image/vnd.djvu" to the end of MimeType list. If I don't do this then
  evince is unable to view djvu files. Please add "image/vnd.djvu" to
  MimeType in the official version of this file so that I (and
  presumably all other millions of Ubuntu Linux users, who are too lazy
  to open a bugreport for it) don't have to edit it manually. Thank you.

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

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

[Desktop-packages] [Bug 1833498] Re: Upgrading evince always breaks djvu support

Oh sorry, I forgot to include the info you requested. I am using Ubuntu
Linux 18.04.2 and I don't use "nautilus". I always open djvu files using
the command "evince filename,djvu" from within terminal. Well, sometimes
I use "djview filename.djvu" (when I want to find out the resolution),
but normally evince is more convenient.

I thought this bug is well-known because for about a year (or maybe
longer) I saw it mentioned on stackexchange and that is where I learned
about the workaround of adding "image/vnd.djvu" to the end of MimeTypes
in the file /usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument
.evince-backend.

As for the file example --- just get ANY djvu file from anywhere you like, e.g. 
from my website:
http://www.bibles.org.uk/guardian-plates.html Of course it fails not only with 
the files produced by myself, but with any other djvu files. The error message 
from evince is always "File type DjVu image (image/vnd.djvu) is not supported".

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

Title:
  Upgrading evince always breaks djvu support

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Every time I upgrade evince (as part of "sudo apt update; sudo apt
  upgrade") I have to remember to edit the file /usr/lib/x86_64-linux-
  gnu/evince/4/backends/djvudocument.evince-backend and add
  "image/vnd.djvu" to the end of MimeType list. If I don't do this then
  evince is unable to view djvu files. Please add "image/vnd.djvu" to
  MimeType in the official version of this file so that I (and
  presumably all other millions of Ubuntu Linux users, who are too lazy
  to open a bugreport for it) don't have to edit it manually. Thank you.

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

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

[Desktop-packages] [Bug 1833498] Re: Upgrading evince always breaks djvu support