[Desktop-packages] [Bug 2037577] [NEW] [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect

[Alexey Kulik]

Public bug reported:

When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is
modified, the GNOME Shell theme remains in the default state, i.e. it
switches between light and dark together with the ‘Dark Style’ toggle.
It is impossible to set the Shell theme to be unconditionally dark or
light.

To reproduce:

1. Run command
gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark'
or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 
'prefer-dark' via the Dconf Editor GUI.
2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick settings.

What should happen:

The Shell dialogs like the quick settings menu and the 
calendar-and-notifications menu should be rendered in dark style.

What happens instead:

The Shell dialogs are still light.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 27 20:04:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-09-21 (371 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
RelatedPackageVersions: mutter-common 45.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago)

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


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

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

Title:
  [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has
  no effect

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is
  modified, the GNOME Shell theme remains in the default state, i.e. it
  switches between light and dark together with the ‘Dark Style’ toggle.
  It is impossible to set the Shell theme to be unconditionally dark or
  light.

  To reproduce:
  
  1. Run command
  gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark'
  or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 
'prefer-dark' via the Dconf Editor GUI.
  2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick 
settings.

  What should happen:
  
  The Shell dialogs like the quick settings menu and the 
calendar-and-notifications menu should be rendered in dark style.

  What happens instead:
  
  The Shell dialogs are still light.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 20:04:08 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-21 (371 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago)

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


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

[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

[Alexey]

The same is here 
Ubuntu 22.04.1 LTS

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

Title:
  Scrolling jumps after switching windows

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

[Desktop-packages] [Bug 1977545] [NEW] xrandr: Failed to get size of gamma for output default

[Alexey V. Galkin]

Public bug reported:

spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080  77.0*

Display setup

GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SettingsDaemon was not provided by any .service files

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jun  3 17:50:08 2022
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:09b4]
InstallationDate: Installed on 2022-05-27 (7 days ago)
InstallationMedia: VMI 14.04 - Release amd64
MachineType: Dell Inc. Vostro 3681
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed 
root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet 
i915.alpha_support=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2022
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.8.2
dmi.board.name: 0X9X1W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.2:bd01/13/2022:svnDellInc.:pnVostro3681:pvr:rvnDellInc.:rn0X9X1W:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 3681
dmi.sys.vendor: Dell Inc.
drirc:
 
 
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jun  3 17:29:43 2022
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.11

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


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

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

Title:
  xrandr: Failed to get size of gamma for output default

Status in xorg package in Ubuntu:
  New

Bug description:
  spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  77.0*

  Display setup

  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SettingsDaemon was not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jun  3 17:50:08 2022
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:09b4]
  InstallationDate: Installed on 2022-05-27 (7 days ago)
  InstallationMedia: VMI 14.04 - Release amd64
  MachineType: Dell Inc. Vostro 3681
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed 
root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet 
i915.alpha_support=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.2
  dmi.board.name: 0X9X1W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell 

[Desktop-packages] [Bug 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window

[Langer Alexey]

The bug is reproduced on Eclipse IDE (screenshot
https://disk.yandex.ru/i/z7kqQV47z8xeFQ). Left click always closes the
popup window instead of set focus on it. Pressing the "F2" buttons leads
to the same result.

Ubuntu 20.04.3 LTS
GNOME Shell 3.36.9
Eclipse 2021-12 (4.22.0)

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

Title:
  GNOME Shell consistently ignores mouse clicks in a particular app
  window

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/475

  ---

  This is similar in some ways to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but
  affects only the mouse, not the keyboard, and is consistent almost all
  (99%+) of the time.  This is happening for Ubuntu 18.04.2 LTS (bionic)
  in the default desktop environment (Ubuntu).  It also happens for the
  GNOME and GNOME Classic desktop environments.  The version of gnome-
  shell is 3.28.3-0ubuntu0.18.04.4.

  Our program is a blend of C# winforms (Mono) with embedded web browser
  windows using Geckofx45 (mozilla version 45).  Editing windows in the
  program use HTML to display formatting and  typescript/javascript code
  to assist with popup dialogs and other editing help.  Inside these
  editing windows, left mouse clicks are essentially ignored.
  Keyboarding still works fine as far as I can tell.  Clicking on the
  gear button inside the editing window fails to bring up the Styles
  dialog more than 95% of the time.  When the dialog does display, it is
  always (100%) nonfunctional as the first click in it causes it to
  close immediately.

  Tracing the internal behavior of the code, it appears that clicking
  the first time inside the editing (browser) window causes a series of
  WM_FOCUS messages to be sent and the javascript to hook up a left
  mouse click handler to a gear button displayed in the lower left
  corner of the editing window.  This is the expected behavior, and the
  same as on other window managers.  But then, on GNOME Shell only, a
  series of WM_KILLFOCUS messages are sent immediately.  This does not
  happen for other window managers.  (The main window receives a
  WM_ACTIVATE message with the argument to make it deactivate.)  Any
  other left mouse clicks inside that window are ignored >95% of the
  time, probably only when double clicking quickly enough to occur
  before those messages to lose focus/deactivate are handled.  (Right
  mouse clicks are handled at a higher level and appear to function
  normally.)

  The program in question is called Bloom.  The source code is available
  at https://github.com/BloomBooks/BloomDesktop and prebuilt
  debian/ubuntu packages are available at
  http://packages.sil.org/ubuntu/ as bloom-desktop or bloom-desktop-
  beta.  After spending a few days looking at this problem, I've
  reluctantly come to the conclusion that it must be a GNOME Shell bug
  that I can't work around in our code.  It's working fine in Microsoft
  Windows and all the other Linux window managers that I've tested
  (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE).

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


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

[Desktop-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

[Alexey Gusev]

the same problem on 21.10 
pulseaudio package 1:15.0+dfsg1-1ubuntu2

default output is reset in random order after resume from sleep.
Sometimes it stays as it was before suspend, but more often it just
changes to HDMI or dock output.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Desktop-packages] [Bug 1870597]

[alexey]

Was this patch sent to the maintainers? If so, was it applied?

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

Title:
  libinput says "your system is too slow"

Status in GNOME Shell:
  Unknown
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  During the freeze, the output of the install had a message from "gdm-
  x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5570
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

[Alexey Kulik]

I can also confirm that update with hirsute-proposed enabled solves the problem 
for me.
Before this, the problem used to be readily reproduced by the procedure 
described in comment #51.

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

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

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

[Alexey]

I've found this forum thread:

https://forums.developer.nvidia.com/t/solus-nvidia-gtx-1070-brightness-
control-not-working/54472

If I understand correctly, the OP resolved his issue by setting the
kernel boot parameter

nvidia.NVreg_EnableBacklightHandler=1

This did not solve the issue for me, however.

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

Title:
  brightness control broken nvidia

Status in gnome-power:
  Confirmed
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

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

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

[Desktop-packages] [Bug 1751759] Re: Add option to turn off Ubuntu dock

[Alexey Kulik]

The built-in extensions (Desktop Icons, Ubuntu AppIndicators, Ubuntu Dock) can 
be deactivated using the Extensions app.
Is it enough to close the issue?

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

Title:
  Add option to turn off Ubuntu dock

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

Bug description:
  There should be an option to turn off the ubuntu dock via either tweak
  tool or in the ubuntu settings . In tweak tool the ubuntu dock and the
  ubuntu appindicators shows up as off but are still on.

  These plus the addition apps button should re implemented to improve Ubuntu 
UX.
  Im aware the gnome-session is available to install.

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

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

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Alexey Tsitsin]

Sorry, I changed the issue's type accidently.

** Information type changed from Public Security to Public

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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

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

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Alexey Tsitsin]

This problem still persist and SPNEGO won't work even with new policies:

https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthServerAllowlist
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthNegotiateDelegateAllowlist

The policies are loaded successfully but  kerboros negotiation won't
work

** Information type changed from Public to Public Security

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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

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

[Desktop-packages] [Bug 1866732] Re: [snap] Unable to add policies

[Alexey Tsitsin]

The bug is solved

We need to create folder mkdir -p /etc/chromium-browser/policies/managed 
manually and then browsre check the policies successfully

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

Title:
  [snap] Unable to add policies

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  When using the Chromium snap, the policies located in the directory
  /etc/chromium-browser/policies/managed/ are no longer being read. The
  consequence is that the policies are not applied.

  This is particularly problematic on, for example, public computers,
  where browsing history and passwords may be saved, or on school
  computers, where the dinosaur game will be easily available.

  Is there another way I'm unaware of to add system-wide policies when
  using the Chromium snap? If not, would it be possible to make the snap
  read the settings in the /etc/chromium-browser/policies/managed/
  directory? This would make the transition from deb to snap easier on
  systems which are already configured with system-wide policies.

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

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

[Desktop-packages] [Bug 1414753] Re: Chromium browser 39.0.2171.65 does not load policies

[Alexey Tsitsin]

Hello!
This bug still persist in Chromium 87.0.4280.66 (Official Build) snap (64-bit)
Ubuntu 20.10

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

Title:
  Chromium browser 39.0.2171.65 does not load policies

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Following the information I gathered from

  http://www.chromium.org/administrators/linux-quick-start
  http://www.chromium.org/administrators/linux-quick-start
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802

  I tried to set a simple policy for the browser.
  All I did is create a file "policy.json" in /etc/chromium-
  browser/policies/managed with the following content:

  {
"HomepageLocation": "www.chromium.org"
  }

  However when starting chromium there is no sign of the policy: "about:policy" 
  does not show any policy being set. Running 'strings /usr/lib/chromium-
  browser/chromium-browser|grep policies' gives me:

  /etc/chromium/policies
  /etc/chromium-browser/policies

  so everything should be fine. To be sure I also tried setting the policy in 
  /etc/chromium/policies. I also tried to set the policy in "recommended"  in 
  both paths. I also tested running chromium under a new user account, but it 
  did not change anything. The policy is simply not set. Either I am doing 
  something wrong or this is not working.
  To be on the safe side I also tried a different content:

  {
"RestoreOnStartup": 4,
"RestoreOnStartupURLs": ["http://www.chromium.org;
  }

  Did not work either.

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

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

[Desktop-packages] [Bug 1453514] Re: Highlighted text in pdf files is not shown on prints

[Alexey]

To add to my point 2: the same effect happens when using `pdftocairo` in
command line, so maybe the current issue is not about Evince.

It remains the problem with annotations created in Evince that just
disappear on printing.

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

Title:
  Highlighted text in pdf files is not shown on prints

Status in Evince:
  New
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Highghted text in pdf files is shown correctly in the viewer, but not
  in the print preview & the printouts, there only a yellow bar (the
  highlighting) is visible, and the actual text is behind it (since it
  is selectable in the print preview).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 10 12:11:42 2015
  ExecutablePath: /usr/bin/evince-previewer
  InstallationDate: Installed on 2015-05-06 (3 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1453514] Re: Highlighted text in pdf files is not shown on prints

[Alexey]

In fact, there seem to be multiple issues with printing annotations (at
least text highlighting).

This is about Evince 3.36.7 and Okular 20.08.2.

1. If a highlighting annotation is created in Evince, it is visible when
the file is opened with Evince, Okular, or Xournal++, but it disappears
on printing to PDF file from any of these programs, and it disappears on
exporting to PDF from Xournal++. (I believe it also disappears on actual
printing.)

2. If a highlighting annotation is created in Okular, it is visible in
Evince, Okular, and Xournal++, but when printing to PDF from Evince or
Xournal++, the first highlighting is ok, but all the others hide the
text that is supposed to be highlighted.

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

Title:
  Highlighted text in pdf files is not shown on prints

Status in Evince:
  New
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Highghted text in pdf files is shown correctly in the viewer, but not
  in the print preview & the printouts, there only a yellow bar (the
  highlighting) is visible, and the actual text is behind it (since it
  is selectable in the print preview).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 10 12:11:42 2015
  ExecutablePath: /usr/bin/evince-previewer
  InstallationDate: Installed on 2015-05-06 (3 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892584] Re: wine game 'rune classic' hungs the OS on exit

[Alexey Kuznetsov]

I've tested ubuntu kernel 5.4.0-26-generic + debian packages (full os
install). It works fine. I can conclude this not kernel issue but
X-server or amd drivers.

Debian packages which works:

ii  x11-xserver-utils7.7+8   
amd64X server utilities
ii  xserver-common   2:1.20.4-1+deb10u1  
all  common files used by various X servers
ii  xserver-xephyr   2:1.20.4-1+deb10u1  
amd64nested X server
ii  xserver-xorg 1:7.7+19
amd64X.Org X server
ii  xserver-xorg-core2:1.20.4-1+deb10u1  
amd64Xorg X server - core server
ii  xserver-xorg-input-all   1:7.7+19
amd64X.Org X server -- input driver metapackage
ii  xserver-xorg-input-libinput  0.28.2-2
amd64X.Org X server -- libinput input driver
ii  xserver-xorg-input-wacom 0.34.99.1-1 
amd64X.Org X server -- Wacom input driver
ii  xserver-xorg-legacy  2:1.20.4-1+deb10u1  
amd64setuid root Xorg server wrapper
ii  xserver-xorg-video-all   1:7.7+19
amd64X.Org X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu18.1.99+git20190207-1   
amd64X.Org X server -- AMDGPU display driver
ii  xserver-xorg-video-ati   1:19.0.1-1  
amd64X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev 1:0.5.0-1   
amd64X.Org X server -- fbdev display driver
ii  xserver-xorg-video-intel 2:2.99.917+git20180925-2
amd64X.Org X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-nouveau   1:1.0.16-1  
amd64X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-qxl   0.1.5-2+b1  
amd64X.Org X server -- QXL display driver
ii  xserver-xorg-video-radeon1:19.0.1-1  
amd64X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa  1:2.4.0-1   
amd64X.Org X server -- VESA display driver
ii  xserver-xorg-video-vmware1:13.3.0-2  
amd64X.Org X server -- VMware display driver

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

Title:
  wine game 'rune classic' hungs the OS on exit

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Hello!

  Rune Classic hungs OS on exit (music plays, but X or keyboard caps
  lock not responding), Debian 10 works fine.

  https://www.gog.com/game/rune_classic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 22 19:03:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.10: added
   wireguard, 1.0.20200611: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431DA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431DA
  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.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431DA_UM431DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  

[Desktop-packages] [Bug 1727321] Re: drag and drop through the side panel to activate the window is not working.

[Alexey Kulik]

** Tags added: focal groovy

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

Title:
  drag and drop through the side panel to activate the window is not
  working.

Status in GNOME Shell:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  drag and drop through the side panel to activate the window is not
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:39:57 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2015-08-27 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1892584] [NEW] wine game 'rune classic' hungs the OS on exit

