date:20200116

** Summary changed:

- Display freaks out when external monitors are attached
+ Long delays and repeated flashing when docking laptop with multiple monitors

** Tags added: performance

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

Title:
  Long delays and repeated flashing when docking laptop with multiple
  monitors

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1848202] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)

2020-01-16 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

automake-1.16/1:1.16.1-4ubuntu3 (s390x)
libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el)
umockdev/0.13.2-1 (armhf, i386)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tracker/2.3.0-1 (armhf)
glib2.0/2.62.3-2~ubuntu19.10.1 (i386)
cmake-extras/1.3+17.04.20170310-5 (armhf)
netplan.io/0.98-0ubuntu1 (ppc64el, i386)
dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386)
ocaml-cairo2/unknown (armhf)
netplan.io/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el)
snapd-glib/1.49-0ubuntu1.19.10.0 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Use after free in gdbus leads to eds segfaults

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

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

  [ Fix ]

  This bug was fixed upstream in 2.62.2 (see the links below). That
  update is being issues to eoan.

  [ QA ]

  Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't
  need to explicitly test that this bug is fixed. Nevertheless, to
  verify this bug please give the desktop a good workout. Ideally
  install the SRU and use your machine as you would normally for a
  variety of tasks. Make sure there are no regressions.

  [ Regression potential ]

  1) The changes involve mutexes and stuff, which is error prone.

  2) It's GLib, a core library, so any bad regressions will be really
  serious for the desktop as a whole.

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

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

[Desktop-packages] [Bug 1844853] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)

2020-01-16 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

automake-1.16/1:1.16.1-4ubuntu3 (s390x)
libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el)
umockdev/0.13.2-1 (armhf, i386)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tracker/2.3.0-1 (armhf)
glib2.0/2.62.3-2~ubuntu19.10.1 (i386)
cmake-extras/1.3+17.04.20170310-5 (armhf)
netplan.io/0.98-0ubuntu1 (ppc64el, i386)
dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386)
ocaml-cairo2/unknown (armhf)
netplan.io/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el)
snapd-glib/1.49-0ubuntu1.19.10.0 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Fix Committed
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850932] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)

2020-01-16 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

automake-1.16/1:1.16.1-4ubuntu3 (s390x)
libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el)
umockdev/0.13.2-1 (armhf, i386)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tracker/2.3.0-1 (armhf)
glib2.0/2.62.3-2~ubuntu19.10.1 (i386)
cmake-extras/1.3+17.04.20170310-5 (armhf)
netplan.io/0.98-0ubuntu1 (ppc64el, i386)
dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386)
ocaml-cairo2/unknown (armhf)
netplan.io/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el)
snapd-glib/1.49-0ubuntu1.19.10.0 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] Backport 2.62.3-2

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  I'm creating this bug report to have a place to describe the proposed
  backport of glib2.0 2.62.3-2 from focal.

  One purpose of this backport is to fix bug #1844853.

  But there are several other changes. Here's the diff of NEWS:

  +Overview of changes in GLib 2.62.3
  +==
  +
  +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject 
to
  +  FD limits (#954)
  +
  +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917)
  +
  +* Bugs fixed:
  + - #954 The g_spawn_sync() function uses select() which has limitations
  + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type 
'(null)' in cast to 'GDBusServer'
  + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7
  + - #1903 use-after-free in mimeapps test causes intermittent segfault during 
testing
  + - #1916 objcopy not used from cross-compilation file in GIO tests
  + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and 
new GCC
  + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62
  + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to 
