[Desktop-packages] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #645
   https://gitlab.freedesktop.org/xorg/xserver/issues/645

** Changed in: xorg-server
   Status: Fix Released => Unknown

** Changed in: xorg-server
 Remote watch: gitlab.freedesktop.org/xorg/xserver/issues #672 => 
gitlab.freedesktop.org/xorg/xserver/issues #645

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

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy() from
  wl_callback_destroy() from xwl_present_sync_callback() from
  ffi_call_unix64()

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/008c7bd0fdc996890cce5f67e5f0214f280aefd8

  ---

  I do not know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.4-1ubuntu2
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 10:31:56 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.19.30-041930-generic, x86_64: 
installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.3-050003-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1552033916
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (109 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/caravena
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.3-050003-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  UpgradeStatus: Upgraded to disco on 2018-12-02 (109 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Derk Willem te Bokkel]

the above comment .. is perhaps a bit brief .. in spite of the log
showing a pam pass no login screen was available .. it was blanked out
.. gone just a cursor and that also disappeared after a bit .. (still
using testing partition sda6 for all this)

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Derk Willem te Bokkel]

journalctl -b-1 > prevboot3.txt  post group change .. no joy ..also
makes machine wide open no passwd required
 .. i will revert this

On Tue, Mar 26, 2019 at 12:35 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> It sounds like the solution might be a simple matter of adding 'derk' to
> /etc/group on line:
>
>   nopasswdlogin:x:132:
>
> So that becomes:
>
>   nopasswdlogin:x:132:derk
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821609
>
> Title:
>   Xorg freeze - fails to start or stay going screen blanks-grub  seems
>   involved
>
> Status in kwallet-pam package in Ubuntu:
>   New
> Status in lightdm package in Ubuntu:
>   New
>
> Bug description:
>   Okay the has happened recently at least since march 18, 2019 iso and
>   march 22, 2019 iso are both effected very similar to one of my
>   previously reported bugs .. which was related to xorg not being
>   installed ..
>
>
>   back ground .. PC is lenovo sl 500 with evo860 SSD drive
>
>   3 partions contain installs of disco sda1 -- main working system -- I
>   usually install grub from here as master ..
>
>   sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
>   03-22-2019 repectively
>
>
>   on the test installs as long as the iso is using the grub boot loader
> installed from that install the system will boot normally .. the display
> manger tends to flicker on and off but does final start and login can
> proceed.
>
>   but if another install re-installs grub as master  the display manager
>   fails to stay active or even come-up  for sda6 or sda7 only if their
>   own grubs are reinstalled will they work normally
>
>   sda1 display manager/xorg login works always no matter which "grub-
>   source" is in control.
>
>   if I use rescue boot from any grub as master I can get the displays to
> work by running dpkg fix which does nothing .. and then resuming the boot
> .. then things work normally..
>   if the "non-rescue" boots are used the screen/computer locks and only a
> power down and reboot gives access. (sometime requiring radical depowering
> .. unpluging and removing battery)
>
>   now the is a message that appears that RCs??? level is missing.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu11
>   ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
>   Uname: Linux 5.0.0-7-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu23
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: XFCE
>   Date: Mon Mar 25 11:25:58 2019
>   DistUpgraded: Fresh install
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GpuHangFrequency: Several times a day
>   GpuHangReproducibility: Yes, I can easily reproduce it
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Intel Corporation Mobile 4 Series Chipset Integrated Graphics
> Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics
> Controller [17aa:20e4]
>  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics
> Controller [17aa:20e4]
>   InstallationDate: Installed on 2019-03-23 (1 days ago)
>   InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
>   MachineType: LENOVO 2746CTO
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
> root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2010
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 6AET64WW
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: 2746CTO
>   dmi.board.vendor: LENOVO
>   dmi.board.version: LENOVO 6AET64WW
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: LENOVO 6AET64WW
>   dmi.modalias:
> dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
>   dmi.product.name: 2746CTO
>   dmi.product.version: ThinkPad SL500
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.97-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> 

[Desktop-packages] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

[Bug Watch Updater]

** Changed in: xorg-server
   Status: New => Fix Released

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

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy() from
  wl_callback_destroy() from xwl_present_sync_callback() from
  ffi_call_unix64()

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/008c7bd0fdc996890cce5f67e5f0214f280aefd8

  ---

  I do not know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.4-1ubuntu2
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 10:31:56 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.19.30-041930-generic, x86_64: 
installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.3-050003-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1552033916
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (109 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/caravena
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.3-050003-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  UpgradeStatus: Upgraded to disco on 2018-12-02 (109 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Daniel van Vugt]

Please have a look to see if any of the existing bug reports might be
the same issue:

https://bugs.launchpad.net/ubuntu/+source/kwallet-pam

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

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Daniel van Vugt]

It sounds like the solution might be a simple matter of adding 'derk' to
/etc/group on line:

  nopasswdlogin:x:132:

So that becomes:

  nopasswdlogin:x:132:derk

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Daniel van Vugt]

It appears the problem is related to lightdm and PAM:

Mar 25 23:26:07 zlink2 lightdm[840]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
Mar 25 23:26:07 zlink2 lightdm[840]: PAM adding faulty module: pam_kwallet.so
Mar 25 23:26:07 zlink2 lightdm[840]: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
Mar 25 23:26:07 zlink2 lightdm[840]: PAM adding faulty module: pam_kwallet5.so
Mar 25 23:26:07 zlink2 lightdm[840]: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "derk"

I'm not sure if this is a problem specific to lightdm, or a general PAM
problem that would affect gdm3 in normal Ubuntu too.

Please look into the causes of the above errors on your machine.

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

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

** Package changed: lightdm (Ubuntu) => kwallet-pam (Ubuntu)

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  

[Desktop-packages] [Bug 1012658] Re: thunderbird icon disappears from launcher

[Launchpad Bug Tracker]

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

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

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

Title:
  thunderbird icon disappears from launcher

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  After starting up correctly from the dash, the thunderbird icon
  disappears after a short amount of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 14.0~b1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  ApportVersion: 2.2.1-0ubuntu2
  Architecture: amd64
  Date: Wed Jun 13 14:01:26 2012
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to quantal on 2012-06-11 (2 days ago)

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

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

[Desktop-packages] [Bug 1010402] Re: Problem opening UNICODE file

[Launchpad Bug Tracker]

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

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

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

Title:
  Problem opening UNICODE file

Status in gedit package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  apt-cache policy gedit
  gedit:
Installé : 3.4.1-0ubuntu1
Candidat : 3.4.1-0ubuntu1
   Table de version :
   *** 3.4.1-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  What you expected to happen
  gedit to open file

  What happened instead
  gedit has problem opening attached RawText file test.rc generated by Windows 
7; edit displays:
  "There was a problem opening the file /mnt/hgfs/vmware/test/test.rc.
  The file you opened has some invalid characters. If you continue editing this 
file you could corrupt this document.
  You can also choose another character encoding and try again."

  MOST IMPORTANT INFO:
  After opening file test.rc with Windows' Notepad and removing 'END' at line 
387, then saving file, gedit can open file without any problem. After re-adding 
'END' at line 387 (using gedit or Notepad) and saving file, gedit can no longer 
open file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun  8 05:37:04 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 399998] Re: Message Filters not run automatically

[Launchpad Bug Tracker]

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

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

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

Title:
  Message Filters not run automatically

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  When mail arrives in Inbox,  message filter for that folder  is not
  run automatically. Subsequent use of Tools->Run Filters on Folder
  works OK - filters are applied correctly.

  Ubuntu 9.04
  Thunderbird version 2.0.0.22 (20090608)

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: mozilla-thunderbird 2.0.0.22+build1+nobinonly-0ubuntu0.9.04.1
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.28-13-generic i686

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

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

[Desktop-packages] [Bug 1270120] Re: a non existent floppy is shown when usb device is plugged in

[Launchpad Bug Tracker]

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

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

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