[Alexey Kuznetsov]

Public bug reported:

Hello!

Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock
not responding), Debian 10 works fine.

https://www.gog.com/game/rune_classic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-amdgpu 19.1.0-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 22 19:03:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.10: added
 wireguard, 1.0.20200611: added
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX431DA.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX431DA
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.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX431DA_UM431DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-video-amdgpu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  wine game 'rune classic' hungs the OS on exit

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Hello!

  Rune Classic hungs OS on exit (music plays, but X or keyboard caps
  lock not responding), Debian 10 works fine.

  https://www.gog.com/game/rune_classic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 22 19:03:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.10: added
   wireguard, 1.0.20200611: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431DA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431DA
  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.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431DA_UM431DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Alexey]

Just deleted 240G syslog file after system stalled.
Syslog.1 is 20G full of folowing:
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An 
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: 
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An 
invalid handle value was provided.

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

For now I can send udev event instead of replugging:

ls -l /sys/class/hidraw/ | grep :1050: | awk -F/ '{print $NF}' | xargs
-r -L1 -I T udevadm trigger -c add --name-match=T

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Hm, now I updated chrome to 84.0.4147.105 (1260) and can reproduce it
reliably by inserting yubikey and then starting chromium with new
profile (chromium --user-data-dir=./111).

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Sorry for long delay. No I can't reproduce it anymore in a way I described 
before, but it still happens to me. For now certain is that repluging yubikey 
fixes the problem, reboot doesn't.
Upgrading the snap most probably triggering it, need to test it more times.

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Funny thing. I have Yubikey 5C Nano and it is hard to get out of port.
So I plugged spare Yubikey 4 to get dmesg lines and it worked with
chromium. Then I replugged my yubikey 5c nano and it worked too. Then I
rebooted without unplugging yubikey and it not working in chromium again
but works in firefox.

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical*
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more
  stable way for all Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: 12 days ago, at 19:18 MSK
