[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[bartje]

Still happens here on a HP Pavilion. I have tried the intel onboard
video, the nvidia, with the nvidia drivers. If it's of hep the xrandr
output shows: HDMI-1 disconnected, so it is seen but not activated. When
booting in Windows all works fine...

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080 60.02*+  60.0159.9759.9659.9340.02  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
HDMI-1 disconnected (normal left inverted right x axis y axis)

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   

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

[Christian Ehrhardt ]

[08:14]  jibel: we got the FFe on 1819207 and the change into Debian
[08:14]  jibel: the only other change in Debian we want as well (an 
evolved version of a fix I already had tested and followed the upstream 
resolution)
[08:15]  jibel: that means we now want to do a syncpackage - should I 
or do you want to?
[08:17]  hi cpaelzer , can you do it please?

I kicked the syncpackage and we can later on the day check if it all
built and migrated as expected.

-- 
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:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in open-vm-tools source package in Disco:
  Triaged
Status in ubiquity source package in Disco:
  Triaged
Status in ubuntu-drivers-common source package in Disco:
  In Progress

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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

[fessmage]

@vangugt - I installed gnome-shell and gnome-shell-common from bionic-proposed 
and now problem fixed:
gnome-shell/bionic-proposed,now 3.28.3+git20190124-0ubuntu18.04.1 amd64 
[installed]
gnome-shell-common/bionic-proposed,bionic-proposed,now 
3.28.3+git20190124-0ubuntu18.04.1 all [installed]

I was confused by message from sil2100 where he claims: "The verification of 
the Stable Release Update for gnome-shell has completed successfully and the 
package has now been released to -updates." 
Obviously, right now - it is not in updates, still only in proposed.

-- 
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 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

[Josua Dietze]

The behaviour of Huawei modems depends on the respective firmware and
may result in very different 'target modes'. These are the ones that can
be used with Linux AFAIK:

1. Ethernet mode (controlled via built-in web interface)
2. NCM mode (CDC NCM interface with 'hybrid' AT control)
3. Serial mode (traditional serial ports for PPP connection and diag messages)

No.3 is becoming rare. No.1 is simple to use but the browser control is
a bit awkward.

No.2 is preferable for modems >3G and should be supported by kernel and Modem 
Manager. It has the least overhead.
Not sure if and how SMS features are included there - that's not my field of 
expertise.

Josua Dietze (usb_modeswitch upstream)

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

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Triaged
Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G4
  dmi.product.sku: X3T22AV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
 

[Desktop-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

[Josua Dietze]

Addendum:

The "official" switching message suggested by Huawei may bring up either
mode No.1 or mode No.2 in recent models. If No.1 shows up, there is a
possibility that the "HuaweiAltMode" message may bring up No.2 instead.

This is up to the user though, there is no comprehensive information
available about the different Huawei models and firmwares AFAIK.

(BTW, mode No.2 is what Huawei calls "HiLink".)

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

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Triaged
Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G4
  dmi.product.sku: X3T22AV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vend

[Desktop-packages] [Bug 1820569] [NEW] !!

[track-gc]

Public bug reported:

!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-144.170-generic 4.4.176
Uname: Linux 4.4.0-144-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Mar 18 15:47:04 2019
DistUpgraded: 2019-03-18 15:36:08,567 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned 
an error code (1)'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.34, 4.4.0-124-generic, i686: installed
 virtualbox, 5.1.34, 4.4.0-127-generic, i686: installed
 virtualbox, 5.1.34, 4.4.0-137-generic, i686: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
InstallationDate: Installed on 2017-08-01 (593 days ago)
InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
MachineType: LENOVO 3626AT9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-144-generic 
root=UUID=cd062b33-bfd2-492b-b719-0b0d0359d78a ro locale=zh_CN
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2019-03-18 (0 days ago)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET52WW (1.22 )
dmi.board.name: 3626AT9
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3626AT9:pvrThinkPadX201:rvnLENOVO:rn3626AT9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3626AT9
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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: Mon Mar 18 14:09:08 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16401 
 vendor LEN
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial

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

Title:
  !!

Status in xorg package in Ubuntu:
  New

Bug description:
  !

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-144.170-generic 4.4.176
  Uname: Linux 4.4.0-144-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 18 15:47:04 2019
  DistUpgraded: 2019-03-18 15:36:08,567 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned 
an error code (1)'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.4.0-124-generic, i686: installed
   virtualbox, 5.1.34, 4.4.0-127-generic, i686: installed
   virtualbox, 5.1.34, 4.4.0-137-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2017-08-01 (593 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: LENOVO 3626AT9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-144-generic 
root=UUID=cd062b33-bf

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

[Daniel van Vugt]

OK that message in comment #43 was bound to cause confusion. It was
actually about the fix for 18.10 (cosmic).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1820323] Re: xorg crash

[Timo Aaltonen]

>From xserver.errors.txt:

"module ABI major version (10) doesn't match the server's version (9)
Failed to load module "glx" (module requirement mismatch, 0)
Screen 0 deleted because of no matching config section."

So I think you need to reinstall libgl1-amdgpu-mesa-glx as well. The
askubuntu suggestion to remove amdgpu-pro is mainly for after upgrade to
18.04, in this case 16.04 is still used and amdgpu-pro probably still
needed, so amdgpu reinstall (or upgrade to latest one available for
16.04) is likely the only supported way.

-- 
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:
  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 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

Hi Daniel,

will install the patch later today and let you know.

Thanks for pointing me to a possible solution (I completely missed it).

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

Title:
  Network icons in status menu disappearing

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

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1820569] Re: !!

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

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

Title:
  !!

Status in Ubuntu:
  Incomplete

Bug description:
  !

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-144.170-generic 4.4.176
  Uname: Linux 4.4.0-144-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 18 15:47:04 2019
  DistUpgraded: 2019-03-18 15:36:08,567 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned 
an error code (1)'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.4.0-124-generic, i686: installed
   virtualbox, 5.1.34, 4.4.0-127-generic, i686: installed
   virtualbox, 5.1.34, 4.4.0-137-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2017-08-01 (593 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: LENOVO 3626AT9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-144-generic 
root=UUID=cd062b33-bfd2-492b-b719-0b0d0359d78a ro locale=zh_CN
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-03-18 (0 days ago)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET52WW (1.22 )
  dmi.board.name: 3626AT9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3626AT9:pvrThinkPadX201:rvnLENOVO:rn3626AT9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3626AT9
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Mon Mar 18 14:09:08 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16401 
   vendor LEN
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1819240] Re: Many sites will not connect. Very slow. Some siezing.

[Daniel van Vugt]

It sounds like you might be having Internet problems. Are you having any
problems with a particular app or browser?

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

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

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

Title:
  Many sites will not connect. Very slow. Some siezing.

Status in Ubuntu:
  Incomplete

Bug description:
  N/A

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar  8 19:20:55 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1]
  InstallationDate: Installed on 2016-09-11 (908 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard p6710f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE0480TV4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6710f
  dmi.sys.vendor: Hewlett-Packard
  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  8 18:28:14 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Launchpad Bug Tracker]

This bug was fixed in the package open-vm-tools - 2:10.3.5-8

---
open-vm-tools (2:10.3.5-8) unstable; urgency=medium

  [ Jean-Baptiste Lallement ]
  * [0f35aee] Add modaliases to open-vm-tools-desktop.
