date:20191023

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] cannot pause video with bluetooth headset buttons any more
  (MPRIS  denied by apparmor)

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 19.04 I could press the button on my Bluetooth headset and
  the YouTube video playing in my Chromium would pause/resume.  This no
  longer works in 19.10.  What happens instead is I get an OSD popup
  with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
  shell.

  I suspect the additional sandboxing of the snap package is the
  culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  Date: Mon Oct 21 15:04:13 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
   tmpfs  tmpfs  7,7G  122M  7,6G   2% /dev/shm
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (130 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20Q0CTO1WW
  dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1848123] Re: After I turn on the machine in the morning (probably from S3 sleep), it just blinks the displays for a few moments, than it turns to black for seconds and this is

2019-10-23 Thread vinibali

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

Thanks Daniel!

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

Title:
  After I turn on the machine in the morning (probably from S3 sleep),
  it just blinks the displays for a few moments, than it turns to black
  for seconds and this is an endless loop

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

Bug description:
  Hello there!

  I have an HP 840 G5, with an external docking station (HP USB-C Dock G4). All 
the input and output devices are connected to this docking station"
  - display on Displayport (x2)
  - ethernet
  - keyboard
  - mouse
  After I turn on the machine in the morning (probably from S3 sleep), it just 
blinks the displays for a few moments, than it turns to black for seconds and 
this is an endless loop. If I reconnect the docking station I can get back one 
of the displays to life, but the other one remain in sleep state.
  In the meanwhile after each of these problems, the intel_pstate driver seems 
to fail, all the processors cores are clocked to 3.6GHz.
  If I reboot the machine, both the screens are usable again and the 
intel_pstate driver is able to change the freqency.
  Kernel version 5.0.0-23 was not able to lower the frequency at all, I had to 
use the ondemand scheduler.
  I found these lines for about 5 days in a previous dmesg log.
  [10443.450243] [drm:intel_mst_enable_dp [i915]] *ERROR* Timed out waiting for 
ACT sent
  [10443.703810] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
  [10444.257321] [drm:intel_mst_enable_dp [i915]] *ERROR* Timed out waiting for 
ACT sent

  If I can help in any other way, please let me know!

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct 15 06:29:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
  InstallationDate: Installed on 2019-10-08 (6 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: HP HP EliteBook 840 G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-31-generic 
root=/dev/mapper/elxnoname--vg-root ro audit=0 noquiet nosplash 
sysrq_always_enabled
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.07.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.59.00
  dmi.chassis.asset.tag: 5CG8322Y91
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.07.00:bd04/17/2019:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.59.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G5
  dmi.product.sku: 3WQ22EC#ABB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1839620] Re: New upstream stable version 3.32.3

2019-10-23 Thread Mathew Hodson

** Tags added: upgrade-software-version

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

Title:
  New upstream stable version 3.32.3

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  That's a stable update in the GNOME 3.32 serie, the details of the changes 
are in 
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.2.news
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.3.news

  [ Test case ]

  That's a standard GNOME bugfix update and covered by
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the filemanager still work correctly, browse some
  locations, copy some files and directories, open the documents

  
  [ Regresison potential ]

  The update include several fixes, several of those are around the
  marking of favorites files/folders so check that feature works as
  expected

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

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

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

2019-10-23 Thread Mathew Hodson

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-10-23 Thread Brian Burch

I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan
(with gnome mostly at 3.34). The symptoms have not changed... my desktop
still hangs, loses keyboard events, and the log fills with the GTK 2/3
conflict messages. Meanwhile my Studio system behaves perfectly!

The log messages are generated by nautilis, gnome terminal, thunderbird,
and several other applications, but I do not think they are the culprits
- just the victims of something unseen.

The Studio system also has many GTK2 packages installed alongside the
GTK3 ones, so there isn't a simple explanation for the difference in
behaviour. I will do a side-by-side comparison of installed packages to
see if there is some sort of clue.

Meanwhile, I would be grateful if anyone could suggest how to identify
the guilty component. I would love to purge it!

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

Title:
  Slow and lost keyboard and mouse events

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

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.1
  ProcVersionSignature:

[Desktop-packages] [Bug 1063440] Re: sys_ptrace denied with Firefox 16

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

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

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

Title:
  sys_ptrace denied with Firefox 16

Status in firefox package in Ubuntu:
  Expired

Bug description:
  This might have been happening earlier, but I'm logging it now.

  Oct  7 16:52:35 sec-precise-amd64 kernel: [ 3861.291488] type=1400
  audit(1349646755.357:34): apparmor="DENIED" operation="capable"
  parent=14062 profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=18584
  comm="firefox" capability=19  capname="sys_ptrace"

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

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

[Desktop-packages] [Bug 885211] Re: firefox generates apparmor violations

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

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

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

Title:
  firefox generates apparmor violations

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Running along minding my own business in firefox, the following errors occur:
  Nov  2 09:22:21 host kernel: [50808.599850] type=1400 
audit(1320240141.763:51): apparmor="DENIED" operation="open" parent=13091 
profile="/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}" 
name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13092 comm="pulseaudio" 
requested_mask="r" denied_mask="r" fsuid=2501 ouid=0
  Nov  2 09:22:21 host kernel: [50808.599873] type=1400 
audit(1320240141.763:52): apparmor="DENIED" operation="open" parent=13091 
profile="/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}" 
name="/sys/devices/virtual/dmi/id/board_vendor" pid=13092 comm="pulseaudio" 
requested_mask="r" denied_mask="r" fsuid=2501 ouid=0
  Nov  2 09:22:21 host kernel: [50808.599887] type=1400 
audit(1320240141.763:53): apparmor="DENIED" operation="open" parent=13091 
profile="/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=13092 comm="pulseaudio" 
requested_mask="r" denied_mask="r" fsuid=2501 ouid=0
  Nov  2 09:22:21 host kernel: [50808.600112] type=1400 
audit(1320240141.763:54): apparmor="DENIED" operation="capable" parent=13091 
profile="/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}" pid=13092 
comm="pulseaudio" capability=19  capname="sys_ptrace"
  Nov  2 09:22:21 host kernel: [50808.600118] type=1400 
audit(1320240141.763:55): apparmor="DENIED" operation="ptrace" parent=13091 
profile="/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}" pid=13092 
comm="pulseaudio" target=5002

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

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

[Desktop-packages] [Bug 1152478] Re: apparmor blocks file_mmap for Flash, prevents Flash DRM from working on Hulu

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

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

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

Title:
  apparmor blocks file_mmap for Flash, prevents Flash DRM from working
  on Hulu

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Hulu reports error 3302.  This does not happen for all titles, only
  some which use Flash DRM.  The Flash plugin downloads and installs the
  library/module/plugin/whatever it needs, but it fails to load because
  of apparmor.

  $ dmesg
  type=1400 audit(1362725657.016:6916): apparmor="DENIED" operation="file_mmap" 
parent=7907 profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/me/.adobe/Flash_Player/NativeCache/1A51D5DAA3D68D562FE5E59686445EA2/752b8c40/libadobecp-301806-2.so"
 pid=16454 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000

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

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

[Desktop-packages] [Bug 1486462] Re: libreoffice draw drops from being shown in unity dashboard

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

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

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

Title:
  libreoffice draw drops from being shown in unity dashboard

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  Libreoffice Draw does not show in the Unity Dash when doing the
  following in trusty and bionic:

  1) press the Meta key to activate Dash search
  2) Type "libreo"
  3) notice how Libreoffice Draw is still showing as it should
  4) continue to type f to result in "libreof"
  5) notice how Libreoffice Draw was dropped from the result set which should 
not happen

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

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

[Desktop-packages] [Bug 1811530] Re: Impress embeded video files show flickering white stripes

2019-10-23 Thread shemgp

Upgrading to HWE kernel and graphic stacks somewhat relieves the
problem. At least now the presentation doesn't show it, but only the
info screen.

PPA: https://www.youtube.com/watch?v=zQwcmxjdg1g
Snap: https://www.youtube.com/watch?v=6RzSdrM-tWs
Linux 5.3 ppa & snap: https://www.youtube.com/watch?v=1hCP0g2kbOo

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

Title:
  Impress embeded video files show flickering white stripes

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

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1849484] Re: ultra-wide monitor recognized properly when plugged in only intermittently

Please try logging into both "Ubuntu" and "Ubuntu on Wayland". Do they
both have the bug?

Please also plug the monitor in to reproduce the bug and then
immediately run these commands and send us the resulting files:

  journalctl -b0 > journal.txt
  xrandr > xrandr.txt


** 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/1849484

