[Desktop-packages] [Bug 1792932] Re: Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' fail

[Daniel van Vugt]

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu Bionic)
   Importance: Undecided => High

** Summary changed:

- Cosmic Desktop fails to boot in vbox:  Xorg assert failure: Xorg: 
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion 
`!global_keys[type].created' failed.
+ Desktop fails to boot in vbox:  Xorg assert failure: Xorg: 
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion 
`!global_keys[type].created' failed.

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

Title:
  Desktop fails to boot in vbox:  Xorg assert failure: Xorg:
  ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
  `!global_keys[type].created' failed.

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280
  https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80

  ---

  Test Case:
  Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box

  Actual Result
  Black screen or dropped to the login screen if the user skips ubiquity-dm

  Workaround:
  Add nomodeset on the kernel command line or from the boot menu, press F6 then 
select nomodeset

  Possibly a duplicate of bug 1432137

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  CasperVersion: 1.395
  CompositorRunning: None
  Date: Mon Sep 17 12:42:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:

  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd ---  keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92
   __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, 
function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101
   dixRegisterPrivateKey ()
  Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[Sebastien Bacher]

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

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824285] Re: Xorg crashed after login

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1792932
   Desktop fails to boot in vbox:  Xorg assert failure: Xorg: 
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion 
`!global_keys[type].created' failed.

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

Title:
  Xorg crashed after login

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  After login I see crash report.


  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://kg.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://kg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  nvidia-driver-418:
Installed: (none)
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages

  https://errors.ubuntu.com/oops/546067c2-5c1b-11e9-a404-fa163e102db1

  /usr/lib/xorg/Xorg:Xorg: ../../dix/privates.c:385:
  dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed

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

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

[Desktop-packages] [Bug 1824285] Re: Xorg crashed after login

[Gennady]

** Package changed: nvidia-graphics-drivers-319 (Ubuntu) => nvidia-
graphics-drivers-418 (Ubuntu)

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

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

Title:
  Xorg crashed after login

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  After login I see crash report.


  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://kg.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://kg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  nvidia-driver-418:
Installed: (none)
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages

  https://errors.ubuntu.com/oops/546067c2-5c1b-11e9-a404-fa163e102db1

  /usr/lib/xorg/Xorg:Xorg: ../../dix/privates.c:385:
  dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Kai-Heng Feng]

I can confirm that once the section is commented out, libinput is in
use, and multitouch works.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Incomplete

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1822839]

[Libreoffice-commits]

Stephan Bergmann committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/3d27b2fa9c5a03f78e5145377402f8a88e3da1be%5E%21

tdf#124503: Support JRE installations with unknown java.vendor property

It will be available in 6.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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

[Desktop-packages] [Bug 1822839]

[Sbergman]

(In reply to Commit Notification from comment #9)
> Stephan Bergmann committed a patch related to this issue.
> It has been pushed to "master":
> 
> https://git.libreoffice.org/core/+/
> 3d27b2fa9c5a03f78e5145377402f8a88e3da1be%5E%21
> 
> tdf#124503: Support JRE installations with unknown java.vendor property
> 
> It will be available in 6.3.0.

See the mail thread starting at

"On backporting fix for tdf#124503 'LibreOffice doesn't detect JVM
because of unexpected java.vendor property value'" for a discussion
whether and how to backport that.

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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

[Desktop-packages] [Bug 1822839]

[Libreoffice-commits]

Stephan Bergmann committed a patch related to this issue.
It has been pushed to "libreoffice-6-2":

https://git.libreoffice.org/core/+/feca4bf320ae33dd1926f3a1afdc77c3b4f7b2a4%5E%21

tdf#124503: Support JRE installations with unknown java.vendor property

It will be available in 6.2.4.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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

[Desktop-packages] [Bug 1822839]

[Libreoffice-commits]

Stephan Bergmann committed a patch related to this issue.
It has been pushed to "libreoffice-6-1":

https://git.libreoffice.org/core/+/c4aa8b366fb879b0dd37241e70c5842825305620%5E%21

tdf#124503: Support JRE installations with unknown java.vendor property

It will be available in 6.1.6.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when desktop icons are constantly changing

[Daniel van Vugt]

** Summary changed:

- gnome-shell high memory and CPU usage when using zsh and a custom 
XDG_DESKTOP_DIR="$HOME/"
+ gnome-shell high memory and CPU usage when desktop icons are constantly 
changing

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

Title:
  gnome-shell high memory and CPU usage when desktop icons are
  constantly changing

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  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-extension-desktop-icons/+bug/1815550/+subscriptions

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

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

[Norbert Preining]

On Thu, 11 Apr 2019, Kasia Gauza wrote:
>   info missing help docs "info info" and "H" command return error
>   The info command in Ubuntu 18.04 lacks it's own info page. This means

Install
texinfo-doc-nonfree

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

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

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

Status in texinfo package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1824451] [NEW] Snap app permissions do not persist

[lost]

Public bug reported:

Steps to reproduce:

1. open gnome-software
2. search for 'caprine' (a Facebook Messenger app)
3. install it
4. on its page click 'Permissions'
5. click toggles to allow camera, disallow home directory access
6. click 'Close'
7. reopen 'Permissions'

Expected: the new state of permissions is shown
Actual: permissions have their original values

Ubuntu 18.04.2 LTS
gnome-software:
  Installed: 3.28.1-0ubuntu4.18.04.8

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 19:23:53 2019
InstallationDate: Installed on 2019-04-11 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Snap app permissions do not persist

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. open gnome-software
  2. search for 'caprine' (a Facebook Messenger app)
  3. install it
  4. on its page click 'Permissions'
  5. click toggles to allow camera, disallow home directory access
  6. click 'Close'
  7. reopen 'Permissions'

  Expected: the new state of permissions is shown
  Actual: permissions have their original values

  Ubuntu 18.04.2 LTS
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 11 19:23:53 2019
  InstallationDate: Installed on 2019-04-11 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824446] Re: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  it does not get updated with sudo apt-get update and keeps causing
  problems

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 21:24:06 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-10  21:23:53
   Commandline: apt-get -f install
   Requested-By: vinaya (1000)
   Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 
1:5.1.6~rc2-0ubuntu1~xenial6)
  DuplicateSignature:
   package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6
   Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ...
   dpkg: error processing package libreoffice-impress (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-27 (592 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.29ubuntu0.1
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824415] Re: Vertical line screen flickers randomly appears on built-in laptop display only

[Daniel van Vugt]

Sorry, but this looks to me like a broken (or just poorly connected) LCD
panel in the laptop. Not a software problem.

I've had similar problems myself before, and the fix each time was to
either replace the LCD panel, or to just reconnect its wires (sometimes
the problem is just a bad connection).

As a first point of call you should return the laptop to where you
bought it, or contact HP Support about a warranty claim.

** Summary changed:

- Screen flickers randomly appears on built-in laptop display only
+ Vertical line screen flickers randomly appears on built-in laptop display only

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

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

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

Title:
  Vertical line screen flickers randomly appears on built-in laptop
  display only

Status in Ubuntu:
  Invalid

Bug description:
  The issue is similar to:
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912

  the short video with the problem
  https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 11 22:42:06 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  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 2018-12-03 (129 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP EliteBook 840 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.04.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: F51020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1824446] [NEW] package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Vinaya Chandiramani]

Public bug reported:

it does not get updated with sudo apt-get update and keeps causing
problems

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Apr 10 21:24:06 2019
DpkgHistoryLog:
 Start-Date: 2019-04-10  21:23:53
 Commandline: apt-get -f install
 Requested-By: vinaya (1000)
 Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 
1:5.1.6~rc2-0ubuntu1~xenial6)
DuplicateSignature:
 package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6
 Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ...
 dpkg: error processing package libreoffice-impress (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-08-27 (592 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.29ubuntu0.1
SourcePackage: libreoffice
Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  it does not get updated with sudo apt-get update and keeps causing
  problems

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 21:24:06 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-10  21:23:53
   Commandline: apt-get -f install
   Requested-By: vinaya (1000)
   Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 
1:5.1.6~rc2-0ubuntu1~xenial6)
  DuplicateSignature:
   package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6
   Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ...
   dpkg: error processing package libreoffice-impress (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-27 (592 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.29ubuntu0.1
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks)

[Daniel van Vugt]

Although this bug was reported against Fedora, it sounds like Seb has
reproduced it with Ubuntu 19.04.

** Summary changed:

- Onboard crashes the entire desktop
+ Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks)

** Tags added: disco

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1824402] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1820314
   [ASRock FM2A75M-DGS] No sound at all

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

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  with latest alsa daily situation did not get better

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Apr 11 19:59:35 2019
  InstallationDate: Installed on 2016-09-07 (945 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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

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

[Desktop-packages] [Bug 1824405] Re: [HDA-Intel - HD-Audio Generic, playback] Playback problem

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1820314
   [ASRock FM2A75M-DGS] No sound at all

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  with latest alsa daily situation did not get better

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Apr 11 20:05:47 2019
  InstallationDate: Installed on 2016-09-07 (945 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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

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

[Desktop-packages] [Bug 1824297] Re: Wallpapers that are more than twice the screen resolution sometimes appear blurry in 3.32.0

[Daniel van Vugt]

mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Wallpapers that are more than twice the screen resolution sometimes
  appear blurry in 3.32.0

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

Bug description:
  Wallpapers that are more than twice the screen resolution sometimes
  appear blurry in 3.32.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-10.11-generic 5.0.6
  Uname: Linux 5.0.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Thu Apr 11 15:23:31 2019
  InstallationDate: Installed on 2018-12-04 (128 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824438] [NEW] libvte: syntax error in /etc/profile.d/vte-2.91.sh

[ALinuxUser]

Public bug reported:

 etc/profile.d  $  sh -n vte-2.91.sh
 vte-2.91.sh: 61: vte-2.91.sh: Syntax error: word unexpected (expecting ")")

I believe that this problem leads to the creation of a file called
'config-err' in my /tmp folder.

Linux Mint 19.1 x64 
Cinnamon
Kernel: 5.0.7-050007-generic

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libvte: syntax error in /etc/profile.d/vte-2.91.sh

Status in vte2.91 package in Ubuntu:
  New

Bug description:
   etc/profile.d  $  sh -n vte-2.91.sh
   vte-2.91.sh: 61: vte-2.91.sh: Syntax error: word unexpected (expecting 
")")

  I believe that this problem leads to the creation of a file called
  'config-err' in my /tmp folder.

  Linux Mint 19.1 x64 
  Cinnamon
  Kernel: 5.0.7-050007-generic

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

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

[Desktop-packages] [Bug 1768078] Re: gnome-control-center network panel missing DNS search

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Confirmed => New

** Changed in: gnome-control-center
   Importance: High => Unknown

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

Title:
  gnome-control-center network panel missing DNS search

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

Bug description:
  The Unity network panel offered a means to set DNS search data on
  fixed IP connections maintained via NetworkManager in
  /etc/NetworkManager/system-coonections/ dns-search variable.

  This feature is absent in 18.04 Gnome's gnome-control-center network
  panel.

  Lack of the feature means the dns-search variable is unset which also
  causes /etc/resolv.conf to leave the search to be unset. This is
  unacceptable in a assigned IP address Enterprise environment.

  One workaround is to manually edit the NetworkManager system-
  connections file after its creation to set the variable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Apr 30 12:36:30 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1404358]

[Rb-henschel]

*** Bug 45240 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/1404358

Title:
  [Upstream] EDITING: multiple graphic objects cannot be selected with
   key or 'Select' tool with mouse

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This bug was reported by Gleb to upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=79990).

  Problem description:
  When selecting multiple graphic objects with  key or 'Select' tool 