Added Modaliases to open-vm-tools-desktop to auto-discover and
auto-install the driver on Ubuntu via ubuntu-drivers. The driver is then
installed at installation time and available on first boot for an
improved user experience (LP: #1819207)

  [ Bernd Zeimetz ]
  * [dc4e1ce] Load vmwgfx module before vmtoolsd starts.
As discussed on github in vmware/open-vm-tools#214
we need to load the vmwgfx module before starting vmtoolsd
for desktop users. Otherwise it is not able to retrieve the KMS
resolutions and resizing the VM desktop fails.
Thanks to @thomashvmw @rhertzog (Closes: #924518)

 -- Bernd Zeimetz   Wed, 13 Mar 2019 22:15:22 +0100

** Changed in: open-vm-tools (Ubuntu Disco)
   Status: Triaged => 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:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Triaged
Status in ubuntu-drivers-common source package in Disco:
  In Progress

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 1681816] Re: [description information] some application have no description information

[quankang]

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [description information] some application have no description
  information

Status in Ubuntu Kylin:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New
Status in ukui-indicators package in Ubuntu:
  New
Status in youker-assistant package in Ubuntu:
  New

Bug description:
  [system]
  zesty-daily-0406-i386/zesty-daily-0407-amd64/zesty-final-i386/amd64

  [bug description]
  1.put the cursor on Youker weather and network in right bottom of desktop
  2.no description information shows up

  [expectation]
  all applications in panel have description information

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

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

[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco

[Bas Zoetekouw]

The problem still occurs with the .91 version from disco-proposed.
I'll attach the requested files to the upstream report.

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1719192] Re: Some Top Icons Disappear After Screen Locks - 17.10

[Dominik Steffen]

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

I can confirm this issue on my system with this version/kernel:
Ubuntu 18.04.2 LTS
Linux clds 4.19.0-041900-generic #201810221809 64Bit

Different applications are disappearing after locking the screen while
some are still shown after screen lock

alt + f2 -> "r" -> return works as a temporary solution.

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

Title:
  Some Top Icons Disappear After Screen Locks - 17.10

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

Bug description:
  Hi friends. I'm testing Ubuntu 17.10 with Gnome 3.26. I noticed some
  top bar icons disappear after my screen locks and I go back in to my
  active session. As an example, I currently have Quassel, Telegram, and
  Nextcloud sync client in the upper right corner displaying their task
  tray icons. If I lock my screen and re-authenticate back in to my
  active session, Quassel remains, but Telegram and Nextcloud are gone.
  The only way to get them back is by closing the application the
  missing icon belongs to and re-launching it.

  Thanks for all of your hard work!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 10:57:24 2017
  InstallationDate: Installed on 2017-09-01 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  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/1719192/+subscriptions

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

[Desktop-packages] [Bug 1820571] [NEW] package gedit 3.30.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Thanh Nhan]

Public bug reported:

I can't download anything with terminal elements

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: gedit 3.30.1-1
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.2
Architecture: amd64
Date: Mon Mar 18 15:44:37 2019
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-11-10 (128 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.2
SourcePackage: gedit
Title: package gedit 3.30.1-1 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: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic

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

Title:
  package gedit 3.30.1-1 failed to install/upgrade: package is in a very
  bad inconsistent state; you should  reinstall it before attempting
  configuration

Status in gedit package in Ubuntu:
  New

Bug description:
  I can't download anything with terminal elements

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gedit 3.30.1-1
  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.2
  Architecture: amd64
  Date: Mon Mar 18 15:44:37 2019
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-11-10 (128 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: gedit
  Title: package gedit 3.30.1-1 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/gedit/+bug/1820571/+subscriptions

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

[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

[Michel-Ekimia]

I think that is a real important problem, could anybody at least
reproduce the issue ?

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

Status in OEM Priority Project:
  Expired
Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  More an nvidia driver fail but happens in a oem-config scenario :

  - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) 
  - full-upgrade
  - ubuntu-drivers autoinstall ( To get nvidia drivers) 
  - Reboot and confirm nvidia driver work great

  
  - oem-config-prepare

  - Send machine to client

  - client goes through oem-config wizard normally

  - instead of going to the new desktop , client gets a blackscreen

  - After reboot he always get a black screen.

  - If he logs into TTY1 , he can login and startx to get a gnome3
  desktop.

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

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

[Desktop-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version

[Till Kamppeter]

Now my Bionic test box is running for the whole weekend and it does not
show any irregularities. No crash reports. The new network-manager seems
to work fine on Bionic.

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

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

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

[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

[Daniel van Vugt]

Please follow the instructions in comment #8.

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

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

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

Status in OEM Priority Project:
  Expired
Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  More an nvidia driver fail but happens in a oem-config scenario :

  - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) 
  - full-upgrade
  - ubuntu-drivers autoinstall ( To get nvidia drivers) 
  - Reboot and confirm nvidia driver work great

  
  - oem-config-prepare

  - Send machine to client

  - client goes through oem-config wizard normally

  - instead of going to the new desktop , client gets a blackscreen

  - After reboot he always get a black screen.

  - If he logs into TTY1 , he can login and startx to get a gnome3
  desktop.

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

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

[Desktop-packages] [Bug 1820524] Re: Sync zziplib 0.13.62-3.2 (main) from Debian unstable (main)

[Dmitry Shachnev]

This bug was fixed in the package zziplib - 0.13.62-3.2
Sponsored for Logan Rosen (logan)

---
zziplib (0.13.62-3.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Invalid memory access in zzip_disk_fread (CVE-2018-6381) (Closes: #889096)
  * Reject the ZIP file and report it as corrupt if the size of the central
directory and/or the offset of start of central directory point beyond the
end of the ZIP file (CVE-2018-6484, CVE-2018-6541, CVE-2018-6869)
(Closes: #889089)
  * bus error in zzip_disk_findfirst function in zzip/mmapped.c
(CVE-2018-6540) (Closes: #923659)
  * out of bound read in mmapped.c:zzip_disk_fread() causes crash
(CVE-2018-7725) (Closes: #913165)
  * Bus error in zip.c:__zzip_parse_root_directory() cause crash via crafted
zip file (CVE-2018-7726) (Closes: #913165)
  * Memory leak triggered in the function __zzip_parse_root_directory in zip.c
(CVE-2018-16548) (Closes: #910335)

 -- Salvatore Bonaccorso   Mon, 04 Mar 2019 22:43:14
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16548

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6381

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6484

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6540

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6541

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6869

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7725

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7726

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

Title:
  Sync zziplib 0.13.62-3.2 (main) from Debian unstable (main)

Status in zziplib package in Ubuntu:
  Fix Released

Bug description:
  Please sync zziplib 0.13.62-3.2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: invalid mem access in zzip_disk_fread
  - debian/patches/CVE-2018-6381.patch: check sizes in zzip/memdisk.c.
  - CVE-2018-6381
* SECURITY UPDATE: alignment and bus errors in __zzip_fetch_disk_trailer
  - debian/patches/CVE-2018-6484.patch: check sizes in zzip/zip.c.
  - CVE-2018-6484
  - CVE-2018-6541
  - CVE-2018-6869
* SECURITY UPDATE: bus error in zzip_disk_findfirst
  - debian/patches/CVE-2018-6540.patch: check endbuf in zzip/mmapped.c.
  - CVE-2018-6540
* SECURITY UPDATE: invalid memory dereference
  - debian/patches/CVE-2018-7725.patch: check zlib space in
zzip/memdisk.c, zzip/mmapped.c.
  - CVE-2018-7725
* SECURITY UPDATE: bus error in __zzip_parse_root_directory
  - debian/patches/CVE-2018-7726-1.patch: check rootseek and rootsize in
zzip/zip.c.
  - debian/patches/CVE-2018-7726-2.patch: check rootseek in zzip/zip.c.
  - debian/patches/CVE-2018-7726-3.patch: check zz_rootsize in
zzip/zip.c.
  - CVE-2018-7726
  All CVE fixes are now in Debian, plus one new one (for CVE-2018-16548) that 
we don't currently have.

  Changelog entries since current disco version 0.13.62-3.1ubuntu1:

  zziplib (0.13.62-3.2) unstable; urgency=medium

* Non-maintainer upload.
* Invalid memory access in zzip_disk_fread (CVE-2018-6381) (Closes: #889096)
* Reject the ZIP file and report it as corrupt if the size of the central
  directory and/or the offset of start of central directory point beyond the
  end of the ZIP file (CVE-2018-6484, CVE-2018-6541, CVE-2018-6869)
  (Closes: #889089)
* bus error in zzip_disk_findfirst function in zzip/mmapped.c
  (CVE-2018-6540) (Closes: #923659)
* out of bound read in mmapped.c:zzip_disk_fread() causes crash
  (CVE-2018-7725) (Closes: #913165)
* Bus error in zip.c:__zzip_parse_root_directory() cause crash via crafted
  zip file (CVE-2018-7726) (Closes: #913165)
* Memory leak triggered in the function __zzip_parse_root_directory in zip.c
  (CVE-2018-16548) (Closes: #910335)

   -- Salvatore Bonaccorso   Mon, 04 Mar 2019
  22:43:14 +0100

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

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

[Desktop-packages] [Bug 1819126] Re: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]

[Didier Roche]

I confirmed that 3.32.0 + trunk commits fixes the crash.

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

Title:
  gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-
  content.c:155:st_image_content_get_preferred_size: assertion failed
  (priv->width > -1): (-1 > -1)]

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1027
  https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b

  ---

  The crash happened when a new application or system crash report
  window from update-notifier showed up.

  Reproducer:
  1. sleep 1000 on one terminal
  2. kill -SIGSEGV $(pidof sleep)
  -> wait for update-notifier to try showing up apport (application crash) or 
update-notifier (system crash) windows. This can take up to 180s.

  -

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 09:32:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-05-24 (287 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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_cmpnum () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   clutter_actor_get_preferred_size () at 
/usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0
   clutter_actor_get_transformed_size () at 
/usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2019-01-08 (58 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1818246] Re: update-notifier's notification is huge due to large icon

[Didier Roche]

Ok, after some more testing with new GNOME Shell (3.32.0 + some commits 
backported), the situation has now improved when this case happens:
- there is no more icons for applications not having any appinfo, like the 
update-notifier one.
- applications with appinfo have an icon with a decent size (typically 48x48).

I think if we really want an application to have the icon showing up,
let's add then appinfo to it, otherwise, the current behaviour is fine.


** Changed in: gnome-shell (Ubuntu Disco)
   Status: Confirmed => 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/1818246

Title:
  update-notifier's notification is huge due to large icon

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

Bug description:
  I got a "update-notifier is ready" notification, with a HUGE icon
  which made the notification huge.  update-notifier is a service, so
  shouldn't be opening a window itself.  After the notification I never
  actually got a window.  Also the shell should scale the icon to a
  proper size.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Łukasz Zemczak]

@ian-gordon does this mean the fix does not work for you? I'll release
it into bionic-updates since it seems to work for others and not
introduce any regressions, but if you are still encountering issues
please open a new bug.

-- 
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: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1783298] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for cups has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: 

[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.2.7-1ubuntu2.4

---
cups (2.2.7-1ubuntu2.4) bionic; urgency=medium

  * fix-a-parsing-bug-in-the-new-authentication-code.patch,
fix-cups-auth-find-for-schemes-without-parameters.patch: Backported
authentication fixes from upstream (LP: #1783298).

 -- Till Kamppeter   Sun,  3 Mar 2019 12:28:01
+0100

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

-- 
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: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To 

[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3

[Łukasz Zemczak]

Ken: what kind of testing have you performed? What packages have you used 
during verification?
Also, it seems that the xdg-desktop-portal autopkgtests are failing for this 
upload. Could you take a look at those and see if they're not regressions?

** Changed in: xdg-desktop-portal (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

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

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

[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3

[Łukasz Zemczak]

Ah, I suppose that Andrew's comment actually points to the testing done,
I guess I got confused by one person changing the tags and another
commenting! Still, I'd like someone to take a look at the failed
autopkgtests.

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

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

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

[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco

[Sebastien Bacher]

Thanks!

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1681816] Re: [description information] some application have no description information

[Sebastien Bacher]

How is that a n-m-applet issue, what does it needs to do? (the .desktop
entry has a description entry)

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Incomplete

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

Title:
  [description information] some application have no description
  information

Status in Ubuntu Kylin:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in ukui-indicators package in Ubuntu:
  New
Status in youker-assistant package in Ubuntu:
  New

Bug description:
  [system]
  zesty-daily-0406-i386/zesty-daily-0407-amd64/zesty-final-i386/amd64

  [bug description]
  1.put the cursor on Youker weather and network in right bottom of desktop
  2.no description information shows up

  [expectation]
  all applications in panel have description information

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

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

[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

[Mitchell Clifford]

I'm using Xorg with an AMD Vega 64.  Both displays are connected to the
GPU.  My main 144hz display is connected via Display Port, and my second
60hz display is connected via HDMI.

I'm using Mesa 19.1.0-devel - padoka PPA

When I perform the test case in the first post, I get high framerates
when the secondary display is disabled, and only 60 fps when it's
enabled.

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Released
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell redraws at 60 FPS at most, regardless of the hardware
  refresh rate, and regardless of the current display mode. This is
  particularly annoying for owners of 144Hz/120Hz/240Hz displays.

  [Test Case]

  0. Find a monitor or laptop with a high refresh rate (120Hz or more),
  noting NOT to trust gnome-control-center or xrandr because an
  unrelated bug in mutter may cause those to report 120Hz even on 60Hz
  displays. Make sure the advertised hardware specs show the display is
  a high frame rate.

  1. Edit /etc/environment and add:
     CLUTTER_SHOW_FPS=1

  2. Reboot.

  3. Open a terminal window and run:
     journalctl -f | grep FPS

  4. In a new window run 'glmark2' or some other OpenGL benchmark that
  is not frame rate limited (note: glxgears for unrelated reasons IS
  frame rate limited in Wayland sessions, but can be used in Xorg
  sessions).

  5. Verify the terminal window from step 4 shows high FPS values coming
  from the journalctl log that match the hardware spec, and are much
  higher than 60.

  [Regression Potential]

  Medium to low. This patch has been used upstream and in Ubuntu 19.04
  for some months already without any issues. Although minor syntactical
  changes had to be made to avoid conflicts when backporting it from
  mutter 3.32 to mutter 3.30. If regressions did occur they would be
  visible in the frame rate of the entire screen.

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Ian McMichael]

Looking good on 18.04.1 LTS Desktop.  I have installed the patch from
comment #23 and the network icon now appears consistently on both the
status bar and the status menu.

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

Title:
  Network icons in status menu disappearing

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

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

[Sebastien Bacher]

Thank you for your bug report. What's the issue exactly? The
configuration is not restored in the session after logging? Or it it
only about the login screen? Lightdm doesn't import the session
configuration either so that's not really a workaround solution?

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

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

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

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

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

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

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver + numlockx(optionally)

  ERROR(syslog) = "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
  Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach
  VGA as primary monitor and HDMI(wireless Tx) as secondary to projector
  and then apply custom monitor positioning using g-c-c "Displays"
  panel.

  RESULT = correct positioning and working of multiple displays until
  reboot or shutdown, then--problems until HDMI cable is unseated and
  rebooted again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus

[Sebastien Bacher]

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  apps launched from gnome shell do not get input focus

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

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/gnome-shell/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek

[Efthimios Chaskaris]

I opened Ubuntu 19.04 in a VM and selected The Try Ubuntu option. The
bug is still present. This is the bug in gitlab gnome:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1079

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1079
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1079

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

Title:
  OSK Enter, space and backspace keys don't work when typing in Greek

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The enter, space and backspace keys on the Ubuntu On-screen keyboard
  don't work when typing in Greek.

  Ubuntu 18.10

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

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

[Desktop-packages] [Bug 1820439] Re: gnome-control-center crashed with SIGSEGV

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Medium => Low

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

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crash occurred while working with adding my printer.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.0.1-1ubuntu5
  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: ubuntu:GNOME
  Date: Sat Mar 16 16:51:08 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-12 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1c2ace9683:mov%rcx,0x18(%rsi)
   PC (0x7f1c2ace9683) ok
   source "%rcx" ok
   destination "0x18(%rsi)" (0x40180018) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   pango_layout_line_unref () at /lib/x86_64-linux-gnu/libpango-1.0.so.0
   () at /lib/x86_64-linux-gnu/libpango-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version

[Till Kamppeter]

Also on the Bionic VM on my main laptop I have updated network-manager
to 1.10.14 and there are no issues.

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Ian Gordon]

@sil2100 it works for me as long as I set AuthType Default for / (which
I didn't have to set before but I'm happy to set it now)

-- 
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: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[Sebastien Bacher]

Thank you for your bug report, I don't see the problem with your
screenshot ... could you be a bit more specific with the actions you
take, the result and what else you would expect?

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

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

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

Following up on #30 and #29 I can confirm that ubuntu 18.04.2 is working
fine with the patch from comment #23

Thanks a lot for the support !

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

Title:
  Network icons in status menu disappearing

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

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles

[Sebastien Bacher]

Thank you for your bug report, could you try on a recent Ubuntu verison
(maybe from a liveCD) if that's still an issue?

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

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

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Incomplete

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

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

[Desktop-packages] [Bug 1820561] Re: color picker window is not movable

[Sebastien Bacher]

Thank you for your bug report. That's still the current behaviour in
disco. The color picker is made model for the writer view and gnome-
shell does enforce the position and grey the background in those cases.
Unsure if the dialog needs to be modal though, that's a libreoffice
design decision

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

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

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

Title:
  color picker window is not movable

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  From the highlight color button on the toolbar, you Left click on
  custom color. That opens a window called "Pick a color". If you click
  on the top bar of the window, it won't let you drag the window to the
  side so you can see what colors you highlighted in your document.

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

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

[Desktop-packages] [Bug 1820560] Re: color picker hex# field only takes 5 out of 6 chars

[Sebastien Bacher]

Thank you for your bug report. That's indeed an issue in bionic but
works in disco. It might get fixed with a stable update, but doesn't
seem worth a SRU by itself otherwise

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

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

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

Title:
  color picker hex# field only takes 5 out of 6 chars

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  From the highlight color button on the toolbar, you Left click on
  custom color. That opens a window called "Pick a color". If you select
  the hex number field (which was filled with "ff"), and you type in
  6 characters, it only takes the first 5 characters because it has
  still left the last "f". It ignores your last character entered, no
  matter what character you enter, and it leaves the f in the place of
  the 6th character. So then you have to take another step to select the
  "f" and delete it, or to put the cursor at the end of the line,
  backspace over the f, and enter whatever was supposed to be the 6th
  character.

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

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

[Desktop-packages] [Bug 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()

[Sebastien Bacher]

Thank you for your bug report. That eems indeed worth fixing, it's a bit
difficult to know how sensitive the problem is without details though.
Could you provide a bit more context on the bug, maybe a way to trigger
it?

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

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

Title:
  Avoid use-after-free in _XimProtoSetIMValues()

Status in libx11 package in Ubuntu:
  New

Bug description:
  I think that the patch
  
https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad
  (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49)
  should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04
  LTS Bionic.

  Although it didn't get an explicit CVS, use-after-free scenarios
  should not get underestimated.

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

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

[Desktop-packages] [Bug 388047] Re: Rhythmbox can't create folder in MTP device

[Paul White]

No reply to comment #5 so marking tasks that did not expire as invalid
to close

** Changed in: hundredpapercuts
   Status: Incomplete => Invalid

** Changed in: rhythmbox
   Status: Incomplete => Invalid

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

Title:
  Rhythmbox can't create folder in MTP device

Status in One Hundred Papercuts:
  Invalid
Status in Rhythmbox:
  Invalid
Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  I use Rhythmbox for copy my mp3 and ogg in my Sansa Fuze but Rhythmbox
  copy directly mp3 in the parent folders. Or winamp and other player
  create a artist folder's and album folder's.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Till Kamppeter]

Ian, could you perhaps apply the patch of comment #13 and see whether
you get your problem fully solved (no need of setting AuthType Default
for /)?

-- 
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: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[shemgp]

The search bar widget is showing at the background of the path bar when
nautilus is expanded at the time when the path bar needs to be centered.

I've attached a screenshot that looks fine. Then later I'll attach a
screenshot with the bug.

** Attachment added: "Just fine"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820489/+attachment/5247254/+files/Screenshot%20from%202019-03-18%2019-50-17.png

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[shemgp]

Where the bug is showing.

** Attachment added: "Where the bug is showing"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820489/+attachment/5247255/+files/Screenshot%20from%202019-03-18%2019-50-32.png

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Treviño]

Since no regression shell-side has been reported so far and verification
has beend done with a matching kernel, I think we can safely verify this
SRU (also coming as part of GNOME upstream changes) unblocking it from
the queue.

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[shemgp]

I expect that the search bar widget won't show until I press the search
button.

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[Sebastien Bacher]

What theme and screen resolution do you use? I can't confirm that visial
glithc either using Adwaita nor Yaru (the default theme) on disco

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

[dreamcat4]

Hello again. Well this is promising news. Because I am also using xorg
with multiple monitors. And observing the same exact issue. Taking that
discussion over to the other bug then.

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Released
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell redraws at 60 FPS at most, regardless of the hardware
  refresh rate, and regardless of the current display mode. This is
  particularly annoying for owners of 144Hz/120Hz/240Hz displays.

  [Test Case]

  0. Find a monitor or laptop with a high refresh rate (120Hz or more),
  noting NOT to trust gnome-control-center or xrandr because an
  unrelated bug in mutter may cause those to report 120Hz even on 60Hz
  displays. Make sure the advertised hardware specs show the display is
  a high frame rate.

  1. Edit /etc/environment and add:
     CLUTTER_SHOW_FPS=1

  2. Reboot.

  3. Open a terminal window and run:
     journalctl -f | grep FPS

  4. In a new window run 'glmark2' or some other OpenGL benchmark that
  is not frame rate limited (note: glxgears for unrelated reasons IS
  frame rate limited in Wayland sessions, but can be used in Xorg
  sessions).

  5. Verify the terminal window from step 4 shows high FPS values coming
  from the journalctl log that match the hardware spec, and are much
  higher than 60.

  [Regression Potential]

  Medium to low. This patch has been used upstream and in Ubuntu 19.04
  for some months already without any issues. Although minor syntactical
  changes had to be made to avoid conflicts when backporting it from
  mutter 3.32 to mutter 3.30. If regressions did occur they would be
  visible in the frame rate of the entire screen.

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

-- 
Mailing list: https://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 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all

[nicola]

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

 No It isn't One Is foto the Blue Port One for green one
Il lunedì 18 marzo 2019, 04:25:37 CET, Daniel van Vugt 
 ha scritto:  
 
 *** 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
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound 
at all

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1820319

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  even under xubuntu 16.04 my rear output did not work with headphones or Trust 
usb powered 2 way speaker even the front jack of my case does not work.
  the problem persist even if I have upgraded from 16.04 to 18.04 both lts

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1709 F pulseaudio
  /dev/snd/controlC0:  hp        1709 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:39:40 2019
  InstallationDate: Installed on 2016-09-07 (918 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: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1709 F pulseaudio
  /dev/snd/controlC0:  hp        1709 F pulseaudio
  /dev/snd/seq:        timidity  1238 F timidity
  Symptom_Jack: Blue Line In, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  even under xubuntu 16.04 my rear output did not work with headphones or Trust 
usb powered 2 way speaker even the front jack of my case does not work.
  the problem persist even if I have upgraded from 16.04 to 18.04 both lts

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1709 F pulseaudio
   /dev/snd/controlC0:  hp 1709 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:39:40 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[shemgp]

I guess it doesn't show up in Yaru, but it does show up, albeit, nicely
in Adwaita.  I'm using NewAdwaita-slim and I've fixed it already this
theme by doing what Yaru does: hides it since the height can't be
changed.

Thanks for your help.

** Attachment added: "Screenshot from 2019-03-18 20-49-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820489/+attachment/5247271/+files/Screenshot%20from%202019-03-18%2020-49-36.png

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

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1820489] Re: nautilus search bar showing up when window with is expanded

[Sebastien Bacher]

So it was a theme bug? Good to know, thanks

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions

[dreamcat4]

multiple monitors on xorg
=

Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

Another user + myself have the following issue:

The slowest connected display limits the FPS. The test case we used is
over at the top of the other bug report ^^

This we found today happens with either amd vega graphics, or nvidia
pascal graphics, the vendor doesn't seem to matter. We have both seen
the same issue (xorg).

This is on 18.10, and booting into the 'Gnome (xorg)' login option. With
the FPS being logged by journalctl -f. With only single monitor
attached. Then it initially goes as high as the primary monitor can
show. (And glmark2 running in background, to maintain a continued load).
Which is 120fps for my case. Then as soon as secondary monitor is
plugged in, which is a 60hz TV. This is being plugged into the HDMI port
of the same graphics card in real time. Then the FPS logged by
'journalctl -f' drops, and becomes capped to 60hz, in the output being
printed by journalctl -f.

My setup:
kernel 5.0.0-05-lowlatency #201903032031
NVIDIA Driver for UNIX platforms  415.27 (the closed source one)
ubuntu 18.10

mutter version:

mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version
number, it seems to be that we have updated now on our client machines
the be most recent bugfix updates, kindly provided by Daniel. Which
closed the other bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
referred to, as being solved for people's single monitor scenarios.

Thanks again for the other recent bug fixes in this area, it is a nice
progress. Very helpful! We hope you can also look into this latest
problem / issue for the multiple monitor scenario.

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

Title:
  Very poor multi-monitor performance in Wayland sessions

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/3

  ---

  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

-- 
Mailing list: https://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 1814133] Re: update to openjdk 11 in 18.04 LTS

[Matthias Klose]

On 16.03.19 11:35, Goonie wrote:
> 1) It should not switch to Java 11 by force. For a LTS, this is way too
> intrusive. It breaks many parts of my build system which I specifically
> built on an LTS because it's supposed to be stable.

You misunderstand. 18.04 LTS already has OpenJDK 10 as the default.  Reverting
back to OpenJDK 8 is no option.

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

Title:
  update to openjdk 11 in 18.04 LTS

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

[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)

[Timo Aaltonen]

Please test xserver from ppa:canonical-x/x-staging

It has a patch where the server should fall back to using fb instead of
crashing. You need to uninstall x-x-v-intel and then log out and back
in, before seeing if it works or not.

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

Title:
  intel video driver not installed by default in ubuntu 19.04 (Disco)

Status in xorg package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed 
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then 
updated grub. Restarted the computer and on booting the ISO no login screen 
appeared. However,after pressing alt + ctrl + F2, logging in at command 
prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and 
unity" I was able to get to the desktop by running the command 'sudo service 
lightdm start'.  Command 'startx and X" gave xorg error saying server could not 
be connected. Command "sudo service gdm(3) start' went back to command prompt 
($).  
   This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing 
intel video driver and running startx command i was able to get to the desktop.
  Whether, "xserver-xorg-video-intel" package is not being installed by default 
in ubuntu or support for "intel core2duo processor" has been withdrawn.

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

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

[Desktop-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version

[Till Kamppeter]

Now after 3 months time for testing and no complaints coming up, Ken
VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this
SRU as verified. So I have marked this bug report appropriately.

Thanks to everyone who has tested this.

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

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

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

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

[Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab

[Olivier Tilloy]

Does this happen if you start firefox with the -safe-mode argument?

firefox -safe-mode

How do you try to open a new tab (+ button in the tabs bar, Ctrl+T
keyboard shortcut)? How does it fail?

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

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

Title:
  Firefox 66 can't open new tab

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  With the disco upgrade to firefox 66, I can't open new tabs, and the
  browser doesn't cleanly exit on closing windows.  Disabling all
  extensions does not fix, downgrading to firefox 65 does.  Safe mode
  also appears to fix, but weird that disabling extensions doesn't?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   2363 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Sat Mar 16 10:09:11 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-26 (171 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Olivier Tilloy]

I don't have the hardware to test on ppc64el. Can anyone else with such
hardware confirm?

The other commenters on the bug (Ftarkin and Pat Clash) mention x86-64
and i386, which I cannot confirm, testing on those architectures works
here. Could it be that you installed updates from the ubuntu-mozilla-
security PPA, by any chance? There was a faulty early build of
66.0+build3 in there, which I fixed last night, so if this is the case
updating again should resolve the issue. I'd appreciate if you could
confirm/refute.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails

[Olivier Tilloy]

I can successfully save the page you linked to in the description.
That's on disco, fully up-to-date, on real hardware.

Does saving the page with the Ctrl+S keyboard shortcut yield the same
problem?

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

Title:
  Saving a web page from Tom's Hardware forums fails

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  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

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Pat Clash]

Yes , I update firefox from ubuntu-mozilla-security PPA (firefox
(66.0+build3-0ubuntu0.16.04.1) xenial);

I just see that there is an other build, so I will try to update this
evening when I go home

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails

[Olivier Tilloy]

Also, can you try running firefox in safe mode and see if that makes a
difference?

firefox -safe-mode

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

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

Title:
  Saving a web page from Tom's Hardware forums fails

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  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

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

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

[Desktop-packages] [Bug 1789642] Re: Nautilus highlights new filename without focusing input field.

[Sebastien Bacher]

Thanks, that's not a bug then. When you click navigate the directories,
the focus ring around the filename entry is removed which indicates well
that the focus has been moved away to the disk navifation part of the
dialog. The filename remains selected because it makes sense to keep the
state for when you focus that wideget again. There is nothing here not
working as intended, that's not a bug

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Nautilus highlights new filename without focusing input field.

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Opening nautilus in order to save picture from e.g. browser does so
  the name of the new file is highlighted but the focus is not on the
  input field. I expect when the name is highlighted that it is also
  focused.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 14:18:08 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-03-08 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+subscriptions

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

[Desktop-packages] [Bug 1820023] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': Operation

[Olivier Tilloy]

Please try running the following command in a terminal:

sudo apt install --reinstall libreoffice-common

and let us know whether the update installed correctly. Thanks!

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

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to
  install/upgrade: unable to open
  '/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': Operation not
  permitted

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to
  install/upgrade: unable to open
  '/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': Operation not
  permitted

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Mar 14 10:38:23 2019
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial4
   Unpacking libreoffice-common (1:5.1.6~rc2-0ubuntu1~xenial6) over 
(1:5.1.6~rc2-0ubuntu1~xenial4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_1%3a5.1.6~rc2-0ubuntu1~xenial6_all.deb
 (--unpack):
unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2016-04-28 (1050 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to 
install/upgrade: unable to open 
'/usr/lib/libreoffice/share/gallery/sg36.sdv.dpkg-new': Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()

[Matthias Dieter Wallnöfer]

Unfortunately I just stumbled over this commit by accident since I
checked the commit log of libX11. So for a reproduction we would need to
contact the original reporter Sami Farin
(https://bugs.freedesktop.org/show_bug.cgi?id=93186) but I do not find
any valid email address from him.

** Bug watch added: freedesktop.org Bugzilla #93186
   https://bugs.freedesktop.org/show_bug.cgi?id=93186

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

Title:
  Avoid use-after-free in _XimProtoSetIMValues()

Status in libx11 package in Ubuntu:
  New

Bug description:
  I think that the patch
  
https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad
  (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49)
  should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04
  LTS Bionic.

  Although it didn't get an explicit CVS, use-after-free scenarios
  should not get underestimated.

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

-- 
Mailing list: https://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 1820489] Re: nautilus search bar showing up when window with is expanded

[shemgp]

Let's just say it's a nautilus feature that should be fixed by themes that
make the height of the header bar smaller.

On Mon, Mar 18, 2019 at 9:30 PM Sebastien Bacher 
wrote:

> So it was a theme bug? Good to know, thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1820489
>
> Title:
>   nautilus search bar showing up when window with is expanded
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820489/+subscriptions
>

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-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
  CurrentDesktop: GNOME
  Date: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1745105] Re: Make "Revert (Display) settings" the default option

[Sebastien Bacher]

Note that 'enter' seems to validate the change on windows as well. Using
Esc does undo the change though, which can be used even if your screen
isn't working

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

Title:
  Make "Revert (Display) settings" the default option

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

Bug description:
  In Display settings, the default option when changes the configuration is 
"keep changes".
  If there is a problem and you can NOT see the message, if you press "Intro" 
(accidently or because you don't know what to do) is going to keep the change 
so you are going to be in troubles.

  Should not be "Revert settings" the default option?

  System:
  Ubuntu 17.10
  GNOME Shell 3.26.2

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

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

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

[Andreas Schildbach]

@Matthias: The current Gradle 3.4.1 doesn't requre Java 10 or 11. It
runs fine with Java 8, and the declared package dependencies also
reflects that.

For an LTS, I'm suggesting to keep the compatiblity to Java 8,
especially since upstream Gradle works fine with Java 8 (even the
current version). I did *not* suggest to revert the JDK default.

Tiago has updated bug 1820389 with more insight about the issue.

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

Title:
  update to openjdk 11 in 18.04 LTS

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

[Desktop-packages] [Bug 1816264] Re: software center stuck on Chrome package dialog

[Sebastien Bacher]

How do you call gnome-software? Here when closing and re-opening it
displays the main screen and not the previously open page. Could you add
your journalctl log after getting the issue?

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

Title:
  software center stuck on Chrome package dialog

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 18.10 with Wayland in a fresh VM. I configured the
  VM to use Wayland, downloaded Google Chrome from
  https://google.com/chrome, installed Chrome by opening the package
  with Ubuntu Software Center and pressing the install button, and
  closed Ubuntu Software Center. Now, when I open Ubuntu Software Center
  again, I see a dialog with title "google-chrome-stable" (the package
  name) and some information about the package. The dialog has something
  that looks like a "back" button in the top-left corner, but clicking
  it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu5
  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: Sat Feb 16 22:35:53 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu5
  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/1816264/+subscriptions

-- 
Mailing list: https://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 1820413] Re: Firefox 66 can't open new tab

[Joe Barnett]

there is no + button in the tab bar (actually the tab bar doesn't even show
the current tab).  Ctrl + T does nothing, control + click on link does
nothing.  opening eg, preferences from the hamburger menu (which usually
tries to open in a new tab) does nothing.  safe mode does work, but
disabling/removing all extensions does not.  fresh profile works, and
installing all the same extensions to the fresh profile still works.

On Mon, Mar 18, 2019 at 7:35 AM Olivier Tilloy 
wrote:

> Does this happen if you start firefox with the -safe-mode argument?
>
> firefox -safe-mode
>
> How do you try to open a new tab (+ button in the tabs bar, Ctrl+T
> keyboard shortcut)? How does it fail?
>
> ** Changed in: firefox (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1820413
>
> Title:
>   Firefox 66 can't open new tab
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions
>

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

Title:
  Firefox 66 can't open new tab

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  With the disco upgrade to firefox 66, I can't open new tabs, and the
  browser doesn't cleanly exit on closing windows.  Disabling all
  extensions does not fix, downgrading to firefox 65 does.  Safe mode
  also appears to fix, but weird that disabling extensions doesn't?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   2363 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Sat Mar 16 10:09:11 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-26 (171 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

[Chris Rainey]

** Description changed:

  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
  screensaver + numlockx(optionally)
  
- ERROR(syslog) = "Failed to get current display configuration state:
- GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
- "org.gnome.Mutter.DisplayConfig" does not exist"
+ TL;DR
+ 
+ After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
+ monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting
+ a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K
+ projector and then configuring the logical monitor layout in the
+ "Displays" settings dialog, I can successfully create and use a multi
+ monitor setup in my current session. However, upon a reboot or power
+ cycle of the computer and a successful login from GDM(gdm3), the HDMI
+ goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even
+ though I set it as 'Primary' in the "Displays" dialog. The monitors.xml
+ file, attached, shows the correct layout and survives the reboot without
+ alteration. I am unable to see anything on the 'Primary' display, which
+ has incorrectly been given to the  HDMI projector. Unseating the HDMI
+ cable does not restore the VGA to 'Primary' display automatically and I
+ must reboot the computer while leaving the HDMI unplugged in order to
+ restore my ability to see the 'Primary' display on the VGA connection.
+ Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is
+ repeatedly provable through multiple reboots or changes to the logical
+ layout of the screens in the 'Displays' settings of gnome-control-
+ center.
+ 
+ 
+ ERROR(syslog) = "Failed to get current display configuration state: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
"org.gnome.Mutter.DisplayConfig" does not exist"
  
  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17
  
  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
  Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA
  as primary monitor and HDMI(wireless Tx) as secondary to projector and
  then apply custom monitor positioning using g-c-c "Displays" panel.
  
  RESULT = correct positioning and working of multiple displays until
- reboot or shutdown, then--problems until HDMI cable is unseated and
- rebooted again.
+ reboot or shutdown and then subsequent login from gdm3, then--problems
+ until HDMI cable is unseated and rebooted again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

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

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver + numlockx(optionally)

  TL;DR

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a 4K projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session. However, upon a reboot or power
  cycle of the computer and a successful login from GDM(gdm3), the HDMI
  goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor
  even though I set it as 'Primary' in the "Displays" dialog. The
  monitors.xml file, attached, shows the correct layout and survives the
  reboot without alteration. I am unable to see anything on the
  'Primary' display, which has incorrectly been given to the  HDMI
  projector. Unseating the HDMI cable does not restore the VGA to
  'Primary' display automatically and I must reboot the computer while
  leaving the HDMI unplugged in order to restore my ability to see the
  'Primary' display on the VGA connection. Replacing GDM(gdm3) wit

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

[Chris Rainey]

@seb128 I have edited the bug description to provide more information on
how the issue is triggered. The bug occurs during the handoff of gdm3
---> gnome-shell(mutter?) _after_ login. The issue is repeatedly and
consistently triggered until GDM(gdm3) is replaced by LightDM(slick-
greeter) and then the issues disappears completely and the system is
works across multiple reboots or changes to the monitors.xml through the
"Displays" settings.

This is clearly related to how GDM appears to set-up or create the user
session and I would be glad to test any ideas you have to solve it while
using GDM, however---after 4-hours of messing with it, I had to go with
a solution that "Just Works":  slick-greeter or lightdm.

Please let me know what else I can provide or do to clarify this issue.

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

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

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver + numlockx(optionally)

  TL;DR

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a 4K projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session. However, upon a reboot or power
  cycle of the computer and a successful login from GDM(gdm3), the HDMI
  goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor
  even though I set it as 'Primary' in the "Displays" dialog. The
  monitors.xml file, attached, shows the correct layout and survives the
  reboot without alteration. I am unable to see anything on the
  'Primary' display, which has incorrectly been given to the  HDMI
  projector. Unseating the HDMI cable does not restore the VGA to
  'Primary' display automatically and I must reboot the computer while
  leaving the HDMI unplugged in order to restore my ability to see the
  'Primary' display on the VGA connection. Replacing GDM(gdm3) with
  LightDM(slick-greeter) fixes the issue and is repeatedly provable
  through multiple reboots or changes to the logical layout of the
  screens in the 'Displays' settings of gnome-control-center.

  
  ERROR(syslog) = "Failed to get current display configuration state: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
"org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
  Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach
  VGA as primary monitor and HDMI(wireless Tx) as secondary to projector
  and then apply custom monitor positioning using g-c-c "Displays"
  panel.

  RESULT = correct positioning and working of multiple displays until
  reboot or shutdown and then subsequent login from gdm3, then--problems
  until HDMI cable is unseated and rebooted again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

[Chris Rainey]

** Description changed:

  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
  screensaver + numlockx(optionally)
  
  TL;DR
  
  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting
  a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K
  projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session. However, upon a reboot or power
  cycle of the computer and a successful login from GDM(gdm3), the HDMI
  goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even
  though I set it as 'Primary' in the "Displays" dialog. The monitors.xml
  file, attached, shows the correct layout and survives the reboot without
  alteration. I am unable to see anything on the 'Primary' display, which
  has incorrectly been given to the  HDMI projector. Unseating the HDMI
  cable does not restore the VGA to 'Primary' display automatically and I
  must reboot the computer while leaving the HDMI unplugged in order to
  restore my ability to see the 'Primary' display on the VGA connection.
  Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is
  repeatedly provable through multiple reboots or changes to the logical
  layout of the screens in the 'Displays' settings of gnome-control-
  center.
  
- 
- ERROR(syslog) = "Failed to get current display configuration state: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
"org.gnome.Mutter.DisplayConfig" does not exist"
+ ERRORS(syslog) = "Failed to get current display configuration state:
+ GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
+ "org.gnome.Mutter.DisplayConfig" does not exist"
  
  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17
  
  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
  Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA
  as primary monitor and HDMI(wireless Tx) as secondary to projector and
  then apply custom monitor positioning using g-c-c "Displays" panel.
  
  RESULT = correct positioning and working of multiple displays until
- reboot or shutdown and then subsequent login from gdm3, then--problems
- until HDMI cable is unseated and rebooted again.
+ reboot or shutdown and then subsequent login from gdm3. HDMI
+ monitor(projector) goes blank and the VGA monitor only shows 'Secondary'
+ monitor screen without any user visible controls or windows as they are
+ all being painted to the now blanked 'Primary' HDMI connected display.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

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

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver + numlockx(optionally)

  TL;DR

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a 4K projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session. However, upon a reboot or power
  cycle of the computer and a successful login from GDM(gdm3), the HDMI
  goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor
  even though I set it as 'Primary' in the "Displays" dialog. The
  monitors.xml file, attached, shows the correct layout and survives the
  reboot without alteration. I am unable to see anything on the
  'Primary' display, which has incorrectly been given to the  HDMI
  projector. Unseating the HDMI cable does not restore the VGA to
  'Primary

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Olivier Tilloy]

Thanks for the confirmation Pat.
Please note the description of the PPA:

 « Staging PPA for Mozilla and other browser-related security updates.
Unless you are testing updates, you should not install packages from
this PPA »

So in general it is not recommended to use that PPA, you should wait to
get the updates through the -security channel.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab

[Olivier Tilloy]

That sounds like a corrupted profile. Not sure how or why, though. I
would advise to start afresh with a new profile.

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

Title:
  Firefox 66 can't open new tab

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  With the disco upgrade to firefox 66, I can't open new tabs, and the
  browser doesn't cleanly exit on closing windows.  Disabling all
  extensions does not fix, downgrading to firefox 65 does.  Safe mode
  also appears to fix, but weird that disabling extensions doesn't?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   2363 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Sat Mar 16 10:09:11 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-26 (171 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

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

[Amr Ibrahim]

Bug #1820650 Preferences window fails to open in jabref
3.8.2+ds-12~18.04 from bionic-proposed.

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

Title:
  update to openjdk 11 in 18.04 LTS

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

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

[Sebastien Bacher]

The previous has the right color onces 1.15.12-1ubuntu0.1 installed on
cosmic, marked cosmic verified as well now

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

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

Title:
  Evince displays pdf file fine, but prints colors inverted

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

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

[Chris Rainey]

** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #474
   https://gitlab.gnome.org/GNOME/gdm/issues/474

** Also affects: gdm via
   https://gitlab.gnome.org/GNOME/gdm/issues/474
   Importance: Unknown
   Status: Unknown

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

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

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver + numlockx(optionally)

  TL;DR

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a 4K projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session. However, upon a reboot or power
  cycle of the computer and a successful login from GDM(gdm3), the HDMI
  goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor
  even though I set it as 'Primary' in the "Displays" dialog. The
  monitors.xml file, attached, shows the correct layout and survives the
  reboot without alteration. I am unable to see anything on the
  'Primary' display, which has incorrectly been given to the  HDMI
  projector. Unseating the HDMI cable does not restore the VGA to
  'Primary' display automatically and I must reboot the computer while
  leaving the HDMI unplugged in order to restore my ability to see the
  'Primary' display on the VGA connection. Replacing GDM(gdm3) with
  LightDM(slick-greeter) fixes the issue and is repeatedly provable
  through multiple reboots or changes to the logical layout of the
  screens in the 'Displays' settings of gnome-control-center.

  ERRORS(syslog) = "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
  Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach
  VGA as primary monitor and HDMI(wireless Tx) as secondary to projector
  and then apply custom monitor positioning using g-c-c "Displays"
  panel.

  RESULT = correct positioning and working of multiple displays until
  reboot or shutdown and then subsequent login from gdm3. HDMI
  monitor(projector) goes blank and the VGA monitor only shows
  'Secondary' monitor screen without any user visible controls or
  windows as they are all being painted to the now blanked 'Primary'
  HDMI connected display.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804744] Re: Restoring from new location does not find backup files

[Sebastien Bacher]

Cosmic indeed fails to restore the backup with the described steps, it
does work after installing 38.0-1ubuntu0.1 from proposed, marking cosmic
verified

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

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

Title:
  Restoring from new location does not find backup files

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Bionic:
  Fix Released
Status in deja-dup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When a user tries to restore a backup on a fresh Ubuntu install, deja-
  dup will not be able to find their backup at first.

  A workaround is to set the current backup location on the fresh
  install to the old backup location. But that's not at all an obvious
  path. A user would not normally try that.

  [Test Case]

  1. Back up some files to a temporary dir.
  2. gsettings reset-recursively org.gnome.DejaDup
  3. Try to restore from that temporary dir.

  Notice that deja-dup will complain about waiting for Google Drive to
  be set up (even though your backup drive has nothing to do with
  Google).

  [Regression Potential]

  The proposed patch mostly affects the restore dialog. Any regressions
  would likely be in that flow.

  [Original Report]

  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ethan-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ethan-laptop'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ethan-laptop'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ethan-laptop'
  org.gnome.DejaDup.Local folder '/media/ethan/porta_500gb/m1330'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ethan-laptop'
  org.gnome.DejaDup.Drive uuid '1919a422-d154-4e19-b551-f74b56cf1f0e'
  org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk 
drive'
  org.gnome.DejaDup.Drive folder 'm1330'
  org.gnome.DejaDup.Drive name 'porta_500gb'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ethan-laptop'
  org.gnome.DejaDup.GOA type 'google'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

To

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

[Amr Ibrahim]

Bug #1807602 Scilab does not start on disco and bionic-proposed.

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

Title:
  update to openjdk 11 in 18.04 LTS

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

** Description changed:

+ [Impact]
+ 
+  * The new modemmanager package adds DW5820e support.
+  * This modemmanager version is needed to support new devices.
+ 
+ [Test Case]
+ 
+  * install modemmanager, libmbim, and libqmi from -proposed
+  * reboot and try WWAN function to see if any regression there.
+  * perform general dogfooding of its reverse dependencies (network-
+manager, gnome-control-center etc.)
+ 
+ [Regression Potential]
+ 
+  * The package comes from Zesty and should not have regression there.
+  * Every new upstream release can potentially break existing dependencies 
+if any of the required features have been changed/removed, so besides 
+regular testing a general dogfooding session with the new modemmanager 
+is advised.
+ 
+ [Original Description]
+ 
  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  In Progress
Status in libqmi source package in Bionic:
  In Progress
Status in modemmanager source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
 manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies 
 if any of the required features have been changed/removed, so besides 
 regular testing a general dogfooding session with the new modemmanager 
 is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1820685] [NEW] Wrong resolution during boot

[Bart van Pelt]

Public bug reported:

When booting the startup screen is in low resolution while before it was
in high resolution.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 18:04:57 2019
DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
InstallationDate: Installed on 2018-01-04 (437 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. CM6870
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
dmi.bios.date: 12/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0708
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM6870
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: CM6870
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Sep 26 20:09:04 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: nouveau

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


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

Title:
  Wrong resolution during boot

Status in xorg package in Ubuntu:
  New

Bug description:
  When booting the startup screen is in low resolution while before it
  was in high resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 18:04:57 2019
  DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
  InstallationDate: Installed on 2018-01-04 (437 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chas

[Desktop-packages] [Bug 1820683] Re: [disco-proposed] The new version came out on 13/03 and we still have not received an update.

[Edson José dos Santos]

The new version came out on 13/03 and we still have not received an
update. See attachments.

** Attachment added: "The new version came out on 13/03 and we still have not 
received an update. See attachments."
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820683/+attachment/5247315/+files/Captura%20de%20tela%20de%202019-03-18%2014-10-56.png

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

Title:
  [disco-proposed] The new version came out on 13/03 and we still have
  not received an update.

Status in nautilus package in Ubuntu:
  New

Bug description:
  The new version came out on 13/03 and we still have not received an
  update. See attachments.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-1ubuntu2
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 14:06:26 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'193'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(884, 464)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2019-02-11 (34 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1820683] [NEW] [disco-proposed] The new version came out on 13/03 and we still have not received an update.

[Edson José dos Santos]

Public bug reported:

The new version came out on 13/03 and we still have not received an
update. See attachments.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.31.90-1ubuntu2
Uname: Linux 5.0.1-050001-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 14:06:26 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'193'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(884, 464)'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2019-02-11 (34 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug disco

** Attachment added: "The new version came out on 13/03 and we still have not 
received an update. See attachments."
   
https://bugs.launchpad.net/bugs/1820683/+attachment/5247309/+files/Captura%20de%20tela%20de%202019-03-18%2013-55-26.png

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

Title:
  [disco-proposed] The new version came out on 13/03 and we still have
  not received an update.

Status in nautilus package in Ubuntu:
  New

Bug description:
  The new version came out on 13/03 and we still have not received an
  update. See attachments.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-1ubuntu2
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 14:06:26 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'193'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(884, 464)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2019-02-11 (34 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.6.3

---
ubuntu-drivers-common (1:0.6.3) disco; urgency=medium

  [ Jean-Baptiste Lallement ]
  * ubuntu-drivers,
UbuntuDrivers/detect.py,
tests/ubuntu_drivers.py:
- Add a --free-only parameter, so as to allow installing only the
 available free drivers (LP: #1819207).
- Add support for testing against a fake archive with free and
  non-free components.

 -- Alberto Milone   Mon, 18 Mar 2019
16:20:49 +0100

** Changed in: ubuntu-drivers-common (Ubuntu Disco)
   Status: In Progress => 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:
  Triaged
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:
  Triaged
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 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Jo Shields]

I'm not certain about the fine detail, but looking at the relevant build
logs:

https://launchpadlibrarian.net/411366522/buildlog_ubuntu-xenial-ppc64el.firefox_65.0.1+build2-0ubuntu0.16.04.1_BUILDING.txt.gz
https://launchpadlibrarian.net/411366844/buildlog_ubuntu-xenial-amd64.firefox_65.0.1+build2-0ubuntu0.16.04.1_BUILDING.txt.gz

There's definitely something different about how they're building
build/unix/stdc++compat/stdc++compat.cpp, the library which is supposed
to handle hiding the libstdc++ ABI issues.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

[Josua Dietze]

Correction:

The mode that Huawei calls "HiLink" is No.1, not No.2.

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

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Triaged
Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G4
  dmi.product.sku: X3T22AV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook

[Desktop-packages] [Bug 1820691] [NEW] WSL give error in installing (required for openfoam installtion)

[mehul]

Public bug reported:

To use OpenFOAM in windows I have to install OpenFOAM in WSL(windows
subsystem for Linux)

OpenFOAM is highly depended on libXt-dev version 1.1.5_1, while direct
installing it from the terminal or from synaptic package manager it
gives me a hash mismatch error.

so I try to install it with downloading .deb file from the Ubuntu
repository but it gives me a lzma error telling that archive is corrupt.

so please help to install these packages; so, I can install OpenFOAM and
continue my work.

Thanks.

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

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

Title:
  WSL give error in installing (required for openfoam installtion)

Status in libxt package in Ubuntu:
  New

Bug description:
  To use OpenFOAM in windows I have to install OpenFOAM in WSL(windows
  subsystem for Linux)

  OpenFOAM is highly depended on libXt-dev version 1.1.5_1, while direct
  installing it from the terminal or from synaptic package manager it
  gives me a hash mismatch error.

  so I try to install it with downloading .deb file from the Ubuntu
  repository but it gives me a lzma error telling that archive is
  corrupt.

  so please help to install these packages; so, I can install OpenFOAM
  and continue my work.

  Thanks.

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

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

[Desktop-packages] [Bug 1820690] [NEW] Ibus unikey not start with ibus after log in

[Quan Duong]

Public bug reported:

I'm running: 
Ubuntu 18.04.2 Gnome 3.28.
Ibus-unkey 0.6.1-1.1

The problem happen when login from the lock screen, vietnamese ibus
disappear on the system tray and I cannot switch to it. To get it back,
I need to start typing something on any input or text editor, then the
vietnamese ibus shows again for selecting.

** Affects: ibus-unikey (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ibus unikey not start with ibus after log in

Status in ibus-unikey package in Ubuntu:
  New

Bug description:
  I'm running: 
  Ubuntu 18.04.2 Gnome 3.28.
  Ibus-unkey 0.6.1-1.1

  The problem happen when login from the lock screen, vietnamese ibus
  disappear on the system tray and I cannot switch to it. To get it
  back, I need to start typing something on any input or text editor,
  then the vietnamese ibus shows again for selecting.

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

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

[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

[Anonymous]

I can confirm kernel 4.18.10 there is no flickering.

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Jo Shields]

builder@xam-power8-1:~$ uname -m
ppc64le
builder@xam-power8-1:~$ objdump -T /usr/lib/firefox/libxul.so | grep 
GLIBCXX_3.4.22
  DF *UND*    GLIBCXX_3.4.22 
_ZNSt6thread15_M_start_threadESt10unique_ptrINS_6_StateESt14default_deleteIS1_EEPFvvE
  DF *UND*    GLIBCXX_3.4.22 
_ZNSt6thread6_StateD2Ev

vs

root@breakfast:/# uname -m
x86_64
root@breakfast:/# objdump -T /usr/lib/firefox/libxul.so | grep GLIBCXX_3.4.22

The mangling of
std::thread::_M_start_thread(std::unique_ptr >, void (*)()) and
std::thread::_State::~_State() is supposed to be handled by the block in
build/unix/stdc++compat/stdc++compat.cpp starting at line 104:

#if MOZ_LIBSTDCXX_VERSION >= GLIBCXX_VERSION(3, 4, 21)
/* Expose the definitions for the old ABI, allowing us to call its functions */
#  define _GLIBCXX_THREAD_ABI_COMPAT 1
#  include 

namespace std {
/* The old ABI has a thread::_M_start_thread(shared_ptr<_Impl_base>),
 * while the new has thread::_M_start_thread(unique_ptr<_State>, void(*)()).
 * There is an intermediate ABI at version 3.4.21, with
 * thread::_M_start_thread(shared_ptr<_Impl_base>, void(*)()).
 * The void(*)() parameter is only there to keep a reference to pthread_create
 * on the caller side, and is unused in the implementation
 * We're creating an entry point for the new and intermediate ABIs, and make
 * them call the old ABI. */

__attribute__((weak)) void thread::_M_start_thread(shared_ptr<_Impl_base> impl,
   void (*)()) {
  _M_start_thread(std::move(impl));
}

#  if MOZ_LIBSTDCXX_VERSION >= GLIBCXX_VERSION(3, 4, 22)
/* We need a _Impl_base-derived class wrapping a _State to call the old ABI
 * from what we got by diverting the new API */
struct StateWrapper : public thread::_Impl_base {
  unique_ptr mState;

  StateWrapper(unique_ptr aState) :
mState(std::move(aState)) {}

  void _M_run() override { mState->_M_run(); }
};

__attribute__((weak)) void thread::_M_start_thread(unique_ptr<_State> aState,
   void (*)()) {
  auto impl = std::make_shared(std::move(aState));
  _M_start_thread(std::move(impl));
}

/* For some reason this is a symbol exported by new versions of libstdc++,
 * even though the destructor is default there too */
__attribute__((weak)) thread::_State::~_State() = default;
#  endif
}  // namespace std
#endif

I don't know what's broken in the build process causing this code not to
be included in ppc64el builds.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores o

[Desktop-packages] [Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails

[Jani Uusitalo]

Tested all combinations of both (Ctrl-s/context menu in safe mode and
normal mode), all with the same results. Could this be locale-dependent?
The UI is in English in safe mode though, so I'm guessing safe mode
should be locale-independent, as I'm on fi_FI.UTF-8 otherwise.

And just to clarify: my testing of Bionic was on real hardware as well,
and I ran these latest tests on Cosmic on another computer (real
hardware).

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

Title:
  Saving a web page from Tom's Hardware forums fails

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  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

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

** Description changed:

  [Impact]
  
-  * The new modemmanager package adds DW5820e support.
-  * This modemmanager version is needed to support new devices.
+  * The new modemmanager package adds DW5820e support.
+  * This modemmanager version is needed to support new devices.
  
  [Test Case]
  
-  * install modemmanager, libmbim, and libqmi from -proposed
-  * reboot and try WWAN function to see if any regression there.
-  * perform general dogfooding of its reverse dependencies (network-
-manager, gnome-control-center etc.)
+  * install modemmanager, libmbim, and libqmi from -proposed
+  * reboot and try WWAN function to see if any regression there.
+  * perform general dogfooding of its reverse dependencies (network-
+    manager, gnome-control-center etc.)
  
  [Regression Potential]
  
-  * The package comes from Zesty and should not have regression there.
-  * Every new upstream release can potentially break existing dependencies 
-if any of the required features have been changed/removed, so besides 
-regular testing a general dogfooding session with the new modemmanager 
-is advised.
+  * The package comes from Disco and should not have regression there.
+  * Every new upstream release can potentially break existing dependencies
+    if any of the required features have been changed/removed, so besides
+    regular testing a general dogfooding session with the new modemmanager
+    is advised.
  
  [Original Description]
  
  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  In Progress
Status in libqmi source package in Bionic:
  In Progress
Status in modemmanager source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Jean-Baptiste Lallement]

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

** Changed in: ubiquity (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: ubiquity (Ubuntu Disco)
Milestone: None => ubuntu-19.04

** Changed in: ubuntu-drivers-common (Ubuntu Disco)
Milestone: None => ubuntu-19.04

-- 
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:
  In Progress
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:
  In Progress
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 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Pat Clash]

Issue fixed by the latest PPA : firefox (66.0+build3-0ubuntu0.16.04.2)
xenial

Yes I use PPA because I would have the latest version from Mozilla
(Firefox and Thunderbird)

I test also the beta channel directly from Mozilla

;)

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1820743] [NEW] Pulseaudio is sometimes broken after resume from suspend

[Pedro Côrte-Real]

Public bug reported:

Sometimes when resuming from suspend pulseaudio is broken and only the
dummy output is available. After "pulseaudio -k" audio again works.
Here's what I found in the logs:

$ journalctl --since "1 day ago" | grep pulseaudio
Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.

--- Here I ran pulseaudio -k ---

Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed 
to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26616]: [pulseaudio] pid.c: Daemon already 
running.


The "Failed to create sink input" seems to happen on every resume but only some 
times does it actually break. Don't know if the ofono message is related or not.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Mar 18 19:11:09 2019
InstallationDate: Installed on 2018-05-31 (291 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

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

Title:
  Pulseaudio is sometimes broken after resume from suspend

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from suspend pulseaudio is broken and only the
  dummy output is available. After "pulseaudio -k" audio again works.
  Here's what I found in the logs:

  $ journalctl --since "1 day ago" | grep pulseaudio
  Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
  Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.

  --- Here I ran pulseaudio -k ---

  Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
  Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already 
run

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Jo Shields]

@patclash I don't see any fix in the PPA package?

builder@xam-power8-1:/tmp$ dpkg -x 
firefox_66.0+build3-0ubuntu0.16.04.2_ppc64el.deb test/
builder@xam-power8-1:/tmp$ objdump -T /tmp/test/usr/lib/firefox/libxul.so | 
grep GLIBCXX_3.4.22
  DF *UND*    GLIBCXX_3.4.22 
_ZNSt6thread15_M_start_threadESt10unique_ptrINS_6_StateESt14default_deleteIS1_EEPFvvE
  DF *UND*    GLIBCXX_3.4.22 
_ZNSt6thread6_StateD2Ev

The lack of stdc++compat handling on ppc64el seems untouched.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Joachim R.]

Hello, 
what is needed for the fix to land in ubuntu's duplicity package ? This bug has 
bee fixed mainstream and the fix is available in other distro, so if any help 
needed, please tell me where to start.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Committed
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Pat Clash]

@Jo Shields I don't knowwhat was wrong;

After the Friday update my Firefox don't start ;
I try to start it from Terminal and I got the error message that I googled with 
a link for this bug

I am only a (advanced) user , not a developer (I don't know how to debug
for example)

With the today PPA update , Firefox start as normal and run perfectly ;)

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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