installed:84.0.4147.89 (1229) 166MB -

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Still not working. And right link to test is https://demo.yubico.com
/webauthn-technical/registration

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1886075] Re: Switch app windows using mouse wheel over dock icon

[Alexey Kulik]

This option does exist in Ubuntu Dock. It's just disabled by default. It can be 
activated using Dconf Editor. Set the parameter 
'org.gnome.shell.extensions.dash-to-dock' to be equal to 'cycle-windows'.
It can also be easily done by running this command:

gsettings set org.gnome.shell.extensions.dash-to-dock scroll-action
'cycle-windows'

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

Title:
  Switch app windows using mouse wheel over dock icon

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

Bug description:
  Hello, this is not a BUG, rather a feature request, which possibly
  shall be placed elsewhere (where?)

  I'm used to very useful behavior from XFce and that is hovering over various 
icons in system bars and using the wheel actually performs actions immediately 
like e.g.:
  1) in/decreasing volume while on sound icon
  2) switching app windows while on app icon - would be extreme useful here in 
GNOME since more apps windows are already marked by small dots sou user is very 
aware that there are more windows... I know there is ALT+~ but when using mouse 
only its not an option...
  ...

  I've searched event through GNOME tweaks, but no luck - have not found
  it.

  Any way how to add this behavior?

  Thanks a lot #McZ

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  2 19:02:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  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-extension-ubuntu-dock/+bug/1886075/+subscriptions

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

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

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Log attached. Relevant line probably

[92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to
begin udev enumeration.

** Attachment added: "chrom3.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1885159] Re: Firefox after update doesn't start - Ubuntu 16.04.6 LTS

[Alexey]

Same here: Ubuntu 16.04.6 LTS.

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

Title:
  Firefox after update doesn't start - Ubuntu 16.04.6 LTS

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After latest FF beta update - Firefox doesn't start (also there is no
  crash). In system monitor Firefox process is visible, but still app
  doesn't appear.Starting in safe mode doesn't help.

  Previous version: 77.0.1+build1-0ubuntu0.16.04.1
  Updated version: 78.0+build1-0ubuntu0.16.04.2
  Ubuntu version: Ubuntu 16.04.6 LTS
  Apport bug report attached.

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Tested firefox snap - u2f works.

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

I use it only for github, no special setup was needed (udev rules are
already there for PIV). I logged last time some months ago so I don't
know when it stopped working exactly.

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1872026] Re: App icon aspect ratio in the panel is broken

[Alexey Kulik]

It fixes the issue for me after update of gnome-shell package with 
focal-proposed enabled.
gnome-shell version is 3.36.3-1ubuntu1~20.04.2
Tested using winecfg.

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1872026

Title:
  App icon aspect ratio in the panel is broken

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  The aspect ratio of the icon on the top left of the screen (Activites
  bar?) is broken so it looks taller and thinner than normal.

  See attached screenshot.

  [ Test case ]

  - Run an application such as update-manager
  - The application icon on the top panel should have correct propotions

  [ Regression potential ]

  Icons may have wrong vertical aligment

  -

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:10:09 2020
  InstallationDate: Installed on 2020-01-24 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-04-10 09:03:51.154471
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2020-04-03T20:22:43.358127

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

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

[Desktop-packages] [Bug 1884759] [NEW] U2f yubikey stopped working in chromium snap

[Alexey Bazhin]

Public bug reported:

I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
U2f still works in firefox installed as deb.

# snap connections chromium | grep u2f
u2f-devices   chromium:u2f-devices   :u2f-devices   
 manual

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Alexey Kulik]

I have updated yaru-theme from focal-proposed.
I confirm that together with gnome-shell-extension-ubuntu-dock previously 
updated from proposed this fixes the issue for me in focal.

gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1)
yaru-theme (20.04.7)

Many thanks to everyone involved!

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

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: 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/dash-to-dock/+bug/1873321/+subscriptions

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

[Desktop-packages] [Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Alexey Kulik]

I have updated gnome-shell-extension-ubuntu-dock from focal-proposed and it 
doesn't fix the issue for me at the moment. I can guess that this is because 
yaru-theme is not yet updated in focal-proposed.
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1)
yaru-theme-gnome-shell (20.04.6)

** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: 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/dash-to-dock/+bug/1873321/+subscriptions

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

[Desktop-packages] [Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Alexey Kulik]

I confirm that the issue is fixed for me in groovy.
gnome-shell-extension-ubuntu-dock (68ubuntu1)
yaru-theme-gnome-shell (20.10.1)

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: 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/dash-to-dock/+bug/1873321/+subscriptions

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

[Alexey Bazhin]

tarantula!root# ps axu | grep chr
root  561745  0.0  0.0   6436   728 pts/2S+   15:20   0:00 grep chr

tarantula!root# snap  refresh chromium
error: cannot refresh "chromium": snap "chromium" has running apps (chromium)

Had to restart snapd to update chromium snap.

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

[Alexey Bazhin]

tarantula!root# snap refresh
core18 20200427 from Canonical✓ refreshed

tarantula!root# snap refresh
All snaps up to date.

tarantula!root# snap list | grep chromium
chromium   81.0.4044.1221119   latest/stable  canonical*-

tarantula!root# snap info --abs-time chromium
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: 2020-04-25T11:23:52+03:00
channels:
  latest/stable:81.0.4044.129 2020-04-29T17:25:51Z (1135) 161MB -
  latest/candidate: 81.0.4044.129 2020-04-28T18:04:52Z (1135) 161MB -
  latest/beta:  83.0.4103.23  2020-04-25T02:07:58Z (1125) 163MB -
  latest/edge:  84.0.4128.3   2020-04-29T05:50:21Z (1136) 164MB -
installed:  81.0.4044.122  (1119) 161MB -

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

[Alexey Bazhin]

tarantula!root# snap refresh
All snaps up to date.

How do I get the "latest" ?

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

[Alexey Bazhin]

I'm still seeing the problem.

tarantula!root# snap refresh
All snaps up to date.

tarantula!root# snap list | grep chromium
chromium   81.0.4044.1221119   latest/stable  canonical*-

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[Alexey Lovchikov]

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

I have the same problem, I have grouped all applications into categories.
To reproduce the error, I open the category after clicking + and so on several 
times until it freezes.

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[Alexey Lovchikov]

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

Sorry, not the + key, but the key Esc

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872268/+subscriptions

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

[Desktop-packages] [Bug 1870827]

[Alexey Ten (Lynn)]

(In reply to Dennis Mayr from comment #53)

Ubuntu LTS has special policy for some programs (e.g. Firefox) to
upgrade them. I'm using Ubuntu 16.04 and have latest stable Firefox. So
this is not a problem.

> What other workarounds are available in a shorter timeframe?

https://bugzilla.mozilla.org/show_bug.cgi?id=1495900#c44

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

Title:
  Firefox hangs after simultaneously opening Chrome/Electron-based
  applications

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When opening Chrome/Electron-based applications while Firefox is open, 
Firefox' tab contents stop responding, and it becomes necessary to close 
Firefox and reopen it.
  This includes:
  - VSCode: https://code.visualstudio.com/download
  - Atom: https://atom.io
  - Chromium browser

  Here's a link to a screenshot that shows Firefox with a "loading"
  waiting icon on the center of the tab (applies to any other open tab)

  https://imgur.com/PHHr3zt.png

  This has been happening since Ubuntu 14.04, but my previous report was 
quickly dismissed.
  I've done fresh installs for 14.04, 16.04 and 18.04, and the problem persists 
ever since.

  OS: Ubuntu
  Release: 18.04 LTS (other 18.04-based distros such as elementaryOS exhibit 
the same behavior)

  Firefox: 74.0.1, 64-bit (although the problem happens since 32-bit
  60.x or even earlier)

  Current Hardware: Lenovo ThinkPad T410s: Intel i5 540M processor,
  NVidia NVS3100M graphics, 8Gb RAM, 480Gb SSD

  # Expected behavior
  While Firefox is open, any Chrome/Electron-based application that is opened 
works without affecting Firefox, either loaded before or after it.

  # Observed behavior
  While Firefox is open, any Chrome/Electron-based application that is opened 
hangs Firefox, as observed according to the screenshot link provided above.

  Note that if Firefox is loaded *after* Chrome/Electron-based apps, the
  above described behavior isn't exhibited.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Alexey Kuznetsov]

I just found the issue second ago. It is related to SNAP_REEXEC
behavior. The idea is to run snap from snap_core installed from snap. If
you have system snap installed it will be reexec'd from snap core. To
disable it you need to change the source.

Just run this before compilation and you will be ok:

sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/'
snapd-*/cmd/cmd_linux.go

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

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

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Alexey Kuznetsov]

Seems like a new linux virus preventing me from running compiled snap.
Not the right place to report but who knows? When I recompile the snap
package and changed "help" output to "refresh !!! and remove snaps" and
unpack the content of resulting file into 123/. I reinstall the system
package and result md5 sum look like this:

axet@axet-laptop:~/local$ md5sum 123/usr/bin/snap /usr/bin/snap
f6639f5060dcd23506082f6ff0699f72  123/usr/bin/snap
f6639f5060dcd23506082f6ff0699f72  /usr/bin/snap
axet@axet-laptop:~/local$ 

When I run the package from ./123/usr/bin/snap I got my "!!! and remove
snaps" but when I ran the same file (same md5) from /usr/bin/snap I got
the old output.

axet@axet-laptop:~/local$ ./123/usr/bin/snap
The snap command lets you install, configure, refresh !!! and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.

...

axet@axet-laptop:~/local$ /usr/bin/snap
The snap command lets you install, configure, refresh and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.

...

Even when I copy my /usr/bin/snap into 11 file and run it from
another location I still getting my new "!!! and remove" string. Seems
like somthing (bug or virus) load old snap package when I run it from
/usr/bin/snap location and when I read the same file I get my actual
file system data. Not sure what kind of virus, trojan or system nvme,
encryption or kernel bug I have... Maybe anyone knows?

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

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

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Alexey Kuznetsov]

For some reason I unable to rebuild snapd following #29 instruction. All
goes fine, but in the end xdg-open wont work. I've checked
/var/log/syslog and it full of:

chromium_chromium.desktop[1674]: user-open error: Supplied URL scheme
"magnet" is not allowed

What is interesting, when I'm changing the source code of launcher.go I
also changed the line with error text to "Supplied !!! URL scheme"...
but in syslog error line still appears the same with out "!!!" this
conclude changes never goes into the /usr/bin/snap binary file.

I tried to remove ~/.cache/go-build /tmp/go-build turn off wifi, but
still resulting package still produce old version of error text. I have
no idea how to rebuild package correctly, following #28 not working.

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

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

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Alexey Nikitin]

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

I have the same issue on two PCs with HP LaserJet 1020 printer connected
to the Wi-Fi router on Ubuntu 19.10.

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Alexey Gusev]

I confirm this bug is still present in ubuntu 19.10.

My comment in gnome bug tracker: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1154#note_696130

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

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

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

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

I have put CHROMIUM_FLAGS="--force-device-scale-factor=2.0 --new-window"
in ~/.chromium-browser.init as I did before. But multiple options is not
parsed correctly as it was. I getting error:
"[18384:18384:/111220.448169:ERROR:display.cc(55)] Failed to parse
the default device scale factor:2 --new-window"

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

snap disconnect chromium:chromium-config
snap connect chromium:chromium-config

This is resolved my issue

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

# dmesg | grep chromium-browser.init
[803454.414690] audit: type=1400 audit(1572333616.781:52868): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/home/baz/.chromium-browser.init" pid=5334 comm="chromium.launch" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

$ ls -l ~/.chromium-browser.init
-rw-r--r-- 1 baz baz 60 мар 16  2018 /home/baz/.chromium-browser.init

$ snap connections chromium | grep personal-files
personal-fileschromium:chromium-config   :personal-files
 -

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

[Alexey Bazhin]

Chromium snap refuses to start if file exists:

$ chromium
/snap/chromium/917/bin/chromium.launcher: 78: .: Can't open 
/home/baz/.chromium-browser.init

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

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

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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Alexey]

Hello!

The problem is still here. In 17.10, 18.04, 18.10, 19.04 releases...

I found out that all standard layout switches are with that stupid delay. 
But somehow the alternative switching on LShift+RShift works instantly!

I spent few hours to find the place where this action is stored to move
it to standard keybindings like Shfit+Alt, but failed.