glib-2-62
  + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62`
  + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62
  + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by 
kdeinit5” to glib-2-62
  + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1
  + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error”
  + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring 
events” to glib-2-62
  + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” 
to glib-2-62
  +
  +
  +Overview of changes in GLib 2.62.2
  +==
  +
  +* Bugs fixed:
  + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a 
dedicated thread
  + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” 
to glib-2-62
  + - !1156 Backport !1146 Solaris fixes to glib-2-62

  
  This release can be considered to be tested under 
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  There are patches from the upstream master branch rather than this
  stable release:

  + Add-a-test-for-GDBusServer-authentication.patch
  + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch
  + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch
  + Make-ld-executable-configurable.patch

  They are sensible backports which I hope are appropriate for SRU.

  [ QA ]

  The testsuite fixes will verify themselves during the build and
  autopkgtest.

  For the rest of the fixes, please exercise the desktop thoroughly. Log
  in, log out, run many applications and make sure there are no
  regressions.

  [ Regression potential ]

  test fixes> Build failures or autopkgtest failures.

  GLib is a central desktop library. Regressions could break any part of
  the desktop - so QA is important, the SRU exception notwithstanding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions

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

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Can you please run:

  gsettings list-recursively | grep scal

and share the output?

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

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

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Thanks. It's very strange that the dimensions of neither image match
actual screen resolutions. I guess that's one possible reason why
they're not staying full screen -- the window size is not supportable.

Another issue I notice from your screenshots is the unusual panel and
icons hanging down. This makes me think you might be using some
extensions(?). Please try uninstalling all gnome-shell extensions,
reboot and retest. We need to uninstall extensions and not just disable
them because broken extensions might also fail to honour the disable
request.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

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

[Desktop-packages] [Bug 1849055] Re: gnome-extensions fails to load after boot

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

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

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

Title:
  gnome-extensions fails to load after boot

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions 
that I have enabled fail to load.  I am forced to go each time to gnome-tweaks 
to re-enable these extensions which is very 
  frustrating.  This worked fine in Ubuntu 19.04.  I am using a Dell Inspiron 
1420 laptop.  Thank you
  for any help with this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: 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  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 22:14:29 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3]
  InstallationDate: Installed on 2016-01-26 (1363 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 1420
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0Y918J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Oct 20 21:04:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: lightdm
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2016-01-26 (1363 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=789110.

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 2017-10-17T16:50:14+00:00 Mario Sánchez Prada wrote:

Created attachment 361759
Inconsistency in the bluetooth menu

In Endless's fork of GNOME Shell 3.24, we sometimes get an inconsistent
state in the system menu for the Bluetooth, that leads to weird
situations where you see the menu item as "Off" even if bluetooth is
active (and we know that because we can use the BT mouse), with a
submenu item showing "Turn Off".

See the attached picture for a better visual description of the problem.

As far as I can see, this is a problem in master too, patch will be
coming soon..

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/9

On 2017-10-17T17:01:17+00:00 Mario Sánchez Prada wrote:

Created attachment 361760
1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/10

On 2017-10-17T17:01:34+00:00 Mario Sánchez Prada wrote:

Created attachment 361761
2. bluetooth: Be consistent when determining whether Bluetooth is off

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/11

On 2017-10-17T17:13:36+00:00 Florian-muellner wrote:

Review of attachment 361760:

Whoops

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/12

On 2017-10-17T17:39:40+00:00 Florian-muellner wrote:

Review of attachment 361761:

> otherwise we risk showing inconsistent states in each place if.

I'd be interested in how that sentence continues :-p

Joking aside, I don't think this is correct. As far as I can see,
"nConnectedDevices == -1" means there is no Bluetooth adapter that is
powered on - we can toggle the AirplaneMode property as much as we want
(that's what "Turn On/Off" does after all), that's not going to change.
So a better option may be to do

  this._toggleItem.actor.visible = nConnectedDevices > -1;

instead ...

::: js/ui/status/bluetooth.js
@@ +134,3 @@

+// Bluetooth will be considered 'Off' if either the adapter
+// is not available or it's set in irplane mode.

*airplane

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/13

On 2017-10-17T19:20:09+00:00 Mario Sánchez Prada wrote:

Comment on attachment 361760
1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface

(In reply to Florian Müllner from comment #3)
> Review of attachment 361760 [details] [review]:
> 
> Whoops

Thanks for the review. Commmitted:
https://git.gnome.org/browse/gnome-shell/commit/?id=fb3070981c549ad9812d62f8ab868c323ed2ccf5

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/14

On 2017-10-17T19:27:40+00:00 Mario Sánchez Prada wrote:

(In reply to Florian Müllner from comment #4)
> Review of attachment 361761 [details] [review]:
> 
> > otherwise we risk showing inconsistent states in each place if.
> 
> I'd be interested in how that sentence continues :-p

I'd be too, but I can't remember what I had in there :). I suppose it'
was something along the lines of "...if the adapter is available but
it's set in airplane mode".

> Joking aside, I don't think this is correct. As far as I can see,
> "nConnectedDevices == -1" means there is no Bluetooth adapter that is
> powered on - we can toggle the AirplaneMode property as much as we want
> (that's what "Turn On/Off" does after all), that's not going to change. So a
> better option may be to do
> 
>   this._toggleItem.actor.visible = nConnectedDevices > -1;
> 
> instead ...
> 
> ::: js/ui/status/bluetooth.js
> @@ +134,3 @@
>  
> +// Bluetooth will be considered 'Off' if either the adapter
> +// is not available or it's set in irplane mode.
> 
> *airplane

I thought the same thing, but I'm not 100% sure on whether it's possible
to have a BT adapter that would be "powered on"/"available" and would
still report to be in airplane mode (either soft or hard), so I thought
the sane thing to do was to check both things, just in case.

What looks more clear to me, is that the same condition should be used
in both places, since what you want to

[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

Launchpad has imported 23 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=782530.

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 2017-05-11T18:58:52+00:00 BenjaminBerg wrote:

Because of the method that the dbus proxies are created there is
currently a race condition. When an adapter is added it can have an
initial "Powered" state of off which is turned on immediately
afterwards. However, the signal connect to get the update only happens
later.

This can be easily reproduced on thinkpads by running "rfkill block 0"
and "rfkill unblock 0" while looking at the gnome-control-center
bluetooth panel.

Attaching a patch that should fix the issue. I hope I didn't totally
misunderstand how the whole DBus proxy stuff is supposed to work.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/0


On 2017-05-11T19:03:39+00:00 BenjaminBerg wrote:

Created attachment 351663
lib: Rework adapter and device proxy registrations.

This fixes a race condition when a property was updated right after the
object appeared on the bus. Due to the old implementation the property
change would not be registered in that case.

This moves the code to use GDBusObjectManagerClient and using the
provided GObject properties instead of a separate proxy to avoid the
race condition.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/1


On 2017-05-16T09:15:35+00:00 Bugzilla-x wrote:

Review of attachment 351663:

The patch is unreviewable. Make the hunks bigger and try to split up the
changes if at all possible.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/2


On 2017-05-16T11:48:04+00:00 BenjaminBerg wrote:

Created attachment 351966
lib: Rework adapter and device proxy registrations.

This fixes a race condition when a property was updated right after the
object appeared on the bus. Due to the old implementation the property
change would not be registered in that case.

This moves the code to use GDBusObjectManagerClient and using the
provided GObject properties instead of a separate proxy to avoid the
race condition.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/3


On 2017-05-16T11:48:15+00:00 BenjaminBerg wrote:

Created attachment 351967
lib: Always send "default-adapter-powered"

Fix sending of default-adapter-powered in the case that the default
adapter is being disabled.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/4


On 2017-05-16T11:48:38+00:00 BenjaminBerg wrote:

Created attachment 351968
lib: Force custom icon code override to run

The property setter currently contains some magic to modify the icon for
certain device types. Send a property change notification to force this
code to run after a device has been added.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/5


On 2017-05-16T11:49:01+00:00 BenjaminBerg wrote:

There, that is all logical changes split out.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/6


On 2017-05-16T12:27:56+00:00 Bugzilla-x wrote:

I won't have time to review this in the short-term, but a dbusmock
regression test which shows the problem before, and shows it fixed
afterwards would be really useful.

See those in gnome-settings-daemon (though they've been broken for a while for 
different reasons...):
https://git.gnome.org//browse/gnome-settings-daemon/tree/tests/gsdtestcase.py
https://git.gnome.org//browse/gnome-settings-daemon/tree/plugins/power/test.py

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1738838/comments/7


On 2017-05-16T17:23:35+00:00 BenjaminBerg wrote:

The patch might be hard to read as it changes all the property accessors, but 
really it all boils down to the two questions:
 * Is it correct to use GDBusObjectManagerClient to keep track of the objects?
 * Is it good to use GObject properties on the Adapter1/Device1 proxies 
(instead of manually driving a DBus properties interface proxy)?

I agree that dbusmock test would be nice in here. But I

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Here is the whole window showing the inset.

** Attachment added: "gnome-shell-bug_3.png.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5321009/+files/gnome-shell-bug_3.png.png

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

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

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

I'm not so sure about the waking from suspend triggering it now.  I just
tried three times, with no problem.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

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

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

The screenshot was not done perfectly, and it is a tad difficult to get
it that way, because it is uncertain how much of the window title bar to
include. The dimensions I get are 764x436 on the inset part. (See
attachments.)

** Attachment added: "gnome-shell-bug_inset3.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5321008/+files/gnome-shell-bug_inset3.png

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

Title:
Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
This happens with a number of different programs, so I suspect it is a
window manager bug. The best way to describe it is with a screen
shot. The only responsive part of the screen is the small window in
the upper left. You can hit the little maximize box and it goes back
to full screen okay, but after a while it comes back to this. It can
be annoying, because sometimes you can't quickly see what happened to
the title bar. I'm using Ubuntu 19.10. This has been happening for
about a week.

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

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

[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

Confirmed the same bug is still in gnome-shell master (version 3.35).

** Bug watch added: bugzilla.gnome.org/ #789110
   https://bugzilla.gnome.org/show_bug.cgi?id=789110

** Changed in: gnome-shell
   Importance: Medium => Unknown

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

** Changed in: gnome-shell
 Remote watch: GNOME Bug Tracker #789110 => bugzilla.gnome.org/ #789110

** Tags added: focal

** Bug watch added: bugzilla.gnome.org/ #782530
   https://bugzilla.gnome.org/show_bug.cgi?id=782530

** Changed in: gnome-bluetooth
 Remote watch: GNOME Bug Tracker #782530 => bugzilla.gnome.org/ #782530

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

** Changed in: gnome-bluetooth (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in GNOME Shell:
  Unknown
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Desktop-packages] [Bug 1859970] Re: Screenshots from an area selection have tinted colour when running wayland

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

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

Title:
  Screenshots from an area selection have tinted colour when running
  wayland

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

Bug description:
  All my screenshots taken on 20.04 with wayland have an orange tint to
  them. This appears to be the overlay which you get when selecting an
  area. Full screen screenshots and window screenshots are unaffected,
  only area screenshots appear to have the problem.

  Steps to reproduce

  Login to a wayland session
  Hold down Shift and Press PrintScreen
  Select an area to screenshot
  Navigate to ~/Pictures
  Open the picture you just took

  Expected outcome

  Screenshot of area taken as it would have been on screen

  Actual outcome

  Screenshot is taken, but has an orange border and overlay. (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:50:50 2020
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859970] Re: orange tint in screenshots when running wayland

Different colour theme, but same bug: https://gitlab.gnome.org/GNOME
/gnome-shell/issues/1999

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

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1999
   Importance: Unknown
   Status: Unknown

** Summary changed:

- orange tint in screenshots when running wayland
+ Screenshots from an area selection have tinted colour when running wayland

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

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

Title:
  Screenshots from an area selection have tinted colour when running
  wayland

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  All my screenshots taken on 20.04 with wayland have an orange tint to
  them. This appears to be the overlay which you get when selecting an
  area. Full screen screenshots and window screenshots are unaffected,
  only area screenshots appear to have the problem.

  Steps to reproduce

  Login to a wayland session
  Hold down Shift and Press PrintScreen
  Select an area to screenshot
  Navigate to ~/Pictures
  Open the picture you just took

  Expected outcome

  Screenshot of area taken as it would have been on screen

  Actual outcome

  Screenshot is taken, but has an orange border and overlay. (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:50:50 2020
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

I can imagine some delays could be mutter's fault...

(just a theory)

If we get a burst of a number of new connector/hotplug/udev events and
mutter tries to action each one immediately then it will take a long
time and lots of flashing to get through all of them. To avoid that,
mutter should be ignoring such events for some short period so that it
can group them into a single config change that will complete faster.

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

Title:
  Display freaks out when external monitors are attached

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1860036] Re: Samsung 85" TV worked for short time, now doesn't

Please run these commands on the machine while the problem is occurring:

  xrandr > xrandr.txt
  lspci -k > lspcik.txt
  dmesg > dmesg.txt

and then attach the resulting files.

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

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

Title:
  Samsung 85" TV worked for short time, now doesn't

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 18.04 on a media PC connected to a samsung smart
  TV. this morning the TV was no longer displaying, and reporting that
  the resolution was not possible to display. I tinkered with the
  settings, and now the TV will not connect to the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:47:50 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'enable-animations' b'false'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'Adwaita-dark'"
  InstallationDate: Installed on 2020-01-11 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1859996] Re: pulseaudio-equalizer make pulseaudio's start fail

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1859996

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server

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

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

[Desktop-packages] [Bug 1860052] Re: gnome-shell crash when typing into file browser dialog in Discord app

[308904.167775] shaggy gnome-shell[29086]: JS object wrapper for GObject 
0x55863e548a60 (GSettings) is being released while toggle references are still 
pending.
[308904.168190] shaggy gnome-shell[29086]: GNOME Shell crashed with signal 5
[308904.168190] shaggy gnome-shell[29086]: == Stack trace for context 
0x558634ec2380 ==
(missing stack trace)

** Summary changed:

- gnome-shell crash when typing into file browser dialog in Discord app
+ gnome-shell crash when typing into file browser dialog in Discord app [JS 
object wrapper for GObject 0x55863e548a60 (GSettings) is being released while 
toggle references are still pending.]

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

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

Title:
  gnome-shell crash when typing into file browser dialog in Discord app
  [JS object wrapper for GObject 0x55863e548a60 (GSettings) is being
  released while toggle references are still pending.]

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

Bug description:
  This is a specific instance of
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664

  I cannot see the journal that will be attached to the bug in advance,
  so I can't copy the error message to the summary.

  While using the Discord app I clicked the (+) button in order to
  select a file to upload into a chat, which led to the normal file
  browser dialog. I then typed either "/hom" or "~/.l" or ".loc" and
  before the interface could update to show that I had typed anything it
  froze, then a few seconds later almost all programs had closed and
  gnome-shell was restarting after having crashed.

  I am running Ubuntu 19.10, gnome-shell
  3.34.1+git20191024-1ubuntu1~19.10.1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18
  Uname: Linux 4.15.0-1065-oem x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_1065_75_oem_61
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 15:18:26 2020
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-12-28 (19 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-12-30 (17 days ago)

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

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

I would like to understand if the long delay is just the time it takes
for the kernel to advertise the new connectors, or if it's some delay in
mutter.

Separately, yes the desktop should never appear cut in the middle of the
screen like that so that part sounds like a mutter bug. We potentially
have two separate bugs here.

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

Title:
  Display freaks out when external monitors are attached

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

Wow. Already reported, by the same person, 1 bugs ago. Bug 1849955.

** Tags added: eoan

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

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

Title:
  Display freaks out when external monitors are attached

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1687253] Re: Correct desktop scaling factor not used when hotplugging a monitor (until after rebooting)

Is this problem still happening in current Ubuntu releases?

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

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

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

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

Title:
  Correct desktop scaling factor not used when hotplugging a monitor
  (until after rebooting)

Status in Ubuntu GNOME:
  Incomplete
Status in gnome-desktop package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The title is fairly self explanatory: I have an ASUS UX305C laptop
  with a UHD screen, and when I plug it into a 27 inch monitor via an
  HDMI cable to dock it, there's no way to achieve the standard DPI
  scaling that the system UI does without rebooting. With the major
  increases in 4k monitor popularity, docking a laptop to a higher
  resolution monitor is going to become a very common use case in the
  future, and attempts to accommodate it should be made. I know that
  this is difficult to do as not all programs draw things the same way,
  but you should at least be able to make this work for system apps.

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

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

[Desktop-packages] [Bug 1849955] Re: Display jumps on dock/undock and on volume/brightness overlay

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

** This bug has been marked a duplicate of bug 1859955
   Display freaks out when external monitors are attached

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

Title:
  Display jumps on dock/undock and on volume/brightness overlay

Status in mutter package in Ubuntu:
  New

Bug description:
  I often dock/undock my laptop, introducing two additional displays.
  Every time I dock/undock (and when using the volume/brightness
  controls after undocking) the display jumps about. Here's a video
  showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8

  Steps to reproduce.

  * Plug laptop into a docking station (possibly just attach an external 
display)
  * Configure the desktop running spanning all displays
  * Remove the external display / undock
  * Observe the laptop desktop jump around
  * Use the brightness or volume adjust keys
  * Observe the laptop desktop jump around

  Expected behaviour

  * The desktop should not jump around

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 14:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (628 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago)

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

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

[Desktop-packages] [Bug 1695036] Re: multiple screens cannot align askew

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  multiple screens cannot align askew

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Using Ubuntu 17.04 and gnome-shell 3.24.1-0ubuntu on an HP laptop with
  an ASUS screen, I have the screen to the right of the laptop on the
  desk and set back so that *visually* the ASUS screen is to the right
  and about 50% up from the laptop screen.

  On the Unity desktop, when the Display configuration is set to the
  ASUS rectangle is moved up from the baseline of the laptop screen
  rectangle, there is a seamless path for the mouse to travel from one
  screen to the next, up at an angle, the cursor exits at 75% on one
  screen and enters the next at 25% of the height, a very natural
  movement.

  This does not work with Gnome-Shell: no matter how the rectangles in
  the Display system setup are aligned, if the cursor exits one screen
  at 25% of the height, it will enter the other screen also at 25% of
  the height, which is no big deal, but it is annoying and all the more
  so when it works in the deprecated Unity desktop.

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

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

Yeah the data we would like to see attached automatically are:

  lspci -k
  xrandr

Alan, can you please run 'xrandr' before and after docking, and attach
them? I suspect the trigger for this confusion is the introduction of
new monitor connectors (not just new monitors).

Also please run:

  ls /sys/class/drm

before and after docking to see if the results are changing.


** Tags added: multimonitor

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

Title:
  Display freaks out when external monitors are attached

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

2020-01-16 Thread T F

Hey it’s been two years I’m wondering if anyone knows the solution to
this

-- 
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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Thanks.

That shows your screen is natively 1920x1080 but the current mode is
1600x900. Can you please take a screenshot and tell us the dimensions of
the screenshot image vs the dimensions of the the small fullscreen
window within it?

   1920x1080 60.05 +  60.0159.9759.9659.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82*

Also, if the problem continues then please try to write down the steps
required to reproduce it.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

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

[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption

Finally, the problem might be triggered by the atomic modesetting code
used by Xorg sessions. Please try logging into 'Ubuntu on Wayland' and
tell us if that avoids some of the problem.

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

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

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

Title:
  [comet lake] Gnome freezes, icons missing, graphics corruption

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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/linux/+bug/1859730/+subscriptions

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

[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption

This also appears once in your kernel log:

[   24.955117] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe A FIFO underrun

which might be associated with the flashing and out-of-sync screen you
describe. See bug 1550779.

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

Title:
  [comet lake] Gnome freezes, icons missing, graphics corruption

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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/linux/+bug/1859730/+subscriptions

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

[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption

Thanks.

I should have noticed earlier that you're using very new hardware with a
slightly old Ubuntu release. Although it is the latest LTS release.

I am guessing you probably need a newer version of Mesa for this GPU. To
test that theory please try booting Ubuntu 20.04 from USB
(http://cdimage.ubuntu.com/daily-live/current/) and tell us if it has
the same issues.


** Summary changed:

- Xorg freeze
+ [comet lake] Gnome freezes, icons missing, graphics corruption

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

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

Title:
  [comet lake] Gnome freezes, icons missing, graphics corruption

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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/linux/+bug/1859730/+subscriptions

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

[Desktop-packages] [Bug 1859071] Re: Modesetting randomly fails to offer all modes available in the EDID

Thanks!

The login screen uses Wayland so that's also a good test in itself. If
the issue affects the Wayland backend then it sounds like this is a
kernel or hardware problem. To check that, next time the issue happens,
please run:

  grep . /sys/class/drm/*/modes > modes.txt

and then attach the file 'modes.txt' here.

---

Just a guess: The problem might be timeouts on the i2c bus waiting for
the monitor to return its EDID. So that could happen randomly. In that
case, maybe try a different DisplayPort cable if you can.

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

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

** Changed in: linux (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/1859071

Title:
  Modesetting randomly fails to offer all modes available in the EDID

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy lightdm
  lightdm:
Installed: 1.30.0-0ubuntu1
Candidate: 1.30.0-0ubuntu1
Version table:
   *** 1.30.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status
  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  
  I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor 
attached via DisplayPort. The monitor has a native resolution of 2560x1080. 
When I power on my laptop, it is seemingly random whether one of the three 
following situations occurs. 
  1. Displays at the proper native resolution of 2560x1080,
  2. Displays at 1600x1200 but not let me select a higher resolution in display 
settings, or 
  3. The display will fail to connect and stay blank (when I enter display 
settings it will be on "Single Monitor" mode, but from there I can enable Join 
Displays and set it to its native resolution).

  Please note I selected "I don't know" instead of gdm3 or lightdm since
  i've been having this issue since before installing/switching to
  lightdm.

  Please let me know what additional information I can provide at this time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7]
  InstallationDate: Installed on 2020-01-05 (9 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 2478A44
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET96WW(2.56)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478A44
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L530
  dmi.product.name: 2478A44
  dmi.product.sku: LENOVO_MT_2478
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Desktop-packages] [Bug 1859730] [NEW] [comet lake] Gnome freezes, icons missing, graphics corruption

You have been subscribed to a public bug:

ack please..

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.4.11-050411-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Tue Jan 14 20:17:26 2020
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
 backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2020-01-13 (1 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0029 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 7390
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
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: mesa (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic freeze ubuntu
-- 
[comet lake] Gnome freezes, icons missing, graphics corruption
https://bugs.launchpad.net/bugs/1859730
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mesa in Ubuntu.

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

[Desktop-packages] [Bug 1860057] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new

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

** This bug has been marked a duplicate of bug 1849249
   gnome-shell crashed with SIGABRT: 
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: 
(workspace == NULL)

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

Also tracking in:
https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8

as well the existing:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

** Tags added: focal

** Description changed:

  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
+ https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8
  
  gnome-shell crashes with this bug every time that:
  
  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)
  
  The system beeps to indicate that the text isn't found, but then
  crashes.
  
  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.
  
  (Note: I originally thought that if I moved the find window to the other
  window and then searched, gnome-shell crashed, but I think what happens
  is a) I open the window, b) I move it, search for something, and it
  works, c) I close it and re-open it - it then opens on the other monitor
  and searching will crash gnome-shell.)
  
  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.
  
  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
  https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)

  The system beeps to indicate that the text isn't found, but then
  crashes.

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1

[Desktop-packages] [Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

** Changed in: gnome-settings-daemon
   Status: Unknown => New

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

Title:
  The bluetooth gets started automatically whenever a network is
  selected after turning on the wifi.

Status in GNOME Settings Daemon:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Whenever the WiFi feature is turned off after usage,the system
  automatically goes to Airplane mode.If the user turns on the WiFi
  again by selecting the option Select Network in WiFi menu bar then a
  dialog box is displayed with the option of TURN OFF THE AIRPLANE
  MODE.After clicking the option, the Bluetooth automatically gets TURN
  ON without users willing(Even though not required).Or if continue with
  turning on the WiFi ,another dialog box appears with the option of
  TURN ON WiFi. After clicking this option ,the system will search for
  WiFi networks. Once the desired network is selected the WiFi starts
  working. After this if the user check the Bluetooth, it gets started
  automatically with use.This may lead to quick battery drainage.

  In short, the Bluetooth gets automatically started even if not
  required after turning the airplane mode OFF. Please solve this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 00:49:11 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-07 (526 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Vostro 3578
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1859867/+subscriptions

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

[Desktop-packages] [Bug 1860057] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new

2020-01-16 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: focal

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

I reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2113
but that then moved to: 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288

** Project changed: gnome-shell => gnome-settings-daemon

** Changed in: gnome-settings-daemon
   Status: New => Unknown

** Changed in: gnome-settings-daemon
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #2113 => 
gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288

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

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Triaged

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

Title:
  The bluetooth gets started automatically whenever a network is
  selected after turning on the wifi.

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Whenever the WiFi feature is turned off after usage,the system
  automatically goes to Airplane mode.If the user turns on the WiFi
  again by selecting the option Select Network in WiFi menu bar then a
  dialog box is displayed with the option of TURN OFF THE AIRPLANE
  MODE.After clicking the option, the Bluetooth automatically gets TURN
  ON without users willing(Even though not required).Or if continue with
  turning on the WiFi ,another dialog box appears with the option of
  TURN ON WiFi. After clicking this option ,the system will search for
  WiFi networks. Once the desired network is selected the WiFi starts
  working. After this if the user check the Bluetooth, it gets started
  automatically with use.This may lead to quick battery drainage.

  In short, the Bluetooth gets automatically started even if not
  required after turning the airplane mode OFF. Please solve this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 00:49:11 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-07 (526 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Vostro 3578
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1859867/+subscriptions

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

[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() f

^^^
Looks like a typo. See bug 1860052 instead.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from g_logv() from
  g_log() from gjs_callback_closure() from ffi_closure_unix64_inner()
  [any error message logged from JavaScript will look like this]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

2020-01-16 Thread Rocko

This is still 100% reproducible with with an up-to-date Ubuntu 20.04.

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)

  The system beeps to indicate that the text isn't found, but then
  crashes.

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

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

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

[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() f

2020-01-16 Thread sparr

I have created a more specific bug report, for a crash triggered from
the file browser in the Discord app, here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from g_logv() from
  g_log() from gjs_callback_closure() from ffi_closure_unix64_inner()
  [any error message logged from JavaScript will look like this]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1860052] [NEW] gnome-shell crash when typing into file browser dialog in Discord app

2020-01-16 Thread sparr

Public bug reported:

This is a specific instance of https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1736664

I cannot see the journal that will be attached to the bug in advance, so
I can't copy the error message to the summary.

While using the Discord app I clicked the (+) button in order to select
a file to upload into a chat, which led to the normal file browser
dialog. I then typed either "/hom" or "~/.l" or ".loc" and before the
interface could update to show that I had typed anything it froze, then
a few seconds later almost all programs had closed and gnome-shell was
restarting after having crashed.

I am running Ubuntu 19.10, gnome-shell
3.34.1+git20191024-1ubuntu1~19.10.1

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18
Uname: Linux 4.15.0-1065-oem x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_1065_75_oem_61
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 15:18:26 2020
DisplayManager: gdm3
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
InstallationDate: Installed on 2019-12-28 (19 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-12-30 (17 days ago)

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


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

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

Title:
  gnome-shell crash when typing into file browser dialog in Discord app

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is a specific instance of
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664

  I cannot see the journal that will be attached to the bug in advance,
  so I can't copy the error message to the summary.

  While using the Discord app I clicked the (+) button in order to
  select a file to upload into a chat, which led to the normal file
  browser dialog. I then typed either "/hom" or "~/.l" or ".loc" and
  before the interface could update to show that I had typed anything it
  froze, then a few seconds later almost all programs had closed and
  gnome-shell was restarting after having crashed.

  I am running Ubuntu 19.10, gnome-shell
  3.34.1+git20191024-1ubuntu1~19.10.1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18
  Uname: Linux 4.15.0-1065-oem x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_1065_75_oem_61
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 15:18:26 2020
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-12-28 (19 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-12-30 (17 days ago)

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

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

[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() f

2020-01-16 Thread sparr

https://errors.ubuntu.com/oops/89b39b4a-38b3-11ea-b8ae-fa163e102db1
https://errors.ubuntu.com/oops/9d568826-30e1-11ea-a775-fa163ee63de6

these two crashes seem to be this bug. this is a recurring (but not
easily reproducible) problem for me, most often triggered by typing into
the File > Open dialog in various applications (typing in order to
navigate to a file path, often starting with / or .)

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from g_logv() from
  g_log() from gjs_callback_closure() from ffi_closure_unix64_inner()
  [any error message logged from JavaScript will look like this]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1751593] Re: Weird black border flickers around windows in Wayland sessions

** Changed in: mutter
   Status: New => 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/1751593

Title:
  Weird black border flickers around windows in Wayland sessions

Status in GNOME Shell:
  Expired
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Whenever I open any new window, a black border around the window
  appears for a fraction of a second (like a flicker).

  Although this doesn't happen very frequently, happens around 3-4 times
  out of 10. This is most noticeable when I right click on Desktop and
  click on "Open terminal". I can replicate this bug every time when I
  open terminal this way.

  Also, when I open terminal by pressing Control+Alt+T, the caption
  buttons kind of grey out after the flicker and are un-clickable. They
  look as if the window is not at focus. Workaround is to switch to
  another window (Alt+Tab) and then switch back to terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 19:58:24 2018
  InstallationDate: Installed on 2018-02-13 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Unfortunately it is back. I did notice this time that it happened just
after waking from suspend, and I think that has been the pattern. This
should be useful. Here is the xrandr output.

** Attachment added: "xrandr.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320968/+files/xrandr.txt

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

Title:
Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
Incomplete

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

[Desktop-packages] [Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome

2020-01-16 Thread joke2k

Sometimes reinstalling the fonts-noto-color-emoji package fixes the bug
until the reboot.

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

Title:
  fonts-noto-color-emoji not making pretty emojis in google chrome

Status in fonts-noto-color-emoji package in Ubuntu:
  Incomplete

Bug description:
  Google-Chrome and emoji's is being a weird headache. Something's causing it 
not to find the right font to make emoji's:
  
"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions

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

[Desktop-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2020-01-16 Thread Coeur Noir

Oooh sadness ! My flickering problem is back since those recent updates
from official regular repositories :

coeur-noir@asgard:~$ dpkg -l | grep mesa
ii  libegl-mesa0:amd64  19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the EGL API -- Mesa vendor 
library
ii  libegl1-mesa:amd64  19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libgl1-mesa-dri:amd64   19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i38619.2.1-1ubuntu1~18.04.1 
i386 free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64   19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libgl1-mesa-glx:i38619.2.1-1ubuntu1~18.04.1 
i386 transitional dummy package
ii  libglapi-mesa:amd64 19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the GL API -- shared library
ii  libglapi-mesa:i386  19.2.1-1ubuntu1~18.04.1 
i386 free implementation of the GL API -- shared library
ii  libgles2-mesa:amd64 19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libglu1-mesa:amd64  9.0.0-2.1build1 
amd64Mesa OpenGL utility library (GLU)
ii  libglu1-mesa:i386   9.0.0-2.1build1 
i386 Mesa OpenGL utility library (GLU)
ii  libglx-mesa0:amd64  19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the OpenGL API -- GLX vendor 
library
ii  libglx-mesa0:i386   19.2.1-1ubuntu1~18.04.1 
i386 free implementation of the OpenGL API -- GLX vendor 
library
ii  libosmesa6:amd6419.2.1-1ubuntu1~18.04.1 
amd64Mesa Off-screen rendering extension
ii  libosmesa6:i386 19.2.1-1ubuntu1~18.04.1 
i386 Mesa Off-screen rendering extension
ii  libwayland-egl1-mesa:amd64  19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  mesa-utils  8.4.0-1 
amd64Miscellaneous Mesa GL utilities
ii  mesa-utils-extra8.4.0-1 
amd64Miscellaneous Mesa utilies (opengles, egl)
ii  mesa-va-drivers:amd64   19.2.1-1ubuntu1~18.04.1 
amd64Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:amd6419.2.1-1ubuntu1~18.04.1 
amd64Mesa VDPAU video acceleration drivers
ii  mesa-vulkan-drivers:amd64   19.2.1-1ubuntu1~18.04.1 
amd64Mesa Vulkan graphics drivers
coeur-noir@asgard:~$

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in mesa package in Ubuntu:
  Confirmed
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c-d
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :

[Desktop-packages] [Bug 1655348] Re: gpu-manager Error: can't open /lib/modules/

2020-01-16 Thread Fellipe Weno

I'm experiencing those hangs too. I have two different machines running 
different versions of Ubuntu.
One is a Ryzen with a NVIDIA card, using the proprietary drivers. The other is 
a Intel Coffee Lake, no HT and no discrete GPU.

In the first machine(Ryzen + NVIDIA) this started to happen more often
after a upgrade to 19.04. On 18.04 it happened, in the whole year it
ran, no more than a couple of times. Also, different of what the OP
said, in my case even that the machine freezes, it comes back to life
after a couple of minutes. But most of the time I just SSH to the
machine, and kill Chrome or WINE, and it recover faster.

In the second machine(Intel + iGPU), it started to happen after a
reinstall of the 18.04, it didn't happened before. But the behavior is
different, in this machine the XWindow freezes and dies miserably,
ending all processes running on it, and that is the machine I use to
work... so pretty bad.

In terms of LOG, I - like others in this thread; couldn't find anything
useful, in fact is hard to pinpoint the origin of the problem.

I really willing to help with this, but I need guidance to gather
information on this. I just can't see what may be causing this issue, as
I pointed out above, this is not related to what GPU we are using, as I
have two completely different setups. Though it seems to be related to
the graphical system.

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

Title:
  gpu-manager Error: can't open /lib/modules/

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  At least once a day there is an unexpected desktop freeze incl. mouse
  and keyboard. Even magic-sys-rq isn't possible, only hard switch-off.
  From smartmontools I can exclude a hardware failure.

  I've found that gpu-manager and systemd fail to load kernel modules.
  This is among the output of journalctl | grep modules
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Unit entered 
failed state.
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Failed with result 
'exit-code'.
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  (terminal-output attached)

  dito with latest kernel

  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms
  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 14:37:00 2017
  InstallationDate: Installed on 2012-02-05 (1801 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (162 days ago)

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

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

[Desktop-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome

2020-01-16 Thread Norbert

Still reproducible on 20200115 and 20200116 builds.

---

Reproducible method 1:

1. boot installation media
2. select [o] Normal installation, [x] Download updates, [x] Install 
third-party software
3. Wait installation to finish
4. Boot the installed system, wait for Snappy unpacking/initialization/seeding 
(check from tty1 with `snap list`)
5. Login to desktop session
6. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is 
starting to appear.


Reproducible method 2:

1. boot installation media
2. select [o] Normal installation, [ ] Download updates, [ ] Install 
third-party software
3. Wait installation to finish
4. Boot the installed system, wait for Snappy unpacking/initialization/seeding 
(check from tty1 with `snap list`)
5. Install Ubuntu restricted extras with `sudo apt-get install 
ubuntu-restricted-extras` and reboot
6. Login to desktop session
7. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is 
starting to appear.


Guest settings: choosing video acceleration disabled or 3d video acceleration 
does not change behavior. Increasing VRAM from default 16 Mb to 128 Mb (max for 
my machine) does not help either.
VirtualBox versions tested: 

* 5.1.38-dfsg-0ubuntu1.16.04.3 (from multiverse) - crash,
* 5.0.40 (from Oracle) - crash,
* 5.1.38 (from Oracle) - crash, 
* 5.2.36 (from Oracle) - crash, 
* 6.0.16 (from Oracle) - crash,
* 6.1.2 (from Oracle) - crash.

---

Removing `ubuntu-mate-welcome` from autostart with `sudo rm
/etc/xdg/autostart/ubuntu-mate-welcome-autostart.desktop` fixes the
login issue. But direct launch of it with `ubuntu-mate-welcome` ends
with another crash.

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

Title:
  X11 crashed when attempting to open Budgie and MATE Welcome

Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Went to the menu button in upper left corner. Attempted to open Budgie
  Welcome and the X11 session crashed. About 4 lines of error code were
  displayed for a few seconds then the login screen appeared.

  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  budgie-welcome:
Installed: (none)
Candidate: 0.6.1
Version table:
   0.6.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

  Seems to not be installed on a fresh install. So solved but needs
  fixing?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  BootLog:
   [[0;32m  OK  [0m] Stopped Snappy daemon.
Starting Snappy daemon...
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Oct  5 20:36:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 
(20181005)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 
"../../../../../../include/privates.h", line=121, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", 
file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, 
function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
   ?? ()
  Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  User

[Desktop-packages] [Bug 1860037] Re: Typo in the Russian interface of the package

2020-01-16 Thread Gunnar Hjalmarsson

Thanks for your report! It's an upstream issue, and should preferably be
corrected there.

https://l10n.gnome.org/vertimus/gnome-control-center/master/po/ru/

It may be fixed in Ubuntu only for now via the Launchpad interface.

https://translations.launchpad.net/ubuntu/focal/+source/gnome-control-
center/+pots/gnome-control-
center-2.0/ru/+translate?search=%D0%B2%D1%85%D0%BE%D0%B4%D0%B5+%D1%81

** Package changed: gnome-control-center (Ubuntu) => ubuntu-translations

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => Triaged

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Russian Ubuntu Translators (ubuntu-l10n-ru)

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

Title:
  Typo in the Russian interface of the package

Status in Ubuntu Translations:
  Triaged

Bug description:
  The Russian interface of the gnome-control-center package contains a typo. A 
typo is highlighted in the attached screenshot. Instead of "входе с систему" 
you must specify "входе в систему".
  Ubuntu version is 18.04.3 LTS
  gnome-control-center version is 1:3.28.2-0ubuntu0.18.04.5

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

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

[Desktop-packages] [Bug 1860037] [NEW] Typo in the Russian interface of the package

2020-01-16 Thread Ilia Belousov

Public bug reported:

The Russian interface of the gnome-control-center package contains a typo. A 
typo is highlighted in the attached screenshot. Instead of "входе с систему" 
you must specify "входе в систему".
Ubuntu version is 18.04.3 LTS
gnome-control-center version is 1:3.28.2-0ubuntu0.18.04.5

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


** Tags: typo

** Attachment added: "Снимок экрана от 2020-01-16 22-32-14.png"
   
https://bugs.launchpad.net/bugs/1860037/+attachment/5320936/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-01-16%2022-32-14.png

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

Title:
  Typo in the Russian interface of the package

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

Bug description:
  The Russian interface of the gnome-control-center package contains a typo. A 
typo is highlighted in the attached screenshot. Instead of "входе с систему" 
you must specify "входе в систему".
  Ubuntu version is 18.04.3 LTS
  gnome-control-center version is 1:3.28.2-0ubuntu0.18.04.5

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

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

[Desktop-packages] [Bug 1859857] Re: network-manager keeps asking for wifi password can't connect to any wifi

2020-01-16 Thread Michael Moessner

Thanks for looking into this issue!

"From what version to what version did you update?"
I did just one of the regular upgrades, no upgrade to a new ubuntu version. 
Unfortunately, I cannot say which packages were updated.

"What desktop do you use?"
I am using the kubuntu flavour, thus the desktop was kde. Maybe I should note 
that I enabled the kubuntu-backports (kubuntu-ppa-ubuntu-backports-eoan)

I added the result of journalctl -b 0. Please do not wonder, here I used
another kernel as I did, when firstly reporting the bug, however, the
issue is the same.

Some more observations:
- I tried different kernels (5.3.0-23, 5.3.0-26, 5.3.0-26-lowlatency). There is 
always the same behaviour. (This is in contrast to report #1859289, where 
lowlatency seemed to work)
- I tried also to connect to a hotspot created from my mobile, this also does 
not work (it also used wpa password protection).
- I tried to connect to a public access point without password protection. Here 
the wifi is working flawlessy.

Best regards.

** Attachment added: "Result of journalctl -b 0"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1859857/+attachment/5320935/+files/journald.txt

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

Title:
  network-manager keeps asking for wifi password can't connect to any
  wifi

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This bug is the same as reported by #1859289, however I was not able
  to find this when using the ubuntu-bug tool.

  Since the last update my network-manager keeps asking me for wifi
  passworts, but then never connects. Password is definitely correct.
  Everything worked before the update.

  lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Jan 15 19:12:42 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-05-27 (233 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.23 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (83 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1860036] [NEW] Samsung 85" TV worked for short time, now doesn't

2020-01-16 Thread Simon

Public bug reported:

I installed Ubuntu 18.04 on a media PC connected to a samsung smart TV.
this morning the TV was no longer displaying, and reporting that the
resolution was not possible to display. I tinkered with the settings,
and now the TV will not connect to the PC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.2
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 11:47:50 2020
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'enable-animations' b'false'
 b'org.gnome.desktop.interface' b'gtk-theme' b"'Adwaita-dark'"
InstallationDate: Installed on 2020-01-11 (4 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Samsung 85" TV worked for short time, now doesn't

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 on a media PC connected to a samsung smart
  TV. this morning the TV was no longer displaying, and reporting that
  the resolution was not possible to display. I tinkered with the
  settings, and now the TV will not connect to the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:47:50 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'enable-animations' b'false'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'Adwaita-dark'"
  InstallationDate: Installed on 2020-01-11 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1859071] Re: Modesetting randomly fails to offer all modes available in the EDID

2020-01-16 Thread Tizzy

Hello Daniel,
Today the issue occured again, so I was sure to login with "Ubuntu on Wayland", 
but the issue persisted until I rebooted (as usual). Please keep in mind the 
screen is in the wrong resolution while on the login screen, as well.
Let me know if i can do anything else to help.

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

Title:
  Modesetting randomly fails to offer all modes available in the EDID

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy lightdm
  lightdm:
Installed: 1.30.0-0ubuntu1
Candidate: 1.30.0-0ubuntu1
Version table:
   *** 1.30.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status
  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  
  I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor 
attached via DisplayPort. The monitor has a native resolution of 2560x1080. 
When I power on my laptop, it is seemingly random whether one of the three 
following situations occurs. 
  1. Displays at the proper native resolution of 2560x1080,
  2. Displays at 1600x1200 but not let me select a higher resolution in display 
settings, or 
  3. The display will fail to connect and stay blank (when I enter display 
settings it will be on "Single Monitor" mode, but from there I can enable Join 
Displays and set it to its native resolution).

  Please note I selected "I don't know" instead of gdm3 or lightdm since
  i've been having this issue since before installing/switching to
  lightdm.

  Please let me know what additional information I can provide at this time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7]
  InstallationDate: Installed on 2020-01-05 (9 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 2478A44
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET96WW(2.56)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478A44
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L530
  dmi.product.name: 2478A44
  dmi.product.sku: LENOVO_MT_2478
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: eoan

Re: [Desktop-packages] [Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome

2020-01-16 Thread gork skoal

No it's definitely specific to some combination of chrome emoji's and that
fon't
You can replicate that with chrome on ubuntu 19.10
Have that font installed: many people with just that installed on Chrome
either don't get emoji's working, or if they do they're just outlines kind
of like old school clipart.
However if you install Segoe UI, Segoe UI Emoji, Some get full colors some
don't. ^_^

On Thu, Jan 16, 2020 at 7:40 AM Sebastien Bacher  wrote:

> Thank you for your bug report. Is the issue specific to chrome? it might
> be an issue with the browser rather than the font...
>
> ** Changed in: fonts-noto-color-emoji (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1859926
>
> Title:
>   fonts-noto-color-emoji not making pretty emojis in google chrome
>
> Status in fonts-noto-color-emoji package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Google-Chrome and emoji's is being a weird headache. Something's causing
> it not to find the right font to make emoji's:
>
> "[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
> FontService unique font name matching request did not receive a response.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions
>

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

Title:
  fonts-noto-color-emoji not making pretty emojis in google chrome

Status in fonts-noto-color-emoji package in Ubuntu:
  Incomplete

Bug description:
  Google-Chrome and emoji's is being a weird headache. Something's causing it 
not to find the right font to make emoji's:

"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-16 Thread BloodyIron

So far it's fixed for me! Yay!!!

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-16 Thread BloodyIron

Woot! Thanks for rolling this out all involved! \o/ Stuff like this is
why I love FOSS.

Now to try it out!

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

2020-01-16 Thread Andreas Hasenack

Upstream committed more changes in this area, I have to check out what
the latest patches look like. Upstream's intention I think was to switch
wrappers to the krb5 one, which would then call smbspool if no krb5 auth
is involved.

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked

2020-01-16 Thread Jarno Suni

Does it work better with nvidia driver?

You could use another locker in 18.10 as workaround. See contents of
/usr/bin/xflock4 script for hint. (You have to kill light-locker process
and make it not start in "Session and Startup" dialog.

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

Title:
  [nouveau][XFCE] Do not see login screen after screen is blanked

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
  InstallationDate: Installed on 2018-09-03 (263 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: U
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  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/lightdm/+bug/1830408/+subscriptions

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

[Desktop-packages] [Bug 1860005] Re: "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop

** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-
icons (Ubuntu)

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

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

Title:
  "Ask what to do" popup doesn't appear when scripts are executed
  directly from Desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10
  Nautilus (Files) 3.34.1-stable (nautilus: Installed: 1:3.34.1-1ubuntu1)

  Asking whether "Run", "Run in Terminal" or "Display" script after double 
clicking is expected.
  "Ask what to do" option is set in Nautilus (Files) Behavior preferences (see 
attached screenshots).
  "Ask what to do" popup dialogue doesn't appear after double clicking 
Bash/shell script file from Desktop SHELL.
  When script is executed from Desktop and other FOLDERS, "Ask what to do" 
popup appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 17:50:44 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(683, 700)'
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-01-11 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1860005] [NEW] "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop

2020-01-16 Thread komsorg

Public bug reported:

Ubuntu 19.10
Nautilus (Files) 3.34.1-stable (nautilus: Installed: 1:3.34.1-1ubuntu1)

Asking whether "Run", "Run in Terminal" or "Display" script after double 
clicking is expected.
"Ask what to do" option is set in Nautilus (Files) Behavior preferences (see 
attached screenshots).
"Ask what to do" popup dialogue doesn't appear after double clicking Bash/shell 
script file from Desktop SHELL.
When script is executed from Desktop and other FOLDERS, "Ask what to do" popup 
appears.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 17:50:44 2020
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'initial-size' b'(683, 700)'
 b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2020-01-11 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: 19.10 amd64 apport-bug bash eoan files gnome nautilus scripts

** Attachment added: "screensots are inside the attached zip archive"
   
https://bugs.launchpad.net/bugs/1860005/+attachment/5320874/+files/Screens.zip

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

Title:
  "Ask what to do" popup doesn't appear when scripts are executed
  directly from Desktop

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10
  Nautilus (Files) 3.34.1-stable (nautilus: Installed: 1:3.34.1-1ubuntu1)

  Asking whether "Run", "Run in Terminal" or "Display" script after double 
clicking is expected.
  "Ask what to do" option is set in Nautilus (Files) Behavior preferences (see 
attached screenshots).
  "Ask what to do" popup dialogue doesn't appear after double clicking 
Bash/shell script file from Desktop SHELL.
  When script is executed from Desktop and other FOLDERS, "Ask what to do" 
popup appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 17:50:44 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(683, 700)'
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-01-11 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

Hello Adam, or anyone else affected,

Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Fix Committed
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1850932] Re: [SRU] Backport 2.62.3-2

Hello Iain, or anyone else affected,

Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-eoan

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

Title:
  [SRU] Backport 2.62.3-2

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  I'm creating this bug report to have a place to describe the proposed
  backport of glib2.0 2.62.3-2 from focal.

  One purpose of this backport is to fix bug #1844853.

  But there are several other changes. Here's the diff of NEWS:

  +Overview of changes in GLib 2.62.3
  +==
  +
  +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject 
to
  +  FD limits (#954)
  +
  +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917)
  +
  +* Bugs fixed:
  + - #954 The g_spawn_sync() function uses select() which has limitations
  + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type 
'(null)' in cast to 'GDBusServer'
  + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7
  + - #1903 use-after-free in mimeapps test causes intermittent segfault during 
testing
  + - #1916 objcopy not used from cross-compilation file in GIO tests
  + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and 
new GCC
  + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62
  + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to 
glib-2-62
  + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62`
  + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62
  + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by 
