[Desktop-packages] [Bug 1804158] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Nov 20 08:24:43 2018
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-11 (587 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-07-26 (116 days ago)

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

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

[Desktop-packages] [Bug 1804158] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Mollier]

Public bug reported:

package tex-common 6.09 failed to install/upgrade: installed tex-common
package post-installation script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Nov 20 08:24:43 2018
ErrorMessage: installed tex-common package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-04-11 (587 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: installed tex-common 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-07-26 (116 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Nov 20 08:24:43 2018
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-11 (587 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-07-26 (116 days ago)

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

[Andras Veto]

Update: when I tried locking the screen while mirroring my laptop and
external monitor, it failed (needed to be locked twice, dock
disappeared, etc.). When extending the displays, locking works
correctly.

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

Title:
  Lock screen doesn't hide the screen contents

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

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

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1803807/+subscriptions

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

[Desktop-packages] [Bug 1803504] Re: Screen stops redrawing sometimes when moving windows

[Tedesco]

Daniel, thank you very much, it was a pleasure to help a little bit.

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

Title:
  Screen stops redrawing sometimes when moving windows

Status in gnome-shell package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Moving a window, on the bottom of screen there is a zone of 2 or 3 cm you 
can't pas the window.
  The down movement is blocked and the mouse cursor with the closed hand moves 
down into the inner window area. When you try to move the window ones again 
upwards you will see a broken graphic part of the window as background and the 
graphic structure of the window get lost. All these movements with the left 
mouse bottom pressed.
  But:
  If you move first the window to the left border and forward out of the screen 
area you can move the window down without the graphic problem. If at least a 
small part of the window is outside of the left screen area you can move the 
window up again passing through the bottom zone of 2 or 3 cm without problems.
  On the right-hand side of the screen area these movements are impossible.

  A big problem you will have with a windows virtual machine in full screen 
mode.
  You can't use the bottom menu.

  (This week y made the upgrade from 16.04.n to 18.04.1 with big graphic 
problems, black screen etc.
  Then reinstall gnome from command line solved the problems with black screen.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 08:07:37 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 0a) (prog-if 00 [VGA controller])
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
  InstallationDate: Installed on 2016-03-17 (972 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 360
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.96+git1811120630.e642f4~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1811141930.e13dd7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1811141930.e13dd7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1811071935.5e6fa5~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1811140735.746ab3~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b
  xserver.bootTime: Wed Nov 14 13:05:37 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard Hub KEYBOARD, id 8
   inputDell Dell USB Keyboard Hub KEYBOARD, id 9
   inputMicrosoft Basic Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[A Raghuram]

Updated to mutter 3.28.3-2~ubuntu18.04.2.  Works fine with wayland
enabled on my desktop with Intel® Core™2 CPU 6400 @ 2.13GHz × 2
processor and Intel® G33 Graphics.  Great !!

Thanks to all involved in solving this issue.

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1804134] Re: LibreOffice Writer Won't Run on Pentium-4 32-bit Computer

[Olivier Tilloy]

That's very likely a duplicate of bug #1699772.

To confirm this, can you run the following command in a terminal:

sed -i '/enabled/c\false<\/enabled>'
~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

Then execute libreoffice writer and let me know if the crash is still
happening? Thanks!


[For the record, that command disables the JRE (Java Runtime Environment) in 
libreoffice, which is known to cause crashes on 32bits processors. Some 
functions of libreoffice won't work without Java (the most visible probably 
being libreoffice base), but most of the office suite should work just fine.]

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

Title:
  LibreOffice Writer Won't Run on Pentium-4 32-bit Computer

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  On a Dell GX-270 (Intel 32-bit) computer running Lubuntu 18.04, I can
  run LibreOffice, but when I select LibreOffice Writer the LibreOffice
  window disappears, and nothing happens, as if the application just
  terminated normally, without doing anything.

  An AppPort window reporting an error appeared, but when I clicked its
  "Send" button, the window disappeared without doing anything.

  If I run LibreOffice Writer directly from the menu, I get a frame of
  its window (with nothing filled-in inside), which persists for awhile,
  and then disappears.

  In either case, no error message appears, and nothing further happens.

  LibreOffice Calc, on the other hand, appears to run, though I haven't
  tried any spreadsheet using it.

  I expected LibreOffice Writer to initialize, and then use it for
  editing documents (as it did on Lubuntu 16.04), but the LibreOffice
  Writer window disappeared.

  The same problem occurred on a Dell GX-260 computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Nov 19 21:48:52 2018
  InstallationDate: Installed on 2018-06-24 (148 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804134] [NEW] LibreOffice Writer Won't Run on Pentium-4 32-bit Computer

[Aere Greenway]

Public bug reported:

On a Dell GX-270 (Intel 32-bit) computer running Lubuntu 18.04, I can
run LibreOffice, but when I select LibreOffice Writer the LibreOffice
window disappears, and nothing happens, as if the application just
terminated normally, without doing anything.

An AppPort window reporting an error appeared, but when I clicked its
"Send" button, the window disappeared without doing anything.

If I run LibreOffice Writer directly from the menu, I get a frame of its
window (with nothing filled-in inside), which persists for awhile, and
then disappears.

In either case, no error message appears, and nothing further happens.

LibreOffice Calc, on the other hand, appears to run, though I haven't
tried any spreadsheet using it.

I expected LibreOffice Writer to initialize, and then use it for editing
documents (as it did on Lubuntu 16.04), but the LibreOffice Writer
window disappeared.

The same problem occurred on a Dell GX-260 computer.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic i686
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: i386
CurrentDesktop: LXDE
Date: Mon Nov 19 21:48:52 2018
InstallationDate: Installed on 2018-06-24 (148 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic i386

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

Title:
  LibreOffice Writer Won't Run on Pentium-4 32-bit Computer

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On a Dell GX-270 (Intel 32-bit) computer running Lubuntu 18.04, I can
  run LibreOffice, but when I select LibreOffice Writer the LibreOffice
  window disappears, and nothing happens, as if the application just
  terminated normally, without doing anything.

  An AppPort window reporting an error appeared, but when I clicked its
  "Send" button, the window disappeared without doing anything.

  If I run LibreOffice Writer directly from the menu, I get a frame of
  its window (with nothing filled-in inside), which persists for awhile,
  and then disappears.

  In either case, no error message appears, and nothing further happens.

  LibreOffice Calc, on the other hand, appears to run, though I haven't
  tried any spreadsheet using it.

  I expected LibreOffice Writer to initialize, and then use it for
  editing documents (as it did on Lubuntu 16.04), but the LibreOffice
  Writer window disappeared.

  The same problem occurred on a Dell GX-260 computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Nov 19 21:48:52 2018
  InstallationDate: Installed on 2018-06-24 (148 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 616450] Re: hpfax crashed with TypeError in ()

[Launchpad Bug Tracker]

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

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

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

Title:
  hpfax crashed with TypeError in ()

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  Binary package hint: hplip

  I had to restart in secure mood, tho fix problems with the
  nvidiadrivers, and then this bug came

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: hplip 3.10.6-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
  Uname: Linux 2.6.35-14-generic x86_64
  Architecture: amd64
  Date: Wed Aug 11 19:54:42 2010
  ExecutablePath: /usr/lib/cups/backend/hpfax
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  InterpreterPath: /usr/bin/python2.6
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: System manufacturer P5QL-E
  Papersize: a4
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic 
root=UUID=b67e01ec-1845-4d7a-a6c0-ba6df646e66e ro single
  ProcCmdline: python /usr/lib/cups/backend/hpfax
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF8
  PythonArgs: ['/usr/lib/cups/backend/hpfax']
  SourcePackage: hplip
  Title: hpfax crashed with TypeError in ()
  Traceback:
   Traceback (most recent call last):
 File "/usr/lib/cups/backend/hpfax", line 86, in 
   bug("Error importing HPLIP modules: %s\n" % (pid, e))
   TypeError: not all arguments converted during string formatting
  UserGroups:
   
  dmi.bios.date: 10/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/14/2008:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5QL-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1804076] Re: Xorg freeze

[Seth Arnold]

You may need to contact Sophos for support.

Thanks

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  i recently installed OVPN(2) from gnome extentions because the OVPN(1)
  was not working correctly, after that when ever i use my system's Wifi
  i'm getting system freeze for few minutes and again it works
  fine,having this issue on ubuntu but Ubuntu on wayland is working
  perfect. I also used Bleachbit for cleaning junk files and backup from
  my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 20 03:53:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
 Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
  InstallationDate: Installed on 2018-10-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Studio XPS 1640
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0U785D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Studio XPS 1640
  dmi.product.version: A153
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1803849] Re: libgl1-mesa-dri:i386 can not be installed

[Dmitriy Geels]

WTF??? Does this mean you want to get rid of the problem without solving
it?


There is definitely a dependency problem either in libgl1-mesa-dri:i386 or in 
libllvm7:i386.


==
$ apt policy 
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages
 release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages
 release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/main i386 Packages
 release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
 release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=amd64
 origin archive.ubuntu.com
 500 http://archive.canonical.com/ubuntu cosmic/partner i386 Packages
 release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner 
archive,c=partner,b=i386
 origin archive.canonical.com
 500 http://archive.canonical.com/ubuntu cosmic/partner amd64 Packages
 release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner 
archive,c=partner,b=amd64
 origin archive.canonical.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe i386 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 Packages
 release 
v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages
 release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
 release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse i386 Packages
 release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages
 release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic/universe i386 Packages
 release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=i386
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
 release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=amd64
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu cosmic/restricted i386 Packages
 release 

[Desktop-packages] [Bug 1803993] Re: Password appears on the VT1 screen

[Daniel van Vugt]

^^^
That is probably just to verify this really isn't a duplicate of bug 1767918, 
and that you have the fix for bug 1767918 already.

** Summary changed:

- GDM is Exploitable as a Password Collector
+ Password appears on the VT1 screen

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

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

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

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete

Bug description:
  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1803993/+subscriptions

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

[Desktop-packages] [Bug 1804076] Re: Xorg freeze

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  i recently installed OVPN(2) from gnome extentions because the OVPN(1)
  was not working correctly, after that when ever i use my system's Wifi
  i'm getting system freeze for few minutes and again it works
  fine,having this issue on ubuntu but Ubuntu on wayland is working
  perfect. I also used Bleachbit for cleaning junk files and backup from
  my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 20 03:53:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
 Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
  InstallationDate: Installed on 2018-10-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Studio XPS 1640
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0U785D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Studio XPS 1640
  dmi.product.version: A153
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Seth Arnold]