Title:
  a non existent floppy is shown when usb device is plugged in

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I plug in an usb device it shows up in nautilus and unity but
  beside that a non existent floppy drive is shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jan 17 12:15:13 2014
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'934x700+984+24'"
  InstallationDate: Installed on 2014-01-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1264280] Re: Cannot browse file on bluetooth device. Nonsense error message

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot browse file on bluetooth device. Nonsense error message

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Usually I can browse files on my mobile connected via bluetooth from
  the computer.

  Same computer, same phone, now I can't.

  - Click on the bluetooth icon on the notification area
  - select "bluetooth settings" (directly selecting "Browse files" within the 
submenu under the name of the device wouldn't work, as per bug #1254106)
  - select the device which is the only one in the list and click "Browse 
files".

  => I get this nonsense error message: 
  "Unable to find the requested file. Please check the spelling and try again"
  And below: "Unhandled error message: Unable to load location".

  Note the error message suggesting to check the spelling is
  particularly stupid as no typing is involved in the process.

  I've done a hcidump during the process and it is COMPLETELY EMPTY.

  I have removed the phone from the devices, paired it again from
  scratch, and it does not fix the issue.

  It used to work until very few days ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Thu Dec 26 12:04:18 2013
  InstallationDate: Installed on 2013-10-11 (75 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:5507 acl:73 sco:0 events:209 errors:0
TX bytes:3114 acl:76 sco:0 commands:69 errors:0

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

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

[Desktop-packages] [Bug 1181519] Re: Strange work with the icons

[Launchpad Bug Tracker]

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

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

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

Title:
  Strange work with the icons

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  As it's known, for many years neither Gnome nor KDE developed any convenient 
tools to work with links(like Windows' shortcuts). today I downloaded Eclipse 
package andd tried to make a link to it's executable file. Here is what I got: 
http://chod.sk/a08n2
  That would be great if you developed much more sane ways to work with links

  I do understand that a general user would use soft provided from
  repositories but I find it limiting a great range of possibilities a
  modern OS can provide to it's user.

  GNOME project is known for it's total ignoring users' requests about
  different improvements. So hope you accept this feature request.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat May 18 16:24:24 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'676x541+201+56'"
  InstallationDate: Installed on 2013-05-15 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1219361] Re: Nautilus Bad Behavior With Many Items in Directory

[Launchpad Bug Tracker]

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

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

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

Title:
  Nautilus Bad Behavior With Many Items in Directory

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I am working with a directory with many files. Around 1000.

  I am using Nautilus to try and move files into a subdirectory.

  The subdirectory starts with 'M', so you have to scroll down several
  screens to get to it.

  Whenever I select a file and start dragging it to the subdirectory,
  Nautilus refreshes the view, and reverts the vertical position to the
  top.

  This happens every time, before I am able to actually drag the files
  into the directory. It only

  In short, the simple, user/newbie friendly mechanic of 'drag and drop
  the file into the folder' doesn't work on thumbnails view unless the
  folder is on the first screen of the results in the parent folder.

  This is in Ubuntu 13.04, I don't think any dmesg or system specs are
  relevant to this bug, so I won't list them.

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

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

[Desktop-packages] [Bug 1225615] Re: file copy time is calculated wrong

[Launchpad Bug Tracker]

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

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

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

Title:
  file copy time is calculated wrong

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I copy I file from my notebook to any other device (e.g. SMB
  share, USB Stick, etc.) than the copy time is calculated by the reed
  speed of the origin - and not by the write speed of the destination -
  what would be the expected behaviour.

  That is not a nautilus bug, because the same happens in terminel with
  midnight commander - mc - ...

  The whole file is cached in ram - but on an ssd that means - after 2-3
  seconds nautilus and mc show the file as copied and nautilus than
  often freezes - but in system statistics you can see him now writing
  to destination. sometimes nautilus than wakes up and continue to work,
  and sometimes it doesnt...

  why is this calculated this way...?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: amd64
  Date: Sun Sep 15 10:15:38 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1289x574+0+24'"
  InstallationDate: Installed on 2013-01-31 (226 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130131)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1229065] Re: Flash player crashes when watching some video or animation

[Launchpad Bug Tracker]

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

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

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

Title:
  Flash player crashes when watching some video or animation

Status in adobe-flashplugin package in Ubuntu:
  Expired
Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  My problem is that Flash player keeps on crashing always. I'm using dual 
graphics. Yesterday I switched to high GPU and later switched back to intel 
GPU. And the Flash player never worked since then.
  I did some search on forums & Google, then tried every possibilities but 
still problem persists. By the way when I right click settings > flash player 
keeps on crashing and I can't change any settings. How can i fix that ?
  Thank you in advance.

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

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

[Desktop-packages] [Bug 1225201] Re: Nautilus memory leak when thumbnailing jpeg2000 images

[Launchpad Bug Tracker]

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

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Nautilus memory leak when thumbnailing jpeg2000 images

Status in gdk-pixbuf package in Ubuntu:
  Expired

Bug description:
  Nautilus starts with under 300 MB and after thumbnailing some jp2 files (JPEG 
2000) memory ends up above 900 MB. Closing all nautilus windows does not 
release the memory. Memory is only freed when doing nautilus -q.
  The more files is thumbnails the more memory is uses.

  Steps to reproduce:
  Drop a few jp2 files in a folder (I tested with lossless jpeg2000 files about 
3000 by 3000)
  Quit nautilus (nautilus -q)
  Start nautilus again and open the folder containing jp2 files.
  Watch memory go up as nautilus is thumbnailing each file.
  Close nautilus (ALT-F4 or clicking in the red cross), memory is never 
released.
  Quit nautilus (nautilus -q) and memory is freed.

  Valgrind is very helpful, apparently libpixbufloader-jasper.so is used
  to read jp2 files.

  ==3829== 325,112,688 bytes in 11 blocks are possibly lost in loss record 
12,461 of 12,461
  ==3829==at 0x4C2CD7B: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==3829==by 0x72AC150: gdk_pixbuf_new (in 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0)
  ==3829==by 0x288C42CE: ??? (in 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jasper.so)
  ==3829==by 0x72B2CA9: gdk_pixbuf_loader_close (in 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0)
  ==3829==by 0x5471919: ??? (in /usr/lib/libgnome-desktop-3.so.4.0.0)
  ==3829==by 0x5471E51: gnome_desktop_thumbnail_factory_generate_thumbnail 
(in /usr/lib/libgnome-desktop-3.so.4.0.0)
  ==3829==by 0x4D8B2A: ??? (in /usr/bin/nautilus)
  ==3829==by 0x8A70F8D: start_thread (pthread_create.c:311)
  ==3829==by 0x8D7FE1C: clone (clone.S:113)
  ==3829== 
  ==3829== LEAK SUMMARY:
  ==3829==definitely lost: 12,603 bytes in 42 blocks
  ==3829==indirectly lost: 34,224 bytes in 1,064 blocks
  ==3829==  possibly lost: 328,125,169 bytes in 16,209 blocks
  ==3829==still reachable: 226,694,419 bytes in 14,183 blocks
  ==3829== suppressed: 0 bytes in 0 blocks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Fri Sep 13 18:15:06 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'979x653+131+63'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'194'
  InstallationDate: Installed on 2013-03-27 (170 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-25 (140 days ago)

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

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

[Desktop-packages] [Bug 1204378] Re: Copy files from mounted cpio does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  Copy files from mounted cpio does not work

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I double click on a cpio files, causing it to be "mounted"? on the
  files app, so I can click on it and view the files inside. However,
  when I copy a folder inside it and to paste it into normal folder, the
  copy process doesn't work at all.

  It says 0 byte of 600 mb 0 byte per second.

  If I click on big X (to the right) the button goes dark but it wasn't
  cancelled (the window still there).

  Clicking on the tiny x (upper left) doesn't close (just hide /
  minimize) or cancel it either, and can still be accessed by right
  clicking on the Files icon and select show copy dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Wed Jul 24 14:56:20 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x499+232+95'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-06-15 (38 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1243474] Re: clicking and draging to move a folder make window scroll.

[Launchpad Bug Tracker]

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

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

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

Title:
  clicking and draging to move a folder make window scroll.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I click a folder and drag to one folder right above to move it into the 
folder, window scrolls up all the way and I cannnot move it.
  First of all absense of tree view is pretty bad but that's a spec problem. 
But this jumping around issue would be a bug.
  Another problem is when I move a file/folder, the window become blank and I 
cannot do anything while it is blank.
  There are too many problem/complaints to report for 13.10 numbering 
upgrade/practical downgrade.

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

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

[Desktop-packages] [Bug 1154288] Re: with network locations navigation bar shows 'real' names not bookmarked names

[Launchpad Bug Tracker]

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

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

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

Title:
  with network locations navigation bar shows 'real' names not
  bookmarked names

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  with lucid and precise

  the nautilus left panel shows both connected network folders and
  bookmarked network folders but on clicking a bookmarked network folder
  the navigation bar shows the 'real' path not the bookmarked path

  example

  An employee (username = prosserg) has made a connection to a network
  folder eg 'prosserg on esther2' from their bookmarks by opening a
  bookmarked folder named 'H Drive' which is //esther2/prosserg.

  Subsequently when file browsing

  a) on clicking 'H Drive' in the left panel, the navigation bar first
  button says 'prosserg on esther2'

  WHY can't this button say 'H Drive' ie the NAME of the bookmark ?

  b) it is confusing to see, in the left panel, BOTH the bookmark name
  'H Drive' AND the connected network drive 'prosserg on esther2' listed
  since they are the same folder

  'H Drive' is of course windows-speak but for migrators from say XP to
  Ubuntu, the nautilus insistence on displaying the 'real' name of the
  connection rather than the bookmark name, significantly adds to
  confusion.

  I have had several employees experience difficulty locating files as a
  result of this current behaviour.

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

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

[Desktop-packages] [Bug 1209401] Re: [Regression]File-type handling is retarded

[Launchpad Bug Tracker]

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

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

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

Title:
  [Regression]File-type handling is retarded

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Scenario:

  You want to edit a text file, so you make a copy with a different
  name. Later, you want to remind yourself of what the original file
  said, so you find it and open it.

  What you expect to happen:

  Nautilus will use whatever magic numbers and casting of bones that it
  normally does to identify the type of file, see that it's a text file
  the same as any other, and open it using the default text editor.

  What actually happens:

  Nautilus throws up a lame error message that
  "There is no application installed for “backup file” files.
  Do you want to search for an application to open this file?"
  maintaining a database of file extensions like it's Windows 95. Ridiculous.

  It was significantly better than that in Gnome 2.

  Ubuntu 13.04 Raring Ringtail.

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

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

[Desktop-packages] [Bug 1177437] Re: Ubuntu 13.04 doesn't auto-mount ntfs filesystems

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu 13.04 doesn't auto-mount ntfs filesystems

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  1. Using Ubuntu 13.04 x64 for Desktops (tested in 2 PCs with same
  release).

  2. Expected behavior when you modify /etc/fstab as follows in order to
  auto-mount ntfs partitions:

  # /etc/fstab: static file system information.
  # blah, blah...
  # 
 

  UUID=DA3C779E3C77747B  /media/user/Win-Partition   ntfs-3g   
rw,auto,user,fmask=0111,dmask=,nls=utf8,remove_hiberfile


  0  0

  Once Ubuntu boots, Nautilus shows Win-Partition automatically (you
  don't have to select 'Computer' to mount it).

  3. Instead, during Ubuntu's boot, the following appears:

  'An error occurred while mounting /media/user/Win-Partition
  Press S to skip mounting or M for manual.'

  I press S and continue, but I can't mount the partition in Nautilus
  nor Thunar.

  *** I did detected though that this happens when you shutdown the PC
  within Windows 8, NOT WHEN YOU RESTART FROM WIN8 ***

  Nevertheless, this didn't happen with Ubuntu 12.10.

  Hope you fix this guys. Thanks in advance!

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

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

[Desktop-packages] [Bug 1229065] Re: Flash player crashes when watching some video or animation

[Launchpad Bug Tracker]

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

** Changed in: adobe-flashplugin (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Flash player crashes when watching some video or animation

Status in adobe-flashplugin package in Ubuntu:
  Expired
Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  My problem is that Flash player keeps on crashing always. I'm using dual 
graphics. Yesterday I switched to high GPU and later switched back to intel 
GPU. And the Flash player never worked since then.
  I did some search on forums & Google, then tried every possibilities but 
still problem persists. By the way when I right click settings > flash player 
keeps on crashing and I can't change any settings. How can i fix that ?
  Thank you in advance.

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

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

[Desktop-packages] [Bug 1225413] Re: graphic

[Launchpad Bug Tracker]

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

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

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

Title:
  graphic

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Nautilus shows a message that there are too many file to show them
  all, if a folder contains more then 1 files. But if I continue to
  work on that folder (selecting them all with Ctrl+A, deselecting a
  few, trying to delete) nautilus freezes and crashes. During the
  freeze, it does not use any CPU time, but there is no response and no
  graphic update.

  I might depend on the available memory, since it takes sometimes a
  minute before it crashes. And while I am wor...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Sat Sep 14 15:24:48 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'840x550+65+24'"
  InstallationDate: Installed on 2013-09-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130913)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1211937] Re: Nautilus leaks memory right after system start

[Launchpad Bug Tracker]

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

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

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

Title:
  Nautilus leaks memory right after system start

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Directly after logging in, nautilus starts to take more memory with a speed 
of ~4 MB/s. After 10-20 minutes the system freezes so extremely that it doesn't 
respond to any input (alt+f1, reisub).
  This could be caused by something related to the desktop since nautilus is 
used to render the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Tue Aug 13 20:52:16 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'640x750+0+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'152'
  InstallationDate: Installed on 2013-08-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1518863] Re: Ugly Firefox icon because of firefox.png in ~/.thunderbird

[Launchpad Bug Tracker]

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

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

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

Title:
  Ugly Firefox icon because of firefox.png in ~/.thunderbird

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10
  thunderbird:
    Installed: 1:38.3.0+build1-0ubuntu2
    Candidate: 1:38.3.0+build1-0ubuntu2
    Version table:
   *** 1:38.3.0+build1-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  Low res. Firefox icon appears in my Unity few seconds after every
  logon.

  So I search for all the firefox icons on my system, and find out that
  the icon comes from,

  
~/.thunderbird/yprpxtt3.default/extensions/{9533f794-00b4-4354-aa15-c2bbda6989f8}/chrome/skin/icons/linux/hicolor/22x22/apps/firefox.png

  By just renaming that I could get the default Firefox icon back.

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

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

[Desktop-packages] [Bug 1813160] Re: display problem

[Launchpad Bug Tracker]

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  display problem

Status in xserver-xorg-video-intel package in Ubuntu:
  Expired

Bug description:
  display is going black for fraction of second.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 24 18:47:01 2019
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, 
x86_64: installed
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: 
installed
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0841]
  InstallationDate: Installed on 2018-08-26 (151 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 3478
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=a241a9ad-c097-481d-b704-f28b73bb8feb ro acpi_rev_override quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 08R7RH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnVostro3478:pvr:rvnDellInc.:rn08R7RH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Vostro 3478
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 24 16:25:51 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1805 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1813212] Re: Ubuntu dock auto-hide using mouse is unreliable

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu dock auto-hide using mouse is unreliable

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

Bug description:
  This is usability bug that exists in Ubuntu starting from 2012 (see
  this bug report:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/996158)

  Using mouse with Ubuntu dock auto-hide mode makes the mouse to shift
  left while pointer stays in place (at the left edge). The effect is
  your mouse is shifting (every time you try to access the dock) to the
  left until there is no space on the table and you have to take it up
  and move to the right. This is very inconvinient and makes usage of
  the dock unreliable.

  The issue seems to be caused such a reveal mechanizm when you have to
  "push" the pointer do the left edge to make dock to re-appear. The
  faulty behaviour has been introduced in Unity-2D, than copied to Unity
  than copied to gnome-shell-extension-ubuntu-dock.

  Currently there is no other option but DO NOT USE THE AUTO HIDE
  function to avoid frustration.

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

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

[Desktop-packages] [Bug 1821609] [NEW] Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..


back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively


on the test installs as long as the iso is using the grub boot loader installed 
from that install the system will boot normally .. the display manger tends to 
flicker on and off but does final start and login can proceed. 

but if another install re-installs grub as master  the display manager
fails to stay active or even come-up  for sda6 or sda7 only if their own
grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work by 
running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco freeze has-workaround regression reproducible 
ubuntu
-- 
Xorg freeze - fails to start or stay going screen blanks-grub  seems involved
https://bugs.launchpad.net/bugs/1821609
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to lightdm in Ubuntu.

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

[Sam Colegrove]

The above image shows what happens when LibreOffice 6.2.2.2 Impress has
an inserted video.  When the video is started, the previous slide is
shown on top of the video as it is played.  Not a good view  This
happens on Kubuntu 19.04 and I have added all the packages suggested in
the above "solution".

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  New
Status in libreoffice source package in Cosmic:
  New

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  
  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

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

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

[Sam Colegrove]

** Attachment added: "Image from Impress when a video is started"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820062/+attachment/5249324/+files/LO_Impress.jpg

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  New
Status in libreoffice source package in Cosmic:
  New

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  
  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

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

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

[Desktop-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

[Vic Liu]

** Description changed:

  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.
  
  Some more findings:
  
  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).
  
  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging out
  doesn't trigger this bug. So this might(?) also involves systemd-logind
  as well;
  
  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.
  
  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.
  
  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 240-6ubuntu1
+    * 240-6ubuntu1
  * gdm3:
-* 3.31.4+git20190225-1ubuntu1
+    * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every case.
  
-  ### Cosmic
+  ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 239-7ubuntu10
+    * 239-7ubuntu10
  * gdm3:
-* 3.30.1-1ubuntu5
+    * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Cosmic, same with Disco.
  
  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 237-3ubuntu10.12
+    * 237-3ubuntu10.12
  * gdm3:
-* 3.28.3-0ubuntu18.04.3
+    * 3.28.3-0ubuntu18.04.3
  ## Hardware
  * 201811-26623
  
  Summary: only 4.18 kernel with nouveau driver is immune from this issue,
  which follows some changes in user land should be necessary to stabilize
  all the (nouveau) cases. But even with that, from previous results of
  Cosmic/Disco, there should still some works to be done in the nvidia
  driver.
+ 
+ OEM-tag: LP: #1804607

-- 
You received this bug notification because you are a 

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

[TonyR]

I wanted to reconfigure an old PC to be a music server connected to our
HIFI.  It took 3 days and 7 attempts to successfully install 18.04 due
to an issue with installing on PC with multiple drives.  It refused to
correctly write the GRUB boot loader to the same partition it itself
installed Ubuntu to. I had to strip out all the drives to get round the
problem to now discover I cannot connect to the Music media on my main
Windows 10 PC due to this SMB issue.  I got round it by the connect to
server option and bookmark option but Kodi cannot see the share or index
the Music.  Now I'm off to Kodi support.

Using Ubuntu since 2008 it seem that every release for me has bugs affecting 
core features such as USB Wireless card support, Sound, DVD burning software 
and display adapter support.  I cannot understand how the platform can be 
released with such fundamental feature broken.
No problem for those who are expert but for mass use users stuffing around for 
hours on forums searching out solutions is not a viable option.

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in dolphin:
  Unknown
Status in gvfs:
  Fix Released
Status in OEM Priority Project:
  New
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Invalid

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1821663] Re: repeating crackling noise after 19.04 upgrade

[Daniel van Vugt]

Thanks for the bug report. Since pulseaudio is unchanged (the same
version) in 19.04 from 18.10 I think we can exclude that as a possible
cause.

1. The first idea I have about possible causes is a kernel change (and
the kernel has changed a lot). Please try some older kernels from here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

(for reference, Ubuntu 18.10 uses kernel 4.18).

2. Also, is the crackling from internal speakers or headphones?

3. Finally, please check that something hasn't accidentally enabled:

  Settings > Sound > Over-Amplification

  as that could cause crackling.

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

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

** Summary changed:

- repeating crackling noise after 19.04 upgrade
+ [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

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

Title:
  [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Desktop-packages] [Bug 1821663] Re: repeating crackling noise after 19.04 upgrade

[venturia]

** Description changed:

  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.
  
  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
-  and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.
+  and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.
+ 
+ The command "killall pulseaudio" usually stop the noise for 10 seconds,
+ then the noise restart.
  
  The system was running smoothly on 18.10
  
- Alessansdro-
+ Alessandro-
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  alessandro   3310 F pulseaudio
-  /dev/snd/controlC0:  alessandro   3310 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  alessandro   3310 F pulseaudio
+  /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=it_IT.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

Title:
  [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Desktop-packages] [Bug 1821648] Re: Gnome Shell froze GUI entirely with 100% CPU usage

[Daniel van Vugt]

Please:

1. Remove all your extensions since extensions tend to cause most of the
bugs like this one...

b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-
appindicat...@ubuntu.com', 'extensi...@abteil.org',
'hams...@projecthamster.wordpress.com', 'cont...@projecthamster.org',
'dash-to-d...@micxgx.gmail.com', 'user-theme@gnome-shell-
extensions.gcampax.github.com', 'gsconn...@andyholmes.github.io',
'system-moni...@paradoxxx.zero.gmail.com', 'openweather-
extens...@jenslody.de', 'vit...@corecoding.com', 'status-area-
horizontal-spac...@mathematical.coffee.gmail.com', 'autohide-
batt...@sitnik.ru', 'mediapla...@patapon.info', 'dim-on-
batt...@nailfarmer.nailfarmer.com', 'activities-config@nls1729',
'caffe...@patapon.info', 'removeaccesibility@lomegor', 'gnome-fuzzy-
sea...@gnome-shell-exstensions.fffilo.github.com', 'transparent-window-
mov...@noobsai.github.com', 'window-title-in-topbar@fthx']"

2. If the problem reoccurs without extensions then next time use:

  killall -ABRT gnome-shell # or -USR1 ?

to generate a crash report and then follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


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

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

Title:
  Gnome Shell froze GUI entirely with 100% CPU usage

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Without warning or apparent user action, my entire system froze aside
  from the mouse cursor.  I was able to switch to a VT to log in and
  capture this bug report.  After that, I had to `kill -9 gnome-shell`
  after which it restarted properly and my session is now working fine
  again.

  Possibly a dupe of #1709597 but that is quite old.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 25 17:31:56 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-12-09 (470 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (157 days ago)

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Daniel van Vugt]

You seem to be booting in recovery mode, which will also break graphics
support in its own way :/

Please:

1. Reboot and as soon as the purple screen appears tap Escape. Now
choose a normal kernel and not recovery.

2. Reproduce the problem.

3. Reboot again into recovery mode if you need to.

4. Run this command to collect the log from the previous (failed) boot:

   journalctl -b-1 > prevboot.txt

   and send us the file 'prevboot.txt'.

5. Run this command:

   dpkg -l > allpackages.txt

   and send us the file 'allpackages.txt'.

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

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

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in Ubuntu:
  Incomplete

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1821663] [NEW] repeating crackling noise after 19.04 upgrade

[venturia]

Public bug reported:

I'm experiencing a repeating crackling noise after 19.04 upgrade that
start just after the boot and before the login.

I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
 and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

The system was running smoothly on 18.10

Alessansdro-

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alessandro   3310 F pulseaudio
 /dev/snd/controlC0:  alessandro   3310 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 03:29:00 2019
InstallationDate: Installed on 2016-07-09 (989 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
dmi.bios.date: 02/14/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: GA-8TRC410M-NF
dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
dmi.chassis.type: 3
dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
dmi.product.name: IMEDIA 5204
dmi.product.version: PB34310106
dmi.sys.vendor: Packard Bell NEC

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  repeating crackling noise after 19.04 upgrade

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm experiencing a repeating crackling noise after 19.04 upgrade that
  start just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The system was running smoothly on 18.10

  Alessansdro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Desktop-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1818862
   Totem player hangs when seeking video due to [gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)

  ---

  Watching movie 4k, forward and back.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821585] Re: Ubuntu/Gnome dock not working with drag and drop

[Daniel van Vugt]

Possibly related to bug 1727321.

** Tags added: disco

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

Title:
  Ubuntu/Gnome dock not working with drag and drop

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

Bug description:
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04 latest updates installed

  
  To drag and drop a file to the Ubuntu/Gnome dock (favorites) is not working. 
For example I tried to drag the file .local/share/applications/example.desktop 
and drop it to favorites the result is that the starter is not created.

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

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

[Desktop-packages] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530

[Daniel van Vugt]

Please run:

  apport-collect 1821426

to send us more information about the machine.

Please also try these potential workarounds and let us know which one(s)
work:

(a) Edit /etc/gdm3/custom.conf and uncomment the line:

#WaylandEnable=false

and reboot.

(b) Disable integrated graphics/GPU in your BIOS

(c) Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:

sudo update-initramfs

and reboot.


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

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

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

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

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

Title:
  Ubuntu 19.14 disco will not boot on Dell Precision5530

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

Bug description:
  I'm uncertain which package is causing the problem, though I strongly
  suspect it may be nvidia related.

  This laptop runs 18.10 just fine, but attempting to boot 19.04 from a
  USB disk (tried multiple USB boot disks) results in a blank screen
  after Grub. The video will go between black with back light and black
  without back light. I cannot switch to a TTY, I cannot get further,
  keyboard seems to respond (lights up when keys are pressed).

  Additionally, when trying to upgrade from 18.10 the same result
  happens. After running the upgrade and rebooting, I cannot get it to
  boot unless I first start in recovery mode from grub. After that I can
  get to the desktop (nouveau driver seems to be installed by default).
  Any attempt to boot normally results in a black screen. Attempting to
  switch to proprietary nvidia driver results in never getting the luks
  screen (encrypted disk). I get no luks screen when booting normally
  either.

  lspci
  00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers (rev 07)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH 
Thermal Controller (rev 10)
  00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
  00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI 
Controller (rev 10)
  00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
  00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0)
  00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
  00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 
(rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
  00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
  00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI 
Controller (rev 10)
  01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev 
a1)
  3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
  3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
011a

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

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

[Desktop-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Daniel van Vugt]

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

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

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Desktop-packages] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530

[Brian Murray]

** Package changed: ubuntu => xorg (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/1821426

Title:
  Ubuntu 19.14 disco will not boot on Dell Precision5530

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm uncertain which package is causing the problem, though I strongly
  suspect it may be nvidia related.

  This laptop runs 18.10 just fine, but attempting to boot 19.04 from a
  USB disk (tried multiple USB boot disks) results in a blank screen
  after Grub. The video will go between black with back light and black
  without back light. I cannot switch to a TTY, I cannot get further,
  keyboard seems to respond (lights up when keys are pressed).

  Additionally, when trying to upgrade from 18.10 the same result
  happens. After running the upgrade and rebooting, I cannot get it to
  boot unless I first start in recovery mode from grub. After that I can
  get to the desktop (nouveau driver seems to be installed by default).
  Any attempt to boot normally results in a black screen. Attempting to
  switch to proprietary nvidia driver results in never getting the luks
  screen (encrypted disk). I get no luks screen when booting normally
  either.

  lspci
  00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers (rev 07)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH 
Thermal Controller (rev 10)
  00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
  00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
  00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI 
Controller (rev 10)
  00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
  00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0)
  00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
  00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 
(rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
  00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
  00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI 
Controller (rev 10)
  01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev 
a1)
  3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
  3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
011a

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

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

[Desktop-packages] [Bug 1821426] [NEW] Ubuntu 19.14 disco will not boot on Dell Precision5530

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm uncertain which package is causing the problem, though I strongly
suspect it may be nvidia related.

This laptop runs 18.10 just fine, but attempting to boot 19.04 from a
USB disk (tried multiple USB boot disks) results in a blank screen after
Grub. The video will go between black with back light and black without
back light. I cannot switch to a TTY, I cannot get further, keyboard
seems to respond (lights up when keys are pressed).

Additionally, when trying to upgrade from 18.10 the same result happens.
After running the upgrade and rebooting, I cannot get it to boot unless
I first start in recovery mode from grub. After that I can get to the
desktop (nouveau driver seems to be installed by default). Any attempt
to boot normally results in a black screen. Attempting to switch to
proprietary nvidia driver results in never getting the luks screen
(encrypted disk). I get no luks screen when booting normally either.

lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal 
Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI 
Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 
(rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI 
Controller (rev 10)
01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev 
a1)
3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a

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


** Tags: bot-comment
-- 
Ubuntu 19.14 disco will not boot on Dell Precision5530
https://bugs.launchpad.net/bugs/1821426
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1821648] [NEW] Gnome Shell froze GUI entirely with 100% CPU usage

[hackel]

Public bug reported:

Without warning or apparent user action, my entire system froze aside
from the mouse cursor.  I was able to switch to a VT to log in and
capture this bug report.  After that, I had to `kill -9 gnome-shell`
after which it restarted properly and my session is now working fine
again.

Possibly a dupe of #1709597 but that is quite old.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
Uname: Linux 5.0.1-050001-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 25 17:31:56 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-12-09 (470 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (157 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Gnome Shell froze GUI entirely with 100% CPU usage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Without warning or apparent user action, my entire system froze aside
  from the mouse cursor.  I was able to switch to a VT to log in and
  capture this bug report.  After that, I had to `kill -9 gnome-shell`
  after which it restarted properly and my session is now working fine
  again.

  Possibly a dupe of #1709597 but that is quite old.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 25 17:31:56 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-12-09 (470 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (157 days ago)

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

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

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

[Sam James Houlbrook]

im suffering from this problem in 18.0.4

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

Title:
  Unable to type capital letters using onscreen keyboard

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

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

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

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

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

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

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

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

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

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

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

Re: [Desktop-packages] [Bug 1821552] Re: Ubuntu 19.04 Desktop:mouseover preview of option in firefox and mozilla not legible

[Stephen Waines]

I see it happens in thunderbird too.

On 2019-03-25 5:15 p.m., Brian Murray wrote:
> ** Package changed: ubuntu => firefox (Ubuntu)
>

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

Title:
  Ubuntu 19.04 Desktop:mouseover preview of option in firefox and
  mozilla not legible

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,
  I noticed on the gui when you hover your mouse over an option in thunderbird 
or mozilla, i is not legible. 

  -Steve

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

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

[Desktop-packages] [Bug 1821552] Re: Ubuntu 19.04 Desktop:mouseover preview of option in firefox and mozilla not legible

[Paul White]

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

** Tags added: disco

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

Title:
  Ubuntu 19.04 Desktop:mouseover preview of option in firefox and
  mozilla not legible

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

Bug description:
  Hello,
  I noticed on the gui when you hover your mouse over an option in thunderbird 
or mozilla, i is not legible. 

  -Steve

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

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

[Desktop-packages] [Bug 1821552] Re: Ubuntu 19.04 Desktop:mouseover preview of option in firefox and mozilla not legible

[Brian Murray]

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

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

Title:
  Ubuntu 19.04 Desktop:mouseover preview of option in firefox and
  mozilla not legible

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,
  I noticed on the gui when you hover your mouse over an option in thunderbird 
or mozilla, i is not legible. 

  -Steve

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

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

[Desktop-packages] [Bug 1821552] [NEW] Ubuntu 19.04 Desktop:mouseover preview of option in firefox and mozilla not legible

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,
I noticed on the gui when you hover your mouse over an option in thunderbird or 
mozilla, i is not legible. 

-Steve

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


** Tags: bot-comment
-- 
Ubuntu 19.04 Desktop:mouseover preview of option in firefox and mozilla not 
legible
https://bugs.launchpad.net/bugs/1821552
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox in Ubuntu.

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

[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

[Elton]

This bug also affects me. My computer has an AMD R9 280x GPU, a 16 gigs
RAM, as well as a Core i7 processor. The memory allocated to Xorg
triples and sometimes takes up all the available RAM when switching from
themes, as from a dark theme to a light theme for instance. Kubuntu
18.10 with backports ppa is enabled and installed on the computer.

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

[Elton]

It's unlikely that its a bug affecting the current distributions of
Mesa, as I compile and install newer versions of Mesa every day from the
Obilaf ppa.

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

** Summary changed:

- failure to detect and use Intel 620 graphics pci id 3ea0
+ drm fails to accept edid version 2.4

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

Title:
  drm fails to accept edid version 2.4

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A
  

[Desktop-packages] [Bug 1789298] Re: info missing help docs "info info" and "H" command return error

[Kasia Gauza]

"info info" doesn't work: info: No menu item 'info-stnd' in node
'(dir)Top'

"H" from within info works, but "h" doesn't. It should show the
tutorial, but instead gives an error: Cannot find node '(info)Help'

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

Title:
  info missing help docs "info info" and "H" command return error

Status in texinfo package in Ubuntu:
  New

Bug description:
  The info command in Ubuntu 18.04 lacks it's own info page. This means
  that hitting "H" from within info to get a list of key bindings fails,
  as well as invoking info with "info info."

  In GNUs infinite wisdom, many terminal utilities lack a proper man
  page. These man pages include a short description of the program, then
  direct the user to run info for the complete documentation. "man info"
  is a great example of that where it includes a few command line
  options, and no information on what keys are used to navigate through
  the system (except to press H, which fails because the info
  documentation is missing).

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

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

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I was able to get the onboard LCD panel working, finally, as follows:

First I extracted the edid file from the LCD panel using get-edid and
putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel
to take that using the kernel boot option
drm.edid_firmware=edid/ncp.bin. This failed, and dmesg said that the
ncp.bin file had a "bad block 0". Possibly that means that nothing
within Linux can accept edid version 2.4?

Then I grabbed a generic 1920x1080.bin edid file from edid-generator
github and put that one in /lib/firmware/edid/ and used that one with
drm.edid_firmware and the display worked for the first time!

I am still unsure why Linux couldn't accept the version 2.4 edid data
from the LCD panel.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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 

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

[Amr Ibrahim]

Apparently Java 11 has switched to gtk3. The gtk3-java theming in
Ambiance theme is very incomplete in Bionic. I can see a lot of theming
artefacts in scilab (default look) and jabref (after switching to gtk
look).

Could it be switched back to gtk2 in Bionic?

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in geogebra package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in libjogl2-java package in Ubuntu:
  New
Status in libpdfbox-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mongo-java-driver package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openhft-chronicle-threads package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox-hwe package in Ubuntu:
  New
Status in activemq source package in Bionic:
  Fix Committed
Status in afterburner.fx source package in Bionic:
  Fix Committed
Status in annotation-indexer source package in Bionic:
  Fix Committed
Status in apache-directory-server source package in Bionic:
  Fix Committed
Status in aspectj source package in Bionic:
  Fix Committed
Status in aspectj-maven-plugin source package in Bionic:
  Fix Committed
Status in batik source package in Bionic:
  Fix Committed
Status in bindex source package in Bionic:
  Fix Committed
Status in bridge-method-injector source package in Bionic:
  Fix Committed
Status in carrotsearch-hppc source package in Bionic:
  Fix Committed
Status in clojure source package in Bionic:
  Fix Committed
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in commons-httpclient source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in ecj source package in Bionic:
  Fix Committed
Status in eclipselink source package in Bionic:
  Fix Committed
Status in elki source package in Bionic:
  Fix Committed
Status in figtree source package in Bionic:
  Fix Committed
Status in fontawesomefx source package in Bionic:
  Fix Committed
Status in geogebra source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gluegen2 source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in hikaricp source package in Bionic:
  Fix Committed
Status in hsqldb source package in Bionic:
  Fix Committed
Status in hsqldb1.8.0 source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in jabref source package in Bionic:
  Fix Committed
Status in jackson-core source package in Bionic:
  Fix Committed
Status in jackson-databind source package in Bionic:
  Fix Committed
Status in jackson-dataformat-xml source package in Bionic:
  Fix Committed
Status in jackson-module-jaxb-annotations source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javafxsvg source package in Bionic:
  Fix Committed
Status in javamail source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jboss-classfilewriter source package in Bionic:
  Fix Committed
Status in jboss-jdeparser2 source package in Bionic:
  Fix Committed
Status in jboss-modules source package in Bionic:
  Fix Committed
Status in jcommander source package in Bionic:
  Fix Committed
Status in jersey1 source package in Bionic:
  Fix Committed
Status in jftp source package in Bionic:
  Fix Committed
Status in jhove source package in Bionic:
  Fix Committed
Status in jmdns source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jruby-openssl source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jts source package in Bionic:
  Fix Committed
Status in junit4 source package in Bionic:
  Fix Committed
Status in jxgrabkey source package in Bionic:
  Fix Committed
Status in jython source 

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Below is the EDID information from the onboard panel. Why can't drm/i915
deal with it?


guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid 
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
1 potential busses found: 5
128-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier ""
ModelName ""
VendorName "NCP"
# Monitor Manufactured week 1 of 2018
# EDID version 2.4
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "false"
Modeline"Mode 0" 138.50 1920 1968 2000 2080 1080 1083 1088  
+hsync -vsync 
EndSection

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I think the problem is that the laptop's onboard LCD panel is reporting
EDID data with version 2 and the i915 driver can only deal with version
1 at the moment. How can this be fixed?

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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: 

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Correction: last message should read "Why is the driver/module expecting
EDID major version *1* and getting *2*?

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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: 

[Desktop-packages] [Bug 1637988] Re: Enable the nfs backend

[Steve Langasek]

Why has this SRU been pushed against the current 2.0 version of libnfs
in bionic and cosmic, when the Security Team has identified outstanding
concerns with 2.0 in the MIR bug (LP:# 1746598;
https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/comments/23)?

This does not look releasable as an SRU in its current state.

Marking verification-failed to block promotion, until the MIR concerns
for the earlier libnfs version are resolved.

Also, note that this currently breaks daily image builds in bionic now
that gvfs-backends in -proposed depends on libnfs11 from universe.

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

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

Title:
  Enable the nfs backend

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

Bug description:
  * Impact
  The gio/nautilus nfs:// locations handling is missing

  * Test case
  Try to connect to/browse a nfs server from nautilus by using a nfs:// location

  * Regression potential
  It's a new backend being enabled, it shouldn't have an impact on the existing 
ones

  Note that the backend relies on libnfs which got promoted in disco and
  would need to be promoted in cosmic/bionic as well then

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

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

[Desktop-packages] [Bug 1746598] Re: [MIR] libnfs

[Steve Langasek]

** Also affects: libnfs (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: libnfs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [MIR] libnfs

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

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year 
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.

  The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988

  qemu-block-extra could also enable libnfs support.

  Security
  
  No known CVEs.

  https://security-tracker.debian.org/tracker/source-package/libnfs
  https://launchpad.net/ubuntu/+source/libnfs/+cve

  Quality assurance
  =
  - Desktop Packages team is subscribed.
  - dh_auto_test runs but the tests shipped by upstream cant'b be run at build 
time since they modify the system.
  - Autopkgtests are added in 3.0.0-1, running upstream's test suite which 
includes running tests with valgrind, too.

  https://bugs.launchpad.net/ubuntu/+source/libnfs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs
  https://github.com/sahlberg/libnfs/issues

  https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed:
  see https://bugs.debian.org/921578 )

  https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in
  Debian because they request machine isolation which isn't implemented
  there yet)

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  3.9.8, debhelper compat 9, dh7 simple rules

  Maintenance
  ===
  Actively maintained:
  https://github.com/sahlberg/libnfs

  Not team maintained in Debian.
  https://tracker.debian.org/pkg/libnfs

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[João Marques]

I have tested without gnome extensions and the same happens to me. 
I've also tried the theory of ekimai by switching workspaces with mouse scroll 
on right bottom corner, unfortunately with the same crash.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Progress! Based on information in dmesg, pasted in at the end of this
message, I thought maybe the graphics device was found OK but the laptop
was trying to drive an external monitor instead of the onboard display.
Sure enough, when I boot without nomodeset option and with an external
HDMI monitor attached the system does display to the external monitor
with proper 1920x1080 resolution.

What does the "EDID is invalid:" message mean? Why is the driver/module
expecting EDID major version 2 and getting 1? Does this have to do with
the version of kbl_dmc firmware loaded to the graphics device?


guest@guest-ZenBook-UX431FA:~$ dmesg | egrep  "drm|i915"
[3.196687] fb: switching to inteldrmfb from EFI VGA
[3.196881] [drm] Replacing VGA console driver
[3.210304] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.210306] [drm] Driver supports precise vblank timestamp query.
[3.212814] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.214857] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
[3.228865] [drm] EDID has major version 2, instead of 1
[3.236620] [drm] EDID has major version 2, instead of 1
[3.240878] [drm] EDID has major version 2, instead of 1
[3.244590] [drm] EDID has major version 2, instead of 1
[3.244595] i915 :00:02.0: eDP-1: EDID is invalid:
[3.244597] [drm] EDID has major version 2, instead of 1
[3.290049] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0
[3.326674] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.356268] fbcon: inteldrmfb (fb0) is primary device
[4.724973] i915 :00:02.0: fb0: inteldrmfb frame buffer device

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection 

[Desktop-packages] [Bug 1776235] Re: Ubuntu 18.04 with RealVnc client. Clipboard only works with stock terminal

[Aleksey Shcherbina]

In my case (vino on Ubuntu 18.04 and RealVNC viewer on Windows 7) I can
only copy something from Windows to Ubuntu, but not back. Meanwhile vino
3.8.1-0ubuntu9.2 (this version info has been copied from another PC with
Linux Mint with RealVNC Viewer) seems to be working.

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

Title:
  Ubuntu 18.04 with RealVnc client. Clipboard only works with stock
  terminal

Status in vino package in Ubuntu:
  New

Bug description:
  Just as the title says.

  Clipboard only works with ubuntu 18.04 terminal. I can copy from
  terminal and paste into my Windows real vnc client.

  However, copying from any other application won't be able to reach vnc
  client.

  Even if I start cat, type something, then try to copy, VNC client
  won't see it.

  I won't complain if the clipboard doesn't work at all. However based
  on the fact that it only works on terminal, it indicates vino is doing
  some filtering and it won't tell. Somebody is messing with the users.

  An explanation is expected. Thanks!

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

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

[Desktop-packages] [Bug 1820899] Re: Neonode AirBar 13.3 inresponsive

[Bug Watch Updater]

** Changed in: libinput
   Status: Unknown => New

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

Title:
  Neonode AirBar 13.3 inresponsive

Status in libinput:
  New
Status in libinput package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  New

Bug description:
  I am having problems with this device in recent versions of kernel
  (4.x),

  It is showing up on `dmesg`, but doesn't work under any Linux desktop
  (so far). It has worked before, and works flawlessly on the MS OS (no
  Hardware issues).

  Could someone help me to identify the correct list/bug-tracker to issue this 
report ?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: KDE neon 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:1946]
  InstallationDate: Installed on 2018-10-14 (156 days ago)
  InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07dc Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: libinput (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L73 Ver. 01.11
  dmi.board.name: 1946
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 89.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: A3009CD1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~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 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: KDE neon 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:1946]
  InstallationDate: Installed on 2018-10-14 (156 days ago)
  InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55
  Package: libinput (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L73 Ver. 01.11
  dmi.board.name: 1946
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 89.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: A3009CD1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Derk Willem te Bokkel]

this bug was filed from sda6 partition.. 
with this command and the following errors generated

ubuntu-bug
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
(/usr/lib/firefox/firefox:5674): dconf-WARNING **: 11:31:02.271: Unable to open 
/var/lib/snapd/desktop/dconf/profile/user: Permission denied

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1812683] Re: rhythmbox crashes when trying to play music

[Didier Roche]

We need a decision if we SRU the workaround or not. After further 
investigations, I still can't reproduce it.
There is nothing clear in the bindings and it seems people can reproduce it 
without the plugin?

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Cosmic)
   Status: Confirmed => Incomplete

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Bionic)
   Status: Confirmed => Incomplete

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

Title:
  rhythmbox crashes when trying to play music

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar source package in Bionic:
  Incomplete
Status in rhythmbox-plugin-alternative-toolbar source package in Cosmic:
  Incomplete
Status in rhythmbox-plugin-alternative-toolbar source package in Disco:
  Fix Released

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #37 0x4d57 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 16:14:12 2019
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1821609] [NEW] Xorg freeze - fails to start or stay going screen blanks-grub seems involved

[Derk Willem te Bokkel]

Public bug reported:

Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..


back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively


on the test installs as long as the iso is using the grub boot loader installed 
from that install the system will boot normally .. the display manger tends to 
flicker on and off but does final start and login can proceed. 

but if another install re-installs grub as master  the display manager
fails to stay active or even come-up  for sda6 or sda7 only if their own
grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work by 
running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco freeze has-workaround regression reproducible 
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/1821609

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final 

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Is it known whether any machines with Intel Graphics 620 with pci id
0x3ea0 have functioning graphics with any version of Ubuntu?

This is relatively new hardware, but it seems unlikely that I am the
only one in the world who has tried this combination, and if other
people with different machines with the same 0x3ea0 pci id do have
working graphics then that would suggest that the problem is some quirk
of my particular ASUS UX431FA (perhaps some initialization timing quirk
or hardware/design bug that is worked-around for the Windows 10
installation that came with the system).

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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: 

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:6.2.2-0ubuntu1

---
libreoffice (1:6.2.2-0ubuntu1) disco; urgency=medium

  * New upstream release

  [ Rene Engelhard ]
  * debian/control.gtk3.in:
- make libreoffice-gtk3 recommend gstreamer1.0-gtk3 (LP: #1820062)

 -- Olivier Tilloy   Sun, 24 Mar 2019
22:44:21 +0100

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

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  New
Status in libreoffice source package in Cosmic:
  New

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  
  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

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

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

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I tried booting 4.18.0-16-generic (which i believe is the hwe kernel)
with kernel option drm.debug=0xff. When the system came up of course it
had no video but I could ssh in and grab the dmesg output, which is
attached to this message. dmesg had many drm-related debugging messages
and i915-related messages, but none of it was particularly helpful to me
yet.

** Attachment added: "dmesg-drm.debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249204/+files/dmesg-drm.debug.txt

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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: 

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Just in case my addition of i915 to initramfs was causing a problem with
drm-intel-next, I removed i915 from initramfs and repeated the test. The
result was the same, no video after a certain point in the boot process
with nomodeset using the drm-intel-next kernel as in #8.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  

[Desktop-packages] [Bug 1821523] Re: Installed snaps miss dependencies and permissions

[Will Cooke]

Thanks for taking the time to report this bug.

Generally speaking snaps do not have dependencies as such, everything is
bundled inside the snap.  Some snaps use platform snaps to provide some
core libs, but that's not relevant in this case.  FWIW, I tested the
notepad++ snap from Taqi Raza and it worked fine, all the interfaces
connected as they should have done, and I was able to browse my home
directory and open files.

GNOME Software is not in the critical path for setting permissions, and so I 
have to assume that this is a problem with the snaps you were trying to 
install.  You should contact the snap developers for support.  You can find 
contact info on the store page, for example:
https://snapcraft.io/notepad-plus-plus

GNOME Software does have the ability to toggle interfaces on and off.
Click the "Permissions" button from the application details page (next
to Launch and Remove).


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

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

Title:
  Installed snaps miss dependencies and permissions

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  When testing some text editors I have stumbled over multiple problems,
  after the software is installed.

  The first test was with notepad++. After installing the snap nothing
  worked. The program did not even start, nor provide some information
  what is wrong. After checking the interfaces of the notepad++ snap, I
  assume that there is a dependency to wine. At least the "notepad-plus-
  plus:wine-platform-plug" let me guess it.

  I was a little bit surprised that additional software is needed,
  because the software description in the software center did not
  mention any additional dependencies. Also I am used that the required
  dependencies are installed along with the selected software.

  I did not want to experiment with wine for now, so I have selected
  another editor: notepadqq. After the installation at least the program
  can be started, but no text files can be opened. The bug is also
  described at the project:
  https://github.com/notepadqq/notepadqq/issues/822

  On the Open File dialog a file system is visible that is not the file system 
of my PC. I guess it is the file system of the confined environment. The 
problem is that a text editor that can not access the files of my PC is useless.
  I had to install notepadqq with the classic option, so the file system of my 
PC can be accessed by notepadqq.

  The problem of software center is, that this step is not possible
  within the software center, but only via command line.

  I think it is important that the software center consider the dependencies 
when installing software and give the software all permissions needed to run.
  When permission should not be given without review/check/ the user can be 
asked what access right a software should get. At least an information should 
be given, that permissions are insufficient and how this can be changed.

  Cheers Matthias

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

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

[Desktop-packages] [Bug 1821585] Re: Ubuntu/Gnome dock not working with drag and drop

[Paul White]

** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)

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

Title:
  Ubuntu/Gnome dock not working with drag and drop

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

Bug description:
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04 latest updates installed

  
  To drag and drop a file to the Ubuntu/Gnome dock (favorites) is not working. 
For example I tried to drag the file .local/share/applications/example.desktop 
and drop it to favorites the result is that the starter is not created.

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

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

[Desktop-packages] [Bug 1794033]

[Oss-linuxpf]

Created attachment 143768
Debug trace.

I got debug traces. Please see attached file.
PID needs to be checked is 2602.
After that this process was exited with "i965: Failed to submit batchbuffer: 
Bad address".
At that time I repeated to copy and delete of files by rsync.

Note: This is occurred on core i3-6100E. Software version are same as
the above.

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Confirmed

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

[El jinete sin cabeza]

See LP: #1818862

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)

  ---

  Watching movie 4k, forward and back.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I installed kernel and modules and headers from
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
and rebooted without nomodeset option. Same behavior: after the "loading
initramfs" message the screen blanks and never comes back.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: 

[Desktop-packages] [Bug 1821585] [NEW] Ubuntu/Gnome dock not working with drag and drop

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:Ubuntu Disco Dingo (development branch)
Release:19.04 latest updates installed


To drag and drop a file to the Ubuntu/Gnome dock (favorites) is not working. 
For example I tried to drag the file .local/share/applications/example.desktop 
and drop it to favorites the result is that the starter is not created.

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

-- 
Ubuntu/Gnome dock not working with drag and drop
https://bugs.launchpad.net/bugs/1821585
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu.

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

[Desktop-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

[El jinete sin cabeza]

** No longer affects: totem

** No longer affects: mesa

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)

  ---

  Watching movie 4k, forward and back.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

[El jinete sin cabeza]

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

** Description changed:

  https://github.com/intel/intel-vaapi-driver/issues/451
- https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
  
  ---
  
  Watching movie 4k, forward and back.
- 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

Status in Mesa:
  Unknown
Status in Totem:
  New
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)

  ---

  Watching movie 4k, forward and back.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Timo Aaltonen]

note that having 800x600 with nomodeset is perfectly normal, and
expected...

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A
  

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Timo Aaltonen]

That pci-id should be known by all components of the stack on 19.04, so
it should work with X just fine. If it doesn't, it's likely a bug in the
kernel module. You could try with a mainline build of the drm-intel-next
branch:

https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/

install linux-image-unsigned and linux-modules for amd64, then boot
without nomodeset

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: 

[Desktop-packages] [Bug 1821523] Re: Installed snaps miss dependencies and permissions

[Matthew Paul Thomas]

software-center does not provide snaps at all. This is either a problem
with the snap itself, or with gnome-software.

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  Installed snaps miss dependencies and permissions

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When testing some text editors I have stumbled over multiple problems,
  after the software is installed.

  The first test was with notepad++. After installing the snap nothing
  worked. The program did not even start, nor provide some information
  what is wrong. After checking the interfaces of the notepad++ snap, I
  assume that there is a dependency to wine. At least the "notepad-plus-
  plus:wine-platform-plug" let me guess it.

  I was a little bit surprised that additional software is needed,
  because the software description in the software center did not
  mention any additional dependencies. Also I am used that the required
  dependencies are installed along with the selected software.

  I did not want to experiment with wine for now, so I have selected
  another editor: notepadqq. After the installation at least the program
  can be started, but no text files can be opened. The bug is also
  described at the project:
  https://github.com/notepadqq/notepadqq/issues/822

  On the Open File dialog a file system is visible that is not the file system 
of my PC. I guess it is the file system of the confined environment. The 
problem is that a text editor that can not access the files of my PC is useless.
  I had to install notepadqq with the classic option, so the file system of my 
PC can be accessed by notepadqq.

  The problem of software center is, that this step is not possible
  within the software center, but only via command line.

  I think it is important that the software center consider the dependencies 
when installing software and give the software all permissions needed to run.
  When permission should not be given without review/check/ the user can be 
asked what access right a software should get. At least an information should 
be given, that permissions are insufficient and how this can be changed.

  Cheers Matthias

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

-- 
Mailing list: https://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 1821022] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

[nicola]

Here some logs

hp@hp-desktop:~$ sudo apt remove timidity
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
Il pacchetto "timidity" non è installato e quindi non è stato rimosso
0 aggiornati, 0 installati, 0 da rimuovere e 5 non aggiornati.

those updates are firefox related


Il lunedì 25 marzo 2019, 02:40:52 CET, Daniel van Vugt 
 ha scritto:  
 
 Can you please run:

  dpkg -l > allpackages.txt

and then attach 'allpackages.txt'?

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying 
alsa-base in options snd-hda-intel model=auto or options snd-hda-intel 
model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio 
port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work 
perfectly when I connected to TV HDMI input (but could not steal TV 4 ever)
  
https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858
  https://streamable.com/5j96k

  
  BIOS setting in the video above

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1577 F pulseaudio
  /dev/snd/controlC0:  hp        1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 20 15:42:37 2019
  InstallationDate: Installed on 2016-09-07 (923 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
  LANGUAGE=it
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=it_IT.UTF-8
  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1577 F pulseaudio
  /dev/snd/controlC0:  hp        1577 F pulseaudio
  /dev/snd/seq:        timidity  1083 F timidity
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  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.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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.
  modified.conffile..etc.modprobe.d.alsa-base.conf:
  #options snd-hda-intel model=3stack-6ch
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-19T20:25:47.409210

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

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

** Attachment added: "alsa-info.txt.hPiFJm7LPP"
   
https://bugs.launchpad.net/bugs/1821022/+attachment/5249179/+files/alsa-info.txt.hPiFJm7LPP

** Attachment added: "Istantanea_2019-03-25_12-37-39.png"
   
https://bugs.launchpad.net/bugs/1821022/+attachment/5249180/+files/Istantanea_2019-03-25_12-37-39.png

** Attachment added: 
"=?UTF-8?b?bG9nX2F1ZGlvX3Byb2JsZW1lYXV0by1tYXNrNC0xLm9ndg==?="
   
https://bugs.launchpad.net/bugs/1821022/+attachment/5249181/+files/%3D%3FUTF-8%3Fb%3FbG9nX2F1ZGlvX3Byb2JsZW1lYXV0by1tYXNrNC0xLm9ndg%3D%3D%3F%3D

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying 
alsa-base in options snd-hda-intel model=auto or options snd-hda-intel 
model=asrock-mobo or options snd-hda-intel model=generic.; all on 

Re: [Desktop-packages] [Bug 1821022] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

[nicola]

Forgot to write that even microphone does not work at all
Il lunedì 25 marzo 2019, 02:40:52 CET, Daniel van Vugt 
 ha scritto:  
 
 Can you please run:

  dpkg -l > allpackages.txt

and then attach 'allpackages.txt'?

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying 
alsa-base in options snd-hda-intel model=auto or options snd-hda-intel 
model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio 
port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work 
perfectly when I connected to TV HDMI input (but could not steal TV 4 ever)
  
https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858
  https://streamable.com/5j96k

  
  BIOS setting in the video above

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1577 F pulseaudio
  /dev/snd/controlC0:  hp        1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 20 15:42:37 2019
  InstallationDate: Installed on 2016-09-07 (923 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
  LANGUAGE=it
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=it_IT.UTF-8
  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1577 F pulseaudio
  /dev/snd/controlC0:  hp        1577 F pulseaudio
  /dev/snd/seq:        timidity  1083 F timidity
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  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.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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.
  modified.conffile..etc.modprobe.d.alsa-base.conf:
  #options snd-hda-intel model=3stack-6ch
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-19T20:25:47.409210

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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying 
alsa-base in options snd-hda-intel model=auto or options snd-hda-intel 
model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio 
port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work 
perfectly when I connected to TV HDMI input (but could not steal TV 4 ever)
  
https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858
  https://streamable.com/5j96k

  
  BIOS setting in the video above

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1577 F pulseaudio
   /dev/snd/controlC0:  hp 1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 20 15:42:37 2019
  InstallationDate: Installed on 2016-09-07 (923 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - 

[Desktop-packages] [Bug 1821523] [NEW] Installed snaps miss dependencies and permissions

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When testing some text editors I have stumbled over multiple problems,
after the software is installed.

The first test was with notepad++. After installing the snap nothing
worked. The program did not even start, nor provide some information
what is wrong. After checking the interfaces of the notepad++ snap, I
assume that there is a dependency to wine. At least the "notepad-plus-
plus:wine-platform-plug" let me guess it.

I was a little bit surprised that additional software is needed, because
the software description in the software center did not mention any
additional dependencies. Also I am used that the required dependencies
are installed along with the selected software.

I did not want to experiment with wine for now, so I have selected
another editor: notepadqq. After the installation at least the program
can be started, but no text files can be opened. The bug is also
described at the project:
https://github.com/notepadqq/notepadqq/issues/822

On the Open File dialog a file system is visible that is not the file system of 
my PC. I guess it is the file system of the confined environment. The problem 
is that a text editor that can not access the files of my PC is useless.
I had to install notepadqq with the classic option, so the file system of my PC 
can be accessed by notepadqq.

The problem of software center is, that this step is not possible within
the software center, but only via command line.

I think it is important that the software center consider the dependencies when 
installing software and give the software all permissions needed to run.
When permission should not be given without review/check/ the user can be 
asked what access right a software should get. At least an information should 
be given, that permissions are insufficient and how this can be changed.

Cheers Matthias

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

-- 
Installed snaps miss dependencies and permissions
https://bugs.launchpad.net/bugs/1821523
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 1631715] Re: Password required twice returning from suspend

[Theo Linkspfeifer]

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Password required twice returning from suspend

Status in light-locker package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Clean install - no updates available.

  Suspend machine and restart.

  Lock screen requiring password - enter password and return to
  suspended desktop.

  Within a few seconds machine locks and password is required once more.

  Appears to depend on how fast I enter the password the first time.

  Using the same hardware I've installed nvidia 340.96 and tried to
  reproduce the issue without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: light-locker 1.7.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Oct  9 09:15:38 2016
  InstallationDate: Installed on 2016-10-09 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821498] Re: Last card disappears in thirteen

[Jouni Mettala]

I am setting this bug invalid. Nice that you pointed a reason in your
last comment.

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

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

Title:
  Last card disappears in thirteen

Status in aisleriot package in Ubuntu:
  Invalid

Bug description:
  In the game thirteen, sometimes when I get to the last card, the "no
  more moves" modal doesn't pop up. Then, if I click on the last
  discard, it vanishes, and then the modal pops up

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

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

[Launchpad Bug Tracker]

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

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

  * d/p/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch:
- update the patch to fix a logic error in the code which made tracker
  never being used even if it's installed (lp: #1767817)

 -- Sebastien Bacher   Wed, 06 Mar 2019 17:31:08
+0100

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

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

Title:
  Full text search does not work

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

Bug description:
  * Impact
  The text search feature, which is depending on tracker, is not working even 
when the service is installed

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  -> the file should be listed

  * Regression potential

  That's changing the search provider logic, make sure that searching
  for file without tracker still works (that only look at filenames) and
  there is no extra logging/cpu usage

  ---

  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
    Installed: 1:3.26.3-0ubuntu4
    Candidate: 1:3.26.3-0ubuntu4
    Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

[Łukasz Zemczak]

Thank you for testing the package, I have promoted it to bionic-updates.
The cosmic counterpart still needs verification though. Could someone
test the 18.10 package so we could get it released as well?

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

Title:
  Full text search does not work

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

Bug description:
  * Impact
  The text search feature, which is depending on tracker, is not working even 
when the service is installed

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  -> the file should be listed

  * Regression potential

  That's changing the search provider logic, make sure that searching
  for file without tracker still works (that only look at filenames) and
  there is no extra logging/cpu usage

  ---

  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
    Installed: 1:3.26.3-0ubuntu4
    Candidate: 1:3.26.3-0ubuntu4
    Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1767817] Update Released

[Łukasz Zemczak]

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

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

Title:
  Full text search does not work

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

Bug description:
  * Impact
  The text search feature, which is depending on tracker, is not working even 
when the service is installed

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  -> the file should be listed

  * Regression potential

  That's changing the search provider logic, make sure that searching
  for file without tracker still works (that only look at filenames) and
  there is no extra logging/cpu usage

  ---

  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
    Installed: 1:3.26.3-0ubuntu4
    Candidate: 1:3.26.3-0ubuntu4
    Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles

[van hanegen]

Just the same issue with my Galaxy C5 PRO, when i'm  trying to get
access to Сamera folder inside DCIM  folder on the micro-sd card. Both
with Ubuntu 16.04 and Ubuntu 18.04 (default nau managers)

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Incomplete

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

-- 
Mailing list: https://launchpad.net/~desktop-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: gdm3, hybrid nvidia with modeset=1, no external monitors detected

[Juan Cabello]

After adding the line "/usr/bin/xinit" to gdm3.service I get this in
every boot:

ProblemType: Crash
Architecture: amd64
Date: Mon Mar 25 19:17:11 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1543339632
ProcCmdline: /usr/lib/xorg/Xorg :0
...

Did you guys find out why? And, why does it take too long to show the
login screen?

-- 
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:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

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

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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed the graphics problem in DragonFlyBSD (I
cannot tell for certain if the graphics problem was fixed there due to
another, unrelated problem, but the fix definitely allowed the boot to
proceed further and the text did seem to switch to full screen
resolution).

The update-initramfs operation failed on the v5.1-rc2 kernel because of
two missing firmware files.

The update-initramfs operation succeeded on the 4.x kernels I had
installed, one of which is the hwe kernel (I believe). I verified the
presence of the i915 module in the initramfs for those kernels using
lsinitramfs. Unfortunately, booting with i915 in the initramfs on the
4.x kernels and without nomodeset did not solve the problem.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-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: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends 

[Desktop-packages] [Bug 1821508] Re: there is a lagging while i am accessing the software or browing

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => 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/1821508

Title:
  there is a lagging while i am accessing the software or browing

Status in Ubuntu:
  New

Bug description:
  i have serious issues while surfing in browsers. also video lags too much 
while i am playing any video in youtube.
  so tried to install intel drives.. thought it may solve my issue.
  any one could u please help me in solving this.

  also i have issue in processing fast

  i have system with following config please any one sugggest how can i
  speed up my application along with video lagging

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 24 16:45:03 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:011f]
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:011f]
  InstallationDate: Installed on 2018-11-04 (140 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731)
  MachineType: Acer Extensa 5220
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=5d6083c5-92be-466a-b199-35f0ebb59423 ro quiet nomodeset splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.32
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.32:bd02/01/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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
  xserver.bootTime: Sun Mar 24 16:26:55 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLenovo Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

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