date:20180425

I would be curious to see the value of 'depth' in:
standard_pict_format_for_depth (int depth)

Maybe it's a valid but unusual value. Or maybe it's junk, so your theory
about memory corruption sounds plausible...

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

That's annoying. We should be able to retrace any crash from any package
versions. Seems like we've made reporting crashes more difficult than it
should be.

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

Too late!  The world has moved on, and I can no longer upload this bug:

You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:

libdb5.3, libplist3, libssl1.1, openssl

I guess if it happens on another machine, I'll upload it properly and
add a link here.

I still have the .crash file if you want 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/1766938

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

2018-04-25 Thread Julian Bieringer-Hinterbuchinger

@Dave Goldsbrough

Thank you for your suggestion, but unfortunately i tried this approach
already multiple times and it didn't help. I also thought it probably is
an issue due to battery saving mode so I tried the following command
without any positive result:

sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/'
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

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

Title:
  Wifi interface does often not show up after reboot

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766968] Re: loss of launcher and desktop graphic

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

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

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

Title:
  loss of launcher and desktop graphic

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Logged out to change from gnome to unity and lost services and all
  ability to change Desktop to include Graphic,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 25 15:03:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
  InstallationDate: Installed on 2017-01-21 (459 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 4180W4B
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=debe0dd6-6497-46f9-afe1-933bd5f7cbaf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET67WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W4B
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4180W4B:pvrThinkPadT420:rvnLENOVO:rn4180W4B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W4B
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Wed Apr 25 14:45:00 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 738 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1765772] Re: xserver-xorg-video-intel crashes xorg session

See also:
https://www.phoronix.com/scan.php?page=news_item&px=X-Server-1.20-Fixing-DRI3-Fall

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

Title:
  xserver-xorg-video-intel crashes xorg session

Status in gnome-shell package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  System: Ubuntu 18.04
  PC: Dell inspiron n5110 laptop
  CPU: intel i7 2630QM
  GPU: nvidia gt 525m

  Reproduce:
  1- install nvidia proprietary driver, restart
  2- open nvidia-setting, select intel driver, reboot (or prime-select)

  Result:
  you cant login xorg session but you can login wayland
  (xorg or gnome-shell crashing and back to gdm)

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

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

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

If you're coming from a 17.10 or older system then you will need to
apply the workaround from bug 994921 first.

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

Sure, sorry for uploading it wrong in the first place.
The new bug is ... uh... it didn't create one, it just went into the ether, in 
a cloud of dots.

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-25 Thread Shih-Yuan Lee

@Taihsiang,

Have you checked Ubuntu 16.04.0 and 16.04.1?
If not, could you check if they have the similar issues?

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  New
Status in gnome-menus package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** 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 (376.4 KB)
    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):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds

Hi Dan,

I can't seem to find any other reports of that crash. But to ensure it's
been retraced accurately and correctly classified, please use this
command to upload the crash file:

  ubuntu-bug /var/crash/YOURFILE.crash

And then mention here the ID of the new bug created.

** Summary changed:

- gnome-shell crashes after a few seconds
+ gnome-shell crashed in standard_pict_format_for_depth()

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

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

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

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

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear

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

apport-collect 1766775

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


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

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

Title:
  Notifications do not disappear

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

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

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

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

[Desktop-packages] [Bug 1740146] Re: [AMD/radeon] System slow on wayland, lagging mouse (but fast in Xorg)

** Summary changed:

- [AMD C-60] System slow on wayland, lagging mouse (but fast in Xorg)
+ [AMD/radeon] System slow on wayland, lagging mouse (but fast in Xorg)

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

Title:
  [AMD/radeon] System slow on wayland, lagging mouse (but fast in Xorg)

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

Bug description:
  Ubuntu 18.04 development branch @ 26/12/2017

  Overall system is lagging when opening programs and mouse, not smooth to work 
with
  on gnome and the default wayland session, the xorg session is fast without 
lags. Tested the same machine on 17.10 and have same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 17:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6290] [1025:0598]
  InstallationDate: Installed on 2017-12-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  Lsusb:
   Bus 002 Device 002: ID 0402:7675 ALi Corp.
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer AO722
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Type1Family
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1763751] Re: Poor performance of the Wayland session in Ubuntu 18.04

Hi Giovanni,

I am tracking a couple of reasons why Wayland sessions might be slower
than Xorg sessions [1]. But I wonder - are you using multiple
monitors/screens? If so then this would be bug 1730460.

Otherwise, let's group this under bug 1740146.

[1] https://trello.com/c/Q6JYXPPs

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

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

Title:
  Poor performance of the Wayland session in Ubuntu 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Poor performance of the Wayland session in Ubuntu 18.04 with AMD
  A10-7300 in Acer E5-551G. No problems with Xorg session.

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

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

This bug is closed, so please help us by opening new bugs to discuss any
ongoing problems.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

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

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

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent

Bob, I think you want bug 1765261, not this one.

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

Title:
  Blocked at gdm login screen on 18.04 if user password has a circumflex
  accent

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I have a bug since the recent updates on Ubuntu 18.04 (post 10th
  March): when the user password contains a circumflex accent, like "û",
  access is denied even if password entered is correct and I stay
  blocked in a loop at gdm login screen - error message (translated from
  French): "Sorry, it doesn't work, please try again".

  Even after modifying it on recovery mode with passwd without û, it
  stays blocked. Only way to solve it is to reinstall.

  Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
  Kernel driver in use: radeon
  Kernel modules: radeon, amdgpu

  Steps to reproduce :

  I did a fresh and new install with 18.04 daily iso from 21st March,
  formatting / and /home with following user password:

  Ubuntu42

  At startup, I could log successfully both on Xorg and Wayland sessions. Then 
I modified and tested those passwords, with all of them I could again boot and 
connect, on Xorg and Wayland:
  ArchLinux43
  LinuxMint@28
  KDENeon=51
  Fedora_1984

  But the last one made me blocked at the gdm login screen:

  Debianû74

  Here unable to modify it on recovery session, error message in French:
  "erreur de manipulation du jeton d'authentification".

  Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but
  F2, F3... F12 freezes it! I only can update in chroot with lie USB.

  I had to again format and reinstall, with a password without any
  circumflex accent.

  
  How and when I discovered it :

  On 10th March, I ran since many weeks the alpha version of Ubuntu
  18.04, with a password having a "û" inside, which had always worked
  fine. I did an update, cumulating the last 3 weeks before.

  On next startup, when I typed my password, both on Xorg and Wayland
  sessions, no error message but no desktop, nothing appeared but a few
  seconds later I was back on login screen.

  I could well log in on terminal (Ctrl Alt F2) or chroot with a live
  USB, and do the last updates in the next days, but nothing changed.

  On console, if I ran "startx" I got the message "timeout in locking
  authority file" and "fatal server error: cannot open log file
  ./local/share/xorg/Xorg.0.log

  Both / and /home were not full - more than 60% space available,
  verified with df -Th ; echo ; df -Ti

  I tried to reinstall Ubuntu with daily live of 15th March, formatting
  / but not /home as it was protected by ecryptfs and I didn't save some
  files, using same user name and password, still blocked.

  So I copied the /home and .Private folders to another disk to try
  later recover them, reinstall again, formatting both / and /home,
  always with my usual password having a "û" (I verified French
  language, keyboard with French activated, upper case, symbols... OK).

  This time, again both for Xorg or Wayland sessions, at gdm login I did
  not success to connect, I got an error message "Désolé ça n'a pas
  fonctionné, veuillez réessayer",

  I tried to modify the password in recovery mode, with no special
  characters nor accents, but still blocked at gdm. And no terminal
  available with Ctrl Alt F2...

  On 23rd March, I re-reinstalled all Ubuntu, formatting / and /home,
  this time with daily iso from 21st March, but with a modification: to
  avoid any misconfiguration with languages on live USB, I chose a very
  easy password, only with normal letters and numbers.

  On startup, yes, finally I could log at gdm on default Xorg session
  and enter desktop !

  I went to my user configuration, changed to put my usual password
  (with an "û"), and bam, back to the future, still blocked at gdm
  screen on restart, either on Xorg or Wayland, Ctr Alt F2 not working.

  It made me understand that the bug came from a special character in my
  password, then I tried the different ones explained on top of this
  report to discover it was "û".

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

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