Could you remove all the gnome extensions you've got installed and try
again? I understand those are pretty brittle.

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I pressed a button on my Wacom tablet at the Gnome shell lock screen.
  Once it crashed I was able to see the apps/desktop for a while until
  the lock screen appeared again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 18:38:17 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-13 (616 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa27d2b2b38:cmp%ebp,0x8(%rax)
   PC (0x7fa27d2b2b38) ok
   source "%ebp" ok
   destination "0x8(%rax)" (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (87 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1804007] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  idk why every time i want install graphic card on 18.04 LTS always
  being like this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Nov 19 12:10:24 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-11-17 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803915] Re: nose

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  nose

Status in xorg package in Ubuntu:
  New

Bug description:
  erro de video

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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.1
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Nov 18 23:01:57 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Core Processor 
Integrated Graphics Controller [1462:1039]
  InstallationDate: Installed on 2018-11-08 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 
Bluetooth
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-1454
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=c1a50982-6add-41a3-aacc-6bbf1417cd04 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1454IIA.11C
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1454
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MS-1454
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1454IIA.11C:bd02/10/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-1454:pvrREV1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-1454:rvrREV1.0:cvnMS-1454:ct10:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-1454
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/xorg/+bug/1803915/+subscriptions

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

[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show

[Yuan-Chen Cheng]

** Changed in: oem-priority
   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/1745888

Title:
  Two instances of a program launch whenever you touch a favorites icon,
  or app grid won't show

Status in OEM Priority Project:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

  Using a touch screen, if you tap on a favorites icon on the ubuntu
  dock, two (or more) instances of an application launch.

  Also the app grid doesn't show after a quick tap on the apps icon

  [ Test case ]

  - Look for xterm in gnome-shell activities and add it to favourtes
  - With the ubuntu-dock showing in the desktop, touch the xterm icon
  - Only one instance if it should open
  - Tapping the app icons grid should properly open the g-s overview
  - Tapping on dock icons when in overview mode should work normally

  [ Regression potential ]

  Taps on other gnome-shell buttons could not work poperly (like some
  menu items or app grid)

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 28 19:47:17 2018
  InstallationDate: Installed on 2018-01-28 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Yuan-Chen Cheng]

** Changed in: oem-priority/bionic
   Status: Fix Committed => Fix Released

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Unable to type capital letters using onscreen keyboard

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1786206] Re: Not updating to 0.19 yet

[Jeremy Bicha]

This bug was fixed in the package libraw - 0.19.0-4

---
libraw (0.19.0-4) unstable; urgency=medium

  [ Jeremy Bicha ]
  * debian/libraw19.symbols: Mark 2 symbols as optional
which disappear when built with -O3 on Ubuntu's ppc64el

 -- Matteo F. Vescovi   Fri, 09 Nov 2018 22:53:58 +0100

** Changed in: libraw (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Not updating to 0.19 yet

Status in libraw package in Ubuntu:
  Fix Released

Bug description:
  The 0.19 update is in Debian experimental and has a soname
  change/requires a transition. We don't need it enough to justify the
  extra work/doing the transition ahead of Debian, that bug documents
  that we are staying on 0.18 until there is a real need for the update
  or until Debian upload it to unstable

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

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

[Desktop-packages] [Bug 1803840] Re: color calibration with huey pro greenish

[Daniel van Vugt]

Thanks! Your feedback sounds like the missing piece to this puzzle.
Until now the greenish problem had only been reported by people who
didn't have a colorimeter so we just blamed the default profiles.
However your comments now make me think it might have been a
miscalculation in colord (or such) that is exaggerating the green
channel most visibly.

The previous existing bug 1785764 mentions the greenish issue but isn't
really about it. Let's make this bug 1803840 about the green problem.


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

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

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

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

Title:
  color calibration with huey pro greenish

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  First of all: Congratulations, after an absence due to bad configurability of 
my rig I came back to ubuntu and was very positively surprisedthere is one 
thing that bothers me: after using the calibration feature for my screens this 
leads to greenish displays, even a icc profile made with the same hardware 
under windows10 (where configurability decreased since my update to v10) makes 
the same effect used with ubuntu 16.04...am I not aware of some more setting or 
is this a bug?
  Please let me know what more information you need from me besides I am using 
a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is turned off 
for displays, I am using it just for Blenders Cycles renderer. I am a 
left-handed CG enthusiast who needs the wacom buttons on the right-hand side...

  Thank you,
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 23:43:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:181b]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M] [103c:181b]
  InstallationDate: Installed on 2018-11-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1785764] Re: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled.

[Daniel van Vugt]

The greenish problem is now being tracked separately, in bug 1803840.

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

Title:
  Chrome/Chromium and Image Viewer distort colours if a colour profile
  is enabled.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 18.04.1 LTS 
  Running on an i7-6700k with a GTX 1080
  Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau
  and a single 4K screen (TV) connected via HDMI.

  The issue:
  Any dark content displayed by an effected application (e.g. a very dark image 
or dark themed web page) is much darker than intended making it almost 
unusable. 

  This only effects applications that are launched when the 4K screen is
  connected. If i disconnect the 4K screen, launch the app via a
  different 1080p monitor then reconnect the 4K screen the app remains
  unaffected.

  The only apps i have found so far that are effected by this are Google
  Chrome and Image Viewer. That said this is only noticeable when the
  app is displaying dark contend so if other apps are affected it may be
  impossible to tell.

  The attached screenshot uses a black to white gradient image to clearly 
demonstrate the issue. 
  Is seems like it may be an issue with colour depth as bellow a certain 
brightness it just goes strait to black.

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

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

[Desktop-packages] [Bug 1804008] Re: Gnome Shell extensions crash

[Daniel van Vugt]

Actually, it's pretty obvious ubuntu-dock is crashing for you from the
above log.

However please still try removing all your other gnome-shell extensions
to see if that stops the problem from happening.

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

** Changed in: gnome-shell-extension-ubuntu-dock (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/1804008

Title:
  Gnome Shell extensions crash

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

Bug description:
  All my gnome-shell extensions randomly (apparently) crash. This
  behavior began when i upgraded to cosmic.

  Here's a excerpt of my logs:

  Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1   5566ae293bb8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3   5566ae293b00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5   5566ae293a80 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7   5566ae293a00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9   5566ae293978 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11   5566ae2938e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13   5566ae293860 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15   5566ae2937e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1   5566b0c47bf0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3   5566b0c47b38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5   5566b0c47ab8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7   5566b0c47a38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9   5566b0c479b0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11   5566b0c47918 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13   5566b0c47898 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15   5566b0c47818 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined")
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no 

[Desktop-packages] [Bug 1785775] Re: New 2.42 version

[Jeremy Bicha]

https://launchpad.net/ubuntu/+source/librsvg/2.44.8-3

** Changed in: librsvg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  New 2.42 version

Status in librsvg package in Ubuntu:
  Fix Released

Bug description:
  There is a new upstream version available but it depends on a new
  toolchain which we don't want yet

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

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

[Desktop-packages] [Bug 1804008] Re: All Gnome Shell extensions crash

[Daniel van Vugt]

Please try removing all your gnome-shell extensions and then
reintroducing them one-by-one to figure out which one is crashing.

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

** Summary changed:

- All Gnome Shell extensions crash
+ Gnome Shell extensions crash

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

Title:
  Gnome Shell extensions crash

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

Bug description:
  All my gnome-shell extensions randomly (apparently) crash. This
  behavior began when i upgraded to cosmic.

  Here's a excerpt of my logs:

  Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1   5566ae293bb8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3   5566ae293b00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5   5566ae293a80 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7   5566ae293a00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9   5566ae293978 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11   5566ae2938e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13   5566ae293860 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15   5566ae2937e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1   5566b0c47bf0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3   5566b0c47b38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5   5566b0c47ab8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7   5566b0c47a38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9   5566b0c479b0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11   5566b0c47918 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13   5566b0c47898 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15   5566b0c47818 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined")
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
  Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1   5566a7f84270 i   

[Desktop-packages] [Bug 1803992] Re: Lock screen, notifications panel crashes

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu-mate-meta (Ubuntu)

** Changed in: ubuntu-mate-meta (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/1803992

Title:
  Lock screen, notifications panel crashes

Status in ubuntu-mate-meta package in Ubuntu:
  Incomplete

Bug description:
  Multiple issues:
  1) Lock screen crashes revealing the desktop after sleep/wake

  2) Notification panel crashes constantly (with ubuntu-mate)

  3) Ability to send report fails for whatever reason

  Pics attached here: https://imgur.com/a/dtUaXQF

  Happy to work with anyone to get this resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Nov 19 08:40:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.87, 4.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] [3842:6161]
  LightdmLog:
   [+119931.86s] DEBUG: Seat seat0 changes active session to 
   [+119934.82s] DEBUG: Seat seat0 changes active session to c2
   [+119934.82s] DEBUG: Session c2 is already active
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Designare
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/hostname--vg-root ro initrd=initrd.gz text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23g
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Designare-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Designare:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Designare-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Designare
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1803149] Re: Update to 2.2.9

[Jeremy Bicha]

https://launchpad.net/ubuntu/+source/cups/2.2.9-1

** Changed in: cups (Ubuntu)
   Status: Triaged => 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/1803149

Title:
  Update to 2.2.9

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  There is a new 2.2.9 version available

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

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

[Desktop-packages] [Bug 1803149] Re: Update to 2.2.9

[Jeremy Bicha]

But the autopkgtest fails in the new version.

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

Title:
  Update to 2.2.9

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  There is a new 2.2.9 version available

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

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

[Desktop-packages] [Bug 1804079] Re: Xorg freeze

[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) => xorg-server (Ubuntu)

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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I recently reported but now im having this issue on wayland as well

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 20 04:41:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
 Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
  InstallationDate: Installed on 2018-10-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Studio XPS 1640
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0U785D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Studio XPS 1640
  dmi.product.version: A153
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1803821] Re: trackpoint scrolling not working after update to Ubuntu 18.10

[Daniel van Vugt]

Thanks. Please try removing the old input driver:

  sudo apt remove xserver-xorg-input-synaptics

to see if that fixes the problem. When synaptics is removed you will get
the new default 'libinput' driver instead.

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

Title:
  trackpoint scrolling not working after update to Ubuntu 18.10

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Scrolling by pressing the middle button + moving the trackpoint no
  longer works on my Lenovo E560 after recently updating to Ubuntu
  18.10. Other functions of the middle button besides scrolling work
  fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sat Nov 17 12:40:30 2018
  DistUpgraded: 2018-11-06 01:04:28,107 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5049]
 Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:5049]
  InstallationDate: Installed on 2016-05-12 (918 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=fb8caa1e-e7e1-4c22-9a7e-fd410dd71da0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-06 (11 days ago)
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R00ET42W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR00ET42W(1.17):bd04/20/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E560
  dmi.product.name: 20EVCTO1WW
  dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560
  dmi.product.version: ThinkPad E560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Thu Nov 15 15:55:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1803504] Re: Screen stops redrawing sometimes when moving windows

[Daniel van Vugt]

Thanks for your hard work.

We have now established the original bug here was caused by LP-PPA-
oibaf-graphics-drivers, so not a bug in Ubuntu itself. That makes this
bug report 'Invalid'.

The next problem you encountered is bug 1727356. Only older Intel CPUs
(Core2 or older) will have a problem with that. It is now fixed in
Ubuntu Updates but the fix won't be included in the ISO until version
18.04.2.