May be someone can suggest the way how to find action on key binding in
Ubuntu to do this?

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

[Alexey]

Someone should revert this 'Fix Released' status - it is here again in
18.04 (and according to forums in 17.x also).

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

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

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

[Desktop-packages] [Bug 1830482] [NEW] budgie-wm overclock when plaing video, nvidia 390, profile intel

[Alexey]

Public bug reported:

budgie-wm overclock when playing video in browser or instant player
nvidia 390, profile intel
similar to 
https://discourse.ubuntubudgie.org/t/19-04-budgie-wm-constant-cpu-load-after-changing-scale/1879/15

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.3+git20190124-0ubuntu18.04.2
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat May 25 15:48:38 2019
InstallationDate: Installed on 2018-02-17 (461 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
SourcePackage: mutter
UpgradeStatus: Upgraded to bionic on 2018-05-04 (385 days ago)

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


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

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

Title:
  budgie-wm overclock when plaing video, nvidia 390, profile intel

Status in mutter package in Ubuntu:
  New

Bug description:
  budgie-wm overclock when playing video in browser or instant player
  nvidia 390, profile intel
  similar to 
https://discourse.ubuntubudgie.org/t/19-04-budgie-wm-constant-cpu-load-after-changing-scale/1879/15

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 25 15:48:38 2019
  InstallationDate: Installed on 2018-02-17 (461 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (385 days ago)

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

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

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

[Alexey]

There is no 3.28.4 release yet: https://gitlab.gnome.org/GNOME/gnome-
shell/tags

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Fix Released

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

  ---

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1796888] Re: Lock screen does not unlock with valid password if non-english keyboard layout was selected before screen was locked

[Alexey Chernikov]

This bug affect me too - can't enter correct password in gnome-
screensaver. I'm using lightdm for login, if it matters

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

Title:
  Lock screen does not unlock with valid password if non-english
  keyboard layout was selected before screen was locked

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  The bug could be reproduced the following way:
  1) Select EN keyboard layout - Lock the screen - Enter the valid password - 
Success
  2) Select other keyboard layout (RU in my case) - Lock the screen - Enter the 
valid password (lock screen shows that EN layout is used) - Password is not 
accepted

  Keyboard shortcuts for input source switch does not work properly when the 
screen is locked.
  Also, I tried to switch input source with the button displayed in the lock 
screen - it shows as if the input source was changed, but it does not produce 
any effect, the password is still rejected. Also,  have checked that the Caps 
lock is switched in the proper position.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 15:55:06 2018
  InstallationDate: Installed on 2018-09-04 (34 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to bionic on 2018-10-08 (1 days ago)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Alexey Sys]

Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install
and applying nvidia-390

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu

[Alexey]

Hm, after checking out the links Daniels provided, I am wondering if
this is not a duplicate or a different manifestation of bug #1774957...
I think I will not open a new upstream bug but will sign up to the
existing one: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

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

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  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/1755986/+subscriptions

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