kdeinit5” to glib-2-62
  + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1
  + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error”
  + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring 
events” to glib-2-62
  + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” 
to glib-2-62
  +
  +
  +Overview of changes in GLib 2.62.2
  +==
  +
  +* Bugs fixed:
  + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a 
dedicated thread
  + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” 
to glib-2-62
  + - !1156 Backport !1146 Solaris fixes to glib-2-62

  
  This release can be considered to be tested under 
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  There are patches from the upstream master branch rather than this
  stable release:

  + Add-a-test-for-GDBusServer-authentication.patch
  + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch
  + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch
  + Make-ld-executable-configurable.patch

  They are sensible backports which I hope are appropriate for SRU.

  [ QA ]

  The testsuite fixes will verify themselves during the build and
  autopkgtest.

  For the rest of the fixes, please exercise the desktop thoroughly. Log
  in, log out, run many applications and make sure there are no
  regressions.

  [ Regression potential ]

  test fixes> Build failures or autopkgtest failures.

  GLib is a central desktop library. Regressions could break any part of
  the desktop - so QA is important, the SRU exception notwithstanding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions

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

[Desktop-packages] [Bug 1848202] Re: Use after free in gdbus leads to eds segfaults

Hello errors.ubuntu.com, or anyone else affected,

Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  Use after free in gdbus leads to eds segfaults

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

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

  [ Fix ]

  This bug was fixed upstream in 2.62.2 (see the links below). That
  update is being issues to eoan.

  [ QA ]

  Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't
  need to explicitly test that this bug is fixed. Nevertheless, to
  verify this bug please give the desktop a good workout. Ideally
  install the SRU and use your machine as you would normally for a
  variety of tasks. Make sure there are no regressions.

  [ Regression potential ]

  1) The changes involve mutexes and stuff, which is error prone.

  2) It's GLib, a core library, so any bad regressions will be really
  serious for the desktop as a whole.

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

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