The remaining issues should be discussed in new bug reports. Please
remember to keep each bug report about one issue only.


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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Screen stops redrawing sometimes when moving windows

Status in gnome-shell package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Moving a window, on the bottom of screen there is a zone of 2 or 3 cm you 
can't pas the window.
  The down movement is blocked and the mouse cursor with the closed hand moves 
down into the inner window area. When you try to move the window ones again 
upwards you will see a broken graphic part of the window as background and the 
graphic structure of the window get lost. All these movements with the left 
mouse bottom pressed.
  But:
  If you move first the window to the left border and forward out of the screen 
area you can move the window down without the graphic problem. If at least a 
small part of the window is outside of the left screen area you can move the 
window up again passing through the bottom zone of 2 or 3 cm without problems.
  On the right-hand side of the screen area these movements are impossible.

  A big problem you will have with a windows virtual machine in full screen 
mode.
  You can't use the bottom menu.

  (This week y made the upgrade from 16.04.n to 18.04.1 with big graphic 
problems, black screen etc.
  Then reinstall gnome from command line solved the problems with black screen.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 08:07:37 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 0a) (prog-if 00 [VGA controller])
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
  InstallationDate: Installed on 2016-03-17 (972 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 360
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.96+git1811120630.e642f4~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1811141930.e13dd7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1811141930.e13dd7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1811071935.5e6fa5~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1811140735.746ab3~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b
  xserver.bootTime: Wed Nov 14 13:05:37 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard Hub KEYBOARD, id 8
   inputDell Dell USB Keyboard Hub KEYBOARD, id 9
   inputMicrosoft Basic Optical Mouse MOUSE, id 10
  

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

[Daniel van Vugt]

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

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

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

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

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

Title:
  Lock screen doesn't hide the screen contents

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

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

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1803807/+subscriptions

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

[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Daniel van Vugt]

I suggest trying a more stable newer version in that case, like:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.2/

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1802573/+subscriptions

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

[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[Daniel van Vugt]

Great! Now we just need bionic ISOs with the fix built-in. Maybe 18.04.2
in February?

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1790010] Re: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1700085
   Mouse cursor is tiny on HiDPI screens

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

Title:
  Cursor reverts to default size and theme after login, when hovering
  over certain parts of the UI

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

Bug description:
  Dock, dash and top bar do not respect cursor size setting from
  "Settings" (gnome-control-center) straight after login.

  Occurring in Ubuntu 18.04.1, on two machines.

  Expected behaviour: cursor size set to medium (32px) or large (48px?)
  should remain consistent between windows, desktop and dock/dash/top
  bar.

  Observed behaviour: cursor shrinks to default (24px) when hovering
  over dock/dash/top bar. If the cursor state changes (e.g. to loading
  spin wheel) the cursor fixes itself.

  Not sure whether it is a bug in GNOME or the shell extension.

  Sizes set using "gsettings set org.gnome.desktop.interface cursor-size
  32" and "gsettings set com.ubuntu.user-interface.desktop cursor-size
  32" exhibit the same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 23:45:14 2018
  InstallationDate: Installed on 2018-08-24 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799614] Re: Use new media API

[Robert Ancell]

Support in snapd in version 2.36 [1] which is not currently in any
Ubuntu release.

[1]
https://github.com/snapcore/snapd/commit/08bbeb7289fb943ab6c78432579eaceae555ac71

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  In Progress
Status in gnome-software source package in Cosmic:
  New

Bug description:
  snapd now provides 'media' which replaces the old 'screenshots' data.
  We need to migrate to this as the old screenshot data will be removed
  in the future.

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

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

[Desktop-packages] [Bug 1789355] Re: Yaru login screen gradient contains visible steps

[Daniel van Vugt]

** Bug watch added: github.com/ubuntu/yaru/issues #964
   https://github.com/ubuntu/yaru/issues/964

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/964
   Importance: Unknown
   Status: Unknown

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

Title:
  Yaru login screen gradient contains visible steps

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Yaru login screen gradient contains visible steps.

  I think this is probably because the top and the bottom colours are
  too close in 3D colour space so there isn't enough unique values
  between them when using only 8-bpc colour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: yaru-theme-gnome-shell 18.10.2
  ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
  Uname: Linux 4.17.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Tue Aug 28 14:19:12 2018
  Dependencies:

  InstallationDate: Installed on 2018-05-26 (93 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1796187]

[timur]

Cold be a duplicate of Bug 76260. Please compare console errors.

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

Title:
  Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX

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

Bug description:
  Trying to load the attached DOCX results in a hang.  I force-quit
  after 20 minutes.  The DOCX was created in MS Word (2013 I think), and
  is about 450 pages, thousands of footnotes, but no graphics AFAIK.

  I am using the latest package provided by snap. LibreOffice 6.1.2.1.
  Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  4 23:50:54 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-03 (488 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)

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

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

[Desktop-packages] [Bug 1804079] [NEW] Xorg freeze

[Sajjad Ahmed]

Public bug reported:

I recently reported but now im having this issue on wayland as well

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 20 04:41:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last week or two
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
   Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
InstallationDate: Installed on 2018-10-23 (27 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Studio XPS 1640
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0U785D
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Studio XPS 1640
dmi.product.version: A153
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently reported but now im having this issue on wayland as well

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 20 04:41:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
 Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
  InstallationDate: Installed on 2018-10-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Studio XPS 1640
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0U785D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Studio XPS 1640
  dmi.product.version: A153
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Desktop-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Erik Sjölund]

The problem didn't go away after doing a fresh installation of Ubuntu 18.10.
I have to first disconnect and then connect my Sony MDR-1000x to get the A2DP 
profile to work.

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Adam Kessel]

I installed vmlinuz-4.20.0-042000rc3-generic per your request. The
machine won't boot, and just loops infinitely with the error message:

request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for 
module binfmt-646c, throttling...
request_module: modprobe binfmt-646c cannot be processed, kmod busy with 50 
threads for more than 5 seconds now

I've done some googling and don't see an obvious fix. Any suggestions?

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1802573/+subscriptions

-- 
Mailing list: https://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 1803840] Re: color calibration with huey pro greenish

[Michael Kubinyi]

Hello Daniel and Team

I produced ICC-profiles both in windows10 and ubuntu 18.04 with an older
huey pro colorimeter. With Windows 10, everything seems to be working,
under ubuntu both of the profiles have a weird green channel, purpurish
reds are not available anymore. Unluckily, I cannot attach my produced
ICC-profiles, but all of them have a warning sign on the list where one can
select profiles. In Windows and with the huey software, the profiles seem
to work as both of my screens have the same color output. To me, it looks
like the "night mode" when I activate the selfmade profiles with ubuntu,
but maybe my colorimeters green sensor is not responding well with ubuntu?

Thanks for your help,
Michael

Am Mo., 19. Nov. 2018 um 04:30 Uhr schrieb Daniel van Vugt <
daniel.van.v...@canonical.com>:

> A greenish hue has been reported by other users in the past. It is
> caused by using an incorrect colour profile for the display. Please try
> removing all active colour profiles and tell us if that solves the
> problem.
>
> Also, are you using any special hardware to generate your colour
> profile? If not then that's a mistake. You need to use an external
> device to generate a profile and verify its correctness for your
> monitor, or use none at all. One relatively cheap option is
> https://hughski.com/colorhug2.html
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803840
>
> Title:
>   color calibration with huey pro greenish
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   First of all: Congratulations, after an absence due to bad
> configurability of my rig I came back to ubuntu and was very positively
> surprisedthere is one thing that bothers me: after using the
> calibration feature for my screens this leads to greenish displays, even a
> icc profile made with the same hardware under windows10 (where
> configurability decreased since my update to v10) makes the same effect
> used with ubuntu 16.04...am I not aware of some more setting or is this a
> bug?
>   Please let me know what more information you need from me besides I am
> using a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is
> turned off for displays, I am using it just for Blenders Cycles renderer. I
> am a left-handed CG enthusiast who needs the wacom buttons on the
> right-hand side...
>
>   Thank you,
>   Michael
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Nov 17 23:43:53 2018
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DkmsStatus:
>nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
>nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics
> Controller [103c:181b]
>NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1)
> (prog-if 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M]
> [103c:181b]
>   InstallationDate: Installed on 2018-11-11 (5 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC
>   ProcEnviron:
>LANGUAGE=de_CH:de
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_CH.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic
> root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/02/2012
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.22
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 181B
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: 52.24
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
>   dmi.product.name: HP ENVY dv6 Notebook PC
>   

[Desktop-packages] [Bug 1800179] Re: Search in recent files list only works with lowercase letters

[Paul White]

Upstream report closed via commit 370cdd33
Fix should find its way into Ubuntu in due course


** Changed in: gedit (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Search in recent files list only works with lowercase letters

Status in gedit package in Ubuntu:
  Fix Committed

Bug description:
  When clicking “Open” and typing to search the recently opened files,
  any search involving uppercase letters fails to return any result,
  even if files with uppercase letters in their file names have recently
  been opened. Searching for the same file names, but using all-
  lowercase letters, does yield results (see attached screenshot). So it
  seems that gedit converts the recently used file names to lowercase
  before comparing to the search term, which is incorrect.

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

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

[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[fleamour]

sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate

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

Title:
  package python3 3.6.5-3 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hello, error came up while updating. Paketmanager has canceled the
  update completely. Not yet analyzed for errors with console ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 00:01:23 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago)

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Olivier Tilloy]

The fix was backported to the upstream 1.10 series.

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

Title:
  Full-tunnel VPN DNS leakage regression

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

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

[Olivier Tilloy]

I still can't reproduce the issue here.

Tomáš, is libreoffice still crashing for you with the latest updates?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1803849] Re: libgl1-mesa-dri:i386 can not be installed

[Timo Aaltonen]

seems like you've enabled an external ppa, and that's causing the issue

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

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

Title:
  libgl1-mesa-dri:i386 can not be installed

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Steam client tries to install a set of i386 libraries. One of them is 
libgl1-mesa-dri:i386.
  But since upgrade to Ubuntu 18.10 this package got broken dependency and thus 
installation fails.

  >The following packages have unmet dependencies:
  > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it 
is not going to be installed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgl1-mesa-dri:i386 (not installed)
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 18 09:54:04 2018
  DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed
   exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed
   exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed
   exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0804]
  InstallationDate: Installed on 2018-03-27 (235 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.product.sku: 0804
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1780365] Re: Credentials located in gnome-keyring can be compromised easily

[Jamie Strandboge]

Thank you for reporting this bug. The access via DBus when the keyring
is unlocked is a well-known issue and the design of the feature as
explained when reading the entirety of
https://wiki.ubuntu.com/SecurityTeam/FAQ#gnome-keyring. Users who prefer
to be prompted can choose to use a separate keyring than the one that is
automatically unlocked upon successful login.