[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu

[Alexey]

Ok, thanks for the links to upstream bugs.

Julian, I propose the following title for GNOME bug report:

"WiFi/network icon and settings randomly disappear or misbehave in
status menu"

One more thing: I forgot to mention that I seem to observe the problem
randomly on roughly 1/2 of boots or logins.  This made me think of some
"race condition"...

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

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  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/1755986/+subscriptions

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

[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu

[Alexey]

In fact, the issue is not limited to wireless networks.  The wired
connection options are also not displayed correctly.  This screenshot
shows what I see in the menu when connected to wired network with wrong
profile.

By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up
for the first time after I added a second wired profile...  But I also
did some other things, so I am not sure it was caused by adding the
second profile.

** Attachment added: "Screenshot of user menu when connected to wired network 
with wrong profile"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170108/+files/Screenshot%20user%20menu%20on%20wrong%20wired%20network.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/1755986

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  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/1755986/+subscriptions

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

[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu

[Alexey]

In fact, the issue is not limited to wireless networks.  The wired
connection options are also not displayed correctly.  This screenshot
shows what I see in the menu when connected to wired network with wrong
profile.

By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up
for the first time after I added a second wired profile...  But I also
did some other things, so I am not sure it was caused by adding the
second profile.

** Attachment added: "Screenshot of user menu when connected to wired network 
with wrong profile"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170109/+files/Screenshot%20user%20menu%20on%20wrong%20wired%20network.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/1755986

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  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/1755986/+subscriptions

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

[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu

[Alexey]

I think I am experiencing the same bug.  Here is a screenshot of my
desktop with user menu when I am connected by WiFi.

By the way, I reinstalled Ubuntu 18.04.1 from scratch last week, but I
kept my user directory intact.  I had this issue since upgrading to
18.04 from 17.10.

** Attachment added: "Screenshot of user menu when connected to WiFi"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170107/+files/Screenshot%20user%20menu%20on%20WiFi.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/1755986

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  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/1755986/+subscriptions

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

[Desktop-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)

[Alexey Zagarin]

I have a similar issue. I'm trying to get the mic working on Beats X
headset. These series of patches helped me to solve the issue:

https://patchwork.freedesktop.org/patch/178198/
https://patchwork.freedesktop.org/patch/178199/
https://patchwork.freedesktop.org/patch/178200/
https://patchwork.freedesktop.org/patch/178201/

Can we get them upstream?
I'm on Ubuntu 18.04.

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

Title:
  Bluetooth audio stuck in A2DP profile ([pulseaudio] module-
  bluez5-device.c: Refused to switch profile to headset_head_unit: Not
  connected)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

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

[Desktop-packages] [Bug 1759644] [NEW] [18.04] Regression: wired network does not work upon resume from suspend

[Alexey Balmashnov]

Public bug reported:

After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.

Reloading the kernel driver module seems to help:
sudo modprobe -r r8169
sudo modprobe r8169

Could this be fixed structurally?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 28 20:08:20 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-01-06 (811 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp5s0 scope link metric 1000 
 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  ethernet  1522260260 
 wo 28 mrt 2018 20:04:20 CEST  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/3  yes enp5s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
 dzente  a899e56b-4048-43a8-bc38-9212d0af383b  wifi  1493769143 
 wo 03 mei 2017 01:52:23 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp5s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/4  
Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp4s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1759644

Title:
  [18.04] Regression: wired network does not work upon resume  from
  suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade to 18.04 (bionic) I've encountered the following
  regression: wired network connection does not work, when system is
  resumed from suspend.

  Reloading the kernel driver module seems to help:
  sudo modprobe -r r8169
  sudo modprobe r8169

  Could this be fixed structurally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 20:08:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-06 (811 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
  nmcli-con:

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

-
$ env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug 
/var/crash/_usr_bin_gnome-shell.1000.crash 

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (38.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): S
-
And that is 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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (734 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

@Daniel

Even
env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug 
/var/crash/_usr_bin_gnome-shell.1000.crash

does not provide needed link.

Are there any system settings that can affect this behavior?

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (734 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1741886] ProcEnviron.txt

[Alexey Balmashnov]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1741886/+attachment/5034294/+files/ProcEnviron.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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (734 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1741886] ProcCpuinfoMinimal.txt

[Alexey Balmashnov]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1741886/+attachment/5034293/+files/ProcCpuinfoMinimal.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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (734 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1741886] JournalErrors.txt

[Alexey Balmashnov]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1741886/+attachment/5034292/+files/JournalErrors.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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (734 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

apport information

** Tags added: apport-collected

** Description changed:

  Upon physical disconnect/connect of a monitor (connected via HDMI) shell
  crashes with signal 11.
  
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
  
  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.
  
  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ GsettingsChanges:
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'cursor-blink' b'false'
+  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
+ InstallationDate: Installed on 2016-01-06 (734 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-25-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1741886/+attachment/5034291/+files/Dependencies.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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

Well, I have done what you suggested. Invoking ubuntu-bug on a crash
file creates corresponding upload* files but does not print any links.

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

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

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

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

@Daniel

The above commands do bring me to a web-page, but there are no uploaded
relevant error reports, although I see them in /var/crash

** Attachment added: "/var/crash screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+attachment/5033441/+files/20180108_ls_var_crash.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/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

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

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

[Desktop-packages] [Bug 1741886] [NEW] GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

Public bug reported:

Upon physical disconnect/connect of a monitor (connected via HDMI) shell
crashes with signal 11.

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.26.2-0ubuntu0.1


Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.


Note that the crash file was generated and according to /var/crash content was 
uploaded, when ubuntu-bug triggered by existence of crash file started up and I 
agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to 
Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  8 13:12:14 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'cursor-blink' b'false'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2016-01-06 (732 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

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

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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Alexey Nezhdanov]

The worst thing one can do it so maintain his position instead of apologising 
after being rude and being called out on that.
At least one workaround was proposed even in this very thread.

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Alexey Balmashnov]

Another possible duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  In Progress

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety you will 
boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  before rebooting you should have a network connection after you
  reboot.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  
  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

Re: [Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Alexey Nezhdanov]

Alex, how much did you pay for your copy of Ubuntu?

The problem is frustrating, but:
1) these people don't owe you anything
2) this is FOSS - go and do it yourself
3) solutions do exist.

Drop that tone!

Am 29.08.2017 9:55 nachm. schrieb "Alex" :

> what the f*cking bullshit 21st century and you can't solve this
> annoying bug during several years??? F*ck your bloody UNITY and solve this
> simplest and most important problem!!!
> how to use the system if not possible to switch layout normally???
> shit! shit! shit!
>
> Ubuntu 17.04
>
> uname -a
> Linux 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 i686
> i686 i686 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370953
>
> Title:
>   layout switch is delayed
>
> Status in console-setup package in Ubuntu:
>   Confirmed
> Status in gconf package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have two layouts configured En and Ru with Ctrl-Shift as layout
>   switch combo.
>
>   When I start typing in wrong layout I notice it, hit Ctrl-Shift and type
> again, but more often than not it is wrong layout again.
>   I repeat the action, but there is no luck. On the third attemt it
> usually either works OR the first letter is still in wrong layout, but the
> second is in correct one - i.e. layout switches as I type.
>
>   The explanation for this is that layout switch takes very unreasonable
>   time - much longer than it is needed to move your fingers from  one
>   key to the other. Each time I encounter the error I retry slower so on
>   the third attempt it is slow enough to actually recognize that layout
>   switch is happening, but with a delay.
>
>   This is extremely annoying and unacceptable. If someone knows how to
>   work around it - please post your suggestions here. It would be nice
>   to have a solution for 3+ layouts setup as well.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/console-setup/+
> bug/1370953/+subscriptions
>

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 1708086] [NEW] package docbook-xml 4.5-7.3 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Alexey Borovkov]

Public bug reported:

It's an error that appeared on booting after unproper shootdown.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docbook-xml 4.5-7.3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug  1 07:49:20 2017
DpkgHistoryLog:
 Start-Date: 2017-08-01  07:49:17
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: imagemagick:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9)
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2017-07-23 (9 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: docbook-xml
Title: package docbook-xml 4.5-7.3 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: docbook-xml (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package docbook-xml 4.5-7.3 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in docbook-xml package in Ubuntu:
  New

Bug description:
  It's an error that appeared on booting after unproper shootdown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: docbook-xml 4.5-7.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 07:49:20 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-01  07:49:17
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: imagemagick:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9), 
imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.8, 8:6.8.9.9-7ubuntu5.9)
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: docbook-xml
  Title: package docbook-xml 4.5-7.3 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docbook-xml/+bug/1708086/+subscriptions

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

[Desktop-packages] [Bug 1704110] [NEW] Totem Movie Player skips last n seconds of music

[Alexey Torgashin]

Public bug reported:

I play this IT music file. It has good ending, in this player i don't
hear it: i hear only cropped sound and last seconds don't play. On Win32
I played it in ModPlug and it was ok.

Ubuntu 16.04.02 LTS x64.
totem:
  Installed: 3.18.1-1ubuntu4

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

** Attachment added: "IT music to test"
   
https://bugs.launchpad.net/bugs/1704110/+attachment/4914038/+files/trch-wil.zip

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

Title:
  Totem Movie Player skips last n seconds of music

Status in totem package in Ubuntu:
  New

Bug description:
  I play this IT music file. It has good ending, in this player i don't
  hear it: i hear only cropped sound and last seconds don't play. On
  Win32 I played it in ModPlug and it was ok.

  Ubuntu 16.04.02 LTS x64.
  totem:
Installed: 3.18.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1687252] Re: Gnome Software Center Showing Duplicate Installed Apps

[Alexey Zotov]

It affects me as well (Ubuntu 17.04). Screenshot is attached.

** Attachment added: "Screenshot-20170624234111-1252x899.png"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1687252/+attachment/4902443/+files/Screenshot-20170624234111-1252x899.png

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

Title:
  Gnome Software Center Showing Duplicate Installed Apps

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  In the software store on Ubuntu Gnome 17.04, fully updated, some apps show up 
as installed twice without be doing anything command line installs, updates, 
etc. This currently effects the Software & Updates app and Chromium app 
(installed from the most popular software store options, I'm also confused why 
3 show there). I installed re-downloaded images on a second computer to verify 
this 
  issue further. Print screen showing the duplicates attached. Several other 
apps showed duplicated on installation (including ImageMagick), but went away 
after rebooting.

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

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

[Desktop-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alexey]

This is the exact discription of who my trackpoint works on Ubuntu now:

 I am unable to achieve acceptable results with all the different knobs
that are available. If I tune down acceleration, I am able to do
detailed pointing, but the stick is generally so slow, that it takes
ages to cross the screen. On the other hand, if I increase the
acceleration, even the slightest movement of the stick makes it jump
significantly on the screen so that I am unable to do detailed
selections.

https://bugs.freedesktop.org/show_bug.cgi?id=99860
here is the thread.
I'm not sure 

Seems like acceleration is now working corretly. How can I find more
info about how this works?

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

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

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

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

[Desktop-packages] [Bug 1686155] [NEW] Trackpoint sensitivity on Dell Latitude 5470 is insane

[Alexey]

Public bug reported:

Hello. I've tried to write on askUbuntu and to the Dell Support but got no 
answers.
My problem is that I can setup my trackpoint properly on Ubuntu. It works 
awesome on Windows with or without drivers installed. 
I've come across this thread 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590
which says that trackpoint is not recognized by ubuntu on 16.04 and it was 
fixed in 17.04
So I thought that 5470 and 7470 are pretty close and tried new 17.04 ubuntu but 
the result is the same.

with xinput on 16.04 command I was able to set up 3 parameters but on
17.04 there are no such parameters:

xinput list-props 13
Device 'AlpsPS/2 ALPS DualPoint Stick':
Device Enabled (140):   1
Coordinate Transformation Matrix (142): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Accel Speed (309): 0.00
libinput Accel Speed Default (310): 0.00
libinput Accel Profiles Available (311):1, 1
libinput Accel Profile Enabled (312):   1, 0
libinput Accel Profile Enabled Default (313):   1, 0
libinput Natural Scrolling Enabled (314):   0
libinput Natural Scrolling Enabled Default (315):   0
libinput Send Events Modes Available (260): 1, 0
libinput Send Events Mode Enabled (261):0, 0
libinput Send Events Mode Enabled Default (262):0, 0
libinput Left Handed Enabled (316): 0
libinput Left Handed Enabled Default (317): 0
libinput Scroll Methods Available (318):0, 0, 1
libinput Scroll Method Enabled (319):   0, 0, 1
libinput Scroll Method Enabled Default (320):   0, 0, 1
libinput Button Scrolling Button (321): 2
libinput Button Scrolling Button Default (322): 2
libinput Middle Emulation Enabled (323):0
libinput Middle Emulation Enabled Default (324):0
Device Node (263):  "/dev/input/event6"
Device Product ID (264):2, 8
libinput Drag Lock Buttons (325):   
libinput Horizontal Scroll Enabled (326):   1

and this is a 16.04 parameters:
https://askubuntu.com/questions/908477/configure-trackpoint-on-dell-latitude-5470

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

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

Title:
  Trackpoint sensitivity on Dell Latitude 5470 is insane

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

Bug description:
  Hello. I've tried to write on askUbuntu and to the Dell Support but got no 
answers.
  My problem is that I can setup my trackpoint properly on Ubuntu. It works 
awesome on Windows with or without drivers installed. 
  I've come across this thread 
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590
  which says that trackpoint is not recognized by ubuntu on 16.04 and it was 
fixed in 17.04
  So I thought that 5470 and 7470 are pretty close and tried new 17.04 ubuntu 
but the result is the same.

  with xinput on 16.04 command I was able to set up 3 parameters but on
  17.04 there are no such parameters:

  xinput list-props 13
  Device 'AlpsPS/2 ALPS DualPoint Stick':
Device Enabled (140):   1
Coordinate Transformation Matrix (142): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Accel Speed (309): 0.00
libinput Accel Speed Default (310): 0.00
libinput Accel Profiles Available (311):1, 1
libinput Accel Profile Enabled (312):   1, 0
libinput Accel Profile Enabled Default (313):   1, 0
libinput Natural Scrolling Enabled (314):   0
libinput Natural Scrolling Enabled Default (315):   0
libinput Send Events Modes Available (260): 1, 0
libinput Send Events Mode Enabled (261):0, 0
libinput Send Events Mode Enabled Default (262):0, 0
libinput Left Handed Enabled (316): 0
libinput Left Handed Enabled Default (317): 0
libinput Scroll Methods Available (318):0, 0, 1
libinput Scroll Method Enabled (319):   0, 0, 1
libinput Scroll Method Enabled Default (320):   0, 0, 1
libinput Button Scrolling Button (321): 2
libinput Button Scrolling Button Default (322): 2
libinput Middle Emulation Enabled (323):0
libinput Middle Emulation Enabled Default (324):0
Device Node (263):  "/dev/input/event6"
Device Product ID (264):2, 8
libinput Drag Lock Buttons (325):   
libinput Horizontal Scroll Enabled (326):   1

  and this is a 16.04 

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Alexey Kachalov]

I have this bug on Ubuntu 16.04 x64 too.
Some people say switching to setxkbmap helps: https://toster.ru/q/72254

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[Alexey]

Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.

Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

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

[Desktop-packages] [Bug 1675934] [NEW] Screen corruption after resuming system from suspend

[Alexey Balmashnov]

Public bug reported:

Upon resuming system from suspend I observe graphical artefacts.

This is a regression, since I've noticed this behaviour only after
latest updates.

Rebooting system resolves the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.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.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Mar 24 22:20:38 2017
DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed
 nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4]
InstallationDate: Installed on 2016-01-06 (442 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: HM65-MXM
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Mar 23 19:44:08 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  Screen corruption after resuming system from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon resuming system from suspend I observe graphical artefacts.

  This is a regression, since I've noticed this behaviour only after
  latest updates.

  Rebooting system resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  

[Desktop-packages] [Bug 1675934] Re: Screen corruption after resuming system from suspend

[Alexey Balmashnov]

** Attachment added: "bug_2017-03-24_22-22-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png

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

Title:
  Screen corruption after resuming system from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon resuming system from suspend I observe graphical artefacts.

  This is a regression, since I've noticed this behaviour only after
  latest updates.

  Rebooting system resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .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.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 24 22:20:38 2017
  DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed
   nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4]
  InstallationDate: Installed on 2016-01-06 (442 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Mar 23 19:44:08 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1537053] Re: vlc screen always on top, buggly.

[Alexey]

For me, the bug permanently disappeared a few months ago. Ubuntu 16.04.

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1622955

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

Title:
  vlc screen always on top, buggly.

Status in xserver-xorg-video-intel package in Ubuntu:
  Expired

Bug description:
  I don't know  whether it's due to 15.10 or due to my laptop being a very new 
model "Asus Zenbook 305CA".
  The screen is always on top. Even if it is minimized.
  The gif below takes may some ten seconds to load.
  http://imgur.com/N3AZkiH

  And in addition, the video quality is sensibly worse than it should
  be, compared to Totem video player which functions properly.

  vlc revision 2.2.1-0-ga425c42
  ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053/+subscriptions

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

[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

[Alexey]

This bug is still affected me in Debian Sid (currently 9.0).
I affected with i3lock.

Sometimes, if wait about 3-4minutes, i3lock allow me to reenter
passphrase, but sometimes I have to reboot my laptop...

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1652253] ProcEnviron.txt

[Alexey Bazhin]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808955/+files/ProcEnviron.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1652253] JournalErrors.txt

[Alexey Bazhin]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808954/+files/JournalErrors.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1652253] Re: Xorg crash

[Alexey Bazhin]

apport information

** Tags added: apport-collected

** Description changed:

  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-11-18 (68 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: xorg 1:7.7+13ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
+ Tags:  yakkety
+ Uname: Linux 4.8.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808953/+files/Dependencies.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 

[Desktop-packages] [Bug 1622955] Re: VLC automatic video output malfunctions on Intel HD Graphics 520 (Skylake)

[Alexey]

After some update or some package installation the problem is fixed now.
Simultaneously, a similar problem with Skype video is fixed too.

I do not know what exactly fixed the problem.

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

Title:
  VLC automatic video output malfunctions on Intel HD Graphics 520
  (Skylake)

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This problem is likely similar or same as #1537053.

  When selecting "Automatic" video output in VLC player, the playback
  malfunctions in several ways.

  1. The video floats on top, covering drop-down menus and other windows
  in front. I tried to take a screenshot, but the video does not appear
  on the screenshot.

  2. The aspect ratio is wrong: the image is squeezed from the sides.
  Trying to change the aspect ratio cuts a different rectangle from the
  image without changing the aspect ratio.  (Note: I have a Full HD
  screen 1920x1080.)

  3. The image cannot be stretched beyond its maximal resolution (as
  understood by VLC after miscalculating the aspect ratio).

  4. When resizing the window, a blue background appears and blinks.
  Sometimes it stays, especially in fullscreen mode.

  These problems are fixed by selecting GLX video output instead of
  Automatic.

  I do not know if this might be relevant, but i suspect that for some
  reason i do not have accelerated graphics in my desktop environment:
  dragging windows around clearly is not accelerated enough.

  WORKAROUND: Uncheck Accelerated video output (Overlay)" in Preference
  > Video > Display.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep 13 11:04:05 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c1d]
  InstallationDate: Installed on 2016-08-24 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: ASUSTeK COMPUTER INC. BU403UA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=4844f5ce-60b0-4b8b-a266-74c1faecf470 ro acpi_osi= 