Title:
  ultra-wide monitor recognized properly when plugged in only
  intermittently

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)

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

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

[Desktop-packages] [Bug 1841709] Re: [regression] gobject.h:767: syntax error

2019-10-23 Thread Treviño

** Description changed:

- Building mutter...
+ [ Impact ]
+ 
+ Building mutter triggers various non-fatal syntax errors:
  
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in 
'  do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at '/'
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')', 
expecting identifier or '(' in '  do { if 
g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at ')'
  /usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')', 
expecting identifier or '(' in '# 770 
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'
  
  Looks like the offending release glib2.0 (2.61.2-2) is from last night's
  updates.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 19.10
+ [ Test case ]
+ 
+ - Just build mutter and ensure that no such errors are triggered
+ 
+ [ Regression potential ]
+ 
+ None, once it builds we're all happy :)
+ 
+ ---
+ 
+ ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: libglib2.0-dev 2.61.2-2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 28 11:30:06 2019
  InstallationDate: Installed on 2019-05-02 (117 days ago)
- InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
- SourcePackage: glib2.0
+ InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 
(20190501)SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [regression] gobject.h:767: syntax error

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

  Building mutter triggers various non-fatal syntax errors:

  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in 
'  do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at '/'
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')', 
expecting identifier or '(' in '  do { if 
g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at ')'
  /usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')', 
expecting identifier or '(' in '# 770 
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'

  Looks like the offending release glib2.0 (2.61.2-2) is from last
  night's updates.

  [ Test case ]

  - Just build mutter and ensure that no such errors are triggered

  [ Regression potential ]

  None, once it builds we're all happy :)

  ---

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: libglib2.0-dev 2.61.2-2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 28 11:30:06 2019
  InstallationDate: Installed on 2019-05-02 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 
(20190501)SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

2019-10-23 Thread Treviño

** Description changed:

- Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
- color profile switching.  The commit at fault is
- 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
- when processing update” (which was intended to fix LP bug 1847044).
+ [ Impact ]
+ 
+ Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
+ The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).
+ 
+ [ Test case ]
+ 
+ - From gnome-control-center display panel, enable the Night Light
+ - Force it on, and ensure that the display color temperature increases
+ 
+ [ Regression potential ]
+ 
+ Display gamma value might be incorrect
  
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1849540] Re: booting issue

Yes I can see those kernel errors causing delays in your logs. They seem
to be referring to the motherboard:

00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI
Express Root Port #6 [8086:9d15] (rev f1) (prog-if 00 [Normal decode])

That's probably either a hardware fault or a kernel bug. If it is a
hardware fault then it might be limited to just your wifi card or
something removable like that...


** Summary changed:

- booting issue
+ "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" 
causing boot delays

** Package changed: xorg (Ubuntu) => linux (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/1849540

Title:
  "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver
  ID)" causing boot delays

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu shows pci bus error severity=corrected when shutting down
  takes time for login page to pop up

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 13:32:16 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
  InstallationDate: Installed on 2019-10-09 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441UAR.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441UAR
  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.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 14_ASUS Laptop X441UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

2019-10-23 Thread Treviño

** Description changed:

+ [ Impact ]
+ 
+ Gnome shell fills the journal with errors as soon as a view is closed
+ from the overview
+ 
  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1
  
- How to reproduce:
- 1) Open terminal and watch journalct -f
- 2) Open Files
+ [ Test case ]
+ 
+ 1) Open terminal and watch journalct -f /usr/bin/gnome-shell
+ 2) Open a window (i.e Files)
  3) Close Files in the activities overview
- 4) gnome-shell errors in journal non stop.
+ 4) gnome-shell spanws errors in the journal.
  
  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)
+ 
+ [ Regression potential ]
+ 
+ Key focus might not work properly in some shell elements, in particular
+ the focus be owned by multiple actors or by none of them.

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

[Desktop-packages] [Bug 1849545] Re: Graphics warning on restart

This looks like bug 982889, but that was fixed in 2013.

Still, since this is the only remaining instance of this bug I have
heard of I would recommend upgrading to Ubuntu 18.04. It is also a long
term support release and if you find gnome-shell is not well suited to
this machine then you can still reinstall Unity (unity-session package).

** Summary changed:

- Graphics warning on restart
+ Xorg repeatedly fails to start [Cannot run in framebuffer mode. Please 
specify busIDs for all framebuffer devices]

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

Title:
  Xorg repeatedly fails to start [Cannot run in framebuffer mode. Please
  specify busIDs for all framebuffer devices]

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 19:22:45 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  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-04-20 (186 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: LENOVO 2241WJE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 2241WJE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T500
  dmi.product.name: 2241WJE
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Wed Oct 23 19:13:21 2019
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

Scrolling back I can't see why I was thinking that in comment #29.

** Tags added: eoan

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

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  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/gnome-desktop/+bug/1825626/+subscriptions

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

[Desktop-packages] [Bug 1848217] Re: No system-ready sound

** Changed in: yaru
   Status: New => Fix Released

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

Title:
  No system-ready sound

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  ubiquity (the Ubuntu installer) tries to play 'system-ready' to
  indicate to visually impared users that the system is ready - so they
  can start the screen reader or whatever they need.

  Unfortunately yaru-theme-sound doesn't ship this sound. This means
  that we broke it when we switch from the old ubuntu-sounds theme.

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

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

[Desktop-packages] [Bug 1849545] Re: Graphics warning on restart

This seems to be a recurring error in your logs:

[26.747] (EE) 
Fatal server error:
[26.747] (EE) Cannot run in framebuffer mode. Please specify busIDs
for all framebuffer devices

That's probably the issue.

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

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

Title:
  Xorg repeatedly fails to start [Cannot run in framebuffer mode. Please
  specify busIDs for all framebuffer devices]

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 19:22:45 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  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-04-20 (186 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: LENOVO 2241WJE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 2241WJE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T500
  dmi.product.name: 2241WJE
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Wed Oct 23 19:13:21 2019
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

I guess we need to reproduce the mutter freeze that the Nvidia driver is
telling us about and with some luck force a stack trace or core dump
while it is happening.

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  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/gnome-desktop/+bug/1825626/+subscriptions

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

On 2019-10-24 00:56, Steve Langasek wrote:
> Contents of the file are:
> 
> include "/usr/share/X11/locale/en_US.UTF-8/Compose"
> <\> <)> : "☭"   # HAMMER AND SICKLE

Hmm.. Looking at  and
wondering if that line shouldn't rather read something like this:

: "☭"   # HAMMER AND SICKLE

(which works with IBus provided that there is a defined compose key)

Even if there was a regression due to the 1.5.19 -> 1.5.21 upgrade of
ibus

* the changed behavior is upstream in nature

* a possible upstream issue would basically say: "Why does IBus no
  longer interpret my syntactically incorrect ~/.XCompose file in
  accordance with my intention?"

So I tend to think that this bug should be closed as invalid, unless you
have some convincing arguments for keeping it open. Your call. :)

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

On Wed, Oct 23, 2019 at 07:24:03PM -, Gunnar Hjalmarsson wrote:
> Also, do you possibly have an ~/.XCompose file which you have played
> with previously?

Why yes, yes I do.

$ ls -l ~/.XCompose 
-rw-r--r-- 1 vorlon vorlon 93 Mar 27  2009 /home/vorlon/.XCompose
$

Moving this file aside and restarting ibus-daemon, the Delete key works as
expected.

Contents of the file are:

include "/usr/share/X11/locale/en_US.UTF-8/Compose"
<\> <)> : "☭"   # HAMMER AND SICKLE

So why is ibus interpreting this file differently in 19.10 than in
previous releases?

** Summary changed:

- ibus in 19.10 breaks the delete key, maps  to ☭
+ ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

** Changed in: ibus (Ubuntu)
   Importance: High => Medium

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

downgrading the bug to 'medium' since most people don't have ~/.XCompose
;)

** Changed in: ibus (Ubuntu)
   Status: New => Triaged

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1849573] [NEW] No way to specify tls-version-min or tls-version-max, please include the config options in the GUI config panel.

2019-10-23 Thread Thomas Ward

Public bug reported:

The OpenVPN plugin for Network Manager does not have any mechanisms to
interpret tls-version-{min,max} directives for OpenVPN.

In Debian upstream, especially in Buster and Unstable, they disable TLS
1.0, 1.1, and 1.2 by default and use only TLS 1.3 by default.
Therefore, with OpenVPN servers that only use TLS 1.2 or older, it is
impossible to establish a tunnel to those locations *unless* you specify
tls-version-{min,max} in the configurations.

This can be done in OVPN files for OpenVPN directly, but there is
currently no mechanism to do this in the GUI.

This is tracked in Debian https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=933177 as the original cause for TLS 1.3 support,
but if Ubuntu ever defaults OpenSSL to not have TLS 1.0-1.2 support
enabled by default, we will be out of luck.

Upstream, GNOME has not yet merged a merge request which would add this
option to the GUI: https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/merge_requests/15

Testing in Debian, the patch works against NetworkManager OpenVPN there.
I am currently testing these in Focal, Eoan, and Bionic to see if this
is something we can possibly include at a future date to fix this issue
long-term.

In the interim, this tracks the request to get these features in.

** Affects: network-manager-openvpn (Ubuntu)
Importance: Wishlist
Status: Triaged

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

Title:
No way to specify tls-version-min or tls-version-max, please include
the config options in the GUI config panel.

Status in network-manager-openvpn package in Ubuntu:
Triaged

Bug description:
The OpenVPN plugin for Network Manager does not have any mechanisms to
interpret tls-version-{min,max} directives for OpenVPN.

In Debian upstream, especially in Buster and Unstable, they disable
TLS 1.0, 1.1, and 1.2 by default and use only TLS 1.3 by default.
Therefore, with OpenVPN servers that only use TLS 1.2 or older, it is
impossible to establish a tunnel to those locations *unless* you
specify tls-version-{min,max} in the configurations.

This can be done in OVPN files for OpenVPN directly, but there is
currently no mechanism to do this in the GUI.

This is tracked in Debian https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=933177 as the original cause for TLS 1.3
support, but if Ubuntu ever defaults OpenSSL to not have TLS 1.0-1.2
support enabled by default, we will be out of luck.

Upstream, GNOME has not yet merged a merge request which would add
this option to the GUI: https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/merge_requests/15

Testing in Debian, the patch works against NetworkManager OpenVPN
there. I am currently testing these in Focal, Eoan, and Bionic to see
if this is something we can possibly include at a future date to fix
this issue long-term.

In the interim, this tracks the request to get these features in.

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

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

[Desktop-packages] [Bug 1846940]

2019-10-23 Thread Xiscofauli

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

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1846499] Re: e2scrub_all.service is a disabled or a static unit not running, not starting it.

** Package changed: gnome-software (Ubuntu) => e2fsprogs (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/1846499

Title:
  e2scrub_all.service is a disabled or a static unit not running, not
  starting it.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Upon attempting to upgrade form Ubuntu 19.04 to Ubuntu 19.10. The
  installation got stuck with this being the last command line output:

  "e2scrub_all.service is a disabled or a static unit not running, not
  starting it."

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

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

[Desktop-packages] [Bug 1848658] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: "error: too early for operation, device not yet seeded or device model not acknowl

2019-10-23 Thread Ian Johnson

What does `snap changes` show here?

Also what does `snap known serial` show on this machine?

Typically that error is for when a device has not yet communicated with
the snap store to get a serial assertion, and thus can't install snaps.
Perhaps this device does not have network access to the store?

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

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

Title:
  package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
  install/upgrade: "error: too early for operation, device not yet
  seeded or device model not acknowledged"

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Packet crash apt install chromium-browser

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 18 08:58:37 2019
  ErrorMessage: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2019-10-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90 
(58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
  Snap.ChromiumVersion:
   mkdir: cannot create directory '/run/user/0': Permission denied
   Chromium 77.0.3865.90 snap
  SourcePackage: chromium-browser
  Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849478] Re: (experimental) pipewire support not available

In third_party/webrtc/webrtc.gni¹:

  # Set this to use PipeWire on the Wayland display server.
  # By default it's only enabled on desktop Linux (excludes ChromeOS) and
  # only when using the sysroot as PipeWire is not available in older and
  # supported Ubuntu and Debian distributions.
  rtc_use_pipewire = is_desktop_linux && use_sysroot

use_sysroot is set to false in snap builds, so rtc_use_pipewire would
need to be explicitly set to true. This might require additional
build/runtime deps (assuming they are available in Ubuntu 18.04, which
is used to build the chromium snaps).


¹ 
https://cs.chromium.org/chromium/src/third_party/webrtc/webrtc.gni?type=cs=rtc_use_pipewire=package:chromium=0=115

** Tags added: snap

** Summary changed:

- (experimental) pipewire support not available
+ [snap] (experimental) pipewire support not available

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

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

Title:
  [snap] (experimental) pipewire support not available

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's
  not possible to enable experimental support for pipewire, as the
  toggle doesn't show up in chrome://flags.

  It would be nice to have chromium compiled with pipewire support, to
  enable screensharing in Hangouts and similar apps.

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

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

[Desktop-packages] [Bug 1849559] [NEW] /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

2019-10-23 Thread Mathieu Trudel-Lapierre

Public bug reported:

The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
location. It is a system-wide default config for dbus, and as such
probably should be in /usr/share/dbus-1/system.d instead; like most
other DBus definitions installed on a typical system.

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


** Tags: writable-etc

** Tags added: writable-etc

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

Title:
  /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

Status in wpa package in Ubuntu:
  New

Bug description:
  The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
  location. It is a system-wide default config for dbus, and as such
  probably should be in /usr/share/dbus-1/system.d instead; like most
  other DBus definitions installed on a typical system.

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

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

[Desktop-packages] [Bug 1848658] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: "error: too early for operation, device not yet seeded or device model not acknowl

I added a snapd task, as I'd like to hear snapd developers' opinion on
this "error: too early for operation, device not yet seeded or device
model not acknowledged".

** Summary changed:

- package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
+ package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to 
install/upgrade: "error: too early for operation, device not yet seeded or 
device model not acknowledged"

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

** Tags added: snap

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

Title:
  package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
  install/upgrade: "error: too early for operation, device not yet
  seeded or device model not acknowledged"

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Packet crash apt install chromium-browser

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 18 08:58:37 2019
  ErrorMessage: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2019-10-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90 
(58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
  Snap.ChromiumVersion:
   mkdir: cannot create directory '/run/user/0': Permission denied
   Chromium 77.0.3865.90 snap
  SourcePackage: chromium-browser
  Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

Ack, that's pretty bad. As requested by Paweł in comment #13, could you
check whether you get apparmor denials when starting chromium? You can
run the following command in a terminal, then launch chromium:

journalctl -f | grep DEN

Please attach the output after the chromium window has appeared. Thanks!

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  New

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1849228] Re: [snap] Chinese Supplementary Unicode characters not rendered at all (but working in .deb-Google Chrome)

Thanks for the report Christian.

I'm running 19.10 with the chromium snap. I opened the test page, and
all chinese characters appear to be rendered correctly. Same in a fully
up-to-date clean 19.10 VM. If I remove fonts-noto-cjk however, the
characters are not rendered correctly any longer.

Can you check whether fonts-noto-cjk is installed on your system?

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

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

Title:
  [snap] Chinese Supplementary Unicode characters not rendered at all
  (but working in .deb-Google Chrome)

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  This is my first bug report in a very very long time, so please bear
  with me, if the report is not that professional.

  I did a fresh install of Ubuntu 19.10 just now and I installed
  (nearly) every single fonts-* package and chromium-browser snap. And
  firefox (deb), falkon (deb) and Google Chrome (deb)

  Firefox and Falkon and Google Chrome do render all Chinese characters 
correctly and instantly:
  http://www.i18nguy.com/unicode/supplementary-test.html

  Works fine with:
  Firefox
  Falkon
  Google Chrome
  Midori
  Arora Browser (package: arora, pretty broken but it works on the test page)
  surf (package: surf, suckless browser)
  netsurf-gtk

  (all tested just now on 19.10 eoan!)

  
  Chromium Browser via snap does *NOT* display the characters at all: 
http://www.i18nguy.com/unicode/supplementary-test.html

  
  I went back to my install of Ubuntu 18.04.3 LTS with the chromium-browser via 
apt as a usual .DEB package. The test page on Ubuntu bionic does work 
absolutely fine and 100% correct. Not even much fonts installed.

  So I'm 100% sure this is snap related for Ubuntu 19.10.

  Expected: Chromium Browser (snap) should display the characters on
  http://www.i18nguy.com/unicode/supplementary-test.html

  What happens: You can't get Chromium browser (snap) in 19.10 to
  display the characters, no matter what.

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

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

2019-10-23 Thread Neil Hanlon

I am seeing this in 19.10 (POP_OS). Nvidia 1060. Mutter is indeed at
3.34.

Basically any time I alt-tab or otherwise switch between windows it
freezes and I get this syslog message.

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  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/gnome-desktop/+bug/1825626/+subscriptions

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

** Bug watch removed: gitlab.gnome.org/GNOME/gnome-control-center/issues #82
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

Thanks Jamie.
I'll mark the bug invalid for chromium. Even though chromium is visibly 
affected, the root cause has been identified and is going to be fixed soon.

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

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

Starting with the side topic (the easy part).

On 2019-10-23 18:50, Steve Langasek wrote:
> Settings -> Region & Language -> Input Sources presents Chinese as
> an option.  It can be reordered in the list, but it is not clickable.
> It has 'view' (eyeball) and 'delete' (trashcan) icons.  The 'view'
> icon pulls up a useless (for Chinese) keymap.

Ok, so you have previously added the Chinese keyboard layout. It's
actually just an alias to the basic English (US) layout.

Please note that the list you see first only shows the options you have
previously made available by adding them. To look for further sources to
add you need to click the + button.

I installed ibus-sunpinyin, relogged in, and found the Chinese
(SunPinyin) option in Settings among the "Other" input sources. Then I
generated the zh_CN.UTF-8 locale, and found that the Chinese item had
been converted to a sub menu, which includes Chinese (SunPinyin)
together with the Chinese XKB layout.

That's how the GNOME design currently works. Not saying I'm too fond of
it. In Unity (with code from GNOME 3.4 or something) the input sources
were simply presented in one long list, and when you started to type the
source you were looking for, it safely showed up.

I have filed an upstream issue about the most apparent shortcoming with
the current design:

https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

It doesn't directly address the issue you stumbled upon, but it's
closely related.

> What is suspicious about the file?
> 
> I moved the directory aside, started ibus-daemon up again, and the
> problem persists.  The ~/.cache/ibus/compose/e6817ed7.cache file has
> been recreated with identical contents as previously.

It was merely the name of the directory, and the string
"IBusComposeTable" in the contents of the cache file which made me say
that. After all your Delete key seems to do some kind of composing
instead of what it's expected to do.

> The problem persists with these settings, as long as ibus-daemon is
> running.

It's ugly behavior, and all we know so far is that it seems to be caused
by something in $HOME. But it may be due to some other cache file, some
dconf setting, or whatever. I'm out of ideas for now as regards how to
nail it.

Well, one thing you may want to try is to move away the
~/.config/dconf/user file and relogin so it gets recreated with only
default values.

Also, do you possibly have an ~/.XCompose file which you have played
with previously?

*Now* I'm out of ideas.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #82
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1849542] Re: Thunderbird empty after update to 19.10