That said, I'm not clear if you are saying that the keyring is not
locked during screensaver or logout. If either of these is the case,
that sounds like a bug. Can you confirm and detail your methodology?

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

Title:
  Credentials located in gnome-keyring can be compromised easily

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Dear all,

  I figure out that login credentials, located in gnome-keyring, can be
  easily compromised.

  Linux based on Gnome basically uses ‘gnome-keyring’ as their backend
  to store login credentials in a secure manner. Specifically, google-
  chrome browser, network-manager and gnome-online-accounts use this as
  a backend solution to store login credentials.

  To use this, authentication is performed together with gnome-keyring as part 
of ‘pam-gnome-keyring.so’. At this point, it remains unlocked until system is 
shut down or logged out. In this state, a simple program that uses ‘Secret 
Service API’ call and their ‘D-Bus’ interface can easily retrieve login 
credentials from those gnome-keyring without any privilege escalation, 
listening into the X events going to another window, or installation an 
application on target computer.
  (please check PoC source https://github.com/sungjungk/keyring_crack and video 
https://youtu.be/Do4E9ZQaPck)

  The issue is different from the content shown on the Ubuntu Security
  FAQ and GnomeKeyring Wiki [1][2]. It was even said that “PAM session
  is closed via the screensaver, all keyrings are locked, and the
  ‘login’ keyring is unlocked upon successful authentication to the
  screensaver”. After trying to crack the keyring, it was far from what
  they really thought. It is no different than plain text file for login
  credentials somewhere on disk.

  To deal with, the root cause of the problem is that ‘Secret Service
  API’ on anyone can be easily accessed on DBus API. If access control
  is enabled, only well-known? or authorized processes, such as google-
  chrome, network-manager, and gnome-online-accounts, will be able to
  access the login credentials.

  DBus originally provides capability that is essential to access
  control of DBus API by defining security policy as a form of *.conf
  file. Currently, various services based on DBus interface are
  employing above security policy feature to perform access control. For
  example, login/system related functions is controlled from ‘login1’
  and its security policy is described in “org.freedesktop.login1.conf”.
  (see
  
https://github.com/systemd/systemd/blob/master/src/core/org.freedesktop.systemd1.conf)

  Likewise, why don’t we try adopting the access control of secret
  service API into gnome-keyring environment?

  Due to the fact that a process with root privilege can access “.conf”
  file, an approved program may only update the target file during
  installation process

  Here is really simple ‘org.freedesktop.secrets.conf’ example.

  
=
   
  http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd;>

  
  

  

  
  

  
  

  
  
  
  
  
=

  Many Thanks!!

  [1] https://wiki.ubuntu.com/SecurityTeam/FAQ#Contact

  [2] https://wiki.gnome.org/Projects/GnomeKeyring/SecurityPhilosophy

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-keyring 3.28.0.2-1ubuntu1
  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.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 17:45:22 2018
  InstallationDate: Installed on 2018-07-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

[Theo Linkspfeifer]

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

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  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: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

[Lawrence Houston]

Confirming this problem exists with my Toshiba Satellite C650 (Core
i3-2350M 2.3 GHz, onboard Intel HD Graphics 3000), with a fresh Xubuntu
18.10 Installation.

In my case switching to another Virtual Terminal and back to VT-7 (Alt-
Ctrl-F7), returns me to an unblanked XFCE Desktop!

For me another "workaround" is plugging an external monitor into the
Satellite C650's VGA Port, which also unblanks my XFCE Desktop.

Although terminating light-locker and running "dm-tool lock" does
trigger the bug, under those conditions my VGA Port "workaround" does
not work.

I have not observed a "Locked Screen" and therefore blindly typing my
password does not work...

The problem does not exist with an Ubuntu 18.10 Installation on my
Satellite C650.

My own Bug Report https://bugs.launchpad.net/bugs/1803268 is a Duplicate
of those one.

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  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: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

[Serdar Sağlam]

spice-vdagent
Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

Ubuntu 18.10 AMD A10 9600P
Hp

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 902899] Re: Please convert cairomm to multiarch

[Bug Watch Updater]

** Changed in: cairomm (Debian)
   Status: New => Fix Released

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

Title:
  Please convert cairomm to multiarch

Status in cairomm package in Ubuntu:
  Fix Released
Status in cairomm package in Debian:
  Fix Released

Bug description:
  Attached is a patch to cairomm which transitions it to use multiarch
  library paths.

  Since libcairomm-1.0-dev contains no build-time-generated include
  files or arch-dependent scripts/executables, it can be safely marked
  as Multi-Arch: same, so this patch does so. Because many of its direct
  and indirect dependencies have not yet been transitioned for
  multiarch, libcairomm-1.0-dev will not currently be multiarch co-
  installable. This is fine, though, and if all of the dependencies were
  ever to be transitioned for multiarch, the libcairomm -dev package
  would immediately become multiarch co-installable.

  Typically the biggest outstanding blocker to multiarch transitions is
  .la files with non-empty dependency_libs lines. However, I checked all
  files listed in http://lintian.ubuntuwire.org/tags/non-empty-
  dependency_libs-in-la-file.html (http://paste.ubuntu.com/766579/) and
  cairomm isn't listed anywhere, so this transition should be safe now
  by that metric.

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

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Gregor Burger]

** Attachment added: "prime-select query = intel"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5214282/+files/gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Gregor Burger]

Hi,

Thinkpad P1 Quadro P1000. prime-select also not working. 
after prime-select intel and a rebeoot nouveau is driving the GPU but not intel.

Thanks

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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

[Desktop-packages] [Bug 1769215] Re: Pcbnew fails to start with Segmentation fault on Ubuntu Mate 18.04 LTS

[Element Green]

Do you have any Python plugins in ~/.kicad_plugins or other plugin
paths? pcbnew started crashing on me with Ubuntu 18.04 and now 18.10
when I install any plugins, works again after removing them. I've
attached a gdb dump. I wonder if this is the same bug? Looking at this
backtrace it seems like it might be something related to the status bar
creation. I'm going to try building Kicad from latest source to see if I
can figure out anything more.

Kicad package: 5.0.1-stable-201810221457+33cea8e~68~ubuntu18.04.1
OS: Ubuntu 18.10
Plugins tried: replicate_layout and delete_selected from 
https://github.com/MitjaNemec/Kicad_action_plugins


** Attachment added: "gdb backtrace after segfault when starting pcbnew."
   
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1769215/+attachment/5214270/+files/pcbnew_plugin_crash_backtrace.txt

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

Title:
  Pcbnew fails to start with Segmentation fault on Ubuntu Mate 18.04 LTS

Status in gtk2-engines package in Ubuntu:
  Confirmed

Bug description:
  After installing a fresh copy of the new Ubuntu Mate 18.04 LTS, I'm
  not able to start the Pcbnew. In the console it throws the following
  error:

   Segmentation fault (core dumped)

  I'm able to view footprints and 3D models in CvPcb.

  Before installing the new Ubuntu Mate, I used Ubuntu GNOME 16.04 LTS
  on the same laptop without any problems.

  In bug #1768174 they advised me to open a bug here.

  The laptop is a Dell Vostro 5468-P75G001 with Intel Corporation HD
  Graphics 620 (rev 02).

  KiCad version is:

  Application: kicad
  Version: 4.0.7-e2-6376~60~ubuntu18.04.1 release build
  wxWidgets: Version 3.0.3 (debug,wchar_t,compiler with C++ ABI 1011,GCC 
7.3.0,wx containers,compatible with 2.8)
  Platform: Linux 4.15.0-20-generic x86_64, 64 bit, Little endian, wxGTK
  Boost version: 1.65.1
  Curl version: libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 
libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
   USE_WX_GRAPHICS_CONTEXT=OFF
   USE_WX_OVERLAY=OFF
   KICAD_SCRIPTING=ON
   KICAD_SCRIPTING_MODULES=ON
   KICAD_SCRIPTING_WXPYTHON=ON
   USE_FP_LIB_TABLE=HARD_CODED_ON
   BUILD_GITHUB_PLUGIN=ON

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gtk2-engines 1:2.20.2-5
  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: MATE
  Date: Fri May  4 20:01:45 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: gtk2-engines
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1790010] Re: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI

[Luca De Luigi]

** This bug is no longer a duplicate of bug 1700085
   Mouse cursor is tiny on HiDPI screens

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

Title:
  Cursor reverts to default size and theme after login, when hovering
  over certain parts of the UI

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

Bug description:
  Dock, dash and top bar do not respect cursor size setting from
  "Settings" (gnome-control-center) straight after login.

  Occurring in Ubuntu 18.04.1, on two machines.

  Expected behaviour: cursor size set to medium (32px) or large (48px?)
  should remain consistent between windows, desktop and dock/dash/top
  bar.

  Observed behaviour: cursor shrinks to default (24px) when hovering
  over dock/dash/top bar. If the cursor state changes (e.g. to loading
  spin wheel) the cursor fixes itself.

  Not sure whether it is a bug in GNOME or the shell extension.

  Sizes set using "gsettings set org.gnome.desktop.interface cursor-size
  32" and "gsettings set com.ubuntu.user-interface.desktop cursor-size
  32" exhibit the same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 23:45:14 2018
  InstallationDate: Installed on 2018-08-24 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740757] Re: package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Olivier Tilloy]

Thank you for the report Santiago, and sorry that this didn't trigger a
response sooner.

Ubuntu 17.10 is EOL now, so presumably you upgraded to 18.04. Are you
still seeing issues with libreoffice updates?

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

Title:
  package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  no se que paso

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Jan  1 12:45:04 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-12-12 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799993] Re: Firefox segfaults on ppc64le

[Olivier Tilloy]

Thanks Christopher, that's useful.

References to "/build" are from the machine where firefox was built, not
your device.

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

Title:
  Firefox segfaults on ppc64le

Status in firefox package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux sams-voo-sandbox-bigbro 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 
10:57:45 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

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

  $ apt-cache policy firefox
  firefox:
Installed: 62.0.3+build1-0ubuntu0.18.04.1
Candidate: 62.0.3+build1-0ubuntu0.18.04.1
Version table:
   *** 62.0.3+build1-0ubuntu0.18.04.1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages

  $ firefox -v
  Mozilla Firefox 62.0.3

  $ firefox --safe-mode
  Segmentation fault

  $ firefox --headless
  *** You are running in headless mode.
  Segmentation fault

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

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

[Desktop-packages] [Bug 1804029] [NEW] Touching on multiple touchscreens simultaneously breaks X11

[Stephen D'Angelo]

Public bug reported:

This bug is fixed in version 0.28.1, which is shipped with Cosmic. I am
requesting this be backported to Bionic. I know this was fixed
relatively recently, so I'm not sure if it's "in the queue" or not.

Here is the libinput bug report:

https://gitlab.freedesktop.org/libinput/libinput/issues/153

Here is the commit that fixes the bug:

https://gitlab.freedesktop.org/xorg/driver/xf86-input-
libinput/commit/a759610292a53067fc811e70703b8dc0cb16

I have verified that installing the following debs from Cosmic fixes the
issue I am seeing:

libinput-bin  1.12.1-1
libinput10:amd64  1.12.1-1
xserver-xorg-input-libinput   0.28.1-1

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Touching on multiple touchscreens simultaneously breaks X11

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

Bug description:
  This bug is fixed in version 0.28.1, which is shipped with Cosmic. I
  am requesting this be backported to Bionic. I know this was fixed
  relatively recently, so I'm not sure if it's "in the queue" or not.

  Here is the libinput bug report:

  https://gitlab.freedesktop.org/libinput/libinput/issues/153

  Here is the commit that fixes the bug:

  https://gitlab.freedesktop.org/xorg/driver/xf86-input-
  libinput/commit/a759610292a53067fc811e70703b8dc0cb16

  I have verified that installing the following debs from Cosmic fixes
  the issue I am seeing:

  libinput-bin  1.12.1-1
  libinput10:amd64  1.12.1-1
  xserver-xorg-input-libinput   0.28.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1804029/+subscriptions

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

[Desktop-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=120663.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-10-17T15:57:39+00:00 Sergio Callegari wrote:

Description:
The fault seems to be on the Libreoffice application running on the computer, 
not on the android impress remote app.

Running libreoffice, the computer reports a bluetoothd error on syslog,
namely

bluetoothd[1491]: RFCOMM server failed for LibreOffice Impress Remote:
rfcomm_bind: Address already in use (98)

After that the remote handset cannot connect via bluetooth to LibO even
if the the bluetooth adapters in the computer and the handset are
paired.

The issue appears in the bug trackers of both Ubuntu and Fedora and
regards Ubuntu 18.04 and Fedora 27.

I am 100% sure that in the past the impress remote was working via
bluetooth on the same hardware (both computer and handset).

It is unclear to me if the issue is with the bluetooth stack of recent
linux distros (bluez? kernel?) or if something has changed in it and
LibO is trying to still use it in some old way that is now wrong.

The issue is now present using any LibO version from 5.4 to 6.1.

See https://bugzilla.redhat.com/show_bug.cgi?id=1581879
and https://bugs.launchpad.net/bugs/1798400

Steps to Reproduce:
See description

Actual Results:
See description

Expected Results:
See description


Reproducible: Always


User Profile Reset: No


Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: StartModule
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/comments/4


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Medium

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  

[Desktop-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[Waynexyz]

Edit:

This terminal ouput is from a Surface Go.

Also there is a guide how to port it to Linux
https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
porting-guide.pdf

Also there have been some updates in the upstream linux-firmware repo.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
they also do not help to get the wifi card working.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 

[Desktop-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[Waynexyz]

Still an issue even four years later.

On Ubuntu 18.10 dmesg outputs:

"[4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 168c:3370
[4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
[4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

There is a board.bin available directly from the vendor
http://www.killernetworking.com/support/K1535_Debian/board.bin

The only thing which is missing is getting this added to
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles . My
problem is that I dont know how to read the board files and modify them
because I do not know the encoding they use.

Any ideas how to get this solved?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit 

[Desktop-packages] [Bug 1799993] Re: Firefox segfaults on ppc64le

[Christopher Gefvert]

attached backtrace as txt file for readability

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

Title:
  Firefox segfaults on ppc64le

Status in firefox package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux sams-voo-sandbox-bigbro 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 
10:57:45 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

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

  $ apt-cache policy firefox
  firefox:
Installed: 62.0.3+build1-0ubuntu0.18.04.1
Candidate: 62.0.3+build1-0ubuntu0.18.04.1
Version table:
   *** 62.0.3+build1-0ubuntu0.18.04.1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages

  $ firefox -v
  Mozilla Firefox 62.0.3

  $ firefox --safe-mode
  Segmentation fault

  $ firefox --headless
  *** You are running in headless mode.
  Segmentation fault

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

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

[Desktop-packages] [Bug 1799993] Re: Firefox segfaults on ppc64le

[Christopher Gefvert]

** Attachment added: "stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/173/+attachment/5214222/+files/stacktrace.txt

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

Title:
  Firefox segfaults on ppc64le

Status in firefox package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux sams-voo-sandbox-bigbro 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 
10:57:45 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

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

  $ apt-cache policy firefox
  firefox:
Installed: 62.0.3+build1-0ubuntu0.18.04.1
Candidate: 62.0.3+build1-0ubuntu0.18.04.1
Version table:
   *** 62.0.3+build1-0ubuntu0.18.04.1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages

  $ firefox -v
  Mozilla Firefox 62.0.3

  $ firefox --safe-mode
  Segmentation fault

  $ firefox --headless
  *** You are running in headless mode.
  Segmentation fault

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

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

[Desktop-packages] [Bug 1799993] Re: Firefox segfaults on ppc64le

[Christopher Gefvert]

.o0O0o.  apt list --installed  | grep firefox

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

firefox/bionic-updates,bionic-security,now 63.0+build2-0ubuntu0.18.04.2 ppc64el 
[installed]
firefox-dbg/bionic-updates,bionic-security,now 63.0+build2-0ubuntu0.18.04.2 
ppc64el [installed]
 .o0O0o.  
 .o0O0o.  firefox -g -d gdb
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/firefox/firefox...Reading symbols from 
/usr/lib/debug/.build-id/28/cf7b63ae3f258e77cc015838854d9059658fb9.debug...done.
done.
(gdb) handle SIG33 noprint nostop
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) run
Starting program: /usr/lib/firefox/firefox 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
RedBlackTree::TreeNode::SetColor 
(aColor=Red, this=) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h:203
203 /build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h: No such 
file or directory.
(gdb) backtrace
#0  0x0001d600 in RedBlackTree::TreeNode::SetColor(NodeColor) (aColor=Red, 
this=) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h:203
#1  0x0001d600 in RedBlackTree::MoveRedRight(RedBlackTree::TreeNode) (this=, aNode=...)
at /build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h:668
#2  0x0001d818 in RedBlackTree::Remove(RedBlackTree::TreeNode) (this=0x77700080, aNode=...)
at /build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h:562
#3  0x0001f024 in RedBlackTree::Remove(arena_chunk_map_t*) (aNode=0x74a00038, 
this=0x77700080) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/rb.h:144
#4  0x0001f024 in arena_t::SplitRun(arena_run_t*, unsigned long, bool, 
bool) (this=0x7770, aRun=0x74a1, aSize=1048576, aLarge=false, 
aZero=)
at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:2394
#5  0x0001f31c in arena_t::AllocRun(unsigned long, bool, bool) 
(this=0x7770, aSize=1048576, aLarge=false, aZero=false) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:2572
#6  0x000100011570 in arena_t::GetNonFullBinRun(arena_bin_t*) 
(this=, aBin=0x777008d8) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:2822
#7  0x00010001366c in arena_t::MallocSmall(unsigned long, bool) 
(aZero=true, aSize=, this=0x7770) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:2968
#8  0x00010001366c in arena_t::Malloc(unsigned long, bool) (aZero=true, 
aSize=, this=0x7770) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:3025
#9  0x00010001366c in BaseAllocator::calloc(unsigned long, unsigned long) 
(aSize=, aNum=, this=) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/mozjemalloc.cpp:4204
#10 0x00010001366c in Allocator::calloc(unsigned long, 
unsigned long) (arg2=, arg1=) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/malloc_decls.h:38
#11 0x00010001366c in calloc(size_t, size_t) (arg1=, 
arg2=) at 
/build/firefox-JAACWQ/firefox-63.0+build2/memory/build/malloc_decls.h:38
#12 0x7571b8e0 in xcb_connect_to_fd () at 
/usr/lib/powerpc64le-linux-gnu/libxcb.so.1
#13 0x7572318c in xcb_connect_to_display_with_auth_info () at 
/usr/lib/powerpc64le-linux-gnu/libxcb.so.1
#14 0x757239b0 in xcb_connect () at 
/usr/lib/powerpc64le-linux-gnu/libxcb.so.1
#15 0x76586758 in _XConnectXCB () at 
/usr/lib/powerpc64le-linux-gnu/libX11.so.6
#16 0x7656db88 in XOpenDisplay () at 
/usr/lib/powerpc64le-linux-gnu/libX11.so.6
#17 0x767be32c in  () at /usr/lib/powerpc64le-linux-gnu/libgdk-3.so.0
#18 0x76771f68 in gdk_display_manager_open_display () at 
/usr/lib/powerpc64le-linux-gnu/libgdk-3.so.0
#19 0x7676efac in gdk_display_open () at 
/usr/lib/powerpc64le-linux-gnu/libgdk-3.so.0
#20 0x72501664 in XREMain::XRE_mainStartup(bool*) (this=0x7fffdc78, 
aExitFlag=0x7fffdbf8) at 

[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Adam Kessel]

This machine is a fresh install so there have been no updates/upgrades.
The initial install was 18.10 and whatever kernel came by default with
that. I will test with the latest upstream kernel and report back.

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1802573/+subscriptions

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

[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Olivier Tilloy]

Another possibly related issue: bug #1762726 (Context menu does not show
on passwords fields).

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1762726] Re: Context menu does not form on passwords fields

[Olivier Tilloy]

I can reliably reproduce the issue in a 18.04 VM with firefox 63.0.
Unsetting the GTK_IM_MODULE environment variable makes the issue go away
(see also bug #1765304, which is probably related).

The same version of firefox in Ubuntu 18.10 is not affected, so it
appears to be a bionic-only issue (which is consistent with what has
been observed for similar issues related to firefox+ibus+password
fields).

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

** Summary changed:

- Context menu does not form on passwords fields
+ Context menu does not show on passwords fields

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

Title:
  Context menu does not show on passwords fields

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  As many people I use a password manager in order to manage my logins.
  For that I simply copy/paste the username and password in the
  respective fields from another application.  Given some webpages block
  this by JavaScript, I have the following about:config preference:

  dom.event.clipboardevents.enabled=false

  This mostly as an information, because it doesn't seem to affect the
  problem.

  Take a login page (I tried AliExpress - https://login.aliexpress.com/), and 
right click in the username field.  A context menu is shown, containing 
-amongst others- "Paste".
  Click right in the password field, and the context menu is not shown.  I 
would expect it to be shown.

  Using Ctrl-V does work.

  I tried a recreated profile in order to exclude profile-based issues.
  The same happens.

  This does not happen on Ubuntu 16.04LTS
  (59.0.2+build1-0ubuntu0.16.04.3) with equivalent version Firefox
  (59.0.2)

  I am not 100% sure this is a firefox issue.  Perhaps this is Gnome
  related, because I use the default interface on each installation:
  Unity on 16.04LTS and Gnome3 on 18.04LTS.

  

  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy firefox
  firefox:
Installed: 59.0.2+build1-0ubuntu1
Candidate: 59.0.2+build1-0ubuntu1
Version table:
   *** 59.0.2+build1-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[Olivier Tilloy]

Thank you for the report Chris.

>From your report it sounds like this is a one-off issue. Have you
observed that problem more than once? Are there specific steps to take
to make it happen? Maybe a specific document?

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

Title:
  soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed.

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Using LibreOffice Calc I was editing a filter on a pivot table and all
  LibreOffice windows hung.  What appeared in /var/log/syslog was:

  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown 
sequence number while processing queue
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely 
this is a multi-threaded client and XInitThreads has not been called
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry 
about that.
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: 
../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  Nov  1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 
'WindowPreviewMenuItem' on the module 'windowPreview'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-calc 1:6.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 13:39:03 2018
  InstallationDate: Installed on 2018-10-29 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

[Olivier Tilloy]

** Bug watch added: Document Foundation Bugzilla #120663
   https://bugs.documentfoundation.org/show_bug.cgi?id=120663

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=120663
   Importance: Unknown
   Status: Unknown

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

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

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

[Desktop-packages] [Bug 1800779] Re: Libreoffice Writer becomes blank when entering very long formulas

[Olivier Tilloy]

I can reliably reproduce the issue with the attached document in
libreoffice 6.0.6 on Ubuntu 18.04 and with the libreoffice snap (version
6.1.3.2).

I'm seeing the following errors when run in a terminal:

(soffice:4331): Gtk-WARNING **: 16:30:16.532: drawing failure for widget 
'OOoFixed': error occurred in libfreetype
(soffice:4331): Gtk-WARNING **: 16:30:16.532: drawing failure for widget 
'GtkEventBox': error occurred in libfreetype
(soffice:4331): Gtk-WARNING **: 16:30:16.532: drawing failure for widget 
'GtkGrid': error occurred in libfreetype
(soffice:4331): Gtk-WARNING **: 16:30:16.532: drawing failure for widget 
'GtkWindow': error occurred in libfreetype

The deb packages for 6.1.3.2 from libreoffice.org are not affected, so
this is NOT an upstream issue.

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

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

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

Title:
  Libreoffice Writer becomes blank when entering very long formulas

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  When I write long formulas everything becomes blank inside the window.
  I can still use the menus and save and close. When I reopen the
  document it works fine but when I try to modify the long formula,
  everything goes blank again.

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

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

[Desktop-packages] [Bug 1796746] Re: Chromium-Browser not recognizing yubikey u2f anymore?

[Olivier Tilloy]

Sorry for the lack of feedback. It looks like this could possibly be a
18.04-specific issue (given that I was not able to observe it on 18.10).

Any chance you could test on 18.10 ? If upgrading is not an option
(sticking to the LTS is understandable), maybe you could try a 18.10 ISO
on a USB stick and running it live (as opposed to installing) ?

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

Title:
  Chromium-Browser not recognizing yubikey u2f anymore?

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm just having a strange problem, seeing it on two different 18.04
  machines. I had been using several u2f tokens, some are just plain u2f
  tokens (yubikey blue ones and other brands), and Yubikey Neo and
  Yubikey 4 as well with the chromium browser.

  Then I haven't been using the Neo/4 keys for u2f for a while, just the
  plain ones (different brand), definitely not since 18.04.

  Today I wanted to use them and chromium just doesn't recognize them
  anymore. They are not blinking. Tested with e.g.
  https://demo.yubico.com/u2f or Google account.


  Observations:

  - tokens are not damaged: All work with u2f-host

  - All work when used with Chromium (maybe not the latest) on Mac OS

  - But with Chromium currently distributed with Ubuntu 18.04 it works
  only with those keys that have u2f only, such as the blue yubikeys and
  the other brands. Chromium ignores the Yubikey 4 and Neo.


  Any idea or hint?

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAMoQBAAQEBAQEWAQOAMx147iVlo1RPoCerUFSlSwDRwIHAAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA4A4RAAAe/ABBSU8gUEMgICAgICAA/QA7PR5EDwAKICAgICAg/wAwMDAwMDEKICAgICAgAF4=
   modes: 1920x1080 1280x1024 1280x720 1024x768 1024x768 800x600 800x600 
640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Mon Oct  8 20:47:15 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-06-09 (121 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InstalledPlugins:
   
  Load-Avg-1min: 0.34
  Load-Processes-Running-Percent:   0.3%
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

[Pierre Rudloff]

I understand, thanks for taking the time to look at this.
I think I will leave hardware acceleration enabled because the performance gain 
is totally worth this small glitch.

(Also, I use hardware acceleration + no compositing on my other
computers and don't have this issue, so it might be linked to a specific
graphics card or driver.)

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3


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

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

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1802573/+subscriptions

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

[Desktop-packages] [Bug 1796397] Re: DuckDuckGo search icon is blurry, low resolution

[Olivier Tilloy]

The firefox snap is also affected by this issue. It appears to be an
upstream bug. Would you mind filing a bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing
the link to that bug here?

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

Title:
  DuckDuckGo search icon is blurry, low resolution

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox 62.0+build2-0ubuntu0.18.04.5 amd64

  To reproduce:
   - Set search engine to DDG
   - Go to the new tab page.

  The DDG search icon is very low resolution and looks like it hasn't
  been updated with the new logo.

  Expected: Use the icon built into Firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 62.0+build2-0ubuntu0.18.04.5
  ProcVersionSignature: User Name 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1610 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1610 F pulseaudio
  BuildID: 20180913170256
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 15:46:16 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-12 (23 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 
600
  MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=62.0/20180913170256 (In use)
   Profile1 - LastVersion=62.0/20180913170346 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-5252eef0-71dd-4e49-8315-64d660180929
   bp-57477e57-d8dd-4ea9-ba66-270d80180929
   bp-821e4afc-cb3c-4fe2-a7ba-586440180929
   bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (6 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

[Olivier Tilloy]

Thanks for the feedback Pierre. Marking the bug invalid as the correct
combination of settings makes it go away.

Hardware acceleration + no compositing is probably not a supported
configuration.

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

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1803807] Re: Lock screen doesn't hide the screen contents

[Andras Veto]

Sorry, I don't appear to have that folder. This is my 
~/.local/share/gnome-shell/
[2018-11-19 9:13:32] ➜  gnome-shell ls -laR
.:
total 12
drwx--  2 andras andras 4096 Nov 19 09:11 .
drwx-- 22 andras andras 4096 Nov 19 09:07 ..
-rw-rw-r--  1 andras andras 3848 Nov 19 09:11 application_state
-rw-rw-r--  1 andras andras0 Nov 15 22:31 gnome-overrides-migrated

I've been playing around trying to break things again, and it seems as
though the issue was having Extensions enabled (which I believe is the
default Ubuntu behavior). Since disabling them, locking and unlocking
works as it should (locking once immediately locks the screen, dock is
not visible on the lock screen, and dock is still present after logging
back in following the locking action).

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

Title:
  Lock screen doesn't hide the screen contents

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

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

  ---

  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
    Installed: 3.30.1-1ubuntu5
    Candidate: 3.30.1-1ubuntu5
    Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1803807/+subscriptions

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

[Desktop-packages] [Bug 1800640] Re: Plane 1 (SMP) characters are not justified properly in Writer

[Olivier Tilloy]

I can reliably reproduce the issue with libreoffice 6.0.6.2 on Ubuntu
18.04, but not with libreoffice 6.1.3.2 installed as a snap.

It appears this might have been fixed in the 6.1 series. Can you test
and confirm?

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

Title:
  Plane 1 (SMP) characters are not justified properly in Writer

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Justifying paragraphs with Unicode Plane 1 (SMP) characters does not
  work as expected. See the attached screenshot of a document with one
  paragraph in Gothic (U+10330–U+1034F) and another one in Old Hungarian
  (U+10C80–U+10CFF). Both paragraphs have been justified but visually
  only the left edge seems aligned. If you try selecting words with the
  keyboard or the mouse, the font metrics are totally off. In the
  attached screenshot, I have selected the second word of the sentence
  (̼̰̰̽̽) but visually it looks like two characters of the following
  word have been selected as well. Both scripts display the same
  behavior although Gothic is an LTR script and Old Hungarian is RTL.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  libreoffice-writer:
Installed: 1:6.0.6-0ubuntu0.18.04.1
Candidate: 1:6.0.6-0ubuntu0.18.04.1
Version table:
   *** 1:6.0.6-0ubuntu0.18.04.1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 11:31:48 2018
  InstallationDate: Installed on 2017-02-13 (624 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago)

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

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

[Desktop-packages] [Bug 1803504] Re: Screen stops redrawing sometimes when moving windows

[Tedesco]

I don't know if it's the design or something wrong, with more than 1 
virt-viewer window open you can't block the screen.
And the key-combination Alt-L don't block the screen.

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

Title:
  Screen stops redrawing sometimes when moving windows

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Moving a window, on the bottom of screen there is a zone of 2 or 3 cm you 
can't pas the window.
  The down movement is blocked and the mouse cursor with the closed hand moves 
down into the inner window area. When you try to move the window ones again 
upwards you will see a broken graphic part of the window as background and the 
graphic structure of the window get lost. All these movements with the left 
mouse bottom pressed.
  But:
  If you move first the window to the left border and forward out of the screen 
area you can move the window down without the graphic problem. If at least a 
small part of the window is outside of the left screen area you can move the 
window up again passing through the bottom zone of 2 or 3 cm without problems.
  On the right-hand side of the screen area these movements are impossible.

  A big problem you will have with a windows virtual machine in full screen 
mode.
  You can't use the bottom menu.

  (This week y made the upgrade from 16.04.n to 18.04.1 with big graphic 
problems, black screen etc.
  Then reinstall gnome from command line solved the problems with black screen.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 08:07:37 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 0a) (prog-if 00 [VGA controller])
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
 Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller 
[1028:0294]
  InstallationDate: Installed on 2016-03-17 (972 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 360
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.96+git1811120630.e642f4~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1811141930.e13dd7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1811141930.e13dd7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1811071935.5e6fa5~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1811140735.746ab3~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b
  xserver.bootTime: Wed Nov 14 13:05:37 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard Hub KEYBOARD, id 8
   inputDell Dell USB Keyboard Hub KEYBOARD, id 9
   inputMicrosoft Basic Optical Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

[Pierre Rudloff]

Indeed, I can't reproduce the issue anymore when it is disabled.

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1799993] Re: Firefox Segfaults

[Olivier Tilloy]

@Christopher: can you install the firefox-dbg package, and reproduce the
crash in gdb again to get a usable stack trace ?

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

** Summary changed:

- Firefox Segfaults
+ Firefox segfaults on ppc64le

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

Title:
  Firefox segfaults on ppc64le

Status in firefox package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux sams-voo-sandbox-bigbro 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 
10:57:45 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

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

  $ apt-cache policy firefox
  firefox:
Installed: 62.0.3+build1-0ubuntu0.18.04.1
Candidate: 62.0.3+build1-0ubuntu0.18.04.1
Version table:
   *** 62.0.3+build1-0ubuntu0.18.04.1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages

  $ firefox -v
  Mozilla Firefox 62.0.3

  $ firefox --safe-mode
  Segmentation fault

  $ firefox --headless
  *** You are running in headless mode.
  Segmentation fault

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

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

[Desktop-packages] [Bug 1799907] Re: package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

[Olivier Tilloy]

According to the dpkg history log:

 - on 2018-10-23 chromium-browser (69.0.3497.81-0ubuntu0.18.04.1) and
chromium-browser-l10n (69.0.3497.81-0ubuntu0.18.04.1) were installed

 - on 2018-10-24 removal was requested for both packages, but package
chromium-browser-l10n was at version 70.0.3538.67-0ubuntu0.18.04.1
whereas chromium-browser was still at version
69.0.3497.81-0ubuntu0.18.04.1

@Branislav: I wonder how the versions got out of sync. Could it be that
you manually downloaded and installed a deb for chromium-browser-l10n
(that seems unlikely, but asking just in case) ?

If you apply all available updates, are you then able to remove
chromium-browser?

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

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

Title:
  package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Unable to remove chromium browser.
  Ubuntu 18.04.1 LTS
  69.0.3497.81-0ubuntu0.18.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-browser-l10n:amd64: Remove
   chromium-browser:amd64: Remove
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLRoNVkxaWhAaAQOAMBt4KlKVpVZUnSUOUFS/74BxT4HAgQCBgJUAqcCzAAEBAjqAGHE4LUBYLEUA3QwRAAAe/QAySx5REQAKICAgICAg/ABTMjJGMzUwCiAgICAg/wBINFpINDExNzA5CiAgAf8CAxGxRpAEHxMSA2UDDAAQAAEdALxS0B4guChVQN0MEQAAHowK0JAgQDEgDEBVAN0MEQAAGIwK0Iog4C0QED6WAN0MEQAAGAAAUA==
   modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 
1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Thu Oct 25 10:46:48 2018
  Desktop-Session:
   'None'
   'None'
   'None'
  DpkgTerminalLog:
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  DuplicateSignature:
   package:chromium-browser:69.0.3497.81-0ubuntu0.18.04.1
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
  Env:
   'None'
   'None'
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2018-10-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Fri Aug  3 08:18:24 2018)
  Load-Avg-1min: 5.92
  Load-Processes-Running-Percent:   0.3%
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=98ec02f9-f4a2-4059-b2db-89f6add91501 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  SourcePackage: chromium-browser
  Title: package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  

[Desktop-packages] [Bug 1804008] [NEW] All Gnome Shell extensions crash

[Gonçalo Marrafa]

Public bug reported:

All my gnome-shell extensions randomly (apparently) crash. This behavior
began when i upgraded to cosmic.

Here's a excerpt of my logs:

Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1   5566ae293bb8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3   5566ae293b00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5   5566ae293a80 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7   5566ae293a00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9   5566ae293978 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11   5566ae2938e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13   5566ae293860 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15   5566ae2937e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1   5566b0c47bf0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3   5566b0c47b38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5   5566b0c47ab8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7   5566b0c47a38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9   5566b0c479b0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11   5566b0c47918 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13   5566b0c47898 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15   5566b0c47818 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1   5566a7f84270 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #3   5566a7f841b8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #5   5566a7f84138 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #7   5566a7f840b8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #9   5566a7f84030 i   

[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

[Wolf Rogner]

played around a little more:

Downloaded LibreOffice 6.2.0.0-beta1 AppImage and low and behold, the
embedded objects and icons are blurred again. Only the current
production version seems to work correctly.

I suggest we drop this bug report and I accept the blurred embeddiments.

Seems like some regression on LOs side.

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()

[Andrea Azzarone]

Fix released in disco with gjs (1.54.3-1)

** Changed in: gjs (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in
  GetPropertyOperation() from Interpret() from js::RunScript()

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs60 package in Ubuntu:
  Invalid
Status in gjs source package in Cosmic:
  In Progress
Status in mozjs60 source package in Cosmic:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/f64145b51a9d0fd20bfff57836b8f743e56c50ba
  https://gitlab.gnome.org/GNOME/gjs/issues/212

  ---

  mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52 which
  was still the latest yesterday)

  Steps to reproduce:

  1. Start gnome-shell (master)
  2. Super+A to show applications
  3. Alt+F2 and type "debugexit" to exit cleanly.

  Backtrace:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=...,
  pc=, script=..., fp=, cx=)
  at ./js/src/vm/JSContext.h:161
  161   ./js/src/vm/JSContext.h: No such file or directory.
  [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))]
  (gdb) bt
  #0  0x7f3bf4033a4e in GetPropertyOperation
  (vp=..., lval=..., pc=, script=..., fp=, 
cx=) at ./js/src/vm/JSContext.h:161
  #1  0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&)
  (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834
  #2  0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&)
  (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418
  #3  0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct)
  (cx=0x55d07921beb0, args=..., construct=)
  at ./js/src/vm/Interpreter.cpp:490
  #4  0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, 
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
  (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=...,
  thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536
  #5  0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, 
JS::Handle, JS::Handle, JS::HandleValueArray const&, 
JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., 
rval=...)
  at ./debian/build/dist/include/js/RootingAPI.h:1128
  #6  0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0
  #7  0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0
  #8  0x7f3bf7625573 in  () at /usr/lib/libgjs.so.0
  #9  0x7f3bf7f65b6d in g_closure_invoke ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x7f3bf7f788f3 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7f3bf7f81882 in g_signal_emit_valist ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x7f3bf7f81ecf in g_signal_emit ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0)
  at clutter-actor.c:5932
  #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0)
  at ../src/st/st-widget.c:354
  #15 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0)
  at ../src/st/st-bin.c:188
  #16 0x7f3bf7f6c448 in g_object_run_dispose ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #17 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0)
  at clutter-actor.c:8615
  #18 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0)
  at clutter-actor.c:19002
  #19 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0)
  at clutter-actor.c:6264
  #20 0x7f3bf7f65b6d in g_closure_invoke ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #21 0x7f3bf7f78c4a in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #22 0x7f3bf7f81882 in g_signal_emit_valist ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #23 0x7f3bf7f81ecf in g_signal_emit ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795a9ba0)
  at clutter-actor.c:5932
  #25 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795a9ba0)
  at ../src/st/st-widget.c:354
  #26 0x7f3bf7f6c448 in g_object_run_dispose ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795a9ba0)
  at clutter-actor.c:8615
  #28 0x7f3bf7025cf5 in st_bin_dispose (gobject=0x55d0795a8260)
  at ../src/st/st-bin.c:185
  #29 0x7f3bf7f6ac13 in g_object_unref ()
  at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #30 0x7f3bf7610f5e in ObjectInstance::release_native_object() ()
  at /usr/lib/libgjs.so.0
  #31 0x7f3bf7618496 in 

[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

[Wolf Rogner]

Some console messages:

wolf@mbpr13b:~$ sudo snap install libreoffice
[sudo] password for wolf: 
libreoffice 6.1.3.2 from Canonical✓ installed
wolf@mbpr13b:~$ snap run libreoffice.writer
main.go:192: cannot change mount namespace of snap "libreoffice" according to 
change mount (/snap/gtk-common-themes/818/share/icons/Suru 
/snap/libreoffice/90/data-dir/icons/Suru none bind,ro 0 0): cannot use 
"/snap/gtk-common-themes/818/share/icons/Suru" as bind-mount source: not a 
directory

(soffice:3000): GLib-GIO-WARNING **: 14:55:35.776: Error creating IO channel 
for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2)
wolf@mbpr13b:~$ man snap 
wolf@mbpr13b:~$ sudo snap remove libreoffice 
libreoffice removed
wolf@mbpr13b:~$ 

Personally I think that an application should not provide WARNINGS that
are ERRORS but should handle this gracefully.

Add: I figured out which theme was used. Is it true that snap uses gtk2
only (I have not seen any gtk3 themes in the /snap/gtk-common-themes/...
folders.

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1083097] Re: Firefox 17 resizes incorrectly with Sawfish WM

[Paul White]

No reply from reporter
Bug did not expire due presence of bug watch
Upstream bug is showing as "VERIFIED FIXED" in 2013
Marking as "Fix released" to close

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

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

Title:
  Firefox 17 resizes incorrectly with Sawfish WM

Status in Apport:
  Invalid
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After updating firefox (and thunderbird) to version 17, the Firefox
  and Thunderbird main windows don't resize correctly.

  Upon opening the main window, everything looks good, but clicking on
  the lower right corner to resize causes the window to become around
  200x100 pixels, and the maximize button to disappear.  Trying to make
  the window larger makes it smaller.

  Downgrading to firefox_16.0.2+build1-0ubuntu0.12.04.1_i386.deb fixes
  the problem.

  The bad build appears to be:
  firefox_17.0+build2-0ubuntu0.12.04.1_i386.deb

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

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

[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

[Wolf Rogner]

@Oliver: I installed the snap version (I do not like snap as it leaves
artefacts lying around).

a) the same blurred effect as with the apt installation
b) path's, settings and other customisation is lost
c) theme is ... well which one does get used there? Certainly not mine

Concluding: The issue is the same in snap packages.

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

[Wolf Rogner]

Sorry about my unprecise report last time.

In 18.04(.1) I observed this issue only when embedding OLE objects. I
first attributed this to maybe a slight difference in width or height of
the embedded object.

I can reign out this as I have adjusted the size.

Under 18.10 I not only see this obscured embeddiment happen with OLE
objects but with any object that I include. Be it presentations,
documents or spread sheets. Further, the icons from the toolbar are
blurred as well.

This regards the default installation (6.1.2.1)

I tried to pin it down to screen resolution (my Mac has 2550 x 1600 with
a default of 200% scaling). Even with 100% I can verify the blurred
display (although it requires a magnifying glass to see).

Today I figured that using cropped images in presentations has negative
impact on the display of fonts (font size and font family change
randomly).

In comparison, I tried AppImage (6.1.3) from LO site.

Here I cannot see any of the blurred effects at all. Embedded components
and icons are displayed sharp.

Personally I come to the conclusion that the default installation
packages must be compiled with settings incompatible with the display
manager.

Concluding: Anything other than bare text gets rendered blurred in some
way.

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

[Theo Linkspfeifer]

You have layers.acceleration.force-enabled set to 'true'. Does changing
it back to 'false' + restart make a difference?

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1496558] Re: Firefox crashes repeatedly with no apparent pattern