acpi_backlight=native
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: BU403UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: BU403UA
  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:bvnASUSTeKCOMPUTERINC.:bvrBU403UA.303:bd06/27/2016:svnASUSTeKCOMPUTERINC.:pnBU403UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnBU403UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: BU403UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1622955/+subscriptions

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

[Desktop-packages] [Bug 1652253] [NEW] Xorg crash

[Alexey Bazhin]

Public bug reported:

[  3122.921] (EE) 
[  3122.921] (EE) Backtrace:
[  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
[  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
[  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
[  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
[  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
[  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
[  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
[  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
[  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
[  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
[  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
[  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
[  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7fcac3f703f1]
[  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
[  3122.922] (EE) 
[  3122.922] (EE) Bus error at address 0x7fcaa65ab400
[  3122.922] (EE) 
Fatal server error:
[  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
[  3122.922] (EE) 
[  3122.922] (EE)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Dec 23 11:53:30 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-11-18 (34 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug crash yakkety

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1650864] [NEW] In new version fields are not colored as they have to be

[Alexey Stogny]

Public bug reported:

This is important gameplay feature, and seems that this was changed by
somebody newer played mines, wasn't it so?

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

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

Title:
  In new version fields are not colored as they have to be

Status in gnome-mines package in Ubuntu:
  New

Bug description:
  This is important gameplay feature, and seems that this was changed by
  somebody newer played mines, wasn't it so?

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

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

[Desktop-packages] [Bug 1622955] Re: VLC automatic video output malfunctions on Intel HD Graphics 520 (Skylake)

[Alexey]

Why is this marked Expired?

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

Title:
  VLC automatic video output malfunctions on Intel HD Graphics 520
  (Skylake)

Status in xserver-xorg-video-intel package in Ubuntu:
  Expired

Bug description:
  This problem is likely similar or same as #1537053.

  When selecting "Automatic" video output in VLC player, the playback
  malfunctions in several ways.

  1. The video floats on top, covering drop-down menus and other windows
  in front. I tried to take a screenshot, but the video does not appear
  on the screenshot.

  2. The aspect ratio is wrong: the image is squeezed from the sides.
  Trying to change the aspect ratio cuts a different rectangle from the
  image without changing the aspect ratio.  (Note: I have a Full HD
  screen 1920x1080.)

  3. The image cannot be stretched beyond its maximal resolution (as
  understood by VLC after miscalculating the aspect ratio).

  4. When resizing the window, a blue background appears and blinks.
  Sometimes it stays, especially in fullscreen mode.

  These problems are fixed by selecting GLX video output instead of
  Automatic.

  I do not know if this might be relevant, but i suspect that for some
  reason i do not have accelerated graphics in my desktop environment:
  dragging windows around clearly is not accelerated enough.

  WORKAROUND: Uncheck Accelerated video output (Overlay)" in Preference
  > Video > Display.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep 13 11:04:05 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c1d]
  InstallationDate: Installed on 2016-08-24 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: ASUSTeK COMPUTER INC. BU403UA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=4844f5ce-60b0-4b8b-a266-74c1faecf470 ro acpi_osi= 
acpi_backlight=native
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: BU403UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: BU403UA
  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:bvnASUSTeKCOMPUTERINC.:bvrBU403UA.303:bd06/27/2016:svnASUSTeKCOMPUTERINC.:pnBU403UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnBU403UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: BU403UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1622955/+subscriptions

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

[Alexey Khisamutdinov]

The same issue.

Dell latitude E6440, ubuntu-gnome 16.04

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

$ uname -a
Linux pcname 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

$ cat /usr/share/gnome/gnome-version.xml


 3
 18
 2
 Ubuntu


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

Title:
  On-screen text disappears after suspend

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  

[Desktop-packages] [Bug 1632123] Re: Nautilus "Open in Terminal" is performing some useless operations and causes an abnormal CPU activity on opening terminal

[Alexey]

Created a new report:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635830

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

Title:
  Nautilus "Open in Terminal" is performing some useless operations and
  causes an abnormal CPU activity on opening terminal

Status in nautilus package in Ubuntu:
  New

Bug description:
  When i select "Open in Terminal" from Nautilus menu, the terminal
  opens in the current folder (as expected) and the cursor rapidly
  blinks for a few seconds, ignoring attempts to type anything at the
  prompt. During this period, the whole system freezes a bit and the
  processor usage can reach 40% on a 6th generation Intel Core i7.

  I am using Ubuntu GNOME 16.04.1.

  nautilus:
Installed: 1:3.18.4.is.3.14.3-0ubuntu5

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

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

[Desktop-packages] [Bug 1635830] [NEW] Nautilus window bar menu commands cause abnormal CPU usage and "freeze"

[Alexey]

Public bug reported:

When i select commands from Nautilus window bar menu such as "New Tab",
"New Folder", "Open in Terminal", the system freezes a bit and the
processor usage can reach 60% on a 6th generation Intel Core i7.

For example, "Open in Terminal" opens the terminal in the current folder
(as expected) and the cursor rapidly blinks for a few seconds, ignoring
attempts to type anything at the prompt.

This abnormal activity does not happen if i choose "New Folder" or "Open
in Terminal" from a pop-up menu, right-clicking in an empty space in the
Nautilus window.

I am using Ubuntu GNOME 16.04.1. According to GNOME developers, GNOME 3.18 is 
not supported anymore:
https://bugzilla.gnome.org/show_bug.cgi?id=772945

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 22 14:03:28 2016
InstallationDate: Installed on 2016-08-24 (58 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Nautilus window bar menu commands cause abnormal CPU usage and
  "freeze"

Status in nautilus package in Ubuntu:
  New

Bug description:
  When i select commands from Nautilus window bar menu such as "New
  Tab", "New Folder", "Open in Terminal", the system freezes a bit and
  the processor usage can reach 60% on a 6th generation Intel Core i7.

  For example, "Open in Terminal" opens the terminal in the current
  folder (as expected) and the cursor rapidly blinks for a few seconds,
  ignoring attempts to type anything at the prompt.

  This abnormal activity does not happen if i choose "New Folder" or
  "Open in Terminal" from a pop-up menu, right-clicking in an empty
  space in the Nautilus window.

  I am using Ubuntu GNOME 16.04.1. According to GNOME developers, GNOME 3.18 is 
not supported anymore:
  https://bugzilla.gnome.org/show_bug.cgi?id=772945

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 22 14:03:28 2016
  InstallationDate: Installed on 2016-08-24 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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