with mouse 
  selection dissapears.

  Steps to reproduce:
  1. Draw some graphic objects (squares, lines, etc)
  2. Press 'Enter', 'Enter', 'Enter' ...
  3. Insert an image from file under graphic objects
  4. Try to select graphic object obe by one with  key pressed or 
'Select' tool with mouse (selection rectangle should contain all objects - 
images and graphic objects).

  Current behavior: when selecting drawn objects with 'shift' pressed an
  image selected unexpectedly.

  Expected behavior: adding 2-nd, 3-rd objects to current selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.7-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Fri Dec 19 21:48:16 2014
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  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/1404358/+subscriptions

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

[Desktop-packages] [Bug 1404358]

[Rb-henschel]

@Norbert X: This bug is really fixed. This bug is about selecting _two
shapes_.

Your problem is to select an image together with a shape. The underlying
reason is the same as for selecting two images. And that is bug 34438.

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

Title:
  [Upstream] EDITING: multiple graphic objects cannot be selected with
   key or 'Select' tool with mouse

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This bug was reported by Gleb to upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=79990).

  Problem description:
  When selecting multiple graphic objects with  key or 'Select' tool 
with mouse 
  selection dissapears.

  Steps to reproduce:
  1. Draw some graphic objects (squares, lines, etc)
  2. Press 'Enter', 'Enter', 'Enter' ...
  3. Insert an image from file under graphic objects
  4. Try to select graphic object obe by one with  key pressed or 
'Select' tool with mouse (selection rectangle should contain all objects - 
images and graphic objects).

  Current behavior: when selecting drawn objects with 'shift' pressed an
  image selected unexpectedly.

  Expected behavior: adding 2-nd, 3-rd objects to current selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.7-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Fri Dec 19 21:48:16 2014
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  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/1404358/+subscriptions

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

[Desktop-packages] [Bug 1404358]

[tml]

Did you read comment #57? Which part of "Please don't reopen bugs that
have been closed for a long time" don't you understand?

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

Title:
  [Upstream] EDITING: multiple graphic objects cannot be selected with
   key or 'Select' tool with mouse

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This bug was reported by Gleb to upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=79990).

  Problem description:
  When selecting multiple graphic objects with  key or 'Select' tool 
with mouse 
  selection dissapears.

  Steps to reproduce:
  1. Draw some graphic objects (squares, lines, etc)
  2. Press 'Enter', 'Enter', 'Enter' ...
  3. Insert an image from file under graphic objects
  4. Try to select graphic object obe by one with  key pressed or 
'Select' tool with mouse (selection rectangle should contain all objects - 
images and graphic objects).

  Current behavior: when selecting drawn objects with 'shift' pressed an
  image selected unexpectedly.

  Expected behavior: adding 2-nd, 3-rd objects to current selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.7-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Fri Dec 19 21:48:16 2014
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  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/1404358/+subscriptions

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

[Desktop-packages] [Bug 1404358]

[Norbert]

Bug is not fixed. 
Still unable to select both image and drawing object with +Click.


Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial1
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group

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

Title:
  [Upstream] EDITING: multiple graphic objects cannot be selected with
   key or 'Select' tool with mouse

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This bug was reported by Gleb to upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=79990).

  Problem description:
  When selecting multiple graphic objects with  key or 'Select' tool 
with mouse 
  selection dissapears.

  Steps to reproduce:
  1. Draw some graphic objects (squares, lines, etc)
  2. Press 'Enter', 'Enter', 'Enter' ...
  3. Insert an image from file under graphic objects
  4. Try to select graphic object obe by one with  key pressed or 
'Select' tool with mouse (selection rectangle should contain all objects - 
images and graphic objects).

  Current behavior: when selecting drawn objects with 'shift' pressed an
  image selected unexpectedly.

  Expected behavior: adding 2-nd, 3-rd objects to current selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.7-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Fri Dec 19 21:48:16 2014
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  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/1404358/+subscriptions

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

[Desktop-packages] [Bug 1768078] Re: gnome-control-center network panel missing DNS search

[Will Dennis]

Opened issue #471 on new Gnome GitLab "gnome-control-center" repo (old Bugzilla 
is deprecated now?)
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/471

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

Title:
  gnome-control-center network panel missing DNS search

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  The Unity network panel offered a means to set DNS search data on
  fixed IP connections maintained via NetworkManager in
  /etc/NetworkManager/system-coonections/ dns-search variable.

  This feature is absent in 18.04 Gnome's gnome-control-center network
  panel.

  Lack of the feature means the dns-search variable is unset which also
  causes /etc/resolv.conf to leave the search to be unset. This is
  unacceptable in a assigned IP address Enterprise environment.

  One workaround is to manually edit the NetworkManager system-
  connections file after its creation to set the variable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Apr 30 12:36:30 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824425] [NEW] network-manager dies in package postinst on cosmic->disco upgrade

[Steve Langasek]

Public bug reported:

I just did a cosmic->disco upgrade and as soon as the network-manager
package was configured, my network dropped.

Setting up network-manager (1.12.4-1ubuntu1) ...

As soon as this package was configured, the NetworkManager service died,
the NM applet disappeared from my desktop, and my network dropped.

The NetworkManager service eventually succeeded in restarting, but it
took 12 minutes.

journalctl output looks like:

Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager...
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.2262] caught 
SIGTERM, shutting down normally.
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.2277] device 
(wlan2): state change: activated -> deactivating (reason 'unmanaged', 
sys-iface-state: 'managed')
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.2392] device 
(wlan2): state change: deactivating -> unmanaged (reason 'removed', 
sys-iface-state: 'managed')
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.3055] dhcp4 
(wlan2): canceled DHCP transaction, DHCP client pid 2596
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.3056] dhcp4 
(wlan2): state changed bound -> done
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.4210] device 
(virbr0-nic): released from master device virbr0
Apr 11 13:30:43 virgil NetworkManager[2684]:   [1555014643.4430] exiting 
(success)
Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded.
Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager.
Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager...
Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation 
timed out. Terminating.
Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, 
code=killed, status=15/TERM
Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 
'timeout'.
Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager.
Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 1.
Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager.
Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager...
Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation 
timed out. Terminating.
Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, 
code=killed, status=15/TERM
Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 
'timeout'.
Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager.
Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 2.
Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager.
Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager...
Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation 
timed out. Terminating.
Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, 
code=killed, status=15/TERM
Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 
'timeout'.
Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager.
Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 3.
Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager.
Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager...
Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation 
timed out. Terminating.
Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, 
code=killed, status=15/TERM
Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 
'timeout'.
Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager.
Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 4.
Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager.
Apr 11 13:38:29 virgil systemd[1]: Starting Network Manager...
Apr 11 13:40:00 virgil systemd[1]: NetworkManager.service: Start operation 
timed out. Terminating.
Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Main process exited, 
code=killed, status=15/TERM
Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Failed with result 
'timeout'.
Apr 11 13:40:01 virgil systemd[1]: Failed to start Network Manager.
Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Scheduled 

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Question for everybody, I noticed that linux-5.0.0-10.11 which is
currently in proposed for cosmic has an explicit fix for this bug
(mentioned in the changelog).  Will this kernel make it into the
official 19.04 release - or will the release use linux-5.0.0-8.9?

If the official release doesn't use linux-5.0.0-10.11 (or something
greater) then many Dell laptop users will be unable to install using the
release ISO, which would be very unfortunate.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
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/ubuntu/+source/linux/+bug/1821820/+subscriptions

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

[Desktop-packages] [Bug 1823778] Re: Unable to set Serbian as Language

[Gunnar Hjalmarsson]

@momcilo: Great! It's not in the bionic archive yet, though. That will
probably take a few weeks, since I'd like to also fix the problem with
setting Serbian-Latin as language.

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

Title:
  Unable to set Serbian as Language

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

Bug description:
  Affected: 18.04.2 (did not try earlier versions of 18.04 series)
  Not affected: 16.04 - any version (UI was different)

  Preparation steps:
  1. open gnome control center
  2. open Region & Language
  3. open Manage installed languages
  4. open Install/Remove languages
  5. select Serbian, click Apply
  6. provide credentials for sudo installation
  7. wait for installation to complete
  8. click Close

  What is wrong:
  1. open gnome control center
  2. open Region & Language
  3. click Language selection
  4. Serbian is not visible

  Notes:
  - Serbian is visible for the Formats selection
  - Any other language I thought of: (Macedonian, Croatian, Bosnian, 
Russion...) simple work.

  
  Here is some dpkg output on installaed packages matching sr (Serbian) or hr 
(Croatian).

  ii  firefox-locale-sr  66.0.2+build1-0ubuntu0.18.04.1 
  amd64Serbian language pack for Firefox
  ii  gnome-getting-started-docs-sr  3.28.2-0ubuntu0.1  
  all  Help a new user get started in GNOME (Serbian)
  ii  gnome-user-docs-sr 3.28.2+git20180715-0ubuntu0.1  
  all  GNOME user's guide (Serbian)
  ii  hunspell-sr1:6.0.3-3  
  all  Serbian dictionary for hunspell
  ii  hyphen-sr  1:6.0.3-3  
  all  Serbian hyphenation patterns
  ii  language-pack-gnome-sr 1:18.04+20180712   
  all  GNOME translation updates for language Serbian
  ii  language-pack-gnome-sr-base1:18.04+20180712   
  all  GNOME translations for language Serbian
  ii  language-pack-sr   1:18.04+20180712   
  all  translation updates for language Serbian
  ii  language-pack-sr-base  1:18.04+20180712   
  all  translations for language Serbian
  ii  libreoffice-l10n-sr1:6.0.7-0ubuntu0.18.04.2   
  all  office productivity suite -- Serbian language package
  ii  thunderbird-locale-sr  
1:60.6.1+build2-0ubuntu0.18.04.1 amd64Serbian language pack 
for Thunderbird
  nebojsa@momcilo-desktop:~$ dpkg -l | grep -e "-hr"
  rc  language-pack-gnome-hr-base1:18.04+20180712   
  all  GNOME translations for language Croatian
  rc  language-pack-hr-base  1:18.04+20180712   
  all  translations for language Croatian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 20:10:54 2019
  InstallationDate: Installed on 2019-04-06 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1823778/+subscriptions

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