[Paul White]

Upstream report closed "RESOLVED INVALID"
Reporter advised crash due bad ram
Marking "Invalid" as not a Firefox issue

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

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

Title:
  Firefox crashes repeatedly with no apparent pattern

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I am not sure how to reproduce this bug, as the crashes seem to happen
  at random, including at times I have left Firefox open and gone away
  from my computer only to find it has crashed in my absence. I have a
  lot of crash reports submitted, but there is no one thing I have found
  that correlates to this. I have tried running in safe mode, disabling
  extensions, and making a new profile, but the crashes continue.

  I submitted this upstream at
  https://bugzilla.mozilla.org/show_bug.cgi?id=1198805

  If I should provide any additional information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: firefox 40.0.3+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1348 F pulseaudio
  BuildID: 20150826185640
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Sep 16 12:59:15 2015
  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 2015-08-05 (42 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.11.1 dev wlan0  proto static  metric 1024 
   1.1.1.1 via 192.168.11.1 dev wlan0  proto dhcp  metric 10 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.11.0/24 dev wlan0  proto kernel  scope link  src 192.168.11.130
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3fd152b2-3c24-4d24-a5f3-21df12150916
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=40.0.3/20150826185640
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7459V1X
  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:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7459V1X:pvrThinkPadX200:rvnLENOVO:rn7459V1X:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7459V1X
  dmi.product.version: ThinkPad X200
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1803992] [NEW] Lock screen, notifications panel crashes