I'm glad you found a way around the problem. Did you keep a copy of the
faulty global-messages-db.sqlite, by any chance?

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

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1849545] [NEW] Graphics warning on restart

2019-10-23 Thread Jonathan

Public bug reported:

On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
Wondering what's going on and whether I should be doing something different.
Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct 23 19:22:45 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
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-04-20 (186 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: LENOVO 2241WJE
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET92WW (3.22 )
dmi.board.name: 2241WJE
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T500
dmi.product.name: 2241WJE
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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: Wed Oct 23 19:13:21 2019
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Graphics warning on restart

Status in xorg package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'

[Desktop-packages] [Bug 1694373]

2019-10-23 Thread Exalm

I guess https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/605
fixes this

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

Title:
  Gnome Shell app list scrolls too quickly with mouse wheel

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

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=707973

  ---

  Gnome Shell app list scrolls too quickly with mouse wheel.

  It seems to scroll one page per wheel tick, which is way too much.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue May 30 14:08:46 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 
'cariboukkk', 'cariboujj']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (27 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849542] Re: Thunderbird empty after update to 19.10

2019-10-23 Thread Loïc Alejandro

Just deleted global-messages-db.sqlite and now it looks like it works
fine. I hopê I didn't loose anything.

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  New

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1849542] [NEW] Thunderbird empty after update to 19.10

2019-10-23 Thread Loïc Alejandro

Public bug reported:

HELP

Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
Thunderbird and the interface is empty. No emails, no folders, no
calendar, I can't even open the "account settings" window.

This is a complete disaster. I need thunderbird for my work.

If I launch TB form terminal I get this:

lalejand@Gedeon:~$ thunderbird 
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
TypeError: aAttrDef.objectNounDef is undefined
-- Exception object --
*
-- Stack Trace --
defineAttribute@resource:///modules/gloda/gloda.js:1922:5
defineAttributes@resource:///modules/gloda/fundattr.js:71:35
init@resource:///modules/gloda/fundattr.js:43:12
@resource:///modules/gloda/everybody.js:13:15
@resource:///modules/gloda/public.js:8:57
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
JavaScript error: chrome://messenger/content/messenger.xul, line 1: TypeError: 
QuickFilterBarMuxer is undefined
JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

What can I do ?

Release: Ubuntu 19.10
Package version: 1:68.1.2+build1-0ubuntu

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

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  New

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

2019-10-23 Thread Jamie Strandboge

Ok, I'll fix this in the next batch of policy updates for snapd.

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

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

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1849540] [NEW] booting issue

2019-10-23 Thread Anand

Public bug reported:

ubuntu shows pci bus error severity=corrected when shutting down
takes time for login page to pop up

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 13:32:16 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
InstallationDate: Installed on 2019-10-09 (14 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X441UAR.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X441UAR
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.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 14_ASUS Laptop X441UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  booting issue

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu shows pci bus error severity=corrected when shutting down
  takes time for login page to pop up

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 13:32:16 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
  InstallationDate: Installed on 2019-10-09 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: American Megatrends Inc.

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

Regardless, it's simply a hypothesis on my part that the fact that I
have configured Chinese input methods in the past may be the cause of
this problem.  The Chinese keyboard setting is not active when this
problem manifests.

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

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

Yes, it is mounted:

ubuntu@bionicvm:~$ mount | grep Private
/home/ubuntu/.Private on /home/ubuntu/Private type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=11d8701311f9dc77,ecryptfs_sig=4ca5cd476d88b7cd,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

> There is a ~/.cache/ibus/compose folder with a suspicious cache file.
> Can you please rename that folder, relogin, and check if the issue is
> still present.

What is suspicious about the file?

I moved the directory aside, started ibus-daemon up again, and the
problem persists.  The ~/.cache/ibus/compose/e6817ed7.cache file has
been recreated with identical contents as previously.

Here are my gsettings values currently:

$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'us+dvorak-alt-intl'), ('xkb', 'gr+polytonic'), ('xkb', 'cn'), ('xkb', 
'ru')]
$ gsettings get org.freedesktop.ibus.general preload-engines
['xkb:us::eng']
$

The problem persists with these settings, as long as ibus-daemon is
running.

> For an IBus IM to be presented in Settings or ibus-setup, the package -
> in your case ibus-sunpinyin - needs to be installed. But when you say
> that only Chinese is listed in Settings, and assuming that ibus-
> sunpinyin is still installed on your machine, can it possibly be that if
> you click the "Chinese" option in Settings, you end up in a sub menu
> which includes Chinese SunPinyin?

Settings -> Region & Language -> Input Sources presents Chinese as an
option.  It can be reordered in the list, but it is not clickable.  It
has 'view' (eyeball) and 'delete' (trashcan) icons.  The 'view' icon
pulls up a useless (for Chinese) keymap.

The ibus-sunpinyin package is installed.

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

2019-10-23 Thread Jamie Strandboge

Ok, that is a read on /home/ubuntu/.Private/. Is the encrypted home
mounted at the time of the denial?

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1849105] Re: [snap] cannot pause video with bluetooth headset buttons any more (MPRIS denied by apparmor)

Fixed with https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=aca99f48134f58c912d6a573ca1233ac601754ed.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [snap] cannot pause video with bluetooth headset buttons any more
  (MPRIS  denied by apparmor)

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  On Ubuntu 19.04 I could press the button on my Bluetooth headset and
  the YouTube video playing in my Chromium would pause/resume.  This no
  longer works in 19.10.  What happens instead is I get an OSD popup
  with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
  shell.

  I suspect the additional sandboxing of the snap package is the
  culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  Date: Mon Oct 21 15:04:13 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
   tmpfs  tmpfs  7,7G  122M  7,6G   2% /dev/shm
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (130 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20Q0CTO1WW
  dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

2019-10-23 Thread Timo Aaltonen

Hello Shih-Yuan, or anyone else affected,

Accepted nvidia-graphics-drivers-430 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-430/430.50-0ubuntu0.18.04.2 in a few hours, and
then in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849512] Re: Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory

2019-10-23 Thread Didier Roche

zsys is handling this (adduser will try to execute it and creates a
dataset, and if it can't, it fallbacks to traditional directory
creation.

zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so
I encourage you to install and test it! Thanks :)

I'll have to mark the bug as invalid.
If you installed zsys and you still see this behavior, do not hesitate to ping 
us back!

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

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

Title:
  Creating a new user on top of ZFS filesystem does not create a new
  dataset for his home directory

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

Bug description:
  When you're using the experimental ZFS on root installation on Ubuntu 19.10 
initially you're creating one user. This user has a home directory mounted on 
different ZFS dataset like in this case:
  https://paste.ubuntu.com/p/CSsNtt5j6c/
  Afterwards when you're adding new users via the gnome-control-center or with 
adduser, the new users home directories are created on rpool/USERDATA but they 
don't have separate ZFS datasets.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 18:12:56 2019
  InstallationDate: Installed on 2019-10-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849105] Re: [snap] cannot pause video with bluetooth headset buttons any more (MPRIS denied by apparmor)

Confirmed, and adding the mpris slot fixes the issue.

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [snap] cannot pause video with bluetooth headset buttons any more
  (MPRIS  denied by apparmor)

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  On Ubuntu 19.04 I could press the button on my Bluetooth headset and
  the YouTube video playing in my Chromium would pause/resume.  This no
  longer works in 19.10.  What happens instead is I get an OSD popup
  with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
  shell.

  I suspect the additional sandboxing of the snap package is the
  culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  Date: Mon Oct 21 15:04:13 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
   tmpfs  tmpfs  7,7G  122M  7,6G   2% /dev/shm
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (130 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20Q0CTO1WW
  dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849522] [NEW] imported non-rpool/bpool zpools are not being reimported after reboot

2019-10-23 Thread satmandu

Public bug reported:

Installed ubuntu 19.10 onto a zfs bpool/rpool.

Installed zsys.

Did a "zpool import" of my existing zfs pools.

Rebooted.

The previously imported zpools are not imported at boot!

I am currently using this hacky workaround:

https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507


I would expect that local zpools I have manually imported would re-import when 
the system is rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: zsys 0.2.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Wed Oct 23 11:40:36 2019
InstallationDate: Installed on 2019-10-19 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  imported non-rpool/bpool zpools are not being reimported after reboot

Status in zsys package in Ubuntu:
  New

Bug description:
  Installed ubuntu 19.10 onto a zfs bpool/rpool.

  Installed zsys.

  Did a "zpool import" of my existing zfs pools.

  Rebooted.

  The previously imported zpools are not imported at boot!

  I am currently using this hacky workaround:

  https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507

  
  I would expect that local zpools I have manually imported would re-import 
when the system is rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zsys 0.2.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 23 11:40:36 2019
  InstallationDate: Installed on 2019-10-19 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2019-10-23 Thread Timo Aaltonen

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-430 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-430/430.50-0ubuntu0.18.04.2 in a few hours, and
then in the -proposed repository.

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

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

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

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

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if

[Desktop-packages] [Bug 1849517] [NEW] latest kernel problem 5.3

2019-10-23 Thread raza

Public bug reported:

when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
   i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
Thanx

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 20:48:03 2019
DistUpgraded: 2019-10-23 15:18:23,354 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: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [103c:8562]
MachineType: Hewlett-Packard HP 245 G7 Notebook PC
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro acpi_osi=Linux quiet splash 
resume=2d8fc2ac-0fa9-4d85-99bc-e3f760724070 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)
dmi.bios.date: 07/03/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8562
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 84.24
dmi.chassis.asset.tag: 5CG9212QLP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 245 G7 Notebook PC
dmi.product.sku: 6JM93PA#ACJ
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan 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/1849517

Title:
  latest kernel problem 5.3

Status in linux package in Ubuntu:
  New

Bug description:
  when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
  i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
 i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
  Thanx

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 20:48:03 2019
  DistUpgraded: 2019-10-23 15:18:23,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark:

[Desktop-packages] [Bug 1849512] [NEW] Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory

2019-10-23 Thread Ivo Hristov

Public bug reported:

When you're using the experimental ZFS on root installation on Ubuntu 19.10 
initially you're creating one user. This user has a home directory mounted on 
different ZFS dataset like in this case:
https://paste.ubuntu.com/p/CSsNtt5j6c/
Afterwards when you're adding new users via the gnome-control-center or with 
adduser, the new users home directories are created on rpool/USERDATA but they 
don't have separate ZFS datasets.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 18:12:56 2019
InstallationDate: Installed on 2019-10-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Summary changed:

- Creating a new user on top of ZFS filesystem does not create a new datase for 
his home directory
+ Creating a new user on top of ZFS filesystem does not create a new dataset 
for his home directory

** Description changed:

- When you're using the experimental ZFS on root installation on Ubuntu 19.10 
initially you're creating one user. This user have a home directory mounted on 
different ZFS dataset like in this case:
+ When you're using the experimental ZFS on root installation on Ubuntu 19.10 
initially you're creating one user. This user has a home directory mounted on 
different ZFS dataset like in this case:
  https://paste.ubuntu.com/p/CSsNtt5j6c/
  Afterwards when you're adding new users via the gnome-control-center or with 
adduser, the new users home directories are created on rpool/USERDATA but they 
don't have separate ZFS datasets.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 18:12:56 2019
  InstallationDate: Installed on 2019-10-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Creating a new user on top of ZFS filesystem does not create a new
  dataset for his home directory

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

Bug description:
  When you're using the experimental ZFS on root installation on Ubuntu 19.10 
initially you're creating one user. This user has a home directory mounted on 
different ZFS dataset like in this case:
  https://paste.ubuntu.com/p/CSsNtt5j6c/
  Afterwards when you're adding new users via the gnome-control-center or with 
adduser, the new users home directories are created on rpool/USERDATA but they 
don't have separate ZFS datasets.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 18:12:56 2019
  InstallationDate: Installed on 2019-10-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849517] Re: latest kernel problem 5.3

** Package changed: xorg (Ubuntu) => linux (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/1849517

Title:
  latest kernel problem 5.3

Status in linux package in Ubuntu:
  New

Bug description:
  when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
  i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
 i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
  Thanx

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 20:48:03 2019
  DistUpgraded: 2019-10-23 15:18:23,354 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: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:8562]
  MachineType: Hewlett-Packard HP 245 G7 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro acpi_osi=Linux quiet splash 
resume=2d8fc2ac-0fa9-4d85-99bc-e3f760724070 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)
  dmi.bios.date: 07/03/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8562
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 84.24
  dmi.chassis.asset.tag: 5CG9212QLP
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 245 G7 Notebook PC
  dmi.product.sku: 6JM93PA#ACJ
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/linux/+bug/1849517/+subscriptions

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

2019-10-23 Thread Alistair Cunningham

Yes, using "Launch email client" fixes the problem for me.

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

I can also observe the issue if I create a custom shortcut with command 
"thunderbird".
However if I use/redefine the existing shortcut for "Launch email client" (in 
the Launchers category), then the issue isn't observable.

The difference lies in the way thunderbird is invoked. For the existing
"Launch email client" shortcut, unity-settings-daemon invokes the
default mailto: URL handler, which calls
g_app_info_get_default_for_uri_scheme("mailto").

I guess the DE (Unity or others) can't easily match a starting process
for thunderbird to an existing desktop file, whereas in the case of the
mailto handler it definitely has all the information needed.

I'd suggest using the existing shortcut and redefining it to suit your
habits.

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

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849142] Re: Discord and appindicator extension slows down ui

2019-10-23 Thread Linus

I've only tried in KDE as well. The icon is there but the icon change
that is supposes to happen when speaking does not show, but i guess
that's on discord to fix. However KDE don't have a slowdown while
speaking like gnome does with the indicator extension installed.

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

Title:
  Discord and appindicator extension slows down ui

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

Bug description:
  Updated bug #1817073 about this, but it's not really the same since
  this does not crash the shell fully.

  When speaking in discord there is supposed to be an icon change on the
  appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable
  to lookup icon for discord1_40.

  The whole desktop freezes for a moment when talking in discord if the 
appindicator package is installed.
  Easily reproduced by joining a voice channel in discord and just doing stuff 
in the gnome ui, watching a video or whatever while talking.

  This is pretty bad since it leaves no choice but to uninstall gnome-
  shell-extension-appindicator and loosing that functionality if people
  wants to use discord on ubuntu.

  This is also reported on the extensions github page:
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157

  Someone also made a video on youtube showing the problem:
  https://www.youtube.com/watch?v=ABavT7yXlso

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

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

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

2019-10-23 Thread Timo Aaltonen

** Also affects: nvidia-graphics-drivers-435 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-435 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 source package in Bionic:
  New
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848918] Re: [snap] "Save As" dialogue: Clicking on Home button opens unexpected folder

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

** This bug has been marked a duplicate of bug 1798450
   [snap] File dialogs show snap's home directory instead of user's

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

Title:
  [snap] "Save As" dialogue: Clicking on Home button opens unexpected
  folder

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In the "save as" dialogue (i.e. via "Save link as...") clicking on the
  Home button icon on the left side opens
  "/home/username/snap/chromium/899" and not my personal folder.

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

Indeed I can see the rules you mention in
/etc/apparmor.d/abstractions/base, which is included by
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium.

However I can reliably reproduce the issue, and I'm seeing the following
denial:

  AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromium" name="/home/ubuntu/.Private/" pid=11167
comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

Also observable using Super+M in Xubuntu which uses that shortcut to
launch the default mail reader.

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

2019-10-23 Thread Jamie Strandboge

Encrypted home is typically setup as ~/.Private, not ~/Private and the
policy already allows:

  owner @{HOME}/.Private/** mrixwlk,
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,

The home interface should already allow ~/Private. What is the denial
you see in the logs?

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1849142] Re: Discord and appindicator extension slows down ui

2019-10-23 Thread Sebastien Bacher

Thank you for your bug report. Does the same indicator work in other
desktop environment (e.g Unity?)

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

Title:
  Discord and appindicator extension slows down ui

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

Bug description:
  Updated bug #1817073 about this, but it's not really the same since
  this does not crash the shell fully.

  When speaking in discord there is supposed to be an icon change on the
  appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable
  to lookup icon for discord1_40.

  The whole desktop freezes for a moment when talking in discord if the 
appindicator package is installed.
  Easily reproduced by joining a voice channel in discord and just doing stuff 
in the gnome ui, watching a video or whatever while talking.

  This is pretty bad since it leaves no choice but to uninstall gnome-
  shell-extension-appindicator and loosing that functionality if people
  wants to use discord on ubuntu.

  This is also reported on the extensions github page:
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157

  Someone also made a video on youtube showing the problem:
  https://www.youtube.com/watch?v=ABavT7yXlso

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

I can confirm this using Ubuntu 18.04 but *only* when starting
Thunderbird from a keyboard shortcut. I tried using Super+T and Ctrl-
Alt-G. For me, the mouse pointer doesn't change to a spinner until
Thunderbird has loaded and is checking for new mail.

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

2019-10-23 Thread David Ledger

I too have the
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
problem, but it only affects one user.

$ cat /etc/default/locale 
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
$ 

... which should be the UK/GB version because that's where I live, but
for testing I set it as above.

I don't have chrome remote desktop and never have had.

It works for my test user logins, so it must be something in my
environment. It's not a shell startup problem because I see the error
message if I run it from an xterm, and the xterm works fine.

There must be something else going on.

David

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

Title:
  Gnome terminal not starting, timeout reached (bionic)

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  After a having my memory filled I had to reboot because the system got
  unresponsive. After that I can no longer open gnome terminal. I tried
  running it from xterm and the following message appears:

  Error constructing proxy for
  org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
  StartServiceByName for org.gnome.Terminal: Timeout was reached

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 10:38:26 2017
  InstallationDate: Installed on 2017-08-21 (126 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private folder

I can reliably reproduce the issue after creating an encrypted Private
directory with ecryptfs-setup-private (see
https://help.ubuntu.com/community/EncryptedPrivateDirectory#Setup_Your_Encrypted_Private_Directory).

The problem stems from the fact that the home interface doesn't allow
reading/writing to hidden folders in $HOME, and the ~/Private folder is
actually backed by encrypted data in ~/.Private.

This is not specific to chromium, other strictly confined snaps using
the home interface would be similarly affected.

Interestingly, saving a file to the folder still works, despite the
error and the fact that the file dialog is unable to show the contents
of the folder.

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

** Summary changed:

- [snap] Permission denied on Private folder
+ [snap] Permission denied on Private encrypted folder

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save

As noted in comment #2, I used to be able to observe the problem, but I
cannot any longer. I upgraded my laptop to 19.10 a while ago while it
was still in development, and I couldn't tell for sure when the problem
went away. I didn't do a fresh install, nor did I create a new user or
cleaned up settings in any way.

@Christopher: from your last comment I understand you're still affected.
Have you upgraded to 19.10 ? If not, are you planning to do it in a not-
too-distant future? If so I'd be interested in knowing whether this
resolves the issue for you.

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

Title:
  print page dialog latency when trying to cancel or to save

Status in chromium-browser package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Since less than a month ago, using the print page dialog (which for me
  defaults to saving as PDF) is outlandishly slow. Once opened, if I try
  to close it (click cancel / press Esc) or to use it (click Save or
  press Enter), there is no visible response, and my system hangs for 10
  seconds.  After that though, the operation concludes successfully and
  things return to normal.

  This did not used to happen. Closing or submitting the print-to-PDF
  used to result in the pop-up window closing immediately and the
  browser regaining responsiveness.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-5:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-6:
   enabled: disabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM=
   modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-7:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   modes: 1920x1080
  Date: Mon Jun 17 14:03:12 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-01-24 (144 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   
  Load-Avg-1min: 3.09
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Desktop-packages] [Bug 1848841] Re: Chromium snap looks tiny in hidpi after gnome shell restart

Thanks for the report Carlos. From your description, it sounds like this
is a regression, i.e. restarting gnome-shell with a running instance of
chromium packaged as a deb would not rescale to 1x. Is that correct?

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

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

Title:
  Chromium snap looks tiny in hidpi after gnome shell restart

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
  to 19.10 and chromium became a snap package. It launches at the right
  scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
  1x (I believe) and everything becomes absurdly tiny. Restarting
  chromium afterwards restores the right scaling factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8=
   modes: 3000x2000
  Date: Sat Oct 19 05:11:37 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   331G   62G  255G  20% /
   tmpfs  tmpfs  7,8G   75M  7,7G   1% /dev/shm
   /dev/nvme0n1p2 ext4   331G   62G  255G  20% /
  InstallationDate: Installed on 2019-06-13 (127 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=08b323c0-f1a9-46a9-8d2c-694dff8193f6 ro quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2018
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.17
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.17:bd07/28/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: HUAWEI MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

2019-10-23 Thread Alistair Cunningham

Certainly; please see:

https://drive.google.com/file/d/1HnddxhNOpZHsQ2Dxb9dAyvL7Vv0ZQpJG/view?usp=sharing

I pressed Super+T just as I said "now". Notice that the mouse pointer
near the middle of the screen does not change.

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

On 2019-10-23 08:09, Steve Langasek wrote:
>> * Which values do the environment variables have?
> 
> $ env | grep -E 'XMOD|_IM'
> GTK_IM_MODULE=ibus
> QT4_IM_MODULE=ibus
> XMODIFIERS=@im=ibus
> CLUTTER_IM_MODULE=ibus
> QT_IM_MODULE=ibus
> $

Looks good.

> I don't know where these are being set, because Xsession is hell.

They are set by im-config on X-sessions on Debian/Ubuntu. (Without im-
config, the most important ones would have been set by GNOME instead.)

>> * Can you reproduce it on a fresh 19.10 (or with a newly created
>> user)?
> 
> No.

Then we know that the issue is caused by something in your $HOME. The
question is what and how it ended up there...

There is a ~/.cache/ibus/compose folder with a suspicious cache file.
Can you please rename that folder, relogin, and check if the issue is
still present.

>> Assuming that you are on standard Ubuntu, using ibus-setup for
>> adding/removing input sources is not the 'right' way
> 
> That's not really a satisfactory position, given that the ibus-setup
> command is shipped in the ibus package, which is seeded as part of
> the Ubuntu Desktop.  If the command should not be used, it should not
> be present.

Fair point. But on non-GNOME desktops ibus-setup is needed, and made
available to the users via an IBus icon. I wouldn't dare to say that you
*never* need to use ibus-setup on a GNOME desktop, but GNOME provides an
integration where XKB layouts and IBus IMs are presented together in
Settings, so normally the users don't need to bother with ibus-setup.

>> it's supposed to be done in Settings -> Region & Language (probably
>> not significant for this issue, but still...).
> 
> I can't find anything under the settings screens that resembles the
> selection of input methods presented by ibus-setup.

The "Input Sources" section in Region & Language is what I'm talking
about. That interface controls the available input sources and saves the
settings as

gsettings get org.gnome.desktop.input-sources sources

The input sources set via ibus-setup are saved as

gsettings get org.freedesktop.ibus.general preload-engines

but on GNOME the latter dconf setting is ignored AFAIK.

> ibus-setup presents 'Chinese SunPinyin', Settings only presents
> 'Chinese'; and removing the Chinese input method from ibus-setup's
> config doesn't change what's displayed in Settings (Chinese is still
> listed here).

For an IBus IM to be presented in Settings or ibus-setup, the package -
in your case ibus-sunpinyin - needs to be installed. But when you say
that only Chinese is listed in Settings, and assuming that ibus-
sunpinyin is still installed on your machine, can it possibly be that if
you click the "Chinese" option in Settings, you end up in a sub menu
which includes Chinese SunPinyin?

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

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Desktop-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

** Tags added: eoan

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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

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

[Desktop-packages] [Bug 172977] Re: File Transfers Cannot be Paused

** Tags added: eoan

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

Title:
  File Transfers Cannot be Paused

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  File Transfers cannot be paused.  I have no idea if this is possible
  or even exists on other OS's (other than Ubuntu), but it would be a
  great addition if pausing a file transfer would be possible.

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

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

[Desktop-packages] [Bug 816669] Re: encrypted-home support in new user dialog

** Tags added: eoan

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

Title:
  encrypted-home support in new user dialog

Status in One Hundred Papercuts:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  seb128 asked me to file this bug...

  He noticed that the Gnome3 new user dialog does not support the
  encrypt-home-directory feature that was present in previous versions
  of Gnome.

  To solve this, the new user dialog would have a boolean checkbox
  (defaulted to un-checked), which asks if this new user's home
  directory should be created.  Talk to mpt about the wordsmithing.  If
  checked, then you need to add --encrypt-home to the 'adduser'
  invocation.  Before running adduser, you'd also need to ensure that
  ecryptfs-utils is installed.

  For real security, you would also need to run (as root) ecryptfs-
  setup-swap, which would encrypt the user's swap space.  This is
  necessary, as any files/data that gets swapped out to disk could be
  written in the clear, thereby circumventing the user's requested
  encryption.  Further note that if swap is encrypted, hibernation
  should be disabled (suspend continues to work just fine).

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

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

[Desktop-packages] [Bug 1051288] Re: LightDM assumes there's only ONE system default layout

** Tags added: eoan

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

Title:
  LightDM assumes there's only ONE system default layout

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  In Greece, the default system layout is "us,gr":
  $ grep XKBLAYOUT /etc/default/keyboard 
  XKBLAYOUT="us,gr"

  For new users that don't have .dmrc or accountsservice entries and are 
supposed to get the system defaults, LightDM assumes their keyboard layout is 
"us".
  So they can't switch languages in the greeter and they can't input national 
characters until they login, go to gnome settings and manually set the keyboard 
layout.

  A similar bug was
  https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/919200, but
  that was only solved for the single-layout case.

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

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

[Desktop-packages] [Bug 1849478] Re: (experimental) pipewire support not available

2019-10-23 Thread Sebastien Bacher

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  (experimental) pipewire support not available

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's
  not possible to enable experimental support for pipewire, as the
  toggle doesn't show up in chrome://flags.

  It would be nice to have chromium compiled with pipewire support, to
  enable screensharing in Hangouts and similar apps.

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

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

[Desktop-packages] [Bug 1849480] Re: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error ex

2019-10-23 Thread Sebastien Bacher

thank you for your bug report, the dmesg log suggests the system had
issue due to lack of memory which isn't really a fprintfd issue

** Changed in: fprintd (Ubuntu)
   Status: New => Invalid

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

Title:
  package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade:
  installed libpam-fprintd:amd64 package post-installation script
  subprocess returned error exit status 1

Status in fprintd package in Ubuntu:
  Invalid

Bug description:
  Caused error on upgrade from 19.04 to 19.10

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: libpam-fprintd:amd64 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 23 12:13:19 2019
  ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-07-04 (1205 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: fprintd
  Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: 
installed libpam-fprintd:amd64 package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run headless chromium as user www-data

The system-wide /tmp is not accessible by strictly-confined snaps, so
/tmp/chromium-home won't work either.

In any case this looks like a limitation hard-coded in snapd, which
won't create $SNAP_USER_DATA if $HOME is not in /home. So this is not
specific to the chromium snap. I'll add a snapd task to the bug.

As a workaround (I realize this is less than ideal), could you maybe
create a user with a home directory in /home just for this purpose, and
have have your server process run chromium as this user?

** Summary changed:

- [snap] Cannot run headless chromium as user www-data
+ [snap] Cannot run chromium as user www-data because home directory is /var/www

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

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

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

Title:
  [snap] Cannot run chromium as user www-data because home directory is
  /var/www

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Since the move to snap, and upgrade to 19.10, I can no longer use
  headless-chromium to do automated conversions.

  The script, as currently run by Apache (user www-data) as a back-end
  server process is:

  /usr/bin/timeout 60 chromium-browser --no-sandbox --headless
  --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
  'http://localhost/[...]' 2>&1 2>&1

  This returns error 1, with:

  dconf-CRITICAL **: 19:41:17.958: unable to create directory
  '/var/www/.cache/dconf': Permission denied.  dconf will not work
  properly.

  WARNING: cannot create user data directory: cannot create 
"/var/www/snap/chromium/899": 
  mkdir /var/www/snap: permission denied
  Sorry, home directories outside of /home are not currently supported.
  See https://forum.snapcraft.io/t/11209 for details.

  So... how are we supposed to use scripted Chrome for headless work, when the 
snaps don't support it?
  This is a major blocker for me, as it completely destroys my ability to do 
any development work, because the build-toolchain for selftests relies on the 
ability of chrome to operate headless.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
   modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  Date: Tue Oct 22 19:48:51 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
   tmpfs  tmpfs   32G  927M   31G   3% /dev/shm
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
  InstallationDate: Installed on 2017-02-03 (991 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro

[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www

Snapd team: this is admittedly a corner case, but users with a home
directory outside of /home might want to run snaps (especially CLI tools
as e.g. user www-data). Would it be feasible to add support for this in
snapd?

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

Title:
  [snap] Cannot run chromium as user www-data because home directory is
  /var/www

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Since the move to snap, and upgrade to 19.10, I can no longer use
  headless-chromium to do automated conversions.

  The script, as currently run by Apache (user www-data) as a back-end
  server process is:

  /usr/bin/timeout 60 chromium-browser --no-sandbox --headless
  --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
  'http://localhost/[...]' 2>&1 2>&1

  This returns error 1, with:

  dconf-CRITICAL **: 19:41:17.958: unable to create directory
  '/var/www/.cache/dconf': Permission denied.  dconf will not work
  properly.

  WARNING: cannot create user data directory: cannot create 
"/var/www/snap/chromium/899": 
  mkdir /var/www/snap: permission denied
  Sorry, home directories outside of /home are not currently supported.
  See https://forum.snapcraft.io/t/11209 for details.

  So... how are we supposed to use scripted Chrome for headless work, when the 
snaps don't support it?
  This is a major blocker for me, as it completely destroys my ability to do 
any development work, because the build-toolchain for selftests relies on the 
ability of chrome to operate headless.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
   modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  Date: Tue Oct 22 19:48:51 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
   tmpfs  tmpfs   32G  927M   31G   3% /dev/shm
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
  InstallationDate: Installed on 2017-02-03 (991 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
  Snap.ChromeDriverVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be 
preloaded (failed to map segment from shared object): ignored.
   ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be 
preloaded (failed to map segment from shared object): ignored.
   Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor:

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

A video demonstrating the problem would be useful, indeed, because I
cannot observe it myself.

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849484] [NEW] ultra-wide monitor recognized properly when plugged in only intermittently

2019-10-23 Thread Jonathan Kamens

Public bug reported:

I have an LG ultra-wide (2560x1080) monitor.

Sometimes when I plug it into my laptop, whose screen was working fine
before I plugged it in, both screens go black but nothing else happens.
I can still see the mouse cursor and move it between the two monitors
(sometimes in the correct location configuration I've configured,
sometimes not), but nothing is rendered on the screens.

Sometimes when I plug the monitor in, it comes on, but the resolution is
wrong.

Sometimes it is actually recognized and configured correctly.

Frequently I have to unplug the monitor and plug it back in three times
or more before it is recognized correctly.

I wish it just worked right the first time. :-/

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 08:34:07 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-09-12 (40 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  ultra-wide monitor recognized properly when plugged in only
  intermittently

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

2019-10-23 Thread Alistair Cunningham

Yes, this happens every time on Unity. In fact, it's been happening for
many years. It's only now that I've got round to reporting it. I can
take a video on my phone if you like.

My keyboard shortcut is configured as:

Name: Thunderbird
Command: thunderbird
Key: Super+T

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849480] [NEW] package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error

2019-10-23 Thread Peter Seale

Public bug reported:

Caused error on upgrade from 19.04 to 19.10

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: libpam-fprintd:amd64 0.9.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Wed Oct 23 12:13:19 2019
ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-07-04 (1205 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: fprintd
Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: 
installed libpam-fprintd:amd64 package post-installation script subprocess 
returned error exit status 1
UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)

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


** Tags: amd64 apport-package eoan

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

Title:
  package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade:
  installed libpam-fprintd:amd64 package post-installation script
  subprocess returned error exit status 1

Status in fprintd package in Ubuntu:
  New

Bug description:
  Caused error on upgrade from 19.04 to 19.10

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: libpam-fprintd:amd64 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 23 12:13:19 2019
  ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-07-04 (1205 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: fprintd
  Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: 
installed libpam-fprintd:amd64 package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1849478] [NEW] (experimental) pipewire support not available

2019-10-23 Thread Alberto Donato

Public bug reported:

I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not
possible to enable experimental support for pipewire, as the toggle
doesn't show up in chrome://flags.

It would be nice to have chromium compiled with pipewire support, to
enable screensharing in Hangouts and similar apps.

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

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

Title:
  (experimental) pipewire support not available

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's
  not possible to enable experimental support for pipewire, as the
  toggle doesn't show up in chrome://flags.

  It would be nice to have chromium compiled with pipewire support, to
  enable screensharing in Hangouts and similar apps.

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

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

[Desktop-packages] [Bug 1826544] Re: media button to disable touchpad not working

** Changed in: gnome-settings-daemon
   Status: Unknown => New

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

Title:
  media button to disable touchpad not working

Status in GNOME Settings Daemon:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I have an ASUS UX305CA laptop and after upgrading to 18.04 I am no
  longer able to disable the touchpad by hitting Fn+F9 .  When I hit
  Fn+F9 it shows the graphic indicating that it's disabling the
  touchpad, but the touchpad continues to work.  I tried using a LiveUSB
  copy of 18.04 and it the button works fine, so there seems to be
  something related to upgrading.  I upgrading from 16.04 where it
  worked fine before.

  I'm not sure which package to file this bug against, sorry.

  Here are some details:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  $ lsmod | grep asus
  asus_nb_wmi28672  0
  asus_wmi   28672  1 asus_nb_wmi
  sparse_keymap  16384  1 asus_wmi
  wmi24576  1 asus_wmi
  video  45056  2 asus_wmi,i915
  asus_wireless  16384  0
  $ dconf read /org/gnome/desktop/peripherals/touchpad/send-events
  'enabled'
   
  I also went through a diff between gsettings on the LiveUSB and my current 
install and nothing stood out to me as being related.  I do have 
`org.gnome.desktop.interface gtk-im-module 'ibus'` which differs from LiveUSB 
which is set to 'gtk-im-context-simple', but I don't know if it's related.

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

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

[Desktop-packages] [Bug 1845000] Re: evince assert failure: double free or corruption (!prev)

** Changed in: evince
   Status: New => Fix Released

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

Title:
  evince assert failure: double free or corruption (!prev)

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/evince/issues/1246

  ---

  I'm working with .pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evince 3.32.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: double free or corruption (!prev)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 09:20:00 2019
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-12-02 (294 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: evince
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption 
(!prev)") at malloc.c:5332
   _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, 
have_lock=) at malloc.c:4317
   g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evince assert failure: double free or corruption (!prev)
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1847103] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() fr

** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast() from BG_RECENT_SOURCE() from
  enumerate_children_finished_cb() from g_task_return_now() from
  complete_in_idle_cb()

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  The settings sometime hit a segfault in the background panel

  * Test case
  There are no specific steps, just check that the error tracker stops 
receiving reports

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

  * Regression potential
  The change is in the background panel, check that it still works correctly

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

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

[Desktop-packages] [Bug 1848090] Re: [snap] Unable to install Extensions

Folders under ~/snap/chromium shouldn't be empty. They contain hidden
files and folders though, so maybe they appear empty to you because
you're not list hidden files. Can you share the output of:

ls -la ~/snap/chromium/current/

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

Title:
  [snap] Unable to install Extensions

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  When attempting to install an extension in the Snap version of Chromium I'm 
presented with an error message
  "An error has occurred Could not create download directory"

  Steps to recreate:
  Menu > More tools > Extensions
  Select any extension to install

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

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

[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

@Joachim: there's no separate bug for this yet, but you're right that
this needs attention. Would you mind filing one to track this
separately? If you can attach examples of custom policies that would be
great, too.

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

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

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

[Desktop-packages] [Bug 1848475] Re: TB with Gnome - main window size problem

Thanks for the report. I cannot observe the issues you describe. I'm
running a fully up-to-date 19.10, with the default GNOME desktop, and I
can tile the unmaximized thunderbird window to the leftmost half of the
screen by dragging it to the top-left corner, and I can also resize the
window so that the width is < half the width of the screen. The latter
probably depends on your screen resolution, and on the layout you use in
thunderbird. Can you share details on those? And can you test again the
first problem and confirm you can reliably reproduce it?

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

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

Title:
  TB with Gnome - main window size problem

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  
  New TB w. 19.10 shows unpleasant behaviour: 
  - dragging non-maximized window to top left left does not resize to 
half-screen-width anymore
  - it is not possible to resize width below about 2 third of screen width

  Any hints on this?

  Kind regards, dsto

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  Uname: Linux 4.20.0-042000-generic x86_64
  NonfreeKernelModules: binder_linux ashmem_linux
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct 17 11:58:37 2019
  DefaultProfileIncompatibleExtensions: Thunderbird (default) - 
{972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfilePrefSources: prefs.js
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-05 (618 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MostRecentCrashID: bp-f3e38668-9150-40db-9571-9d7bd0180523
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "68.0" (prefs.js)
   security.sandbox.plugin.tempDirSuffix: 
"c50f1684-95ba-4509-b70d-60a988a5f236" (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=68.0/20190826194726 (Out of date)
   Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.32
  dmi.board.asset.tag: CZC1365RZ5
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1365RZ5
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.32:bd05/10/2018:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system

Can you start firefox in safe mode and report whether the freeze still
happens?

firefox --safe-mode

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

Title:
  Latest Firefox update freezing my system

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The latest updates of firefox renders my machine useless. I'm sending
  it as is hopefully before it freezes completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  BuildID: 20190828152935
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 01:22:17 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-05-01 (506 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/20190828152935 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key

2019-10-23 Thread Jarek Gołębiowski

I've got same problem at 18.04 with Unity and I confirm that #11 helped.

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

Title:
  [SRU] Screen sharing panels abort using an non-existent vino gsettings
  key

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in vino package in Ubuntu:
  Invalid
Status in unity-control-center source package in Bionic:
  In Progress
Status in unity-settings-daemon source package in Bionic:
  In Progress

Bug description:
  *Impact

  This happens because Gnome removed that particular gsettings key. The
  removal did not happen with the ui removal but rather much later than
  that. That is why it doesn't work with the latest version of vino.

  As of now If users try to open the new sharing panel, unity-control-
  center will crash. This sort behavior is not desired on LTS release
  (18.04).

  
  Test Case

  1) Go to unity-control-center
  2) Click sharing (Remote desktop)


  * Regression potential

  None

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

  Specifically, the error report

   "Settings schema 'org.gnome.Vino' does not contain a key named
  'enabled' "

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

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

[Desktop-packages] [Bug 1848402] Re: No indication that thunderbird is starting

I cannot observe the problem you describe. I've tested in a fully up-to-
date 19.10 VM, with both the default GNOME desktop, and in the Unity
session. In both cases, when starting thunderbird with a keyboard
shortcut, the cursor immediately turns into a spinner, and in the case
of Unity the icon in the launcher immediately starts glowing (if
thunderbird is not a favourite app the icon appears at the bottom of the
launcher).

Can you confirm you can reliably reproduce the problem? How is your
keyboard shortcut configured?

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

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

Title:
  No indication that thunderbird is starting

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is started using a keyboard shortcut, a spinner until the
  main Firefox window is loaded. This provides visual indication that
  it's starting. When Thunderbird is started using a keyboard shortcut,
  no spinner is shown until the main Thunderbird window is shown. It's
  not obvious that Thunderbird is loading, and it's unclear whether the
  keyboard shortcut worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   6738 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 20:42:07 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (791 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.30.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.30.0/24 dev wlp58s0 proto kernel scope link src 192.168.30.235 
metric 600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (12 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1849437] Re: [snap] user has no permissions to open downloaded files if download folder is set to /tmp