[Desktop-packages] [Bug 1860002] [NEW] Airport Extreme not given working option

2020-01-16 Thread ray klassen

Public bug reported:

Description:Ubuntu 18.04.3 LTS
Release:18.04

ubuntu-drivers-common:
  Installed: 1:0.5.2.5
  Candidate: 1:0.5.2.5
  Version table:
 *** 1:0.5.2.5 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:0.5.2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Recently repurposed Macbook Pro (7,1) as ubuntu station. 
Wireless wasn't working. ubuntu-drivers recommended bcmwl-kernel-source. 
Installed as recommended. 

Not reliable on boot. Mostly wlp2s0 Scan_results error (-22).

After some research discovered that firmware-b43-installer supports
chipset on this Mac.

from 
apt-cache show firmware-b43-installer

 Supported chipsets:
  * BCM4306/3;
  * BCM4311;
  * BCM4318;
  * BCM4321;
  * BCM4322 (only 14e4:432b);
  * BCM4312 (with Low-Power a.k.a. LP-PHY).


After purging bcmwl-kernel-source, installing firmware-b43-installer,
wireless works fine.

suggest that firmware-b43-installer be a listed option for bcm4322
(14e4:432b) in ubuntu-drivers

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5.2.5
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 07:18:07 2020
InstallationDate: Installed on 2020-01-14 (1 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Airport Extreme not given working option

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ubuntu-drivers-common:
Installed: 1:0.5.2.5
Candidate: 1:0.5.2.5
Version table:
   *** 1:0.5.2.5 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.5.2 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Recently repurposed Macbook Pro (7,1) as ubuntu station. 
  Wireless wasn't working. ubuntu-drivers recommended bcmwl-kernel-source. 
  Installed as recommended. 

  Not reliable on boot. Mostly wlp2s0 Scan_results error (-22).

  After some research discovered that firmware-b43-installer supports
  chipset on this Mac.

  from 
  apt-cache show firmware-b43-installer
  
   Supported chipsets:
* BCM4306/3;
* BCM4311;
* BCM4318;
* BCM4321;
* BCM4322 (only 14e4:432b);
* BCM4312 (with Low-Power a.k.a. LP-PHY).
  

  After purging bcmwl-kernel-source, installing firmware-b43-installer,
  wireless works fine.

  suggest that firmware-b43-installer be a listed option for bcm4322
  (14e4:432b) in ubuntu-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-drivers-common 1:0.5.2.5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 07:18:07 2020
  InstallationDate: Installed on 2020-01-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1283874] Re: rhythmbox crashed with SIGABRT in do_sigtimedwait()

2020-01-16 Thread Paul White

Bug report won't expire due to bug watch.
No reply to comment #8 from reporter so closing.

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

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

Title:
  rhythmbox crashed with SIGABRT in do_sigtimedwait()

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  Rhythmnox version: 3.0.1-1ubuntu10 0

  While Rhythmnox played music, I clicked on Rhythmbox icon at
  indicator-sound to open it.

  Expected: Open Rhythmbox window.
  Happend: Crash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 24 02:06:27 2014
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2014-01-29 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
  ProcCmdline: rhythmbox
  Signal: 6
  SourcePackage: rhythmbox
  StacktraceTop:
   Py_FatalError () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
   _Py_CheckRecursiveCall () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
   PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
   PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
  Title: rhythmbox crashed with SIGABRT in Py_FatalError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1859750] Re: "Out of Paper" message is NOT displayed.

2020-01-16 Thread Till Kamppeter

Note that the affected printers are a small series of LaserJet printers
from around a decade ago, so therefore we would not develop a distro-
specific fix for this.

You could try to report this upstream, on

https://github.com/OpenPrinting/system-config-printer

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

Title:
"Out of Paper" message is NOT displayed.

Status in system-config-printer package in Ubuntu:
New

Bug description:
1) Ubuntu 19.10
2) system-config-printer 1.5.11
3) system-config-printer detected my HP Laserjet 1020. I printed a page, and
it was added to the print queue. The page did not print and the print job
disappeared from the print queue. I downloaded foo2zjs.tar.gz from
http://foo2zjs.rkkda.com/ and followed the instructions. I was able to get my
printer to successfully print pages. When my HP Laserjet 1020 is out of paper.
The green light on the printer changes to a blinking orange light. An "Out of
Paper" message with a retry button, should have been displayed.
4) An "Out of Paper" message with a retry button, was NOT displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1859750/+subscriptions

[Desktop-packages] [Bug 1858199] Re: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system

2020-01-16 Thread firefoxfans

I have changed the system  to centos7 ,the system is stable .I think  It
should  not be  a hardware problem.

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

Title:
  bugs in libvdpau_radeonsi.so  and amdgpu(or radeon) driver  freeze the
  system

Status in mesa package in Ubuntu:
  New

Bug description:
  1. In 4.15 kernel serires ,vlc or mpv  video player  with  hardware
  acceleration  output   will freeze  the system  in minutes ,the
  desktop screen  display content was frozen  ,but  sometime   the audio
  will continue to play for about 10 seconds  to one miniute,then the
  system dead。I have to  reset the machine to reboot. When upgrade to
  5.3.24 kernel,amdgpu  still hanged immediately,but play video through
  vdpau  in radeon driver the system will no hang immediately,the
  freqency of hanging  is  about serveral  times a day。  some times web
  browser in virtualbox guest  randomly hangs the system。

  2. installing  amdgpu-pro driver  download from amd official site
  (version of  18.40-697810,18.50-756341,19.10-785425,19.30-934563) are
  all the same problem with above.

  3. remove   libvdpau_radeonsi.so.1.0.0  in the system   from  ubuntu
  or installed  in /opt/amdgpu by amdgpu-pro driver  solved the problem
  .   the system  has never  been freezing for several weeks ,but the
  problem happened again  when I  restore the libvdpau_radeonsi.so file。

  4.When use amdgpu driver  the vlc output sound  via  display output port 
(through an active  hdmi adaptor to hdmi monitor) was glitches ,the sound seem 
missing or dropped in every 2~3 seconds，but when use radeon driver  the sound 
was normal.the audio problem is the same with 4.15 kernel when using kernel 
5.3.24. But  mplayer sound  is always  good ,testing with  audio output  of  
pulseaduio  and alsa ,the kernel driver only affected the sound of  vlc (tested 
with all available audio output ),the other applications was normal.
   
  5. Test with the ubuntu 19.10 live image desktop  is the same problem。

  6. My system  have four  monitors,graphics card is R7 360 ,recognized as 
(from lspci) :
  6.02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cape Verde PRO [Radeon HD 7750/8740 / R7 250E].
  infomation from uname -a :
  Linux smzhou-desktop 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue 
Nov 26 14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1859750] Re: "Out of Paper" message is NOT displayed.

** Changed in: system-config-printer (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "Out of Paper" message is NOT displayed.

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) system-config-printer 1.5.11
  3) system-config-printer detected my HP Laserjet 1020. I printed a page, and 
it was added to the print queue. The page did not print and the print job 
disappeared from the print queue. I downloaded foo2zjs.tar.gz from 
http://foo2zjs.rkkda.com/ and followed the instructions. I was able to get my 
printer to successfully print pages. When my HP Laserjet 1020 is out of paper. 
The green light on the printer changes to a blinking orange light. An "Out of 
Paper" message with a retry button, should have been displayed.
  4) An "Out of Paper" message with a retry button, was NOT displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1859750/+subscriptions

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

[Desktop-packages] [Bug 1859996] [NEW] pulseaudio-equalizer make pulseaudio's start fail

2020-01-16 Thread Jean Claveau

Public bug reported:

After installing pulseaudio-equalizer package, Pulseaudio doesn't work
anymore. Due to that, no device can be configured glad to KDE's sound
widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
devices-found-no-settings-no-sound

sudo cat /var/log/syslog | grep pulseaudio
[pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
[pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
[pulseaudio] module-equalizer-sink.c: Master sink not found
[pulseaudio] module.c: Failed to load module "module-equalizer-sink" (argument: 
""): initialization failed.

Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
module-equalizer-sink" from the .config/pulse/default.pa so it continues
to fail at start afterwards.

sudo cat /var/log/syslog | grep pulseaudio
[pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so : 
module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
[pulseaudio] module.c: Failed to open module "module-equalizer-sink".


NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
sudo apt search pulseaudio-equalizer
pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
  Equalizer sink module for PulseAudio sound server

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

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server

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

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

[Desktop-packages] [Bug 1859260] Re: Cant go back to primary monitor when app indicator menu is open

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

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

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

Title:
  Cant go back to primary monitor when app indicator menu is open

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

Bug description:
  This bugs happens if you:

  1. Open app indicator menu (top right);
  2. Move your cursor to the right monitor;

  Now you can't go back. The only way is pressing ESC to close app
  indicator menu so that you can go back to the first monitor.

  This only happens when ubuntu-dock autohide is on.

  Maybe it can be useful: https://github.com/micheleg/dash-to-
  dock/issues/743

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 00:01:41 2020
  InstallationDate: Installed on 2019-12-31 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230)
  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/gnome-shell/+bug/1859260/+subscriptions

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

[Desktop-packages] [Bug 1734034] Re: Cannot Use the Character U07AE on any Editor

It's maybe worth reporting upstream on
https://gitlab.gnome.org/GNOME/gtk/issues

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

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

Title:
  Cannot Use the Character U07AE on any Editor

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

Bug description:
  When using 'Dhivehi' as a keyboard input source, unicode character
  U07AE does not work when typing on LibreOffice or Gedit.

  The character is o on the keyboard. When this key is pressed nothing
  happens.

  All the other keys (characters) work fine except for the one that
  should be given by pressing o. Even Shift+o Works. I also tried
  exchanging the mapping of the unicode to another key. Even with that,
  the unicode character did not work.

  I have tried changing xkbd/symbol mapping to a different key. But that
  didn't help.

  With xev tool, the Unicode symbol is detected in the Terminal. But it
  does not work when tried elsewhere.

  I can insert the character by typing the Unicode, like Ctrl+Shift+
  U07AE. But to do this, I have to change language to English.

  This issue came up on Ubuntu 17.10; in 16.04 it works as it should.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 10:56:19 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-11-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=210cd2fd-b33b-4626-8740-2831bfcb4900 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/gnome-shell/+bug/1734034/+subscriptions

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

[Desktop-packages] [Bug 1859879] Re: PNG images are not displayed

Thank you for your bug report. Could you provide the details requested
on the gitlab ticket?

' Please open the file from the commandline with shotwell /path/to/png
>shotwell-viewer.log 2>&1 and attach that file here, please'

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

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

** Also affects: ubuntuone-shotwell-plugin via
   https://gitlab.gnome.org/GNOME/shotwell/issues/186
   Importance: Unknown
   Status: Unknown

** Changed in: shotwell (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  PNG images are not displayed

Status in ubuntuone-shotwell-plugin:
  Unknown
Status in shotwell package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) Shotwell 0.30.7 – “Celle”
  3) If I click on a .png file, shotwell opens and displays "No photos/videos". 
It does not display the png image. If I click on .jpg/.tif/.bmp files, shotwell 
opens and displays the jpg/tif/bmp images. If I drag/drop the .png file into 
Firefox, Firefox displays the .png image.
  4) Shotwell should display the .png image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1859879/+subscriptions

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

[Desktop-packages] [Bug 1859857] Re: network-manager keeps asking for wifi password can't connect to any wifi

Thank you for your bug report. From what version to what version did you update?
What desktop do you use?
Could you add your 'journalctl -b 0' log from a session where you reproduced 
the issue?

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

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

Title:
  network-manager keeps asking for wifi password can't connect to any
  wifi

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This bug is the same as reported by #1859289, however I was not able
  to find this when using the ubuntu-bug tool.

  Since the last update my network-manager keeps asking me for wifi
  passworts, but then never connects. Password is definitely correct.
  Everything worked before the update.

  lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Jan 15 19:12:42 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-05-27 (233 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.23 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (83 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1859899] Re: Please add a ZFS gui

** Changed in: gnome-disk-utility (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please add a ZFS gui

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Right now the only way is with CLI. I do know the CLI methods but simple 
operations that I'd like to be able to see visually, like the RAID array or the 
allocated drives with ZFS, pools, datasets etc would all be nicely placed in a 
GUI that would double as an input to modify them.
  There are GUI's that exist on Ubuntu for non-ZFS volumes, but since Ubuntu is 
moving towards ZFS as a standard it only makes sense that a GUI would be 
created for such tasks. It's nice to see things like your currently configured 
cron jobs, like scrubs and disk usage etc..

  A GUI for ZFS would be a tremendous advance in terms of expediency,
  utility, and ease of use.

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

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

[Desktop-packages] [Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome

Thank you for your bug report. Is the issue specific to chrome? it might
be an issue with the browser rather than the font...

** Changed in: fonts-noto-color-emoji (Ubuntu)
   Status: New => Incomplete

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

Title:
  fonts-noto-color-emoji not making pretty emojis in google chrome

Status in fonts-noto-color-emoji package in Ubuntu:
  Incomplete

Bug description:
  Google-Chrome and emoji's is being a weird headache. Something's causing it 
not to find the right font to make emoji's:
  
"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

Thank you for your bug report. could you attach the full 'journalctl -b
0' log from the system after triggering the bug? Also could you give
some details on the videocard/driver you are using (Daniel, Marco,
should we update the apport hook to include those informations?)

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

Title:
  Display freaks out when external monitors are attached

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859970] Re: orange tint in screenshots when running wayland

The screenshoting is handled by gnome-shell itself nowadays, reassigning
there

** Package changed: gnome-screenshot (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  orange tint in screenshots when running wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  All my screenshots taken on 20.04 with wayland have an orange tint to
  them. This appears to be the overlay which you get when selecting an
  area. Full screen screenshots and window screenshots are unaffected,
  only area screenshots appear to have the problem.

  Steps to reproduce

  Login to a wayland session
  Hold down Shift and Press PrintScreen
  Select an area to screenshot
  Navigate to ~/Pictures
  Open the picture you just took

  Expected outcome

  Screenshot of area taken as it would have been on screen

  Actual outcome

  Screenshot is taken, but has an orange border and overlay. (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:50:50 2020
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

2020-01-16 Thread Jarno Suni

Guess what? Affects Xubuntu 19.10. What is so difficult in not asking
password when guest session is concerned?

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  [vmware] Background goes white when using scaling (200%, 300% or 400%)

Status in mutter package in Ubuntu:
  In Progress
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  As soon as I set my display to scaled (any percentage) via Settings ->
  Displays -> Scale, the background image disappears and become all
  white. When I choose a different background image via Settings ->
  Background initially nothing happens. As soon as I switch back to 100%
  scaling, the image I choose before now appears.

  This problem started right after updating to 19.04. No such issues
  with either 18.04 or 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:35:49 2019
  DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-03-01 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

** Tags added: fixed-in-3.35.4 fixed-upstream

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

Title:
  Locking and unlocking the screen is slow and stuttery

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 14 10:10:38 2019
  InstallationDate: Installed on 2019-06-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049

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

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

[Desktop-packages] [Bug 1859970] [NEW] orange tint in screenshots when running wayland

Public bug reported:

All my screenshots taken on 20.04 with wayland have an orange tint to
them. This appears to be the overlay which you get when selecting an
area. Full screen screenshots and window screenshots are unaffected,
only area screenshots appear to have the problem.

Steps to reproduce

Login to a wayland session
Hold down Shift and Press PrintScreen
Select an area to screenshot
Navigate to ~/Pictures
Open the picture you just took

Expected outcome

Screenshot of area taken as it would have been on screen

Actual outcome

Screenshot is taken, but has an orange border and overlay. (see
screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.33.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 11:50:50 2020
InstallationDate: Installed on 2018-02-04 (710 days ago)
InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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


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

** Attachment added: "Screenshot from 2020-01-16 11-49-52.png"
   
https://bugs.launchpad.net/bugs/1859970/+attachment/5320829/+files/Screenshot%20from%202020-01-16%2011-49-52.png

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

Title:
  orange tint in screenshots when running wayland

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  All my screenshots taken on 20.04 with wayland have an orange tint to
  them. This appears to be the overlay which you get when selecting an
  area. Full screen screenshots and window screenshots are unaffected,
  only area screenshots appear to have the problem.

  Steps to reproduce

  Login to a wayland session
  Hold down Shift and Press PrintScreen
  Select an area to screenshot
  Navigate to ~/Pictures
  Open the picture you just took

  Expected outcome

  Screenshot of area taken as it would have been on screen

  Actual outcome

  Screenshot is taken, but has an orange border and overlay. (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 11:50:50 2020
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

This bug was fixed in the package mesa - 19.2.1-1ubuntu1~18.04.1

---
mesa (19.2.1-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522)
  * control: Build-depend on libsensors4-dev.
  * Disable vulkan overlay layer, needs meson 0.46.
  * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even
if we have b_ndebug=true. (LP: 1841412)
  * Revert-meson-drop-Wno-foo-bug-workaround.diff: Bionic still has
0.45, so add back a workaround for it.
  * Revert-meson-bump-required-version-to-0.46.diff: Relax meson
requirement.

 -- Timo Aaltonen   Mon, 18 Nov 2019 20:28:40 +0200

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.5+git20191008-0ubuntu1~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.5+git20191008-0ubuntu1~18.04.1) bionic; 
urgency=medium

  * Backport for 18.04.4 HWE stack update. (LP: #1848522)

 -- Timo Aaltonen   Wed, 18 Dec 2019 10:15:29 +0200

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL

This bug was fixed in the package libdrm - 2.4.99-1ubuntu1~18.04.1

---
libdrm (2.4.99-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522)

libdrm (2.4.99-1ubuntu1) eoan; urgency=medium

  * intel-sync-pciids.diff: Sync pci-ids with the kernel. (LP: #1845317)

 -- Timo Aaltonen   Mon, 21 Oct 2019 17:02:40 +0300

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

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

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

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

[Desktop-packages] [Bug 1845149] Re: set fallback drivers to avoid updating pci-id lists

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.5+git20191008-0ubuntu1~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.5+git20191008-0ubuntu1~18.04.1) bionic; 
urgency=medium

  * Backport for 18.04.4 HWE stack update. (LP: #1848522)

 -- Timo Aaltonen   Wed, 18 Dec 2019 10:15:29 +0200

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  set fallback drivers to avoid updating pci-id lists

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The AMD/Intel pci-id's keep changing when new platforms are enabled. 
Currently, the new ones need to be added to the kernel, libdrm, mesa and 
xorg-server. This duplication is silly, as there's a limited number of drivers 
for a platform, so use a default (fallback) DRI driver for a vendor. For Intel 
it's i965, for AMD it's radeonsi.

  
  [Test case]
  check that the correct driver is still used on an Xorg session and DRI works

  [Regression potential]
  shouldn't be any

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

This bug was fixed in the package llvm-toolchain-9 - 1:9-2~ubuntu18.04.1

---
llvm-toolchain-9 (1:9-2~ubuntu18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522)

 -- Timo Aaltonen   Mon, 21 Oct 2019 17:13:41 +0300

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

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1848522] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1848522

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

This bug was fixed in the package libclc -
0.2.0+git20190827-1~ubuntu18.04.1

---
libclc (0.2.0+git20190827-1~ubuntu18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522)

 -- Timo Aaltonen   Mon, 21 Oct 2019 23:59:47 +0300

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

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

This bug was fixed in the package libdrm - 2.4.99-1ubuntu1~18.04.1

---
libdrm (2.4.99-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522)

libdrm (2.4.99-1ubuntu1) eoan; urgency=medium

  * intel-sync-pciids.diff: Sync pci-ids with the kernel. (LP: #1845317)

 -- Timo Aaltonen   Mon, 21 Oct 2019 17:02:40 +0300

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

** Changed in: llvm-toolchain-9 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file

2020-01-16 Thread AsciiWolf

** Attachment added: "texinfo_desktop_entry.png"
   
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1859963/+attachment/5320826/+files/texinfo_desktop_entry.png

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

Title:
  Info package on Ubuntu Focal comes preinstalled with desktop file

Status in texinfo package in Ubuntu:
  New

Bug description:
  The "info" package that is preinstalled on Ubuntu Focal ships with a
  "info.desktop" file that adds a "TeXInfo" desktop launcher displayed
  among other apps. The launcher opens a terminal application that is
  confusing and user unfriendly for many users. Users that actually want
  to use info can do it using a terminal. Please, consider removing the
  desktop file or at least set it to not show among other apps.

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

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

[Desktop-packages] [Bug 1859963] [NEW] Info package on Ubuntu Focal comes preinstalled with desktop file

2020-01-16 Thread AsciiWolf

Public bug reported:

The "info" package that is preinstalled on Ubuntu Focal ships with a
"info.desktop" file that adds a "TeXInfo" desktop launcher displayed
among other apps. The launcher opens a terminal application that is
confusing and user unfriendly for many users. Users that actually want
to use info can do it using a terminal. Please, consider removing the
desktop file or at least set it to not show among other apps.

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


** Tags: focal

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

Title:
  Info package on Ubuntu Focal comes preinstalled with desktop file

Status in texinfo package in Ubuntu:
  New

Bug description:
  The "info" package that is preinstalled on Ubuntu Focal ships with a
  "info.desktop" file that adds a "TeXInfo" desktop launcher displayed
  among other apps. The launcher opens a terminal application that is
  confusing and user unfriendly for many users. Users that actually want
  to use info can do it using a terminal. Please, consider removing the
  desktop file or at least set it to not show among other apps.

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

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

[Desktop-packages] [Bug 1859960] [NEW] Livepatch polkit rules strings are not translatable

2020-01-16 Thread AsciiWolf

Public bug reported:

The "Manage Livepatch" and "Authentication is required to enable
Livepatch" translatable strings from
/usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to be
available to translate on Launchpad. They were translatable and their
translation was correctly applied in Bionic, however since then (Cosmic,
Disco, Eoan, Focal), they are untranslated and not available on
Launchpad.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

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


** Tags: eoan focal l10n

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

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

Title:
  Livepatch polkit rules strings are not translatable

Status in Ubuntu Translations:
  New
Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  The "Manage Livepatch" and "Authentication is required to enable
  Livepatch" translatable strings from
  /usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to
  be available to translate on Launchpad. They were translatable and
  their translation was correctly applied in Bionic, however since then
  (Cosmic, Disco, Eoan, Focal), they are untranslated and not available
  on Launchpad.

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

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

Comparison: Ubuntu on Wayland on same hardware: 
https://www.youtube.com/watch?v=rw0cq5FwpHU
Less flicker than Ubuntu, and faster it seems. Around 13 seconds.

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

Title:
  Display freaks out when external monitors are attached

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859942] Re: Chromium is not recognized in whatsapp web

2020-01-16 Thread Olivier Tilloy

Whatsapp is doing user-agent detection, and blocking a valid browser for
no good reason. This is not a chromium bug. I suggest reporting this
issue to the whatsapp web team, and as a workaround you can use an
extension that impersonates a different browser, like this one:
https://chrome.google.com/webstore/detail/user-agent-switcher-
for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg.

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

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

Title:
  Chromium is not recognized in whatsapp web

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I'm currently using Ubuntu 20.04 daily build for testing purpose and
  install chromium browser.

  Surprisingly, now chromium browser is packed as snap by default (I
  didn't aware this until using 20.04). Everyting went fine, and I'm
  amazed by the good performance.

  But I found an issue regarding Whatsapp Web that can't recognize
  chromium-browser and ask me to use newer version of google chrome,
  firefox or opera.

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

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

[Desktop-packages] [Bug 1859939] Re: keyboard shortcuts not working

2020-01-16 Thread karlsebal

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

** This bug has been marked a duplicate of bug 854382
   Simple Scan window not responding to keyboard shortcuts

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

Title:
  keyboard shortcuts not working

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Keyboard shortcuts are not working unless started with
  XDG_CURRENT_DESKTOP=XFCE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jan 16 09:26:20 2020
  InstallationDate: Installed on 2014-11-13 (1889 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=5259d8a9-df2c-46ad-b1ca-ef05b5a2f02e ro
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2019-04-11 (279 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1708:bd04/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1859939/+subscriptions

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

[Desktop-packages] [Bug 1859955] Re: Display freaks out when external monitors are attached

Comparison: Windows 10 on the same hardware: 
https://www.youtube.com/watch?v=VEvidzgedGk
Process takes 5 seconds, no flicker.

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

Title:
  Display freaks out when external monitors are attached

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1859955] [NEW] Display freaks out when external monitors are attached

Public bug reported:

Running Focal on my ThinkPad T450, but not unique to this release as it
happened on 19.10 (and probably older releases too).

Steps to reproduce.

While running GNOME Shell, attach the laptop to additional external monitors.
(I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

Expected outcome

Desktop on 1 monitor goes away.
Desktop comes back on N monitors.

Actual outcome

Laptop display goes black
Laptop display comes back, moved 50% horizontally
One external monitor comes on
Laptop display goes back to normal
Second external monitor comes on
All three displays go off again
Laptop display comes on again alone
Laptop display goes off again
laptop display comes on again
External monitors come back on again
System is usable.

The entire process takes twenty seconds.

https://www.youtube.com/watch?v=QuSudpxVOao

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 10:21:05 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-02-04 (710 days ago)
InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Display freaks out when external monitors are attached

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login