[Charles Birk]

Public bug reported:

Multiple issues:
1) Lock screen crashes revealing the desktop after sleep/wake

2) Notification panel crashes constantly (with ubuntu-mate)

3) Ability to send report fails for whatever reason

Pics attached here: https://imgur.com/a/dtUaXQF

Happy to work with anyone to get this resolved.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Nov 19 08:40:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.87, 4.15.0-38-generic, x86_64: installed
 nvidia, 390.87, 4.15.0-39-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] [3842:6161]
LightdmLog:
 [+119931.86s] DEBUG: Seat seat0 changes active session to 
 [+119934.82s] DEBUG: Seat seat0 changes active session to c2
 [+119934.82s] DEBUG: Session c2 is already active
MachineType: Gigabyte Technology Co., Ltd. Z170X-Designare
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/hostname--vg-root ro initrd=initrd.gz text
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23g
dmi.board.asset.tag: Default string
dmi.board.name: Z170X-Designare-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Designare:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Designare-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z170X-Designare
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Lock screen, notifications panel crashes

Status in xorg package in Ubuntu:
  New

Bug description:
  Multiple issues:
  1) Lock screen crashes revealing the desktop after sleep/wake

  2) Notification panel crashes constantly (with ubuntu-mate)

  3) Ability to send report fails for whatever reason

  Pics attached here: https://imgur.com/a/dtUaXQF

  Happy to work with anyone to get this resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Nov 19 08:40:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.87, 4.15.0-39-generic, x86_64: 

[Desktop-packages] [Bug 991105] Re: Customize toolbar dialogue does not allow dragging items

[Paul White]

No reply from those affected
Report did not expire due bug watch
Upstream bug closed "RESOLVED FIXED" in 2012
Marking as "Fix Released"

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

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

Title:
  Customize toolbar dialogue does not allow dragging items

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Customize toolbar dialogue does not allow dragging items

  ergo I can't customize the toolbars

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 12.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AddonCompatCheckDisabled: True
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2614 F pulseaudio
   /dev/snd/controlC1:  graingert   2614 F pulseaudio
  BuildID: 20120423122928
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfba0 irq 54'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0892,14627681,00100302 
HDA:80862805,80862805,0010'
 Controls  : 50
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:06:00.0-2, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 13 [81%] [25.50dB] [on]
  Channel: release
  Date: Sun Apr 29 14:21:57 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Firebug - ID=fire...@software.joehewitt.com, Version=1.9.1, minVersion=5.0, 
maxVersion=12.0a1, Location=app-profile, Type=extension, Active=Yes
   Reddit Enhancement Suite - ID=jid1-xUfzOsOFlzSOXg@jetpack, Version=4.0.3, 
minVersion=8.0, maxVersion=11.0a1, Location=app-profile, Type=extension, 
Active=Yes
   LastPass - ID=supp...@lastpass.com, Version=1.90.6, minVersion=1.9a2, 
maxVersion=1.9.6, Location=app-profile, Type=extension, Active=Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120201.1)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.3  metric 1 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.20  metric 
2
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423122928 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V23.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-GD55 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV23.2:bd09/08/2011:svnMSI:pnMS-7681:pvr4.0:rvnMSI:rnZ68A-GD55(MS-7681):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7681
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1708561] Re: netflix does not work Mozilla 54.0

[Paul White]

No reply from anyone affected
Bug showing "VERIFIED FIXED" upstream
Fix appeared in next release of Firefox after report raised
Marking "Fix Released"

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

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

Title:
  netflix does not work Mozilla 54.0

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Netflix does not work Mozilla 54.0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  familia_toshiba   1462 F pulseaudio
  BuildID: 20170612123102
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Aug  3 21:33:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-27 (829 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static  metric 600 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.100  metric 
600
  MostRecentCrashID: bp-7c60b329-9f17-4ca9-8867-a1e401170730
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612123102 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-7c60b329-9f17-4ca9-8867-a1e401170730
   bp-a10060bb-9c0a-488d-b739-716e21170730
   bp-73bbed15-141b-467c-b4c1-a02f21170730
   bp-5800-63b6-44cf-a44b-34fa71170730
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2005
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.80
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 8
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd08/11/2005:svnTOSHIBA:pnSatelliteM45:pvrPSM40U-07X001:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct8:cvrVersion1.0:
  dmi.product.name: Satellite M45
  dmi.product.version: PSM40U-07X001
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 785977] Re: Character set submenus do not appear

[Paul White]

Bug report did not auto-expire due bug watch
Upstream report was closed "RESOLVED FIXED" in 2013
Closing by marking "Fix Released"

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

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

Title:
  Character set submenus do not appear

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu Natty Narwhal 11.04
  Unity 2D
  Firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.2

  When I click on View-->Character Sets, most of the submenus fail to
  appear, including Autodetect,  each of the regional submenus under
  More, and Unicode. The result is that I cannot select any character
  set to view the page in. This makes it harder to diagnose pages with
  improper coding.

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

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

[Desktop-packages] [Bug 1660031] Re: upgrade renders firefox unusable

[Paul White]

No reply from anyone affected so marking "Fix Released" as issue
confirmed fixed upstream.

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

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

Title:
  upgrade renders firefox unusable

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I just apt-upgraded a 16.04 machine to the latest packages, which
  rendered firefox unusable. The firefox gui appears, but it does not
  show contents of webpages, refuses a login to an unencrypted (still
  secure because tunneled) webpage and blasts trillions of messages like

   [  691.871185] audit: type=1400 audit(1485603229.158:2983):
  apparmor="DENIED" operation="mknod"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/dev/shm/org.chromium.fHVuSZ" pid=6325
  comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c"
  fsuid=1000 ouid=1000

  
  into the log. Looks like wrong or outdated apparmor settings keep firefox 
from running properly.

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

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

[Desktop-packages] [Bug 575897] Re: No text cursor for login on CitiCard website

[Paul White]

No reply from reporter but upstream report closed "RESOLVED WORKSFORME".
Site appears to have changed since report raised so Firefox now works. Closing 
by marking "Invalid" as no action appears to have been taken by Mozilla 
developers

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

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

Title:
  No text cursor for login on CitiCard website

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  The cursor disappears on the first login line of the login form of the
  CitiCard website after a second or two and is unrecoverable.  While it
  is present, it is inactive.  This is not a problem with Google Chrome,
  nor with any other website using Firefox in my experience.  It is
  annoying to have to use two web browsers in order to get my work done
  and so would appreciate your remedying this issue.

  Greg Morgansen

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  NonfreeKernelModules: nvidia wl
  Architecture: i386
  Date: Wed May  5 09:57:36 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1195965] Re: Firefox not responding in AOL Inbox

[Paul White]

No reply from reporter
Duplicate is also from same reporter
No confirmation by another user
Ubuntu version long time EOL
Mozilla bug closed "RESOLVED INVALID"
So also marking "INVALID" to close

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

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

Title:
  Firefox not responding in AOL Inbox

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When I turned on my laptop today for once, a small window opened
  telling me that my system has a problem. Usually, lately, I ignore
  these messages because they ask me to give my Ubuntu password and for
  security reasons [I don't normally give it], but this time I checked
  it little bit more.

  So I pressed report the problem and another window appeared. This new
  window had the name  "authenticate" and the following writing: Please
  enter your password to access problem reports of system programs. An
  application is attempting to perform an action that requires
  privileges. AUTHENTICATION IS REQUIRED TO PERFORM THIS ACTION.
  Password...

  Under this on the left bottom was a small upside down triangle and the word 
Details.
  I pressed the Details and appeared: Action :com.ubuntu.apport.apport-gtk-root 
Vendor : Apport}

  Pressing the Vendor word SOMETHING VERY STRANGE HAPPENNED:
  A new window came out: "Close Firefox.  Firefox is already running,but is not 
responding.To open a new window , you must first close the existing Firefox 
process, or restart your system .OK  ."

  BUT FIREFOX WAS NOT OPENED / AND THIS HAS HAPPENED IN THE PAST FEW TIMES.
  I mean that quite few times has happened that WITHOUT Firefox opened the 
system tells me THAT FIREFOX IS ALREADY RUNNING!!!
  Anyway I had to press OK to that so Firefox opened by itself on 
https://wiki.ubuntu.com/Apport.

  I stop everything there and I put on the side this Authenticate
  window. I did not give my password (Please tell me if this comes out
  to you in UBUNTU, and WHY FIREFOX seems to be open when it is not).

  After that I checked my Hotmail account to see if you have sent me
  something from the yesterday problems I had faced and reported to you.
  I had no answer so I logged out from hotmail and I went to my other
  email account in AOL. I succesfully logged in BUT when I tried to
  check my inbox the screen (I only had this window in AOL opened) got
  dark and was not responding. I pressed Ubuntu Help and after while the
  screen got lighter but I could check my emails, AGAIN got darker and I
  had to press alt+f2 several times (was not openning) and finally got
  to send this report to you with all of these details.

  PLEASE ONCE MORE I NEED YOUR HELP.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-screensaver 3.6.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Sat Jun 29 09:39:58 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 3600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-02-12 (136 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to raring on 2013-05-14 (45 days ago)

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

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

[Desktop-packages] [Bug 1730211] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730211

Title:
  Unable to type capital letters using onscreen keyboard

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

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

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

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

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.2

---
mutter (3.28.3-2~ubuntu18.04.2) bionic; urgency=medium

  * d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch:
- Create back buffers in early intel GPU generations (LP: #1727356)
  * d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch,
d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch
- Fix typing capital letters when using OSD keyboard (LP: #1730211)

 -- Marco Trevisan (Treviño)   Wed, 31 Oct 2018
12:19:19 +

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

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

Title:
  Unable to type capital letters using onscreen keyboard

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.2

---
mutter (3.28.3-2~ubuntu18.04.2) bionic; urgency=medium

  * d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch:
- Create back buffers in early intel GPU generations (LP: #1727356)
  * d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch,
d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch
- Fix typing capital letters when using OSD keyboard (LP: #1730211)

 -- Marco Trevisan (Treviño)   Wed, 31 Oct 2018
12:19:19 +

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

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1727356] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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