[Desktop-packages] [Bug 1824415] [NEW] Screen flickers randomly appears on built-in laptop display only

[Oleksandr Varchenko]

Public bug reported:

The issue is similar to:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912

the short video with the problem
https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 22:42:06 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
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 2018-12-03 (129 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: HP HP EliteBook 840 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2018
dmi.bios.vendor: HP
dmi.bios.version: Q78 Ver. 01.04.00
dmi.board.name: 83B2
dmi.board.vendor: HP
dmi.board.version: KBC Version 04.53.00
dmi.chassis.asset.tag: F51020
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 840 G5
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic corruption 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/1824415

Title:
  Screen flickers randomly appears on built-in laptop display only

Status in xorg package in Ubuntu:
  New

Bug description:
  The issue is similar to:
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912

  the short video with the problem
  https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 11 22:42:06 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  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 2018-12-03 (129 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP EliteBook 840 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.04.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: F51020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

[Desktop-packages] [Bug 1824409] [NEW] Client side decoration in Firefox with Pop theme has a slight imperfection

[Franck]

Public bug reported:

With Firefox new client-side decoration, when using Pop theme, there is a small 
white line upon the first tab that looks unclean.
Also, don't use the whole title bar height, which might look cleaner, or not :-)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 66.0.3+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  franck 3795 F pulseaudio
 /dev/snd/pcmC1D0c:   franck 3795 F...m pulseaudio
 /dev/snd/controlC0:  franck 3795 F pulseaudio
BuildID: 20190410124846
Channel: Unavailable
CurrentDesktop: GNOME
Date: Thu Apr 11 20:44:57 2019
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 
 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 
 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 
 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 
 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA9WW (2.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2353CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2353CTO
dmi.product.sku: LENOVO_MT_2353
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco wayland-session

** Attachment added: "Capture d’écran du 2019-04-11 20-51-50.png"
   
https://bugs.launchpad.net/bugs/1824409/+attachment/5254999/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202019-04-11%2020-51-50.png

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

Title:
  Client side decoration in Firefox with Pop theme has a slight
  imperfection

Status in firefox package in Ubuntu:
  New

Bug description:
  With Firefox new client-side decoration, when using Pop theme, there is a 
small white line upon the first tab that looks unclean.
  Also, don't use the whole title bar height, which might look cleaner, or not 
:-)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 3795 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 3795 F...m pulseaudio
   /dev/snd/controlC0:  franck 3795 F pulseaudio
  BuildID: 20190410124846
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Apr 11 20:44:57 2019
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 
   default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 
   10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 
   10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 
   10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - 

[Desktop-packages] [Bug 1824408] [NEW] With client side decoration, Firefox preempts any middle click on title bar

[Franck]

Public bug reported:

Since recent versions, Firefox uses client-side decoration to draw its title 
bar.
I have a mouse shortcut defined in gnome-tweaks that allows me to minimize 
windows on middle mouse button click on title bar 
This works well, except on new Firefox, where it will open a new tab...

I didn't find the way to disable this behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 66.0.3+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  franck 3795 F pulseaudio
 /dev/snd/pcmC1D0c:   franck 3795 F...m pulseaudio
 /dev/snd/controlC0:  franck 3795 F pulseaudio
 /dev/snd/pcmC0D7p:   franck 3795 F...m pulseaudio
BuildID: 20190410124846
Channel: Unavailable
CurrentDesktop: GNOME
Date: Thu Apr 11 20:28:43 2019
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 
 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 
 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 
 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 
 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA9WW (2.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2353CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2353CTO
dmi.product.sku: LENOVO_MT_2353
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  With client side decoration, Firefox preempts any middle click on
  title bar

Status in firefox package in Ubuntu:
  New

Bug description:
  Since recent versions, Firefox uses client-side decoration to draw its title 
bar.
  I have a mouse shortcut defined in gnome-tweaks that allows me to minimize 
windows on middle mouse button click on title bar 
  This works well, except on new Firefox, where it will open a new tab...

  I didn't find the way to disable this behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 3795 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 3795 F...m pulseaudio
   /dev/snd/controlC0:  franck 3795 F pulseaudio
   /dev/snd/pcmC0D7p:   franck 3795 F...m pulseaudio
  BuildID: 20190410124846
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Apr 11 20:28:43 2019
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 
   default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 
   10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 
   10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 
   10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  

[Desktop-packages] [Bug 1823778] Re: Unable to set Serbian as Language

[momcilo78]

@gunnarhj: works!
That was quick.

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

Title:
  Unable to set Serbian as Language

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

Bug description:
  Affected: 18.04.2 (did not try earlier versions of 18.04 series)
  Not affected: 16.04 - any version (UI was different)

  Preparation steps:
  1. open gnome control center
  2. open Region & Language
  3. open Manage installed languages
  4. open Install/Remove languages
  5. select Serbian, click Apply
  6. provide credentials for sudo installation
  7. wait for installation to complete
  8. click Close

  What is wrong:
  1. open gnome control center
  2. open Region & Language
  3. click Language selection
  4. Serbian is not visible

  Notes:
  - Serbian is visible for the Formats selection
  - Any other language I thought of: (Macedonian, Croatian, Bosnian, 
Russion...) simple work.

  
  Here is some dpkg output on installaed packages matching sr (Serbian) or hr 
(Croatian).

  ii  firefox-locale-sr  66.0.2+build1-0ubuntu0.18.04.1 
  amd64Serbian language pack for Firefox
  ii  gnome-getting-started-docs-sr  3.28.2-0ubuntu0.1  
  all  Help a new user get started in GNOME (Serbian)
  ii  gnome-user-docs-sr 3.28.2+git20180715-0ubuntu0.1  
  all  GNOME user's guide (Serbian)
  ii  hunspell-sr1:6.0.3-3  
  all  Serbian dictionary for hunspell
  ii  hyphen-sr  1:6.0.3-3  
  all  Serbian hyphenation patterns
  ii  language-pack-gnome-sr 1:18.04+20180712   
  all  GNOME translation updates for language Serbian
  ii  language-pack-gnome-sr-base1:18.04+20180712   
  all  GNOME translations for language Serbian
  ii  language-pack-sr   1:18.04+20180712   
  all  translation updates for language Serbian
  ii  language-pack-sr-base  1:18.04+20180712   
  all  translations for language Serbian
  ii  libreoffice-l10n-sr1:6.0.7-0ubuntu0.18.04.2   
  all  office productivity suite -- Serbian language package
  ii  thunderbird-locale-sr  
1:60.6.1+build2-0ubuntu0.18.04.1 amd64Serbian language pack 
for Thunderbird
  nebojsa@momcilo-desktop:~$ dpkg -l | grep -e "-hr"
  rc  language-pack-gnome-hr-base1:18.04+20180712   
  all  GNOME translations for language Croatian
  rc  language-pack-hr-base  1:18.04+20180712   
  all  translations for language Croatian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 20:10:54 2019
  InstallationDate: Installed on 2019-04-06 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1823778/+subscriptions

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

[Desktop-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Calvin Cheng]

Yes I also ran into this same problem.

$ traceroute6 -n 2001:4860:4860::
traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2003:XX, 30 
hops max, 24 byte packets
sendto: Invalid argument
 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
 *sendto: Invalid argument
traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
 *sendto: Invalid argument

$ traceroute6 -V
traceroute6 utility, iputils-s20161105

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

$ dpkg-query -s iputils-tracepath
Package: iputils-tracepath
Status: install ok installed
Priority: optional
Section: net

Installed-Size: 76
Maintainer: Ubuntu Developers 
Architecture: amd64
Source: iputils
Version: 3:20161105-1ubuntu2
Depends: libc6 (>= 2.15), libcap2 (>= 1:2.10), libidn11 (>= 1.13)
Suggests: traceroute
Description: Tools to trace the network path to a remote host
 The tracepath utility is similar to the traceroute utility, but also
 attempts to discover the MTU of the path. Supports IPv4 and IPv6.
Original-Maintainer: Noah Meyerhans 

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Desktop-packages] [Bug 1824405] [NEW] [HDA-Intel - HD-Audio Generic, playback] Playback problem

[nicola]

Public bug reported:

with latest alsa daily situation did not get better

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hp 1692 F pulseaudio
 /dev/snd/controlC0:  hp 1692 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Apr 11 20:05:47 2019
InstallationDate: Installed on 2016-09-07 (945 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.70
dmi.board.name: FM2A75M-DGS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  with latest alsa daily situation did not get better

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Apr 11 20:05:47 2019
  InstallationDate: Installed on 2016-09-07 (945 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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

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

[Desktop-packages] [Bug 1803127] Re: remmina not able to redirect smart card reader

[Allanon]

Also affecting me on KDE Neon with Remmina 1.2

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

Title:
  remmina not able to redirect smart card reader

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 19
  1.2.0-rcgit-29 (git rcgit-29)
  Cinamon
  Windows 7 Pro
  RDP
  remmina:
Installed: 1.2.0-rcgit.29+dfsg-1ubuntu1
Candidate: 1.2.0-rcgit.29+dfsg-1ubuntu1
Version table:
   *** 1.2.0-rcgit.29+dfsg-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I expect to see working solution for this problem. The same problem is
  and with Ubuntu 18.04 LTS.

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

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

[Desktop-packages] [Bug 1824402] [NEW] [HDA-Intel - HD-Audio Generic, recording] No sound at all

[nicola]

Public bug reported:

with latest alsa daily situation did not get better

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hp 1692 F pulseaudio
 /dev/snd/controlC0:  hp 1692 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Apr 11 19:59:35 2019
InstallationDate: Installed on 2016-09-07 (945 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hp 1692 F pulseaudio
 /dev/snd/controlC0:  hp 1692 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.70
dmi.board.name: FM2A75M-DGS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  with latest alsa daily situation did not get better

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Apr 11 19:59:35 2019
  InstallationDate: Installed on 2016-09-07 (945 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1692 F pulseaudio
   /dev/snd/controlC0:  hp 1692 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212

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

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  Onboard crashes the entire desktop

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Nathaniel Beaver]

Update: poppler issue here:

https://gitlab.freedesktop.org/poppler/poppler/issues/753

** Bug watch added: gitlab.freedesktop.org/poppler/poppler/issues #753
   https://gitlab.freedesktop.org/poppler/poppler/issues/753

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration

[Derk Willem te Bokkel]

okay a previous "fresh install that was crashing plymouth
screen/lightdm/xorg was fixed by copying a known working set of netplan
conf files into  /etc/netplan ..

the 01-netcfg.yaml from the "network install" uses networkd as the
renderer .. with a working network device config.. plus the  01-network-
manager-all.yaml file as well

proof enough?  of some weird interactions between services

now the minimal 01-network-manager-all.yaml on the new installs seems to be 
lacking something ..
although the documentation says it should work .. which it does if your 
graphics start properly .. Wayland (ubuntu install) or amd/ati cards probably 
nvidia too I have not tested

 but if using the current default netplan  and i915 as module NOT listed
in /etc/modules  .. it does not work it crashes and locks up and only a
powerswitch shutdown works .. no reset button on laptop .. no console
access is available either .. so it has taken a bit of time to determine
all this ..

Anybody know how to fix the netplan config in a "generic way" to cure
this issue?



 the only problem is no control over switching  networks .. NetworkManager does 
not seem to have control over the interface started by networkd ..

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
  netplan mis-configuration maybe underlying cause.

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Aaron Dudek]

I have hit this issue too. via iputils-tracepath under ubuntu 18.04. There are 
actually 2 issues with this, one with ipv6 address and the other to an ipv6 
hostname.
https://github.com/iputils/iputils/issues/68
https://github.com/iputils/iputils/issues/81

I also do not see how this is fixed in the version when the issue wasn't fixed 
by the iputils maintainer until after 10 Nov 2016.  
This is a new issue that is not fixed in the released version of 18.04 
iputils-tracepath or any iptuils utility based on the s20161105 build of 
iptuils.


** Bug watch added: github.com/iputils/iputils/issues #81
   https://github.com/iputils/iputils/issues/81

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

[oga...@gmail.com]

Also confirming that after setting up checkbox in Software Updates ->
Developer Options -> Pre released updates (bionic-proposed) and
upgrading packages, the problem fixed.

Thank you!

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

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

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  [ Impact ]

  Keyboard Layout indicator don't display current layout (empty selected
  drop down box)

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  [ Workarounds ]

  - Switch with keyboard (Super+space) or mouse. BUT if you then logout
  on the login screen *when you press the first character* of the
  password the shown selected keyboard layout resets.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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

[Desktop-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Aaron Dudek]

and no, using the traceroute package does not fix the issue
dudek@test-box:~$ sudo apt-get install traceroute
[sudo] password for adudek:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  traceroute
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 45.4 kB of archives.
After this operation, 152 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 traceroute 
amd64 1:2.1.0-2 [45.4 kB]
Fetched 45.4 kB in 3s (14.3 kB/s)
Selecting previously unselected package traceroute.
(Reading database ... 103312 files and directories currently installed.)
Preparing to unpack .../traceroute_1%3a2.1.0-2_amd64.deb ...
Unpacking traceroute (1:2.1.0-2) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up traceroute (1:2.1.0-2) ...
update-alternatives: using /usr/bin/traceroute.db to provide 
/usr/bin/traceroute (traceroute) in auto mode
update-alternatives: using /usr/bin/lft.db to provide /usr/bin/lft (lft) in 
auto mode
update-alternatives: using /usr/bin/traceproto.db to provide 
/usr/bin/traceproto (traceproto) in auto mode
update-alternatives: using /usr/sbin/tcptraceroute.db to provide 
/usr/sbin/tcptraceroute (tcptraceroute) in auto mode
adudek@test-box:~$ traceroute6 -V
traceroute6 utility, iputils-s20161105
adudek@test-box:~$ traceroute -V
Modern traceroute for Linux, version 2.1.0
Copyright (c) 2016  Dmitry Butskoy,   License: GPL v2 or any later
adudek@test-box:~$ traceroute6 2001:4860:4860::
traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2003:8:8:4:20c:29ff:fe59:583c, 30 hops max, 24 byte packets
sendto: Invalid argument
 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1

adudek@test-box:~$

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Desktop-packages] [Bug 1796251] Re: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_re

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell -
3.32.0+git20190410-1ubuntu1

---
gnome-shell (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merging with debian git snapshot (LP: #1820775, LP: #1818790),
remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Dropped the merged part, kept the fix for cursor scaling.
  * d/p/optional-hot-corner.patch,
d/p/sessionMode-add-support-for-debugFlags-parameter.patch,
d/p/ubuntu/lock_on_suspend.patch,
d/p/ubuntu/resolve_alternate_theme_path.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:15:39 -0500

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV when taking a screenshot, in
  __strlen_avx2() from real_save_png() from
  gdk_pixbuf__png_image_save_to_callback() from
  gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv()

Status in GNOME Shell:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Released

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

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

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

[Desktop-packages] [Bug 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0+git20190410-1ubuntu1

---
mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  (In Xorg sessions only) apps launched from gnome shell do not get
  input focus

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Fix Released

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0+git20190410-1ubuntu1

---
mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Shell task bar menus not updated with external monitor primary
  and laptop screen fractionally scaled

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Invalid
Status in mutter source package in Cosmic:
  Triaged
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Fix Released

Bug description:
  My set-up: a laptop with an internal screen open and scaled to 150%
  and an external monitor at 100% set to act as the primary screen.
  When I open the menus in the GNOME Shell task bar (calendar or
  settings/log-out/etc menu) they are displayed but not updated when I
  mouse over them or click on them.  I can still use them by blind
  clicking.  When I set both screens to 100% I did not see this.  I am
  using the Wayland session.  With the internal screen at 125% I saw
  this too, but after changing the relative position of the two it went
  away.  I think this was a fluke, but I was unable to do the same after
  going back to 150%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 11:23:54 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-06-12 (154 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago)

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

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

[Desktop-packages] [Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0+git20190410-1ubuntu1

---
mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  In a wayland session opening text file in gedit causes busy cursor

Status in GNOME Shell:
  Fix Released
Status in GTK+:
  Fix Released
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Test case:
  Fresh 19.04 daily current image, updated
  Log in to a wayland session, open a single tesxt file in gedit
  Move cursor out of gedit window or close gedit

  What happens: 
  get busy cursor forever. Only way to stop is to either logout or open 2 files 
(tabs) in gedit

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libwayland-cursor0 1.16.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 16:55:31 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312)
  MachineType: LENOVO 20217
  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-7-generic 
root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.sku: LENOVO_BI_IDEAPAD
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1818790] Re: [regression] Desktop zoom is missing the mouse pointer

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell -
3.32.0+git20190410-1ubuntu1

---
gnome-shell (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merging with debian git snapshot (LP: #1820775, LP: #1818790),
remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Dropped the merged part, kept the fix for cursor scaling.
  * d/p/optional-hot-corner.patch,
d/p/sessionMode-add-support-for-debugFlags-parameter.patch,
d/p/ubuntu/lock_on_suspend.patch,
d/p/ubuntu/resolve_alternate_theme_path.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:15:39 -0500

** Changed in: gnome-shell (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Desktop zoom is missing the mouse pointer

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020
  Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454

  ---

  Desktop zoom is missing the mouse pointer.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Wed Mar  6 15:12:04 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-04 (92 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 
(20181203)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To 

[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen) in Xorg sessions

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0+git20190410-1ubuntu1

---
mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Touch input is offset with two screens (even appearing on the wrong
  screen) in Xorg sessions

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

Bug description:
  Using touch input with one screen seems fine.
  However, when connecting a second screen the touch event happens at the wrong 
coordinates.

  Steps to reproduce
  1. Starting with a single screen touch and hold on the background and drag.  
The rubber band selector shows up with the moving corner at your finger.
  2. Connect a second screen
  3. Do the same touch and drag as in step 1 and notice that the moving corner 
is offset to the right and slightly below where the touch is happening.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0+git20190410-1ubuntu1

---
mutter (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merge with debian git snapshot (LP: #1820542), remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:12:29 -0500

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT. Assertion failure in
  meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode ==
  META_POWER_SAVE_ON"

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/509
  https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971

  ---

  In the last few weeks, gnome-shell has been crashing almost every time
  I open my laptop to wake it from suspend.  The rapid pace of package
  updates has stopped Apport from letting me report it until now, but
  the problem persists.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 15 11:22:20 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (1120 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark
  separator:

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

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

[Desktop-packages] [Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items (if extensions are installed that add menu buttons)

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell -
3.32.0+git20190410-1ubuntu1

---
gnome-shell (3.32.0+git20190410-1ubuntu1) disco; urgency=medium

  * Merging with debian git snapshot (LP: #1820775, LP: #1818790),
remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Dropped the merged part, kept the fix for cursor scaling.
  * d/p/optional-hot-corner.patch,
d/p/sessionMode-add-support-for-debugFlags-parameter.patch,
d/p/ubuntu/lock_on_suspend.patch,
d/p/ubuntu/resolve_alternate_theme_path.patch:
- Refreshed.

 -- Marco Trevisan (Treviño)   Wed, 10 Apr 2019
20:15:39 -0500

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

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

Title:
  gnome-shell's user menu/item is not aligned like other menu items (if
  extensions are installed that add menu buttons)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I just noticed that the user menu of gnome-shell is not aligned like
  other menu items.  When clicking it, it shows an extended box too.  I
  expect it to be like other menu items.

  Note that I'm using Default as my gnome-shell user css, but other
  css'es also show this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 19 08:33:12 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-02-16 (31 days ago)

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

-- 
Mailing 

[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)

[Andrea Azzarone]

Fix proposed upstream: http://lists.gnu.org/archive/html/guile-
devel/2019-04/msg00015.html

** Changed in: guile-2.2 (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  guile-2.2 ftbfs in disco (arm64 only)

Status in guile-2.2 package in Ubuntu:
  In Progress
Status in guile-2.2 source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco-
  arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz

  Totals for this test run:
  passes: 41515
  failures:   1
  unexpected passes:  0
  expected failures:  10
  unresolved test cases:  577
  untested test cases:1
  unsupported test cases: 1
  errors: 0

  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  ;;; SSAX warning: Skipping PI: xml

  ;;; SSAX warning: Skipping PI: PI

  ;;; SSAX warning: Skipping PI: PI1

  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: (
   Warning:  Internal DTD subset is not currently handled )
  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: Skipping PI: pi

  ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped
  WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core 
binding `filter'
  FAIL: check-guile
  ==
  1 of 1 test failed
  Please report to bug-gu...@gnu.org
  ==
  make[4]: *** [Makefile:1956: check-TESTS] Error 1
  make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[3]: *** [Makefile:2241: check-am] Error 2
  make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[2]: *** [Makefile:1856: check-recursive] Error 1
  make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[1]: *** [Makefile:2243: check] Error 2
  make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2

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

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

[Desktop-packages] [Bug 1823303] Re: error in 10_ubuntu-dock.gschema.override

[Treviño]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  error in 10_ubuntu-dock.gschema.override

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Hi,

  here is the problem:

  # apt upgrade
  [...]
  Processing triggers for libglib2.0-0:amd64 (2.60.0-1) ...
  override for key “transparency-mode” in schema 
“org.gnome.shell.extensions.dash-to-dock” in override file 
“/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the 
list of valid choices; ignoring override for this key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu5
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  5 10:22:46 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824283] Re: Nautilus progress bar is easily lead users to cancel the running task

[Sean Wang]

Done.
Thanks for the suggestion.
https://gitlab.gnome.org/GNOME/nautilus/issues/985

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #985
   https://gitlab.gnome.org/GNOME/nautilus/issues/985

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

Title:
  Nautilus  progress bar is easily lead users to cancel the running task

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  People often check the progress of tasks when they copying or deleting
  some large files using the nautilus progress bar. Usually, they would
  click a button to close the popped progress bar. The nautilus progress
  bar is very easy to lead users to click the cancel task button since
  there is only one button on the progress bar which is very like a
  closing window button. I suggest it add a confirm message box or
  change the cancel task button to other icons.

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

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

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Nathaniel Beaver]

Done: https://gitlab.gnome.org/GNOME/evince/issues/1127

Should I also report the bug to the xpdf and Okular developers, since it
is not isolated to Evince?

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1127
   https://gitlab.gnome.org/GNOME/evince/issues/1127

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in evince package in Ubuntu:
  New

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824330] Re: crashed when tried to do gedit textname

[Balakrishna]

Actually, i tried to play a video on my machine using vlc ( i.e; after
changing the Display Manager to XFCE). This is the actual problem. Can
you look into it once:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1824345

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

Title:
  crashed when tried to do gedit textname

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  (gedit:18666): dbind-WARNING **: 18:11:43.231: Couldn't connect to
  accessibility bus: Failed to connect to socket /tmp/dbus-EV6hC9BiLn:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: smbclient (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 11 18:08:19 2019
  InstallationDate: Installed on 2018-08-17 (237 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: samba
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

[Dimitri John Ledkov]

** Changed in: ubiquity (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Fix Released
Status in ubuntu-drivers-common source package in Disco:
  Fix Released

Bug description:
  [Rationale]
  On Ubuntu Desktop, we want to install automatically at installation time 
open-vm-tools-desktop and its dependencies to provide an improved user 
experience on first boot after installation of the guest. This method also 
provides an easy way to install the drivers after installation if they have not 
been installed at installation time.

  It is achieved adding an XB-Modaliases field to the control file for
  the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the
  packages to install when running in a VMware guest and adding open-vm-
  tools to the list of whitelisted packages in ubuntu-drivers

  [Impact]
  The change adds an additional field to the control file used by 
ubuntu-drivers to detect the drivers to install automatically. In the worst 
case scenario either the field is not added or the detection by ubuntu-drivers 
fails. In both cases the package o-v-t-desktop is not installed and can still 
be installed manually.

  Note: open-vm-tools-desktop is in universe and must be in main.

  [Test Case]
  With the patched versions of ubuntu-drivers and open-vm-tools
  1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest 
(with VMWare Workstation for example)
  2. Open a terminal, make sure the package cache is up to date with the 
version of o-v-t containing the Modaliases field
  3. Run the command:
     $ ubuntu-drivers list
     and verify that o-v-t-desktop is in the output
  4. Run the command:
     $ ubuntu-drivers devices
     And verify that the output shows the details of the sys entry for this 
device
  5. Run the command:
     $ sudo ubuntu-drivers install
     and verify that the package o-v-t-desktop is installed

  [Regression Potential]
  Very Low. Package may fail to build if for some reason dh-gencontrol fails. 
Otherwise, given that the package is not already installed automatically, if 
automated installation doesn't work then we're still in the same situation than 
today.
  On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist 
using an existing mechanism so other than a typo there is no risk of regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: open-vm-tools-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:02:49 2019
  InstallationDate: Installed on 2014-07-15 (1697 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: open-vm-tools
  UpgradeStatus: Upgraded to disco on 2018-03-24 (349 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1819207/+subscriptions

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

[Desktop-packages] [Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

[Brian Murray]

The ubiquity change was merged and uploaded.

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Fix Released
Status in ubuntu-drivers-common source package in Disco:
  Fix Released

Bug description:
  [Rationale]
  On Ubuntu Desktop, we want to install automatically at installation time 
open-vm-tools-desktop and its dependencies to provide an improved user 
experience on first boot after installation of the guest. This method also 
provides an easy way to install the drivers after installation if they have not 
been installed at installation time.

  It is achieved adding an XB-Modaliases field to the control file for
  the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the
  packages to install when running in a VMware guest and adding open-vm-
  tools to the list of whitelisted packages in ubuntu-drivers

  [Impact]
  The change adds an additional field to the control file used by 
ubuntu-drivers to detect the drivers to install automatically. In the worst 
case scenario either the field is not added or the detection by ubuntu-drivers 
fails. In both cases the package o-v-t-desktop is not installed and can still 
be installed manually.

  Note: open-vm-tools-desktop is in universe and must be in main.

  [Test Case]
  With the patched versions of ubuntu-drivers and open-vm-tools
  1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest 
(with VMWare Workstation for example)
  2. Open a terminal, make sure the package cache is up to date with the 
version of o-v-t containing the Modaliases field
  3. Run the command:
     $ ubuntu-drivers list
     and verify that o-v-t-desktop is in the output
  4. Run the command:
     $ ubuntu-drivers devices
     And verify that the output shows the details of the sys entry for this 
device
  5. Run the command:
     $ sudo ubuntu-drivers install
     and verify that the package o-v-t-desktop is installed

  [Regression Potential]
  Very Low. Package may fail to build if for some reason dh-gencontrol fails. 
Otherwise, given that the package is not already installed automatically, if 
automated installation doesn't work then we're still in the same situation than 
today.
  On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist 
using an existing mechanism so other than a typo there is no risk of regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: open-vm-tools-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:02:49 2019
  InstallationDate: Installed on 2014-07-15 (1697 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: open-vm-tools
  UpgradeStatus: Upgraded to disco on 2018-03-24 (349 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1819207/+subscriptions

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop

[Sebastien Bacher]

The Xserver segfault so likely an issue there, I reported it upstream on
https://gitlab.freedesktop.org/xorg/xserver/issues/679

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/issues/679
   Importance: Unknown
   Status: Unknown

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

Title:
  Onboard crashes the entire desktop

Status in Onboard:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1820323] Re: amdgpu-pro xorg crash

[Jill Manfield]

https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory  Is
there a solution or workaround for this?

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

Title:
  amdgpu-pro xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This is on Precision 3620, Precision 5820, Precision 7820 - systems
  with AMD bundled for OEM fail to properly boot after update/upgrade.
  I believe this is related to this issue:

  https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory

  Since our image contains the amdgpu-pro package we are impacted.
  Canonical image is not impacted.

  Various systems (Precision 3420, 3620, 5820, and 7820) are having login 
issues with AMD GPUs after running system updates on the OEM Ubuntu image.
  After running sudo apt-get update && apt-get upgrade, the system will exhibit 
one of a few different behaviors:
  • Boots to a black screen
  • Loops at login
  • Boots to a screen indicating the system has been forced to low graphics 
mode and hard locks.
  I have a systems in the lab that exhibits this issue and I don’t know how to 
get around it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 15 13:22:36 2019
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell Device [1028:06c7]
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] 
[1002:6995] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b0c]
  InstallationDate: Installed on 2019-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision Tower 3420
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.2
  dmi.board.name: 02K9CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: Precision Tower 3420
  dmi.sys.vendor: Dell Inc.
  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 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 15 13:21:28 2019
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

[Angelo Giacomini Ribas]

As I've explained in the Bug Description, before filling this bug, I'd
tested the same process in my wife's laptop then with 'Ubuntu 16.04 LTS'
and it imported the certificates ('.cer' and '.p12') without issues. But
in my laptop with 'Ubuntu 18.04 LTS' the problem exist (greyed button).

Therefore, there are two possibilities: 1) I'm mad or a liar; or 2) the
statement on comment #15 is wrong.

I may well be mad, but not a liar! But the experiences described on
comments #21 and #24 corroborate to the second possibility, i.e., that
the statement on comment #15 is wrong.

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

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

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

[Kasia Gauza]

Confirmed, 'info info' and 'h' from within 'info' doesn't work on Ubuntu
18.04.2, Info ver: 6.5.0.dfsg.1-2

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

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

Status in texinfo package in Ubuntu:
  Confirmed

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

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

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

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

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Status in texinfo package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1804359] Re: tutorial doesn't work

[Kasia Gauza]

Same here, Ubuntu 18.04.2 LTS, Info Version: 6.5.0.dfsg.1-2

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

Title:
  tutorial doesn't work

Status in texinfo package in Ubuntu:
  Confirmed

Bug description:
  Running `info` and pressing `h` doesn't bring up promised tutorial:

  ---cut---
  File: dir,  Node: Top,  This is the top of the INFO tree.

  This is the Info main menu (aka directory node).
  A few useful Info commands:

'q' quits;
'H' lists all Info commands;
'h' starts the Info tutorial;
'mTexinfo RET' visits the Texinfo manual, etc.

  ---cut---

  The error message displayed is "Cannot find node '(info)Help'"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: info 6.5.0.dfsg.1-4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Wed Nov 21 07:16:55 2018
  InstallationDate: Installed on 2018-11-01 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

[Derk Willem te Bokkel]

okay I stumbled across something .. the network install .. used netplan
to set-up my wifi connection to start on boot .. so as soon as systemd
networkd starts wifi is started  NetworkManager thus has no access or
anyway to try for other networks.. so I tried to change this.. If I edit
the config files to give exclusive control to NetworkManager ..run
netplan apply as long as I don't reboot I can use NetworkManager as per
normal

As soon as I try to reboot back into the install (via and foreign grub
as defined above) I get exactly the same crash pattern as before .. so
the deduction is that

netplan configuration problems are causing the plymouth/xorg issues when
you use only NetworkManager as a renderer .. so I am altering the title
here again

** Summary changed:

- lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan 
mis-configuration maybe underlying cause.

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
  netplan mis-configuration maybe underlying cause.

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1823778] Re: Unable to set Serbian as Language

[Gunnar Hjalmarsson]

I uploaded a modified bionic package to a PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-control-center

@momcilo: Please feel free to test.

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

Title:
  Unable to set Serbian as Language

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

Bug description:
  Affected: 18.04.2 (did not try earlier versions of 18.04 series)
  Not affected: 16.04 - any version (UI was different)

  Preparation steps:
  1. open gnome control center
  2. open Region & Language
  3. open Manage installed languages
  4. open Install/Remove languages
  5. select Serbian, click Apply
  6. provide credentials for sudo installation
  7. wait for installation to complete
  8. click Close

  What is wrong:
  1. open gnome control center
  2. open Region & Language
  3. click Language selection
  4. Serbian is not visible

  Notes:
  - Serbian is visible for the Formats selection
  - Any other language I thought of: (Macedonian, Croatian, Bosnian, 
Russion...) simple work.

  
  Here is some dpkg output on installaed packages matching sr (Serbian) or hr 
(Croatian).

  ii  firefox-locale-sr  66.0.2+build1-0ubuntu0.18.04.1 
  amd64Serbian language pack for Firefox
  ii  gnome-getting-started-docs-sr  3.28.2-0ubuntu0.1  
  all  Help a new user get started in GNOME (Serbian)
  ii  gnome-user-docs-sr 3.28.2+git20180715-0ubuntu0.1  
  all  GNOME user's guide (Serbian)
  ii  hunspell-sr1:6.0.3-3  
  all  Serbian dictionary for hunspell
  ii  hyphen-sr  1:6.0.3-3  
  all  Serbian hyphenation patterns
  ii  language-pack-gnome-sr 1:18.04+20180712   
  all  GNOME translation updates for language Serbian
  ii  language-pack-gnome-sr-base1:18.04+20180712   
  all  GNOME translations for language Serbian
  ii  language-pack-sr   1:18.04+20180712   
  all  translation updates for language Serbian
  ii  language-pack-sr-base  1:18.04+20180712   
  all  translations for language Serbian
  ii  libreoffice-l10n-sr1:6.0.7-0ubuntu0.18.04.2   
  all  office productivity suite -- Serbian language package
  ii  thunderbird-locale-sr  
1:60.6.1+build2-0ubuntu0.18.04.1 amd64Serbian language pack 
for Thunderbird
  nebojsa@momcilo-desktop:~$ dpkg -l | grep -e "-hr"
  rc  language-pack-gnome-hr-base1:18.04+20180712   
  all  GNOME translations for language Croatian
  rc  language-pack-hr-base  1:18.04+20180712   
  all  translations for language Croatian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 20:10:54 2019
  InstallationDate: Installed on 2019-04-06 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1823778/+subscriptions

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

[Desktop-packages] [Bug 1824330] Re: crashed when tried to do gedit textname

[Sebastien Bacher]

Could you provide the details requested?

** Package changed: samba (Ubuntu) => gedit (Ubuntu)

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

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

Title:
  crashed when tried to do gedit textname

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  (gedit:18666): dbind-WARNING **: 18:11:43.231: Couldn't connect to
  accessibility bus: Failed to connect to socket /tmp/dbus-EV6hC9BiLn:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: smbclient (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 11 18:08:19 2019
  InstallationDate: Installed on 2018-08-17 (237 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: samba
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824330] [NEW] crashed when tried to do gedit textname

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

(gedit:18666): dbind-WARNING **: 18:11:43.231: Couldn't connect to
accessibility bus: Failed to connect to socket /tmp/dbus-EV6hC9BiLn:
Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: smbclient (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Apr 11 18:08:19 2019
InstallationDate: Installed on 2018-08-17 (237 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: amd64 apport-bug bionic
-- 
crashed when tried to do gedit textname
https://bugs.launchpad.net/bugs/1824330
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gedit in Ubuntu.

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

[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

The slowness might have caused by some apparmor probs:
pr 11 15:16:58 zander kernel: [13422.621558] audit: type=1400 
audit(1554988618.771:27): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=13888 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:20:43 zander kernel: [13647.282091] audit: type=1400 
audit(1554988843.431:28): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=20908 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:25:43 zander kernel: [13947.374877] audit: type=1400 
audit(1554989143.520:29): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=27940 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:24 zander kernel: [14108.309867] audit: type=1400 
audit(1554989304.459:30): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=424 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:46 zander kernel: [14130.333125] audit: type=1400 
audit(1554989326.483:31): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=1116 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:00 zander kernel: [14984.432581] audit: type=1400 
audit(1554990180.581:32): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26456 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:03 zander kernel: [14987.725323] audit: type=1400 
audit(1554990183.873:33): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26546 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:05 zander kernel: [14989.287668] audit: type=1400 
audit(1554990185.433:34): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26584 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:06 zander kernel: [14990.386287] audit: type=1400 
audit(1554990186.533:35): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26610 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Activating service 
name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.167' (uid=1000 
pid=14054 comm="/usr/bin/python3 /usr/share/system-config-printer/" 
label="unconfined") (using servicehelper)
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Successfully activated 
service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 11 15:55:43 zander kernel: [15747.355081] audit: type=1400 
audit(1554990943.501:36): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=15434 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:58:20 zander kernel: [15904.185434] audit: type=1400 
audit(1554991100.336:37): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=21257 
comm="apparmor_parser"
Apr 11 15:58:20 zander kernel: [15904.185716] audit: type=1400 
audit(1554991100.336:38): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/sbin/cupsd" pid=21257 comm="apparmor_parser"

Did aa-disable cupsd and it seems faster.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 

[Desktop-packages] [Bug 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch

[Sebastien Bacher]

** Description changed:

+ * Impact
+ Gedit segfaults in some cases
+ 
+ * Test case
+ We don't have specific steps to trigger the issue but the fix is right on 
principle. Check that error reports stop and that there is no regression
+ 
+ https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db
+ 
+ * Regression potential
+ The change is in the 'open document selector' source so test that the popover 
UI to open recent files is still working as it should
+ 
+ ---
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gedit.  This problem was most recently seen with package version 
3.22.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db 
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 you can request it at 
http://forms.canonical.com/reports/.

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

Title:
  
/usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch

Status in gedit package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Gedit segfaults in some cases

  * Test case
  We don't have specific steps to trigger the issue but the fix is right on 
principle. Check that error reports stop and that there is no regression

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

  * Regression potential
  The change is in the 'open document selector' source so test that the popover 
UI to open recent files is still working as it should

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gedit.  This problem was most recently seen with package version 
3.22.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1823432] Re: openexr ftbfs in disco (i386 only)

[Sebastien Bacher]

This bug was fixed in the package openexr - 2.2.1-4.1

---
openexr (2.2.1-4.1) unstable; urgency=medium

  * Non-maintainer upload.
  * bug909865.patch: Add -ffloat-store when compiling tests, to fix test
failures on i386. Patch backported from experimental. (Closes: #909865)

 -- Steinar H. Gunderson   Wed, 20 Mar 2019 22:40:43
+0100

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

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  Fix Released
Status in openexr source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

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

[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

I have a situation that is similar but not with a windows server.

I have an experimental server which is installed with Ubuntu Disco.
Queues are authenticated with kerberos. This is IPP-Everywhere queues.

I have a client with Ubuntu 18.04.2 LTS.

Printing did not work with cups-2.2.7-1ubuntu2.4 on the client. Same
symptoms as described here, cannot print, authentication prompt despite
valid kerberos tickets.

I compiled upstream cups 2.2.7 with Eskos fix-password-prompt.patch AND
the kerberos truncate patch from #13 and installed it on the client.

It works, but printing is very slow, at least from firefox.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Nathaniel Beaver]

** Description changed:

  What I expected to happen:
  
  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.
  
  What happened instead:
  
  I can enter the text without issue, but some of the letters are wrongly
  positioned, i.e. the kerning is wrong. For example, the letter "i"
  overlaps with the letter "m" in "Smith" (see attached image). It looks
  like the font in the fields might be displaying a variable width font
  when it is supposed to be a fixed-wdith font.
  
  Discussion:
  
  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
- reader) and because I'm not sure which a dependency is responsible. (I'm
+ reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
- else like a fontconfig issue.)
+ else like a font configuration issue.)
  
  Here is the output for pdffonts ss-5.pdf:
  
  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0
  
  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:
  
  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form
  
  Ubuntu version:
  
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  
  evince version:
  
  $ apt-cache policy evince
  evince:
-   Installed: 3.28.4-0ubuntu1
-   Candidate: 3.28.4-0ubuntu1
-   Version table:
-  *** 3.28.4-0ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.28.2-1 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 3.28.4-0ubuntu1
+   Candidate: 3.28.4-0ubuntu1
+   Version table:
+  *** 3.28.4-0ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.28.2-1 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  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 evince in Ubuntu.
https://bugs.launchpad.net/bugs/1824260

Title:
  wrong kerning in SS-5 PDF form fields

Status in evince package in Ubuntu:
  New

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding 

[Desktop-packages] [Bug 1824283] Re: Nautilus progress bar is easily lead users to cancel the running task

[Sebastien Bacher]

Thank you for your bug report, could you also report it upstream to the
people writting the software on
https://gitlab.gnome.org/GNOME/nautilus/issues ?

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

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

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

Title:
  Nautilus  progress bar is easily lead users to cancel the running task

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  People often check the progress of tasks when they copying or deleting
  some large files using the nautilus progress bar. Usually, they would
  click a button to close the popped progress bar. The nautilus progress
  bar is very easy to lead users to click the cancel task button since
  there is only one button on the progress bar which is very like a
  closing window button. I suggest it add a confirm message box or
  change the cancel task button to other icons.

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

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

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

[Fran]

I have the same problem, with xubuntu 18.04.2, @samweis say that is a
problem in ubuntu, seahorse can import p12 keys well in debian

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

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

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Sebastien Bacher]

Thank you for your bug report, could you also report it upstream to the
people writting the software on
https://gitlab.gnome.org/GNOME/evince/issues ?

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

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in evince package in Ubuntu:
  New

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824188] Re: Software tab is empty on clean 19.04 install

[John Lenton]

By editing /target/etc/environment and setting SNAPD_DEBUG=1 etc before
rebooting into the new system, I get
http://paste.ubuntu.com/p/jTQb2YHhq3/

You can see there snapd coming up and seeding the system, and you can
also watch as pid 724 (snapd-seeded.service) polling, waiting for the
seeding to be done. Grep for pid=724 to follow this one.

That seeding gets marked as done on the line

Apr 11 12:04:29 ubuntu snapd[2115]: daemon.go:296: DEBUG:
pid=724;uid=0;socket=/run/snapd.socket; GET
/v2/snaps/system/conf?keys=seed.loaded 37.034783ms 200

and then 724 stops, as it should. Right after it you start getting
pid=3635 lines, which correspond to gnome-software (via a line in syslog
saying «gnome-software[3635]: disabled plugins: dpkg, dummy, repos,
epiphany»). gnome-software successfully queries snapd for featured and
installed snaps (and if you start the gui, they're right there).

However you can _also_ see a pid=1825. That pid corresponds to gnome-
initial-setup.

The single pid=1825 entry arrives _before snapd has seeded the system_,
and in particular just as snapd has scheduled a restart. I can only
assume that gnome-initial-setup gets back the list of snaps, then tries
to do a find for featured snaps and fails (because snapd is restarting),
and that is the point where it logs

Apr 11 12:03:46 ubuntu gnome-initial-s[1825]: Failed to get featured
snaps: Failed to read from snapd: Error receiving data: Connection reset
by peer


note that this is racy, and gnome-initial-setup could just as well have logged 
'Failed to get installed snaps' when the initial query fails, but succeeded to 
get the featured snaps (and then would go on to break in interesting ways as it 
tries to look things up in a nil container).

In any case, two solutions:

1. retry queries when you get an error from querying snapd (as opposed
to an error response). This is what the 'snap' client does: retries
every 250ms for up to 5s.

2. wait for snapd to be loaded

even with (2), (1) should probably be done anyway (but it'll be harder
to hit).

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

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

Title:
  Software tab is empty on clean 19.04 install

Status in gnome-initial-setup package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Did a clean install of Ubuntu 19.04.
  Rebooted into the new installation.
  Started using it, and after a short while the gnome initial setup appeared.
  I went through each step, but the final one "You're ready to go!" should have 
some software listed from the snap store, but doesn't.

  I have a working internet connection (I'm filing list bug from it)

  See screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-initial-setup 3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 17:13:41 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

[spike speigel]

** Tags added: disco

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

[Stefan]

I'm on ubuntu 18.10 and I get random drops but if I disconnect and
reconnect from the UI, it works. This isn't happening on my laptop which
runs 18.04 also on cable connection.

-network 
   description: Ethernet interface
   product: I211 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:07:00.0
   logical name: enp7s0
   version: 03
   serial: e0:d5:5e:a0:55:0f
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi msix pciexpress bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=igb 
driverversion=5.4.0-k duplex=full firmware=0. 6-1 ip=192.168.0.108 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
   resources: irq:38 memory:f760-f761 ioport:f000(size=32) 
memory:f762-f7623fff

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably 

[Desktop-packages] [Bug 1823421] Re: deja-dup ftbfs in disco

[Launchpad Bug Tracker]

This bug was fixed in the package deja-dup - 38.4-1

---
deja-dup (38.4-1) experimental; urgency=medium

  * New upstream release (LP: #1823421)
- Be more forgiving if packagekit is unresponsive
- Don't run monitor when automatic backups are disabled
- Drop libpeas dependency
- Fix compilation with valac 0.43
- Update app icon
- Update translations
  * Drop libpeas BD per upstream
  * debian/docs: NEWS is now called NEWS.md
  * Take patch from upstream MR !22 to fix many tests under GLib 2.59
g_key_file_get_comment() used to append a stray newline to its return
value, and it stopped doing this with 2.59. deja-dup was accidentally
relying on that behaviour.
  * Take patch from upstream MR !22 to fix whitespace assumption in test.
Since GLib 2.59.1, g_format_size() started using non-breaking spaces
instead of regular ones to separate the size from the unit. deja-dup was
only testing for the latter. Update the test to use a regex with `\s`, so
we match all types of whitespace.

 -- Iain Lane   Wed, 10 Apr 2019 13:56:48 +0100

** Changed in: deja-dup (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  deja-dup ftbfs in disco

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924442/buildlog_ubuntu-disco-amd64
  .deja-dup_38.3-1_BUILDING.txt.gz

  make[1]: Leaving directory '/<>'
 dh_auto_build -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
  [1/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.h
  [2/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.c 
--dependency-file data/resources.c.d
  [3/96] valac -C --debug --pkg gio-2.0 --color=always --directory 
deja-dup/nautilus/248796f@@dirhandling@sta --basedir ../deja-dup/nautilus 
--library dirhandling --header deja-dup/nautilus/dirhandling.h --vapi 
../dirhandling.vapi --pkg=config --pkg=posix --target-glib=2.46 --vapidir 
/<>/vapi --define=HAS_PACKAGEKIT 
/<>/libdeja/DirHandling.vala
  [4/96] valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg 
packagekit-glib2 --pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg 
gio-2.0 --color=always --directory libdeja/ccd1814@@deja@sha --basedir 
../libdeja --library deja --header libdeja/deja.h --vapi ../deja.vapi 
--pkg=config --pkg=posix --target-glib=2.46 --vapidir /<>/vapi 
--define=HAS_PACKAGEKIT --pkg=secret --pkg=uriutils ../libdeja/Backend.vala 
../libdeja/BackendAuto.vala ../libdeja/BackendDrive.vala 
../libdeja/BackendFile.vala ../libdeja/BackendGCS.vala 
../libdeja/BackendGOA.vala ../libdeja/BackendLocal.vala 
../libdeja/BackendOpenstack.vala ../libdeja/BackendRackspace.vala 
../libdeja/BackendRemote.vala ../libdeja/BackendS3.vala 
../libdeja/BackendU1.vala ../libdeja/CommonUtils.vala 
../libdeja/DirHandling.vala ../libdeja/FilteredSettings.vala 
../libdeja/Network.vala ../libdeja/Operation.vala 
../libdeja/OperationBackup.vala ../libdeja/OperationFiles.vala 
../libdeja/OperationRestore.vala ../libdeja/OperationStatus.vala 
../libdeja/OperationVerify.vala ../libdeja/RecursiveDelete.vala 
../libdeja/RecursiveMove.vala ../libdeja/RecursiveOp.vala 
../libdeja/ToolPlugin.vala
  FAILED: libdeja/ccd1814@@deja@sha/Backend.c 
libdeja/ccd1814@@deja@sha/BackendAuto.c 
libdeja/ccd1814@@deja@sha/BackendDrive.c 
libdeja/ccd1814@@deja@sha/BackendFile.c libdeja/ccd1814@@deja@sha/BackendGCS.c 
libdeja/ccd1814@@deja@sha/BackendGOA.c libdeja/ccd1814@@deja@sha/BackendLocal.c 
libdeja/ccd1814@@deja@sha/BackendOpenstack.c 
libdeja/ccd1814@@deja@sha/BackendRackspace.c 
libdeja/ccd1814@@deja@sha/BackendRemote.c libdeja/ccd1814@@deja@sha/BackendS3.c 
libdeja/ccd1814@@deja@sha/BackendU1.c libdeja/ccd1814@@deja@sha/CommonUtils.c 
libdeja/ccd1814@@deja@sha/DirHandling.c 
libdeja/ccd1814@@deja@sha/FilteredSettings.c 
libdeja/ccd1814@@deja@sha/Network.c libdeja/ccd1814@@deja@sha/Operation.c 
libdeja/ccd1814@@deja@sha/OperationBackup.c 
libdeja/ccd1814@@deja@sha/OperationFiles.c 
libdeja/ccd1814@@deja@sha/OperationRestore.c 
libdeja/ccd1814@@deja@sha/OperationStatus.c 
libdeja/ccd1814@@deja@sha/OperationVerify.c 
libdeja/ccd1814@@deja@sha/RecursiveDelete.c 
libdeja/ccd1814@@deja@sha/RecursiveMove.c 
libdeja/ccd1814@@deja@sha/RecursiveOp.c libdeja/ccd1814@@deja@sha/ToolPlugin.c 
libdeja/deja.h libdeja/deja.vapi 
  valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg packagekit-glib2 
--pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg gio-2.0 
--color=always --directory libdeja/ccd1814@@deja@sha --basedir ../libdeja 
--library deja 

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

[Derk Willem te Bokkel]

An additional data point  for reference .. did a netboot install of
xubuntu  using "daily" amd64 netboot mini.iso ..  base install followed
by taskselect install of xubuntu ..

boots normally plymouth and lightdm screens appear as expected .. also
switching to foreign grub .. it still boots normally .. normal expected
behaviour ..

note: regular ubuntu daily also behaves this way .. but uses wayland no
xorg ..

rhetorical question: so what makes the full graphics install so fragile
for intel i915 graphics?

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can
suspend the machine.

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

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

[Desktop-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Launchpad Bug Tracker]

This bug was fixed in the package librsvg - 2.44.10-1ubuntu1

---
librsvg (2.44.10-1ubuntu1) disco; urgency=medium

  * debian/patches/typenum-i386-ftbfs.patch: backport an upstream fix for a
build failure in the vendored typenum crate on i386 (LP: #1823426)
  * debian/patches/i386-rounding-errors.patch: fix a rounding error on i386
that would result in a unit test failure

 -- Olivier Tilloy   Wed, 10 Apr 2019
17:14:57 +0200

** Changed in: librsvg (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg:
  New
Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Disco:
  Fix Released
Status in librsvg package in Debian:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: 

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Keneth C]

Facing the same issue with 18.04.2 LTS
Had the same issue with previous versions as well
Will there be a fix anytime soon?
Thank you.

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI

[Keneth C]

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

Facing the same issue with 18.04.2 LTS
Had the same issue with previous versions as well
Will there be a fix anytime soon?
Thank you.

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

Title:
  Output device doesn't always switch back from HDMI

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I disconnect to an HDMI output sometimes the configuration is
  left in an inconsistent state. It still shows as being connected to
  HDMI in volume up/down but there is no longer an HDMI option in the
  sound settings. After clicking the "Speakers - Built-in Audio" line in
  the Output tab of the settings (the only line available) everything is
  now correct. The same issue was also present in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   32004 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 22:54:14 2018
  InstallationDate: Installed on 2018-05-31 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  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:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1821849] Re: LibreOffice Impress 6.2.2.2 Embedded Video Problem

[Sam Colegrove]

It is now one week since you realized that the bug is with Kubuntu 19.04
and NOT with Ubuntu 19.04.  I assume that by now you have a VM with
Kubuntu 19.04 and tested the impact of an embedded video. Since I have
not heard from you, I expect that you have found the bug that caused me
to start this report.

Since no one has been assigned to solve this bug and its importance is
Undecided, could you please let me know if this bug will be dealt with
by launchpad or is there anywhere else I should head for this bug to be
fixed?

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

Title:
  LibreOffice Impress 6.2.2.2 Embedded Video Problem

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The following bugs are for LibreOffice 6.2.2.2 Impress on Kubuntu
  19.04.

  When I start a slide-show with Impress by using either F5 or Shift F5,
  I get a white screen.  When I click on it, the slide is displayed.
  When I exit the presentation with say "Esc", soffice.bin is in the
  taskbar with the odp file used for the presentation.  If I click on
  the odp file and exit, both tasks are removed.

  Now when I advance to an embedded video I get the image shown with
  this report. When the video is started, the previous slide is shown on
  top of the video as it is being played. Not a good view This
  happens when either starting from the first slide or the one preceding
  embedded video.

  I have tried the gtk3 options in https://launchpad.net/bugs/1820062
  and the changes make no difference to this problem.  I have also
  installed gstreamer1.0-plugins-* which solved  previous problem with
  LibreOffice.

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

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

[Desktop-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Bug Watch Updater]

** Changed in: librsvg (Debian)
   Status: Unknown => Fix Released

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg:
  New
Status in librsvg package in Ubuntu:
  In Progress
Status in librsvg source package in Disco:
  In Progress
Status in librsvg package in Debian:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

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

[Desktop-packages] [Bug 1824297] Re: Wallpapers that are more than twice the screen resolution sometimes appear blurry in 3.32.0

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Wallpapers that are more than twice the screen resolution sometimes
  appear blurry in 3.32.0

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Wallpapers that are more than twice the screen resolution sometimes
  appear blurry in 3.32.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-10.11-generic 5.0.6
  Uname: Linux 5.0.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Thu Apr 11 15:23:31 2019
  InstallationDate: Installed on 2018-12-04 (128 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[Gibus]

Also, the bug still happens, but apparently less frequently, when
libreoffice is launched with env variable LIBGL_DRI3_DISABLE is true
(i.e: LIBGL_DRI3_DISABLE=true /usr/bin/libreoffice) as advised in
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984

It's really hard to reproduce, it seems that most often the bug is
triggered when text is selected (to be copy/cut) in libre-office writer.

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

Title:
  soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Using LibreOffice Calc I was editing a filter on a pivot table and all
  LibreOffice windows hung.  What appeared in /var/log/syslog was:

  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown 
sequence number while processing queue
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely 
this is a multi-threaded client and XInitThreads has not been called
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry 
about that.
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: 
../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  Nov  1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 
'WindowPreviewMenuItem' on the module 'windowPreview'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-calc 1:6.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 13:39:03 2018
  InstallationDate: Installed on 2018-10-29 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Olivier Tilloy]

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

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

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg:
  New
Status in librsvg package in Ubuntu:
  In Progress
Status in librsvg source package in Disco:
  In Progress
Status in librsvg package in Debian:
  Unknown

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

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

[Desktop-packages] [Bug 1714191] Re: hplip contextual menu is wrongly placed

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
28-1

---
gnome-shell-extension-appindicator (28-1) experimental; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release
  * indicatorStatusIcon: Ignore indicators with no menus, monitoring changes
(LP: #1714504)
  * appIndicator: Retry getting a valid menu path (LP: #1714504)
  * dbusMenu: Ignore error on invalid return in AboutToShow
  * appIndicator: Update icon actor size on scale factor change (LP: #1730071)
  * dbusMenu: add isReady property when the menu is available on bus
  * indicatorStatusIcon: Don't support activation if we have a menu
(LP: #1714191, LP: #1716056)
  * d/p/metadata-use-appindicator-namespace-and-naming.patch:
- refresh and reduce diff with upstream

 -- Matteo F. Vescovi   Tue, 09 Apr 2019 22:28:45 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  hplip contextual menu is wrongly placed

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  Tested on wayland

  Test Case
  1. Install hplib-gui and run hp-systray
-> An icon is displayed in the icon bar
  2. Click anywhere on the top panel (eg center of the panel)
  3. Double-click on the HP icon to display the contextual menu

  Expected result
  The menu is displayed below the icon aligned on the left with it

  Actual result
  The contextual menu is displayed somewhere far on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:22:08 2017
  Dependencies:
   
  InstallationDate: Installed on 2013-09-03 (1457 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730071] Re: Application icons appear stretched when using scaling

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
28-1

---
gnome-shell-extension-appindicator (28-1) experimental; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release
  * indicatorStatusIcon: Ignore indicators with no menus, monitoring changes
(LP: #1714504)
  * appIndicator: Retry getting a valid menu path (LP: #1714504)
  * dbusMenu: Ignore error on invalid return in AboutToShow
  * appIndicator: Update icon actor size on scale factor change (LP: #1730071)
  * dbusMenu: add isReady property when the menu is available on bus
  * indicatorStatusIcon: Don't support activation if we have a menu
(LP: #1714191, LP: #1716056)
  * d/p/metadata-use-appindicator-namespace-and-naming.patch:
- refresh and reduce diff with upstream

 -- Matteo F. Vescovi   Tue, 09 Apr 2019 22:28:45 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Application icons appear stretched when using scaling

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  The appindicator gnome extension shows the "system tray icons" in the
  upper right corner of the screen. However the icons appear vertically
  stretched. The problem appears to be purely visual, as they still work
  as expected.

  > lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  > apt-cache policy gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
Installed: 17.10.1
Candidate: 17.10.1
Version table:
   *** 17.10.1 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1716056] Re: Multiple context menus appearing

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
28-1

---
gnome-shell-extension-appindicator (28-1) experimental; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release
  * indicatorStatusIcon: Ignore indicators with no menus, monitoring changes
(LP: #1714504)
  * appIndicator: Retry getting a valid menu path (LP: #1714504)
  * dbusMenu: Ignore error on invalid return in AboutToShow
  * appIndicator: Update icon actor size on scale factor change (LP: #1730071)
  * dbusMenu: add isReady property when the menu is available on bus
  * indicatorStatusIcon: Don't support activation if we have a menu
(LP: #1714191, LP: #1716056)
  * d/p/metadata-use-appindicator-namespace-and-naming.patch:
- refresh and reduce diff with upstream

 -- Matteo F. Vescovi   Tue, 09 Apr 2019 22:28:45 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Multiple context menus appearing

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  In Progress

Bug description:
  I have dropbox installed on my up to date 17.10 system. Clicking the
  dropbox icon triggers multiple menus, over the top of eachother (see
  screenshot). One is a gnome style menu, the other is a white native
  dropbox menu.

  I'd imagine I should really only see one menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 23:09:09 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-08-02 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714504] Re: App indicator is not always displayed

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
28-1

---
gnome-shell-extension-appindicator (28-1) experimental; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release
  * indicatorStatusIcon: Ignore indicators with no menus, monitoring changes
(LP: #1714504)
  * appIndicator: Retry getting a valid menu path (LP: #1714504)
  * dbusMenu: Ignore error on invalid return in AboutToShow
  * appIndicator: Update icon actor size on scale factor change (LP: #1730071)
  * dbusMenu: add isReady property when the menu is available on bus
  * indicatorStatusIcon: Don't support activation if we have a menu
(LP: #1714191, LP: #1716056)
  * d/p/metadata-use-appindicator-namespace-and-naming.patch:
- refresh and reduce diff with upstream

 -- Matteo F. Vescovi   Tue, 09 Apr 2019 22:28:45 +0200

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  App indicator is not always displayed

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  I've 2 apps that should be displayed in the indicator:
  - hp systray (from the package hplip-gui)
  - synology cloud client (download from synology)

  Sometimes the indicators are displayed and sometimes not. The
  extension is loaded and show no error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  1 14:57:16 2017
  Dependencies:

  InstallationDate: Installed on 2013-09-03 (1458 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823581] Re: Multi-touch screen test of checkbox failed on Disco 19.04

[Kai-Heng Feng]

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

Yes it's LP: #1774242.

** This bug has been marked a duplicate of bug 1774242
   Wacom touchscreens should use libinput, not wacom driver

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

Title:
  Multi-touch screen test of checkbox failed on Disco 19.04

Status in linux package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Summary: I use a Dell Precision 5530 (I+N). The tests of checkbox
  failed: 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-
  zoom

  Steps to reproduce:
  1. Install checkbox
  $ sudo add-apt-repository ppa:hardware-certification/public
  $ sudo apt-get update
  $ sudo apt-get install checkbox-ng plainbox-provider-resource-generic 
plainbox-provider-certification-client plainbox-provider-checkbox
  2. Run the test cases - 3-touch-tap, 4-touch-tap, multitouch-rotate and 
multitouch-zoom via checkbox
  $ checkbox-cli

  Expected result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
passed
  Actual result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
failed

  Additional Information:
  The tests can be passed on XPS 13 9380

  Failure rate: 100%

  -

  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  system-manufacturer: Dell Inc.
  bios-version: 1.6.0
  CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x)
  system-product-name: Precision 5530
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2343 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-29 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 004: ID 0c45:671d Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=8e4bee3f-6d32-4221-8bd7-7cdbfcf163b7 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Timo Aaltonen]

The same effect would happen if the touchscreen entries were commented
out from 70-wacom.conf, can you confirm?

** Changed in: xf86-input-wacom (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xf86-input-wacom (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Incomplete

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1823581] Re: Multi-touch screen test of checkbox failed on Disco 19.04

[Timo Aaltonen]

or rather bug 1774242

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

Title:
  Multi-touch screen test of checkbox failed on Disco 19.04

Status in linux package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Summary: I use a Dell Precision 5530 (I+N). The tests of checkbox
  failed: 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-
  zoom

  Steps to reproduce:
  1. Install checkbox
  $ sudo add-apt-repository ppa:hardware-certification/public
  $ sudo apt-get update
  $ sudo apt-get install checkbox-ng plainbox-provider-resource-generic 
plainbox-provider-certification-client plainbox-provider-checkbox
  2. Run the test cases - 3-touch-tap, 4-touch-tap, multitouch-rotate and 
multitouch-zoom via checkbox
  $ checkbox-cli

  Expected result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
passed
  Actual result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
failed

  Additional Information:
  The tests can be passed on XPS 13 9380

  Failure rate: 100%

  -

  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  system-manufacturer: Dell Inc.
  bios-version: 1.6.0
  CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x)
  system-product-name: Precision 5530
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2343 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-29 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 004: ID 0c45:671d Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=8e4bee3f-6d32-4221-8bd7-7cdbfcf163b7 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1823461] Re: Font hinting lost on chrome like browser

[Mohammad Anwar Shah]

I've tested the fix and it works fine.

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

Title:
  Font hinting lost on chrome like browser

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  The file for configuring Japanese rendering with Noto fonts does not
  refer to the font family with sufficient precision, so it may affect
  rendering with other fonts unintentionally. The proposed upload fixes
  the issue.

  [Test Case]

  The real tests have been reported in comment #6 and #7 of this bug
  report.

  To verify that the modified file is properly installed:

  1. Install language-selector-common and language-selector-gnome from
 bionic-proposed

  2. Run this command:

  cat /etc/fonts/conf.avail/69-language-selector-ja.conf | grep 'Noto
  Sans CJK JP'

  (should output the line "Noto Sans CJK JP")

  [Regression Potential]

  That config file was added specifically for rendering Japanese with
  Noto fonts, and the modified file has been confirmed by the original
  author. Hence the regression risk should be low.

  [Original description]

  Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome
  browsers are horrible to use. Font hintings are not working as
  expected. There were always some hairy things above the fonts which
  caused me to abandon Ubuntu. Unfortunately, this bug affected all
  other Ubuntu derivatives as well. I was forced to use Debian and
  Manjaro, because nowhere in the Internet I found a solution.

  I've tested Ubuntu 19.04 again. I removed all of the *.conf file in
  `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are
  okay. Further investigating revealed that the culprit was symlink to
  this file `/etc/fonts/conf.avail/69-language-selector-ja.conf`

  I opened it and found that on Line no 8, it has this

  

  which should instead be

  

  since `JP` is language identifier, not family.

  I manually fixed the file and all is well!

  I'm attaching two screenshot of chrome browser. Inspect the "Autofill"
  and "Appearance" word of the chrome setting page screenshot.

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

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