[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()

Also tracking xorg-server, so people can find this bug more easily, and
in case a fix is required in Xwayland directly.

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

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

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

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.

[Desktop-packages] [Bug 1767013] [NEW] package xdiagnose 3.8.4.1 failed to install/upgrade: サブプロセスインストール済みの post-installation スクリプトはエラー終了ステータス 1 を返しました

2018-04-25 Thread Takeshi Teshima

Public bug reported:

After login, this error was shown.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdiagnose 3.8.4.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
AptOrdering:
 ibus-table: Configure
 unity-control-center: Configure
 xdiagnose: Configure
 ubuntu-desktop: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Apr 25 23:52:53 2018
ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
InstallationDate: Installed on 2017-08-23 (245 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: xdiagnose
Title: package xdiagnose 3.8.4.1 failed to install/upgrade: サブプロセス インストール済みの 
post-installation スクリプト はエラー終了ステータス 1 を返しました
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package xdiagnose 3.8.4.1 failed to install/upgrade: サブプロセス インストール済みの
  post-installation スクリプト はエラー終了ステータス 1 を返しました

Status in xdiagnose package in Ubuntu:
  New

Bug description:
  After login, this error was shown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdiagnose 3.8.4.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  AptOrdering:
   ibus-table: Configure
   unity-control-center: Configure
   xdiagnose: Configure
   ubuntu-desktop: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 25 23:52:53 2018
  ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  InstallationDate: Installed on 2017-08-23 (245 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: xdiagnose
  Title: package xdiagnose 3.8.4.1 failed to install/upgrade: サブプロセス インストール済みの 
post-installation スクリプト はエラー終了ステータス 1 を返しました
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

We know it's broken (and more so in Wayland sessions). For more up to
date information, please see the upstream bug instead:

  https://bugzilla.gnome.org/show_bug.cgi?id=746273

That's where any fix will occur first.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

Status in GTK+:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-25 Thread Yuan-Chen Cheng

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  New
Status in gnome-menus package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** 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 (376.4 KB)
    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):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xe

[Desktop-packages] [Bug 1767014] [NEW] package ibus 1.5.11-1ubuntu2.1 failed to install/upgrade: サブプロセスインストール済みの post-installation スクリプトはエラー終了ステータス 1 を返しました

2018-04-25 Thread Takeshi Teshima

Public bug reported:

After login, this error was shown.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ibus 1.5.11-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 23:52:11 2018
ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
InstallationDate: Installed on 2017-08-23 (245 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: ibus
Title: package ibus 1.5.11-1ubuntu2.1 failed to install/upgrade: サブプロセス 
インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package ibus 1.5.11-1ubuntu2.1 failed to install/upgrade: サブプロセス
  インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

Status in ibus package in Ubuntu:
  New

Bug description:
  After login, this error was shown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 23:52:11 2018
  ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  InstallationDate: Installed on 2017-08-23 (245 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ibus
  Title: package ibus 1.5.11-1ubuntu2.1 failed to install/upgrade: サブプロセス 
インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758653] Re: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied

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

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

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

Title:
  gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission
  denied

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission
  denied

  /var/cache/ has no 'samba' subdir nor file.

  oem@ubuntu:~$ ls -la /var/cache/
  total 80
  drwxr-xr-x 18 root root  4096 Feb 19 18:57 .
  drwxr-xr-x 14 root root  4096 Dec  1 20:15 ..
  drwxr-xr-x  2 root root  4096 Sep 15  2017 apparmor
  drwxr-xr-x  4 root root  4096 Dec  1 20:15 app-info
  drwxr-xr-x  3 root root  4096 Mar 25 14:11 apt
  drwxr-xr-x  3 root root  4096 Feb 19 18:00 apt-xapian-index
  drwxr-xr-x  2 root root  4096 Dec  1 20:15 cracklib
  drwxrwx---  3 root lp4096 Mar 25 07:35 cups
  drwxr-xr-x  2 root root  4096 Mar 23 04:41 debconf
  drwxr-xr-x  2 root root  4096 Dec  1 18:55 dictionaries-common
  drwxr-xr-x  2 root root 12288 Mar 19 04:28 fontconfig
  drwxr-xr-x  2 root root  4096 Oct  9 19:50 gdm
  drwx--  2 root root  4096 Mar 25 14:11 ldconfig
  drwxr-xr-x  2 root root  4096 Dec  1 19:13 localepurge
  drwxr-xr-x 13 man  man   4096 Mar 25 14:11 man
  -rw-r--r--  1 root root 0 Mar 25 08:24 motd-news
  drwxr-xr-x  3 root root  4096 Dec  1 19:57 PackageKit
  drwxr-xr-x  2 root root  4096 Mar 24 14:56 snapd
  drwxr-xr-x  2 root root  4096 Feb 20 04:57 ubuntu-advantage-tools

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 25 14:28:21 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

mutter (3.28.1-1ubuntu1) bionic; urgency=medium

  * Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
xwayland-Don-t-abort-if-Xwayland-crashes.patch:
- Cherry picked from upstream, to reduce noise of mutter on crashes
  which are actually caused by XWayland (LP: #1748450)

 -- Marco Trevisan (Treviño)   Mon, 23 Apr 2018
10:46:57 -0500

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

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-shell source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1556601] Re: gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() from gdk_x11_display_error_trap_pop_internal() from gdk_error_trap_pop_internal() from

mutter (3.28.1-1ubuntu1) bionic; urgency=medium

  * Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
xwayland-Don-t-abort-if-Xwayland-crashes.patch:
- Cherry picked from upstream, to reduce noise of mutter on crashes
  which are actually caused by XWayland (LP: #1748450)

 -- Marco Trevisan (Treviño)   Mon, 23 Apr 2018
10:46:57 -0500

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

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

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

Title:
  gnome-shell crashed with signal 5 in _XIOError() from _XReply() from
  XSync() from gdk_x11_display_error_trap_pop_internal() from
  gdk_error_trap_pop_internal() from meta_screen_free() from
  meta_display_close()

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/c639f8bfee916c8847cf5b231bd46cc7788f7095

  ---

  Prompted to report this bug after login.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 19:48:37 2016
  DisplayManager:

  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-04-07 (341 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

Hi jibel, please refer to the attachment of comment #4. It is the
tarball of /var/log/dist-upgrade

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** 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 (376.4 KB)
    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):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dp

[Desktop-packages] [Bug 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels

gnome-shell (3.28.1-0ubuntu2) bionic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * js-ui-Choose-some-actors-to-cache-on-the-GPU.patch:
- Improve rendering of shell elements moving rendering to GPU
  (LP: #1744001)

  [ Jeremy Bicha ]
  * Cherry-pick polkitAgent-Guard-against-repeated-close-calls.patch:
- Fix PolicyKit authorization prompt after cancelling once (LP: #1765353)

 -- Marco Trevisan (Treviño)   Mon, 23 Apr 2018
15:29:28 -0500

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

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

Title:
  gnome-shell is wasting CPU repainting unchanging panels

Status in GNOME Shell:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the
  panel get repainted. But the panels mostly doesn't change, so should
  be cached via offscreen-redirect instead.

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

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

[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

mutter (3.28.1-1ubuntu1) bionic; urgency=medium

  * Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
xwayland-Don-t-abort-if-Xwayland-crashes.patch:
- Cherry picked from upstream, to reduce noise of mutter on crashes
  which are actually caused by XWayland (LP: #1748450)

 -- Marco Trevisan (Treviño)   Mon, 23 Apr 2018
10:46:57 -0500

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

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

** Attachment added: "201606-22338-dist-upgrade.log.tar.gz"

https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127357/+files/201606-22338-dist-upgrade.log.tar.gz

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

Title:
package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
Incomplete

Bug description:
Dell XPS 13 9360 (CID 201606-22338)
pre-installed image Xenial

[Description]

When I tried to perform 16.04 --> 18.04 update, the update process
failed. The process guide me to file this bug report.

[Steps to reproduce]
1. Update the system to the latest stack by "sudo apt-get update; sudo
apt-get dist-upgrade -y"
2. Reboot
3. Make sure /etc/update-manager/release-upgrades is able to update (The
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not
"Prompt=never").
4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade
-d"
5. During the update process, it prompts for "Configuring gdm3". There are
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the
attachment for the prompt details as well.

We should use "-d" because bionic beaver has not been officially
released yet.

[Expected Result]

The release update completed and I could start using Bionic instead of
Xenial.

[Actual Result]

The update process failed. It shows the error message[1] and
automatically asking for filing this bug report.

[1]

Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb
...
Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over
(5.5.1-1ubuntu1) ...
Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb
...
Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over
(5.5.1-2ubuntu6) ...
(Reading database ... 253705 files and directories currently installed.)
Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
bamfdaemon -> gnome-menus
packages' pending triggers which are or may be unresolvable:
gnome-menus: /usr/share/applications
bamfdaemon: /usr/share/applications
libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
desktop-file-utils: /usr/share/applications
mime-support: /usr/share/applications
dpkg: error processing package gnome-menus (--remove):
triggers looping, abandoned
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
Errors were encountered while processing:
gnome-menus
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/gnome-menus.0.crash'
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an
error code (1)

*** 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 (376.4 KB)
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):

.. (a lot of them)

qml-module-qtquick-controls2:amd64
qml-module-org-kde-kconfig:amd64
libunity-control-center1
libqt5quickcontrols2-5:amd64
libglib2.0-bin
libkf5plasma5:amd64
locales
qml-module-qtqml-models2:amd64
libkf5coreaddons5:amd64
gir1.2-goa-1.0:amd64
libwebkit2gtk-4.0-37:amd64
Processing was halted because there were too many errors.

Upgrade complete

The upgrade has completed but there were errors during the upgrade
process.

To continue please press [ENTER]

ubuntu@201606-22338:~$

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 22:00:01 2018
Dependencies:

DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-04-25 (0 days ago)
InstallationMedia:

[Desktop-packages] [Bug 1767010] Re: [SRU] java-atk-wrapper: replace javah usage with a call to javac

2018-04-25 Thread Tiago Stürmer Daitx

This debdiff removed the javah check in configure.ac

** Patch added: "java-atk-wrapper_0.33.3-20_debdiff_0.33.3-20ubuntu0.1.patch"

https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+attachment/5127356/+files/java-atk-wrapper_0.33.3-20_debdiff_0.33.3-20ubuntu0.1.patch

** Description changed:

[Impact]
Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1]
because it can't find the javah binary.

The javah binary has been removed from OpenJDK 10 and the java compiler
should be used in its place to build native headers by calling "javac
-h".

[Test Case]
Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie.
depends on openjdk-11-jdk), it should FTBFS with:

checking for javah... no
configure: error: Java 1.6 or later is required to build java-access-bridge

When fixed the build is build is expected to succeed.

[Regression Potential]
No regression is expected as javah is not used by java-atk-wrapper.

[Other Info]
- * java-atk-wrapper does not use javah although it is currently declared in
configure.ac4, the build succeeds by simply removing the javah check.
+ * java-atk-wrapper does not use javah although it is currently declared in
configure.ac, the build succeeds by simply removing the javah check.

[References]
[1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html

** Tags added: patch

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

Title:
[SRU] java-atk-wrapper: replace javah usage with a call to javac

Status in java-atk-wrapper package in Ubuntu:
New

Bug description:
[Impact]
Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1]
because it can't find the javah binary.

The javah binary has been removed from OpenJDK 10 and the java
compiler should be used in its place to build native headers by
calling "javac -h".

[Test Case]
Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie.
depends on openjdk-11-jdk), it should FTBFS with:

checking for javah... no
configure: error: Java 1.6 or later is required to build java-access-bridge

When fixed the build is build is expected to succeed.

[Regression Potential]
No regression is expected as javah is not used by java-atk-wrapper.

[Other Info]
* java-atk-wrapper does not use javah although it is currently declared in
configure.ac, the build succeeds by simply removing the javah check.

[References]
[1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+subscriptions

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

[Desktop-packages] [Bug 1767010] [NEW] [SRU] java-atk-wrapper: replace javah usage with a call to javac

2018-04-25 Thread Tiago Stürmer Daitx

Public bug reported:

[Impact]
Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] 
because it can't find the javah binary.

The javah binary has been removed from OpenJDK 10 and the java compiler
should be used in its place to build native headers by calling "javac
-h".

[Test Case]
Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. 
depends on openjdk-11-jdk), it should FTBFS with:

checking for javah... no
configure: error: Java 1.6 or later is required to build java-access-bridge

When fixed the build is build is expected to succeed.

[Regression Potential]
No regression is expected as javah is not used by java-atk-wrapper.

[Other Info]
 * java-atk-wrapper does not use javah although it is currently declared in 
configure.ac, the build succeeds by simply removing the javah check.

[References]
[1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html

** Affects: java-atk-wrapper (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic ftbfs patch

** Tags added: bionic ftbfs

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

Title:
  [SRU] java-atk-wrapper: replace javah usage with a call to javac

Status in java-atk-wrapper package in Ubuntu:
  New

Bug description:
  [Impact]
  Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] 
because it can't find the javah binary.

  The javah binary has been removed from OpenJDK 10 and the java
  compiler should be used in its place to build native headers by
  calling "javac -h".

  [Test Case]
  Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. 
depends on openjdk-11-jdk), it should FTBFS with:

  checking for javah... no
  configure: error: Java 1.6 or later is required to build java-access-bridge

  When fixed the build is build is expected to succeed.

  [Regression Potential]
  No regression is expected as javah is not used by java-atk-wrapper.

  [Other Info]
   * java-atk-wrapper does not use javah although it is currently declared in 
configure.ac, the build succeeds by simply removing the javah check.

  [References]
  [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+subscriptions

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

[Desktop-packages] [Bug 1767005] [NEW] package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2018-04-25 Thread Fernando

Public bug reported:

error appeared when I booted the pc

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Apr 24 08:47:37 2018
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2016-09-28 (574 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libreoffice
Title: package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in libreoffice package in Ubuntu:
  New

Bug description:
  error appeared when I booted the pc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Apr 24 08:47:37 2018
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2016-09-28 (574 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libreoffice
  Title: package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear

2018-04-25 Thread Bug Watch Updater

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

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

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

Title:
  Notifications do not disappear

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

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

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

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

[Desktop-packages] [Bug 1752223] Re: Please remove esound (& rdeps) from Ubuntu

2018-04-25 Thread Łukasz Zemczak

Removed monster-masher from the recommends list in debian-games.
Proceeded with the removal:

$ remove-package -m "Unmaintained, removed from Debian testing; LP: #1752223" 
esound llk-linux monster-masher synaesthesia
Removing packages from bionic:
esound 0.2.41-11 in bionic
esound-common 0.2.41-11 in bionic amd64
esound-common 0.2.41-11 in bionic arm64
esound-common 0.2.41-11 in bionic armhf
esound-common 0.2.41-11 in bionic i386
esound-common 0.2.41-11 in bionic ppc64el
esound-common 0.2.41-11 in bionic s390x
libesd0 0.2.41-11 in bionic amd64
libesd0 0.2.41-11 in bionic arm64
libesd0 0.2.41-11 in bionic armhf
libesd0 0.2.41-11 in bionic i386
libesd0 0.2.41-11 in bionic ppc64el
libesd0 0.2.41-11 in bionic s390x
libesd0-dev 0.2.41-11 in bionic amd64
libesd0-dev 0.2.41-11 in bionic arm64
libesd0-dev 0.2.41-11 in bionic armhf
libesd0-dev 0.2.41-11 in bionic i386
libesd0-dev 0.2.41-11 in bionic ppc64el
libesd0-dev 0.2.41-11 in bionic s390x
llk-linux 2.3~beta1-0ubuntu6 in bionic
llk-linux 2.3~beta1-0ubuntu6 in bionic amd64
llk-linux 2.3~beta1-0ubuntu6 in bionic arm64
llk-linux 2.3~beta1-0ubuntu6 in bionic armhf
llk-linux 2.3~beta1-0ubuntu6 in bionic i386
llk-linux 2.3~beta1-0ubuntu6 in bionic ppc64el
llk-linux 2.3~beta1-0ubuntu6 in bionic s390x
monster-masher 1.8.1-7build2 in bionic
monster-masher 1.8.1-7build2 in bionic amd64
monster-masher 1.8.1-7build2 in bionic arm64
monster-masher 1.8.1-7build2 in bionic armhf
monster-masher 1.8.1-7build2 in bionic i386
monster-masher 1.8.1-7build2 in bionic ppc64el
monster-masher 1.8.1-7build2 in bionic s390x
synaesthesia 2.4-5.1 in bionic
synaesthesia 2.4-5.1 in bionic amd64
synaesthesia 2.4-5.1 in bionic arm64
synaesthesia 2.4-5.1 in bionic armhf
synaesthesia 2.4-5.1 in bionic i386
synaesthesia 2.4-5.1 in bionic ppc64el
synaesthesia 2.4-5.1 in bionic s390x
Comment: Unmaintained, removed from Debian testing; LP: #1752223
Remove [y|N]? y
4 packages successfully removed.


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

** Changed in: llk-linux (Ubuntu)
   Status: New => Fix Released

** Changed in: monster-masher (Ubuntu)
   Status: New => Fix Released

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

** Changed in: esound (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: llk-linux (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: monster-masher (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: synaesthesia (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  Please remove esound (& rdeps) from Ubuntu

Status in esound package in Ubuntu:
  Fix Released
Status in llk-linux package in Ubuntu:
  Fix Released
Status in monster-masher package in Ubuntu:
  Fix Released
Status in synaesthesia package in Ubuntu:
  Fix Released

Bug description:
  esound has been removed from Debian Testing with plans to completely
  remove it from Unstable soon too.

  https://bugs.debian.org/894269

  esound's last release was like a decade ago.

  Please remove it from Ubuntu.

  $ reverse-depends src:esound
  Reverse-Depends
  ===
  * llk-linux (for libesd0)
  * monster-masher(for libesd0)
  * synaesthesia  (for libesd0)

  llk-linux was never in Debian and is unmaintained.

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

-- 
Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

fb keep at it
btu de w9dki / w9gty 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has chang

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

fb 
I will try todo it in gcc / inline machine language if you can’t find the 
problem if you like

de w9dki / w9gty 40

Sent from my iPhoneX+(beta)


> On Apr 3, 2018, at 00:29, Thomas <1748...@bugs.launchpad.net> wrote:
> 
> Xorg
> 
> 
> 
> Van: boun...@canonical.com  namens Daniel van Vugt 
> 
> Verzonden: dinsdag 3 april 2018 3:52
> Aan: tomlemmen...@hotmail.com
> Onderwerp: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in 
> _g_log_abort() from g_log_default_handler() from 
> default_log_handler(message="Connection to xwayland lost") from g_logv() from 
> g_log() from 
> 
> This bug is indeed meant to be wayland only. Which duplicates are from
> Xorg?
> 
> Note that the login screen (gdm3) is using wayland by default. So your
> system may report this crash even if you only use Xorg sessions.
> 
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1759788).
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

-- 
You received this bug notificati

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

fb thx try to fix it...if possible  using cinnamon now and had to shift to a 
macbook pro with homebrew and xcode. slmist a debian (from my dson Derek 
Walters the IphoneX chief engineering team leader🙂
guess who gets the Msc OS “beta” version of new software patches for testing 
...me 🤣

btu de w9dki 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them a

[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear

2018-04-25 Thread hackel

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=721170
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Notifications do not disappear

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

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

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

-- 
Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

fb thx 73 bk
de w9dki 40

Sent from my iPhone

> On Apr 2, 2018, at 23:22, Jean-Baptiste Lallement 
>  wrote:
> 
> I checked tens of duplicates and all the crashes happen from the login
> screen (XDG_CURRENT_DESKTOP=GNOME-Greeter:GNOME)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  Pro

[Desktop-packages] [Bug 1739797] Re: Please remove gnome-python-desktop from Ubuntu

2018-04-25 Thread Łukasz Zemczak

$ remove-package -m "Unmaintained, removed from Debian testing; LP: #1739797" 
gnome-python-desktop hamster-applet memaker sugar-presence-service 
sugar-toolkit xword
Removing packages from bionic:
gnome-python-desktop 2.32.0+dfsg-4build1 in bionic
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic amd64
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic arm64
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic armhf
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic i386
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic ppc64el
python-gnome2-desktop-dev 2.32.0+dfsg-4build1 in bionic s390x
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic amd64
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic arm64
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic armhf
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic i386
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic ppc64el
python-gnomekeyring 2.32.0+dfsg-4build1 in bionic s390x
python-rsvg 2.32.0+dfsg-4build1 in bionic amd64
python-rsvg 2.32.0+dfsg-4build1 in bionic arm64
python-rsvg 2.32.0+dfsg-4build1 in bionic armhf
python-rsvg 2.32.0+dfsg-4build1 in bionic i386
python-rsvg 2.32.0+dfsg-4build1 in bionic ppc64el
python-rsvg 2.32.0+dfsg-4build1 in bionic s390x
python-wnck 2.32.0+dfsg-4build1 in bionic amd64
python-wnck 2.32.0+dfsg-4build1 in bionic arm64
python-wnck 2.32.0+dfsg-4build1 in bionic armhf
python-wnck 2.32.0+dfsg-4build1 in bionic i386
python-wnck 2.32.0+dfsg-4build1 in bionic ppc64el
python-wnck 2.32.0+dfsg-4build1 in bionic s390x
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
amd64
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
arm64
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
armhf
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
i386
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
ppc64el
hamster-applet 2.91.3+git20120514.b9fec3e1-1ubuntu2 in bionic 
s390x
memaker 1.5-0ubuntu6 in bionic
memaker 1.5-0ubuntu6 in bionic amd64
memaker 1.5-0ubuntu6 in bionic arm64
memaker 1.5-0ubuntu6 in bionic armhf
memaker 1.5-0ubuntu6 in bionic i386
memaker 1.5-0ubuntu6 in bionic ppc64el
memaker 1.5-0ubuntu6 in bionic s390x
sugar-presence-service 0.90.2-8 in bionic
sugar-presence-service 0.90.2-8 in bionic amd64
sugar-presence-service 0.90.2-8 in bionic arm64
sugar-presence-service 0.90.2-8 in bionic armhf
sugar-presence-service 0.90.2-8 in bionic i386
sugar-presence-service 0.90.2-8 in bionic ppc64el
sugar-presence-service 0.90.2-8 in bionic s390x
sugar-toolkit 0.112-3 in bionic
python-sugar-toolkit 0.112-3 in bionic amd64
python-sugar-toolkit 0.112-3 in bionic arm64
python-sugar-toolkit 0.112-3 in bionic armhf
python-sugar-toolkit 0.112-3 in bionic i386
python-sugar-toolkit 0.112-3 in bionic ppc64el
python-sugar-toolkit 0.112-3 in bionic s390x
xword 2.0.0~rc2-1 in bionic
xword 2.0.0~rc2-1 in bionic amd64
xword 2.0.0~rc2-1 in bionic arm64
xword 2.0.0~rc2-1 in bionic armhf
xword 2.0.0~rc2-1 in bionic i386
xword 2.0.0~rc2-1 in bionic ppc64el
xword 2.0.0~rc2-1 in bionic s390x
Comment: Unmaintained, removed from Debian testing; LP: #1739797
Remove [y|N]? y
6 packages successfully removed.


** Changed in: gnome-python-desktop (Ubuntu)
   Status: New => Fix Released

** Changed in: hamster-applet (Ubuntu)
   Status: New => Fix Released

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

** Changed in: sugar-presence-service (Ubuntu)
   Status: New => Fix Released

** Changed in: sugar-toolkit (Ubuntu)
   Status: New => Fix Released

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

** Changed in: gnome-python-desktop (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: hamster-applet (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: memaker (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: sugar-presence-service (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds

Doesn't sound like a release blocker offhand, but sheesh.  Boot loops
are no fun.

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

Title:
  gnome-shell crashes after a few seconds

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 10:06:55 2018
  DisplayManager:
   
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-01-04 (111 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds

Ah, that assert is in mutter.

$ mkdir ~/xsrc
$ cd ~/xsrc
$ apt-get source libmutter-2-0
$ cd ~
$ apport-retrace -g _usr_bin_gnome-shell.1000.crash
(gdb) bt
...
(gdb) frame 7
#7  0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303
303 x11/iconcache.c: No such file or directory.
(gdb) directory xsrc/mutter-3.28.1/src
(gdb) list 291
291 static int
292 standard_pict_format_for_depth (int depth)
293 {
294   switch (depth)
295 {
296 case 1:
297   return PictStandardA1;
298 case 24:
299   return PictStandardRGB24;
300 case 32:
301   return PictStandardARGB32;
302 default:
303   g_assert_not_reached ();
304 }

FWIW, that code was added in
https://gitlab.gnome.org/GNOME/mutter/commit/9b903e93e3cd0601b436c55b7cea1fbecf29895f

So... uh... maybe some icon on my system is making it unhappy?

I gather gtk-update-icon-cache is involved?

buildbot@rbb-ubu1804-3:~$ ls -l /usr/share/icons/*/*.cache
-rw-r--r-- 1 root root  35776 Apr 24 14:57 
/usr/share/icons/Adwaita/icon-theme.cache
-rw-r--r-- 1 root root  20312 Apr 25 09:40 
/usr/share/icons/hicolor/icon-theme.cache
-rw-r--r-- 1 root root  49808 Apr 24 14:39 
/usr/share/icons/HighContrast/icon-theme.cache
-rw-r--r-- 1 root root  26816 Apr 24 14:57 
/usr/share/icons/Humanity-Dark/icon-theme.cache
-rw-r--r-- 1 root root 327184 Apr 24 14:57 
/usr/share/icons/Humanity/icon-theme.cache
-rw-r--r-- 1 root root628 Apr 24 14:57 
/usr/share/icons/LoginIcons/icon-theme.cache
-rw-r--r-- 1 root root  54104 Apr 24 14:57 
/usr/share/icons/ubuntu-mono-dark/icon-theme.cache
-rw-r--r-- 1 root root  55040 Apr 24 14:57 
/usr/share/icons/ubuntu-mono-light/icon-theme.cache

But now I can't get it to crash anymore.
so maybe I accidentally fixed it by installing some package that updated the 
icon caches...?

$ grep hicolor /var/log/dpkg.log
...
2018-04-24 14:42:29 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-24 15:33:00 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-25 09:40:43 status installed hicolor-icon-theme:all 0.17-2

Hrmf.  My uneducated theory is that an icon cache was corrupt, but is fine now.
Who knows?

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

Title:
  gnome-shell crashes after a few seconds

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
  Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning 
too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: 
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 6
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
  Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-b

[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds

apport-retrace -g _usr_bin_gnome-shell.1000.crash

bt

indicates it's an assert in standard_pict_format_for_depth:

(gdb) bt
#0  0x7f75c68f0727 in raise (sig=) at 
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x56149221ba6b in dump_gjs_stack_on_signal_handler (signo=6) at 
../src/main.c:367
#2  0x7f75c68f0890 in  () at 
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x7f75c652be97 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:51
#4  0x7f75c652d801 in __GI_abort () at abort.c:79
#5  0x7f75c868dfa5 in g_assertion_message () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f75c868e00a in g_assertion_message_expr () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303
#8  0x7f75c6bb5fbe in pict_format_for_depth (depth=, 
xdisplay=0x56149472f000) at x11/iconcache.c:310
#9  0x7f75c6bb5fbe in surface_from_pixmap 
(xdisplay=xdisplay@entry=0x56149472f000, xpixmap=xpixmap@entry=31457330, 
height=, width=)
at x11/iconcache.c:325
#10 0x7f75c6bb6117 in try_pixmap_and_mask (display=0x5614949c0200, 
src_pixmap=src_pixmap@entry=31457330, src_mask=src_mask@entry=31457332, 
iconp=iconp@entry=0x7fff9d183198) at x11/iconcache.c:345
#11 0x7f75c6bb65a4 in meta_read_icons (screen=0x56149454bcd0, 
xwindow=31457316, icon_cache=0x561495d18df8, wm_hints_pixmap=31457330, 
wm_hints_mask=31457332, iconp=iconp@entry=0x7fff9d183198, ideal_width=96, 
ideal_height=96, mini_iconp=0x7fff9d1831a0, ideal_mini_width=16, 
ideal_mini_height=16) at x11/iconcache.c:546
#12 0x7f75c6bbd3c1 in meta_window_x11_update_icon (window=0x561495d18e30, 
icon=0x7fff9d183198, mini_icon=0x7fff9d1831a0) at x11/window-x11.c:1472
#13 0x7f75c6ba2608 in meta_window_update_icon_now 
(window=window@entry=0x561495d18e30, force=force@entry=1) at core/window.c:5326
#14 0x7f75c6ba9abd in _meta_window_shared_new 
(display=display@entry=0x5614949c0200, screen=screen@entry=0x56149454bcd0, 
client_type=client_type@entry=META_WINDOW_CLIENT_TYPE_X11, 
surface=surface@entry=0x0, xwindow=xwindow@entry=31457316, 
existing_wm_state=existing_wm_state@entry=0, effect=, 
attrs=)
at core/window.c:1148
#15 0x7f75c6bbf6a0 in meta_window_x11_new 
(display=display@entry=0x5614949c0200, xwindow=31457316, 
must_be_viewable=must_be_viewable@entry=0, 
effect=effect@entry=META_COMP_EFFECT_CREATE) at x11/window-x11.c:3148
#16 0x7f75c6bb4554 in handle_other_xevent 
(display=display@entry=0x5614949c0200, event=event@entry=0x7fff9d183640) at 
x11/events.c:1372
#17 0x7f75c6bb4deb in meta_display_handle_xevent (event=0x7fff9d183640, 
display=0x5614949c0200) at x11/events.c:1791
#18 0x7f75c6bb4deb in xevent_filter (xevent=0x7fff9d183640, 
event=, data=0x5614949c0200) at x11/events.c:1830
#19 0x7f75c5e07edf in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#20 0x7f75c5e081c9 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#21 0x7f75c5dd2d70 in gdk_display_get_event () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#22 0x7f75c5e07f72 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#23 0x7f75c8667287 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f75c86674c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f75c86677d2 in g_main_loop_run () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f75c6b94a7c in meta_run () at core/main.c:664

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

Title:
  gnome-shell crashes after a few seconds

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3

[Desktop-packages] [Bug 1173648] Re: F3 side pane is gone in Nautilus 3.6+

2018-04-25 Thread Norbert

The solution is simply drop and ignore GNOME and install MATE DE with
`sudo apt-get install ubuntu-mate-desktop`.

** Tags added: bionic

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

Title:
  F3 side pane is gone in Nautilus 3.6+

Status in Nautilus:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  the double pane functionality that exists in older Nautilus versions is gone 
in the 3.6 version.
  that is a huge usability issue.

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

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

[Desktop-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

2018-04-25 Thread Egmont Koblinger

18.04 Bionic, to be released tomorrow, ships bash-4.4.19. So if Kieran's
guess is correct then it should no longer crash there; Simon could you
please check this once you upgrade your system?

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Desktop-packages] [Bug 1766974] [NEW] /dev/dri/card0

Public bug reported:

There are very many bugs reported recently against xorg with a commmon
theme

the following are just 2 examples from the various xorg logs

(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
(EE) intel(0): [drm] failed to set drm interface version: Permission denied 
[13].

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


** Tags: boot duplicates graphical urgent

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

Title:
  /dev/dri/card0

Status in xorg package in Ubuntu:
  New

Bug description:
  There are very many bugs reported recently against xorg with a commmon
  theme

  the following are just 2 examples from the various xorg logs

  (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission 
denied
  (EE) intel(0): [drm] failed to set drm interface version: Permission denied 
[13].

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

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

[Desktop-packages] [Bug 1766968] [NEW] loss of launcher and desktop graphic

2018-04-25 Thread Willis Taylor

Public bug reported:

Logged out to change from gnome to unity and lost services and all
ability to change Desktop to include Graphic,

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Apr 25 15:03:56 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
 NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
InstallationDate: Installed on 2017-01-21 (459 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 4180W4B
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=debe0dd6-6497-46f9-afe1-933bd5f7cbaf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET67WW (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4180W4B
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4180W4B:pvrThinkPadT420:rvnLENOVO:rn4180W4B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4180W4B
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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: Wed Apr 25 14:45:00 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 738 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  loss of launcher and desktop graphic

Status in xorg package in Ubuntu:
  New

Bug description:
  Logged out to change from gnome to unity and lost services and all
  ability to change Desktop to include Graphic,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 25 15:03:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
  InstallationDate: Installed on 2017-01-21 (459

[Desktop-packages] [Bug 1766638] Re: graphical

similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087

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

Title:
  graphical

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  problem during boot process

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 24 17:14:29 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics Controller 
[1043:817a]
  InstallationDate: Installed on 2016-06-15 (677 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTek Computer INC. P5GZ-MX
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=083e9287-55a1-422d-86ba-6839368c9db8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5GZ-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd11/30/2006:svnASUSTekComputerINC.:pnP5GZ-MX:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GZ-MX:rvrRev1.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.name: P5GZ-MX
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTek Computer INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Tue Apr 24 17:10:36 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, 
id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1825 
   vendor FUS
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1766638] Re: graphical

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

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

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

Title:
  graphical

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  problem during boot process

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 24 17:14:29 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics Controller 
[1043:817a]
  InstallationDate: Installed on 2016-06-15 (677 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTek Computer INC. P5GZ-MX
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=083e9287-55a1-422d-86ba-6839368c9db8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5GZ-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd11/30/2006:svnASUSTekComputerINC.:pnP5GZ-MX:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GZ-MX:rvrRev1.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.name: P5GZ-MX
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTek Computer INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Tue Apr 24 17:10:36 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, 
id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1825 
   vendor FUS
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1766886] Re: xorg

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

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

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On boot up I get a message alot are getting ,, Graphics need
  reconfigured booting in Low Graphics Mode, After log in I get a
  message about a system error referencing the file usr/lib/xorg/xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started Show Plymouth Boot Screen.
Starting Hold until boot process finishes up...
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr 25 10:04:36 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-116-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-119-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-121-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
  InstallationDate: Installed on 2014-05-05 (1450 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 1545
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=cafde4bc-89e6-47f2-a023-feb7fdcf8f08 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/09/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Wed Apr 25 10:00:20 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1766886] Re: xorg

poss duplicate of
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On boot up I get a message alot are getting ,, Graphics need
  reconfigured booting in Low Graphics Mode, After log in I get a
  message about a system error referencing the file usr/lib/xorg/xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started Show Plymouth Boot Screen.
Starting Hold until boot process finishes up...
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr 25 10:04:36 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-116-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-119-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-121-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
  InstallationDate: Installed on 2014-05-05 (1450 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 1545
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=cafde4bc-89e6-47f2-a023-feb7fdcf8f08 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/09/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Wed Apr 25 10:00:20 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

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

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

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

Title:
  Wifi interface does often not show up after reboot

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

2018-04-25 Thread Kieran Grant

Possibly what I encountered and reported to BASH (with my other email address)
Apply this patch https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-019
Or try building from git, bash 4.4.19.
I'll quote report description:
"With certain values for PS1, especially those that wrap onto three or more
lines, readline will miscalculate the number of invisible characters,
leading to crashes and core dumps."

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2018-04-25 Thread Jeremy Bicha

I have updated the bug description with steps to enable the experimental
feature. This feature is not fully complete in GNOME yet and will not be
enabled by default or supported in Ubuntu 18.04 LTS. Apologies for the
inconvenience.

** Description changed:

  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)
  
  ---
  
  I'm using fully updated Ubuntu GNOME 17.04.
  
  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor
  like mine, restricting it to integers is a problem. 1x is annoyingly
  small, and 2x is WAY too big. You need a 1.5x, and presumably to just
  allow most noninteger values to future proof the distribution given 8k
  monitors and all sorts of new and weird things coming out, like windows
  10 has.
  
  Photos of the two annoying sizes are available here (it won't let me
  attach two files):
  
  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg
  
  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you need
  any more information etc.
+ 
+ Workaround
+ ==
+ You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.
+ 
+ gsettings set org.gnome.mutter experimental-features "['scale-monitor-
+ framebuffer']"
+ 
+ If you change your mind and want to get back to supported status, run:
+ 
+ gsettings reset org.gnome.mutter experimental-features

** Description changed:

  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)
  
  ---
  
  I'm using fully updated Ubuntu GNOME 17.04.
  
  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor
  like mine, restricting it to integers is a problem. 1x is annoyingly
  small, and 2x is WAY too big. You need a 1.5x, and presumably to just
  allow most noninteger values to future proof the distribution given 8k
  monitors and all sorts of new and weird things coming out, like windows
  10 has.
  
  Photos of the two annoying sizes are available here (it won't let me
  attach two files):
  
  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg
  
  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you need
  any more information etc.
  
  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.
  
  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"
  
+ After restarting your computer, you should find additional scale options
+ in Settings > Devices > Displays.
+ 
  If you change your mind and want to get back to supported status, run:
  
  gsettings reset org.gnome.mutter experimental-features

** Changed in: ubuntu-gnome
   Importance: Medium => Wishlist

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

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  In Progress
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by e

[Desktop-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

when your wifi fails rather than reboot you might find issuing this
command in a terminal useful

sudo service network-manager restart

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

Title:
  Wifi interface does often not show up after reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2018-04-25 Thread Lonnie Lee Best

This is my number one complaint for 18.04 and GNOME3. I'll be using
16.04.4 until 2021, or until it can compete with the perfection that is
the Unity desktop (which supports fractal scaling).

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  In Progress
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

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

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

[Desktop-packages] [Bug 1766934] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-25 Thread dino99

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Installing WineHQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Thu Apr 26 04:58:45 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UPEya4/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-24 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1766934/+subscriptions

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

[Desktop-packages] [Bug 1766951] Re: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrade:

2018-04-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified:
  usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  failed to install/upgrade: trying to overwrite shared '/usr/share/doc
  /libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is
  different from other instances of package libgstreamer-plugins-
  base0.10-0:i386

Status in gst-plugins-base0.10 package in Ubuntu:
  New

Bug description:
  I was trying to update Ubuntu and it wouldnt stop crashing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 14:45:00 2018
  DuplicateSignature:
   package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
   Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  InstallationDate: Installed on 2018-04-12 (13 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gst-plugins-base0.10
  Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/1766951/+subscriptions

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

[Desktop-packages] [Bug 1766951] [NEW] package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrad

2018-04-25 Thread Samuel Guay

Public bug reported:

I was trying to update Ubuntu and it wouldnt stop crashing.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 14:45:00 2018
DuplicateSignature:
 package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
 Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
InstallationDate: Installed on 2018-04-12 (13 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: gst-plugins-base0.10
Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base0.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified:
  usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  failed to install/upgrade: trying to overwrite shared '/usr/share/doc
  /libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is
  different from other instances of package libgstreamer-plugins-
  base0.10-0:i386

Status in gst-plugins-base0.10 package in Ubuntu:
  New

Bug description:
  I was trying to update Ubuntu and it wouldnt stop crashing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 14:45:00 2018
  DuplicateSignature:
   package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
   Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  InstallationDate: Installed on 2018-04-12 (13 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gst-plugins-base0.10
  Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/1766951/+subscriptions

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

[Desktop-packages] [Bug 1764445] Re: the system is running in low-graphics mode

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

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

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

Title:
  the system is running in low-graphics mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu probably not recognizing installed Intel graphics driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  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
  CurrentDesktop: Unity
  Date: Mon Apr 16 17:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-06-01 (684 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX2 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd09/02/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 16 16:59:16 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

Needs cross-referencing to this bug
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766307

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

Title:
  Wrongly boots into low graphics mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  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
  xserver.bootTime: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1762588] Re: thunderbird 52.6.0/18.04 beta compact folder broken

2018-04-25 Thread Nataraj

I noticed that Thunderbird was upgraded to 52.7 in the 18.04 release,
but for some reason the problem still exists (compact folder missing
from the folder menu) and still works consistantly for me under Ubuntu
14.04.  I'm not sure why.  I'm planning to upgrade my IMAP server and
hoping that will resolve the issue.

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

Title:
   thunderbird 52.6.0/18.04 beta compact folder broken

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Under Thunderbird 52.6.0/Ubuntu 18.04 latest beta, when I connect to
  an IMAP server running Dovecot dovecot-1.0.7-9.el5_11.4 the compact
  command is missing from the individual folder menus. Works fine when I
  connect to Gmail's IMAP server.

  Thunderbird 52.7.0 under Ubuntu 14.04 does not have this issue. I
  notice that the version of Thunderbird under 18.04 is actually older
  than the version under 14.04.

  I sugguest an update to a more recent and stable release of
  Thunderbird before the final release date.

  Thank You,
  Nataraj

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

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

[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

2018-04-25 Thread Gunnar Hjalmarsson

I took the following steps:

* Installed Ubuntu 17.10.1
* Added an extra keyboard layout
* Updated the packages
* Rebooted

No additional layout switch shortcut so far.

Then I run "update-manager -d", and when it was installing the new and
upgraded packages, a window for keybord configuration popped up and I
was prompted to select method for switching between "setting for
national and latin" (see attached image). Alt+Shift was pre-selected. I
found no way to skip that setting, and clicked the "Forward" button.
Result:

$ cat /etc/default/keyboard
XKBLAYOUT="se,us"
XKBVARIANT=","
BACKSPACE="guess"
XKBMODEL="pc105"
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"

So there it is. And at first login those XKBOPTIONS values were imported
by dconf (as expected).

I still can't tell which package is the culprit. Changed to ubuntu-
release-upgrader for now, since it's probably closer to the truth than
gnome-shell.

In any case the upgrade behavior in this respect needs to be
reconsidered, at least for desktop upgrades. No program should make
assumptions and gratuitously set XKBOPTIONS in /etc/default/keyboard,
especially since g-c-c does not offer a way to modify it later. (Is
there a reason for the upgrader to mess with keyboard configuration at
all?)

** Attachment added: "keyboard-config-prompt.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762952/+attachment/5127164/+files/keyboard-config-prompt.png

** Package changed: gnome-shell (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => High

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

Title:
Alternative shortcut for layout switching Alt+Shift unexpectedly set
by default

Status in gnome-control-center package in Ubuntu:
New
Status in ubuntu-release-upgrader package in Ubuntu:
Confirmed

Bug description:
Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
18.04

Steps to reproduce:
1. Define two keyboard input methods in Settings -> Region & Language ->
Input Sources
2. Open several applications
3. Observe that application windows can be iterated with Alt + Tab
4. Once application window iteration was begun with Alt + Tab, try to iterate
backwards with Alt + Shift + Tab.
5. Try to change keyboard input method switching hotkeys in Settings ->
Region & Language -> Input Sources -> Options.
6. Observe that Keyboard shortcut for "Alternative switch to next source" is
set to "Alt + Shift" and that keyboard shortcuts can only be changed in
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
7. Observe that the shortcut for "Alternative switch to next source" is not
available for configuration in Settings -> Devices -> Keyboard -> Keyboard
Shortcuts.

Actual state:
* Performing step 4 does not select the previous app in application switcher
but instead changes keyboard input method.

Expected state:
* The shortcut for "Alternative switch to next source" can be changed and /
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

Notes:
* The above was working fine in Ubuntu 17.10. I assume "Alternative switch to
next source" did not exist in that version of Gnome Shell.

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

[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

2018-04-25 Thread Chris Perry

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

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

Title:
  Wrongly boots into low graphics mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  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
  xserver.bootTime: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1766938] [NEW] gnome-shell crashes after a few seconds

Public bug reported:

I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a
Hades Canyon, and a few other odds and ends, running a mix of ubuntu
16.04 and 17.10.

On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card),
I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop would
come up for about ten seconds, then the system would shut down.

Did 
  systemctl set-default multi-user.target
then removed all traces of the proprietary driver with
  sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
the system was stable running firefox, so it's not an obvious graphics problem.

/var/log/syslog says

Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for 
context 0x556d30f3c4c0 ==
Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated 
service 'org.freedesktop.fwupd'
Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure 
in required component org.gnome.Shell.desktop
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, 
but the fail whale is dead. Sorry

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 10:06:55 2018
DisplayManager:
 
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-01-04 (111 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gnome-shell crashes after a few seconds

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
  a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
  16.04 and 17.10.

  On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 
card),
  I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop 
would
  come up for about ten seconds, then the system would shut down.

  Did 
systemctl set-default multi-user.target
  then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
  and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

  Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
  the system was stable running firefox, so it's not an obvious graphics 
problem.

  /var/log/syslog says

  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
  Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace 
for context 0x556d30f3c4c0 ==
  Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully 
activated service 'org.freedesktop.fwupd'
  Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware upda

[Desktop-packages] [Bug 1766940] [NEW] Wifi interface does often not show up after reboot

2018-04-25 Thread Julian Bieringer-Hinterbuchinger

Public bug reported:

Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that the
wifi interface showed up. Once it showed up it worked continuously for
hours without an issue. When the update came to kernel
4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
until my wifi interface shows up. Once it shows up it works continuously
like on the previous kernel for the whole session but on next reboot the
interface is missing again. It seems random whether the interface is
loaded (or found) when booting. Don't know if this is an kernel issue
but since it got lot worse right after the latest kernel update i assume
so. Wired connections are working well without any issues.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 25 19:16:23 2018
InstallationDate: Installed on 2018-04-16 (9 days ago)
InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu 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/1766940

Title:
  Wifi interface does often not show up after reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766934] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Installing WineHQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Thu Apr 26 04:58:45 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UPEya4/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-24 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1766934/+subscriptions

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

[Desktop-packages] [Bug 1766934] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-04-25 Thread Linh Nguyen

Public bug reported:

Installing WineHQ

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Thu Apr 26 04:58:45 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-UPEya4/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-04-24 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

** Attachment added: "Screenshot from 2018-04-26 05-06-48.png"
   
https://bugs.launchpad.net/bugs/1766934/+attachment/5127138/+files/Screenshot%20from%202018-04-26%2005-06-48.png

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Installing WineHQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Thu Apr 26 04:58:45 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UPEya4/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-24 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1766934/+subscriptions

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

2018-04-25 Thread netslovdlyasnov

It started to work with 390.48-0ubuntu3

Working xorg.conf:


Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection

Section "Device"
Identifier "intel"
Driver "modesetting"
BusID "PCI:0@0:2:0"
Option "AccelMethod" "None"
EndSection

Section "Screen"
Identifier "intel"
Device "intel"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:1@0:0:0"
Option "ConstrainCursor" "off"
EndSection

Section "Screen"
Identifier "nvidia"
Device "nvidia"
Monitor "Monitor0"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
Option "DPMS" "on"
EndSection

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

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 1766890] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

Public bug reported:

Dell XPS 13 9360 (CID 201606-22338)
pre-installed image Xenial

[Description]

When I tried to perform 16.04 --> 18.04 update, the update process
failed. The process guide me to file this bug report.

[Steps to reproduce]
1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get 
dist-upgrade -y"
2. Reboot
3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d"
5. During the update process, it prompts for "Configuring gdm3". There are two 
choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

We should use "-d" because bionic beaver has not been officially
released yet.

[Expected Result]

The release update completed and I could start using Bionic instead of
Xenial.

[Actual Result]

The update process failed. It shows the error message[1] and
automatically asking for filing this bug report.

[1]

Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
(Reading database ... 253705 files and directories currently installed.)
Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  bamfdaemon -> gnome-menus
 packages' pending triggers which are or may be unresolvable:
  gnome-menus: /usr/share/applications
  bamfdaemon: /usr/share/applications
  libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
  desktop-file-utils: /usr/share/applications
  mime-support: /usr/share/applications
dpkg: error processing package gnome-menus (--remove):
 triggers looping, abandoned
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
Errors were encountered while processing:
 gnome-menus
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error 
code (1)

*** 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 (376.4 KB)
  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):

.. (a lot of them)

 qml-module-qtquick-controls2:amd64
 qml-module-org-kde-kconfig:amd64
 libunity-control-center1
 libqt5quickcontrols2-5:amd64
 libglib2.0-bin
 libkf5plasma5:amd64
 locales
 qml-module-qtqml-models2:amd64
 libkf5coreaddons5:amd64
 gir1.2-goa-1.0:amd64
 libwebkit2gtk-4.0-37:amd64
Processing was halted because there were too many errors.

Upgrade complete

The upgrade has completed but there were errors during the upgrade
process.

To continue please press [ENTER]

ubuntu@201606-22338:~$

==

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 22:00:01 2018
Dependencies:

DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-04-25 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-04-25 (0 days ago)

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


** Tags: 201606-22338 amd64 apport-package bionic taipei-lab

** Description changed:

  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial
  
  [Description]
  
  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.
  
- 
  [Step

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** 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 (376.4 KB)
    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):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-menus
  Tit

Re: [Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

2018-04-25 Thread Per-Inge

Yes every time. I changed method and used Power/Automatic suspend instead,
which actually is more convenient.

2018-04-24 23:12 GMT+02:00 Marco Trevisan (Treviño) :

> Great to hear, were you getting this regularly?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1760485).
> https://bugs.launchpad.net/bugs/1724439
>
> Title:
>   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
>   ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
>   function_call()
>
> Status in Mutter:
>   In Progress
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Bionic:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Released
>
> Bug description:
>   https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f
> 429e44c854
>
>   ---
>
>   left virtual box to update win10 came back and got error message
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-shell 3.26.1-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 17 23:37:32 2017
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2017-04-18 (182 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SegvAnalysis:
>Segfault happened at: 0x7feb2ed42d94 :
> mov0x18(%rax),%eax
>PC (0x7feb2ed42d94) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%eax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/
> libmutter-1.so.0
>ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>?? () from /usr/lib/libgjs.so.0
>?? () from /usr/lib/libgjs.so.0
>   Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
>   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/mutter/+bug/1724439/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in Mutter:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-04-25 Thread Jean-Baptiste Lallement

Thanks for your report.

Could you please attach a tarball of the directory /var/log/dist-upgrade
to this bug report?

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

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** 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 (376.4 KB)
    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):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu

[Desktop-packages] [Bug 1232928] Re: The wifi regulatory domain is ignored

2018-04-25 Thread Ken Sharp

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=720331
   Importance: Unknown
   Status: Unknown

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

Title:
  The wifi regulatory domain is ignored

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have edited the /etc/defaults/crda file to configure my system
  regulatory domain to AU.

  When network-manager attaches to the wireless network, this value is not 
sourced. The regulatory domain switches back to US.
  This repeats back and forth, from AU to World to US.

  System detail is:
  root@mythtv:/etc/sysctl.d# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="13.04, Raring Ringtail"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 13.04"
  VERSION_ID="13.04"
  ...

  Here is the output from dmesg when this occurs.

  [   15.579701] cfg80211: Calling CRDA for country: AU
  [   15.583170] cfg80211: Regulatory domain changed to country: AU
  [   15.583173] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   15.583174] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [   15.583175] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583176] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583177] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [   22.265820] wlan0: authenticate with 94:44:52:a7:ed:d3
  [   22.313771] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [   22.315735] wlan0: authenticated
  [   22.319045] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [   22.320563] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [   22.323544] wlan0: associated
  [   22.323571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   22.323611] cfg80211: Calling CRDA for country: US
  [   22.325924] cfg80211: Regulatory domain changed to country: US
  [   22.325927] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   22.325928] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2700 mBm)
  [   22.325930] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
1700 mBm)
  [   22.325931] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325932] cfg80211:   (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325933] cfg80211:   (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325934] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [  216.856143] wlan0: deauthenticating from 94:44:52:a7:ed:d3 by local choice 
(reason=3)
  [  216.884265] cfg80211: Calling CRDA to update world regulatory domain
  [  216.890344] cfg80211: World regulatory domain updated:
  [  216.890350] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.890355] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890359] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890362] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890365] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890368] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890390] cfg80211: Calling CRDA for country: AU
  [  216.895900] cfg80211: Regulatory domain changed to country: AU
  [  216.895904] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.895907] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [  216.895910] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895913] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895915] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  [  217.982078] wlan0: authenticate with 94:44:52:a7:ed:d3
  [  218.005788] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [  218.006865] wlan0: authenticated
  [  218.010870] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [  218.012486] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [  218.015591] wlan0: associated
  [  218.015626] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  218.015680] cfg80211: Calling CRDA for country: US
  [  218.022206] cfg80211: Regulatory domain changed to country: US
  [  218.022210] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  218.022213] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2700 mBm)
  [  218.022216] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
1700 mBm)
  [  218.022218]

[Desktop-packages] [Bug 1766747] Re: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

2018-04-25 Thread Dimitri John Ledkov

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

Can you please attach the tarball of /var/log/installer?

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

Title:
  package apt-config-icons (not installed) failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 127

Status in appstream package in Ubuntu:
  New

Bug description:
  doesnt work

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apt-config-icons (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 24 20:50:23 2018
  DuplicateSignature:
   package:apt-config-icons:(not installed)
   Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ...
   dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack):
dpkg-deb --control subprocess returned error exit status 127
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6~beta1
  SourcePackage: appstream
  Title: package apt-config-icons (not installed) failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned