date:20170925

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

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

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

Title:
  I cant turn the volume.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I checked all of the listed commands on the official ubuntu site but
  nothing works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Jul 22 20:38:46 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

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

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

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

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-09-25 Thread Kai-Heng Feng

Okay, you also need to add more data to
/usr/share/usb_modeswitch/configPack.tar.gz.

$ cat 148f\:2878 
# RaLink MT7601U
TargetVendor=0x148f
TargetProduct=0x7601
StandardEject=1

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end

[Desktop-packages] [Bug 1719495] Re: Gnome/Ubuntu Software does not have Gnome Extension/Add-ons section

2017-09-25 Thread Jeremy Bicha

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

** This bug has been marked a duplicate of bug 1713285
   17.10: Missing Add-ons category

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

Title:
  Gnome/Ubuntu Software does not have Gnome Extension/Add-ons section

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Initially there used to be a section where users can browser and
  install Gnome Extensions via Gnome/Ubuntu Software. While these can
  still be searched and installed, they are not able to be browser as
  that section is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 21:04:52 2017
  InstallationDate: Installed on 2017-09-19 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-09-25 Thread MicWit

Done https://bugs.launchpad.net/ubuntu/+bug/1719500

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

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

2017-09-25 Thread Clerc Mathias

I have the same problem on ubuntu 17.10 with gnome shell 3.26.0

Bug usually occurs while tabbing between active windows. The effect is
the screen freezing for some time and when it comes back gnome-shell
restarting (looks same as restarting it with "ALT+F2, r").

I do not have actual reproduction steps as it does not seem to occur
consistently on my machine, just about once per week.

I have ibus-mozc installed and after each crash it stops reacting to hot keys.
Manually changing input method from the toolbar brings it back to life making 
hotkeys work again.

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Crashed while watching a video

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  7 01:14:13 2011
  ExecutablePath: /usr/bin/gnome-shell
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0ee77f856c :
movzbl 0x16(%r8),%eax
   PC (0x7f0ee77f856c) ok
   source "0x16(%r8)" (0x1af5de016) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to oneiric on 2011-09-19 (17 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 429841] ☯wow! list of events

2017-09-25 Thread Ab3L

Yo!

This is actually  the list of approaching events  you may be interested
in, you might find more info here
http://www.agroblahnita.ro/sites/default/files/ctools/minimal.php?UE80Mjk4NDFAYnVncy5sYXVuY2hwYWQubmV0

Yours faithfully, Kenshin Himura

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

Title:
  broken packaging: package flashplugin-nonfree failed to
  install/upgrade: (breaks upgrade)

Status in flashplugin-nonfree package in Ubuntu:
  Fix Released
Status in flashplugin-nonfree source package in Lucid:
  Fix Released
Status in flashplugin-nonfree source package in Karmic:
  Won't Fix

Bug description:
  TEST CASE for 8.04 -> 10.04 SRU:
  1. use hardy
  2. install flashplugin-nonfree
  3. run "update-manager --proposed" to upgrade to lucid
  4. verify that it fails in flashplugin-nonfree

  5. use fresh hardy ubuntu desktop but enable hardy-proposed this time
  6. repeat 2,3
  7. verify that it works now

  Its not really needed to reproduce the failure (step 2,3,4) because of the 
amount of duplicates. I consider
  this verification a success if 5,6,7 works ok.

  TEST CASE 2: Removal of flashplugin-nonfree
  $ apt-get install flashplugin-nonfree
  $ apt-get remove flashplugin-nonfree

  VERIFICATION DONE:
  - Package is removed cleanly

  
  Binary package hint: flashplugin-nonfree

  Upgrading 9.04 -> latest karmic.

  ProblemType: Package
  Architecture: i386
  Date: Tue Sep 15 06:45:05 2009
  DistroRelease: Ubuntu 9.10
  ErrorMessage:
   ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
  Package: flashplugin-nonfree 10.0.22.87ubuntu1
  ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-nonfree 10.0.22.87ubuntu1 failed to 
install/upgrade:
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/429841/+subscriptions

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

[Desktop-packages] [Bug 780717] Re: Using PKCS#12 file requires password for private key

2017-09-25 Thread Hugo Lía

The solution sugested by connstance does not resolve the problem. In my
case I am trying to access my customer VPN and I cannot password protect
the certificate. In pfSense this is a global option, and if they change
this they need to change all users vpn.

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

Title:
  Using PKCS#12 file requires password for private key

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager-openvpn

  network-manager-openvpn allows to specify PKCS#12 files instead of sep. files 
for CA, cert and key. That's wonderful.
  There's one problem though: When specifying a *.p12 file, one HAS to enter a 
"Private key password" even if the PKCS#12 is not password protected at all.
  When specifying sep. files for CA, cert and key, entering the "Private key 
password" is optional. Not when using the PKCS#12 file.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: network-manager-openvpn-gnome 
0.8.1+git.20100810t173015.1711d04-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  Architecture: amd64
  Date: Tue May 10 21:48:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719495] [NEW] Gnome/Ubuntu Software does not have Gnome Extension/Add-ons section

2017-09-25 Thread motang

Public bug reported:

Initially there used to be a section where users can browser and install
Gnome Extensions via Gnome/Ubuntu Software. While these can still be
searched and installed, they are not able to be browser as that section
is missing.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 21:04:52 2017
InstallationDate: Installed on 2017-09-19 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.0-0ubuntu2
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gnome/Ubuntu Software does not have Gnome Extension/Add-ons section

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Initially there used to be a section where users can browser and
  install Gnome Extensions via Gnome/Ubuntu Software. While these can
  still be searched and installed, they are not able to be browser as
  that section is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 21:04:52 2017
  InstallationDate: Installed on 2017-09-19 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714783] Re: [amdgpu] screen scrambling upon startup

2017-09-25 Thread Charlie Luna

I'm trying to update all of my bug reports per your request to do so.
It's just taking some time to get to it. So far, this particular
instance hasn't occurred again.

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

Title:
  [amdgpu] screen scrambling upon startup

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

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handl

2017-09-25 Thread bikram tuladhar

Thanks!

On Sep 26, 2017 12:17 AM, "Launchpad Bug Tracker" <
1672...@bugs.launchpad.net> wrote:

> This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4
>
> ---
> pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium
>
>   * debian/control: Update Vcs fields to launchpad git.
>   * Cherrypick fixes for common crashes from upstream:
> - cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP:
> #1690028,
>   LP: #1672171)
> - d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP:
> #1562817)
>
>  -- Daniel van Vugt   Fri, 11 Aug 2017
> 15:16:57 +0800
>
> ** Changed in: pulseaudio (Ubuntu Xenial)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672171
>
> Title:
>   pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
>   from pa_bluetooth_transport_set_state() from profile_new_connection()
>   from profile_handler() from _dbus_object_tree_dispatch_and_unlock()
>
> Status in PulseAudio:
>   Fix Released
> Status in pulseaudio package in Ubuntu:
>   Fix Released
> Status in pulseaudio source package in Xenial:
>   Fix Released
>
> Bug description:
>   [Impact]
>   pulseaudio daemon crashes, interrupting sound output/input.
>
>   [Test Case]
>   Theoretical test case (crash does not happen for all users):
>   1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
>  fidelity A2DP and the lower quality headset profiles).
>   2. Pair it with your machine and select the device in sound settings.
>   3. Turn the Bluetooth audio device off and on again, making sure it is
>  set to active if not automatically so.
>   4. Select the device in sound settings.
>   5. Check that that pulseaudio process is still running, with a start
>  time older than when you began this test case.
>
>   [Regression Potential]
>   Low. This SRU affects the pulseaudio daemon only so the worst case would
>   be loss of sound output/input. The same patches have been released to
>   17.10 for a month already and zero regressions of the crashes have
>   occurred worldwide since then.
>
>   [Other Info]
>   Debdiff patch is attached to the most prolific bug 1539209.
>
>   [Original Description]
>
>   Bluetooth device keep disconnect and audio output tab is empty
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.04
>   Package: pulseaudio 1:10.0-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
>   Uname: Linux 4.10.0-11-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia
>   ApportVersion: 2.20.4-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  bikram14994 F pulseaudio
>/dev/snd/controlC0:  bikram14994 F pulseaudio
>   CrashCounter: 1
>   CurrentDesktop: Unity:Unity7
>   Date: Sun Mar 12 21:52:24 2017
>   ExecutablePath: /usr/bin/pulseaudio
>   ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
>   Signal: 6
>   SourcePackage: pulseaudio
>   StacktraceTop:
>pa_bluetooth_transport_set_state () from /usr/lib/pulse-10.0/modules/
> libbluez5-util.so
>?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
>?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
>   Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_
> state()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   dmi.bios.date: 11/14/2013
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 0Y004V
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A07
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: Not Specified
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:
> pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:
> ct8:cvrNotSpecified:
>   dmi.product.name: Inspiron 3437
>   dmi.product.version: Not Specified
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pulseaudio/+bug/1672171/+subscriptions
>

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  pulseaudio daemon crashes,

[Desktop-packages] [Bug 1719485] [NEW] gnome-control-center user-accounts crashes on unlock

2017-09-25 Thread Jasper

Public bug reported:

gnome-control-center user-accounts crashes on unlock.
gnome-control-center does not crash when unlocking if the password is wrong - 
only when password is accepted.

This is on a fresh install of 17.10 daily
Apport does not detect the crash so I cannot generate a crash report with this.

Running `sudo gnome-control-center` shows a completely different menu
and does not respond to clicks.

Release:17.10

gnome-control-center:
  Installed: 1:3.26.0-0ubuntu2
  Candidate: 1:3.26.0-0ubuntu2
  Version table:
 *** 1:3.26.0-0ubuntu2 500
500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

Expected:
Unlock at `user-accounts` by supplying correct password - then able to enable 
automatic login etc.

What happened:
gnome-control-center closes with no message

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


** Tags: artful

** Tags added: artful

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

Title:
  gnome-control-center user-accounts crashes on unlock

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

Bug description:
  gnome-control-center user-accounts crashes on unlock.
  gnome-control-center does not crash when unlocking if the password is wrong - 
only when password is accepted.

  This is on a fresh install of 17.10 daily
  Apport does not detect the crash so I cannot generate a crash report with 
this.

  Running `sudo gnome-control-center` shows a completely different menu
  and does not respond to clicks.

  Release:17.10

  gnome-control-center:
Installed: 1:3.26.0-0ubuntu2
Candidate: 1:3.26.0-0ubuntu2
Version table:
   *** 1:3.26.0-0ubuntu2 500
  500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected:
  Unlock at `user-accounts` by supplying correct password - then able to enable 
automatic login etc.

  What happened:
  gnome-control-center closes with no message

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

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

[Desktop-packages] [Bug 1719484] [NEW] Untranslated information on "About Chromium" page

2017-09-25 Thread Sam Rosewood

Public bug reported:

There is untranslated information on "About Chromium" page: the text "...built 
on Ubuntu, running on" etc.
It looks allogenic on other languages. Screenshot is attached.

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

** Attachment added: "1.png"
   https://bugs.launchpad.net/bugs/1719484/+attachment/4957044/+files/1.png

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

Title:
  Untranslated information on "About Chromium" page

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  There is untranslated information on "About Chromium" page: the text 
"...built on Ubuntu, running on" etc.
  It looks allogenic on other languages. Screenshot is attached.

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

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

[Desktop-packages] [Bug 1717272] Re: HiDPI settings reset on logout

2017-09-25 Thread Jeremy Bicha

I'm reassigning this to mutter since some or all of this issue if fixed
in the mutter git snapshot I am preparing now.

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

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

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

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

Title:
  HiDPI settings reset on logout

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When logging in to my XPS 13 (9360) on 17.10, the only thing that is
  reasonably (200%) scaled is the sidebar. Top bar, windows, and fonts
  are all unscaled and TINY.

  - I'll go to Control Centre, Devices, Displays, and see that scaling is set 
to 200%.
  - I'll then change the scaling to 100%, and hit apply and confirm. At this 
point, windows are scaled to 200%.
  - I need to change the scaling to 100% AGAIN. Now everything is 100%, and 
therefore tiny
  - I then change the scaling to 200%, hit apply and confirm, which does barely 
anything
  - I then need to set scaling to 200% AGAIN, hit apply and confirm, and only 
*then* everything is properly scaled.

  I need to do this every time I log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 16:33:30 2017
  ExecutablePath: /usr/bin/gnome-control-center
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1532508] Re: Screen shown briefly after opening closed laptop lid, before even unlocking

This bug was fixed in the package unity -
7.5.0+17.10.20170925.1-0ubuntu1

---
unity (7.5.0+17.10.20170925.1-0ubuntu1) artful; urgency=medium

  [ Andrea Azzarone ]
  * Fix build issues with gcc-7 and g++-7
  * Refactor the way UserAuthenticator is created and passed around.
Handle failures to create new threads and fallback to a "Switch to
greeter..." button in case of failure. (LP: #1311316)
  * Wait until the color buffer is cleared before suspending. (LP:
#1532508)

  [ Marco Trevisan (Treviño) ]
  * Tests: split unit tests in single binaries, enable unstable tests
  * debian/rules: ignore warnings in armhf and ppc64el

 -- Marco Trevisan (Treviño)   Mon, 25 Sep 2017 16:05:06
+

** Changed in: unity (Ubuntu)
   Status: In Progress => 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/1532508

Title:
  Screen shown briefly after opening closed laptop lid, before even
  unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

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

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

[Desktop-packages] [Bug 1718223] Re: gnome-shell crashed with signal 5 in g_settings_get_value()

(Un)fortunately, gnome-shell-extension-dashtodock is an ubuntu package
:)

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

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Invalid => New

** Summary changed:

- gnome-shell crashed with signal 5 in g_settings_get_value()
+ gnome-shell crashed with signal 5 in g_settings_get_value() because settings 
schema 'org.gnome.shell.extensions.dash-to-dock' does not contain a key named 
'customize-click'

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

Title:
  gnome-shell crashed with signal 5 in g_settings_get_value() because
  settings schema 'org.gnome.shell.extensions.dash-to-dock' does not
  contain a key named 'customize-click'

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New

Bug description:
  After upgrade 17.04 to 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Tue Sep 19 18:31:40 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['alternate-...@gnome-shell-extensions.gcampax.github.com', 
'clipboard-indica...@tudmotu.com', 'proxyswitc...@flannaghan.com', 
'suspend-button@laserb', 'brightness_cont...@lmedinas.org', 
'pomod...@arun.codito.in', 'system-moni...@paradoxxx.zero.gmail.com', 
'dash-to-d...@micxgx.gmail.com', 'todol...@bsaleil.org']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'telegramdesktop.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop']"
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-09-02 (17 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
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking own the Terminal window buttons

** Summary changed:

- Problema do ícones do menu no terminal na sessão Xorg
+ Giant terminal icon is blocking own the Terminal window buttons

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

** Summary changed:

- Giant terminal icon is blocking own the Terminal window buttons
+ Giant terminal icon is blocking out the Terminal window buttons

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719461] Re: package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package liblouis9:amd64 is not ready for configuration cannot configure (current status 'half-installed'

** Tags removed: need-duplicate-check

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

Title:
  package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package
  liblouis9:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in liblouis package in Ubuntu:
  New

Bug description:
  Tried killing process 9070 using sudo kill command. Then tried sudo
  apt-get install freeglut3 freeglut3-dev to install program.

  I received this message.

  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblouis9:amd64 2.6.4-2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Sep 25 17:36:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   liblouis-data 2.6.4-2ubuntu0.1
  DuplicateSignature:
   package:liblouis9:amd64:2.6.4-2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package liblouis9:amd64 (--configure):
package liblouis9:amd64 is not ready for configuration
  ErrorMessage: package liblouis9:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-03-24 (184 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: liblouis
  Title: package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package 
liblouis9:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719461] [NEW] package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package liblouis9:amd64 is not ready for configuration cannot configure (current status 'half-installe

2017-09-25 Thread Jacob Fountain

Public bug reported:

Tried killing process 9070 using sudo kill command. Then tried sudo apt-
get install freeglut3 freeglut3-dev to install program.

I received this message.

Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblouis9:amd64 2.6.4-2
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Sep 25 17:36:16 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 liblouis-data 2.6.4-2ubuntu0.1
DuplicateSignature:
 package:liblouis9:amd64:2.6.4-2
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package liblouis9:amd64 (--configure):
  package liblouis9:amd64 is not ready for configuration
ErrorMessage: package liblouis9:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-03-24 (184 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: liblouis
Title: package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package 
liblouis9:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package
  liblouis9:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in liblouis package in Ubuntu:
  New

Bug description:
  Tried killing process 9070 using sudo kill command. Then tried sudo
  apt-get install freeglut3 freeglut3-dev to install program.

  I received this message.

  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblouis9:amd64 2.6.4-2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Sep 25 17:36:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   liblouis-data 2.6.4-2ubuntu0.1
  DuplicateSignature:
   package:liblouis9:amd64:2.6.4-2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package liblouis9:amd64 (--configure):
package liblouis9:amd64 is not ready for configuration
  ErrorMessage: package liblouis9:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-03-24 (184 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: liblouis
  Title: package liblouis9:amd64 2.6.4-2 failed to install/upgrade: package 
liblouis9:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719462] [NEW] [Translation] "Left" and "Right" must be translated differently in different contexts

2017-09-25 Thread Doctor Rover

Public bug reported:

In 17.10 artful in GNOME Control Center, there are two places where
words "Left" and "Right" are encountered: the Mouse settings and the
Dock settings. Both of the words have only one item to translate in
Rosetta with indication that they are located in two different places in
the sources:

"Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
"Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
I can guess that this is also valid for some other languages, not only Russian.

Please make two independent translations in Rosetta for "Left" and
"Right" in these two different contexts.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

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


** Tags: artful

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

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

Title:
  [Translation] "Left" and "Right" must be translated differently in
  different contexts

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

Bug description:
  In 17.10 artful in GNOME Control Center, there are two places where
  words "Left" and "Right" are encountered: the Mouse settings and the
  Dock settings. Both of the words have only one item to translate in
  Rosetta with indication that they are located in two different places
  in the sources:

  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

  When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
  I can guess that this is also valid for some other languages, not only 
Russian.

  Please make two independent translations in Rosetta for "Left" and
  "Right" in these two different contexts.

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

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

[Desktop-packages] [Bug 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

Since this is crash however...

---
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. However, your crash report is either missing or challenging to deal 
with as a ".crash" file. Please follow these instructions to have apport report 
a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

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

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

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

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

[Desktop-packages] [Bug 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

If it still works commented out then it sounds like your definition of "when a 
new output becomes available" is covered by the similar:
  load-module module-switch-on-port-available

As for removing module-switch-on-connect, we already plan to do that in
18.04 with the introduction of PulseAudio 11 since it has better
defaults which handle all the device hotplugging cases we care about
(Bluetooth devices and USB DACs).

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

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

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

[Desktop-packages] [Bug 1716068] Re: Gnome Shell crashes randomly

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

Thanks. Looks like a duplicate of bug 1706203.

** This bug has been marked a duplicate of bug 1706203
   gnome-shell crashed with heap corruption in g_strfreev() from 
g_themed_icon_finalize()

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

Title:
  Gnome Shell crashes randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using Ubuntu Gnome 16.04, it is common for gnome-shell to crash
  unexpectedly, especially when performing intensive tasks.

  
  I've found that I was able to replicate the error by following these steps:
  Download and install a copy of Ubuntu Gnome 16.04.2 in VirtualBox.
  Open a screen displaying App icons in a menu, such as the app grid in the 
Gnome Shell overlay or the Arc Menu Gnome Shell extension 
(https://extensions.gnome.org/extension/1228/arc-menu/).
  Install all the latest software updates from the Software Updater or Synaptic.
  Upgrading all the packages between 16.04.2 to 16.04.3 seems to over-load 
Gnome Shell and cause the crash in the middle of the installation process.
  This crash always seems to occur after opening a screen with app icons and 
I'm not sure why.

  
  I've attached my .crash file updated with a symbolic stack trace.I hope this 
info and my attachment proves helpful in fixing the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep  8 19:24:22 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['arc-m...@linxgem33.com']"
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 
'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719458] [NEW] "Add a color profile" window is too small

Public bug reported:

In gnome-control-center the dialog that lists the profiles available
when adding a color profile is too small (1 line height) cf screenshot

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 17:12:23 2017
InstallationDate: Installed on 2013-09-03 (1483 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Capture d’écran de 2017-09-25 17-12-00.png"
   
https://bugs.launchpad.net/bugs/1719458/+attachment/4956985/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202017-09-25%2017-12-00.png

** Tags removed: wayland-session

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

Title:
  "Add a color profile" window is too small

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

Bug description:
  In gnome-control-center the dialog that lists the profiles available
  when adding a color profile is too small (1 line height) cf screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 17:12:23 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

>From duplicate bug #1719300, the chromedriver binary also needs the
rpath.

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1719300] Re: chromedriver doesn't start without setting LD_LIBRARY_PATH

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

** This bug has been marked a duplicate of bug 1718885
   chromium doesn't start in guest session (xubuntu 16.04)

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

Title:
  chromedriver doesn't start without setting LD_LIBRARY_PATH

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser won't start unless I set LD_LIBRARY_PATH=/usr/lib
  /chromium-browser.

  I think this is a recent change that and the problem is libffmpeg.so which is 
installed in /usr/lib/chromium-browser.
  Before, I could also launch chromium with 
/usr/lib/chromium-browser/chromium-browser but now I get the following error 
message:
  /usr/lib/chromium-browser/chromium-browser: error while loading shared 
libraries: libffmpeg.so: cannot open shared object file: No such file or 
directory

  The chromium-browser package installs a chromium-browser script in
  /usr/bin that sets LD_LIBRARY_PATH

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

MicWit, please log a separate bug.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

It appears forwarding was blocked by uncertainty around comments made by
the upstream reporter saying he would not accept it (although I'm not
sure he himself is upstream):

https://bugzilla.gnome.org/show_bug.cgi?id=783169#c7

At the time I ignored that comment because it's not a good enough reason
to reject the approach. The patch we use in comment #12 above is trivial
and perfectly solves this bug. However the upstream comment is about the
same approach not solving other issues that might arise from a user
setting his/her own *_BACKEND environment variables.

I don't think that upstream comment should be considered a blocker.
While valid, it is not pragmatic and the patch we use is perfectly safe
and closes the bug. Upstream really is asking us to solve larger
gstreamer design problems which Ubuntu isn't interested in solving right
now.

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  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: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-25 Thread Fusion

Info:
Ubuntu 17:10 upgraded from 17:04 (64bit)
gnome-shell --version: GNOME Shell 3.26.0
loginctl show-session 3 -p Type: Type=x11
Screen resolution: 3840x2160
VGA: nvidia 1050ti - 384.69
kernel: 4.13.0-11-generic

Status:
1. every update is applied.
2. tested with gnome extensions I've install, 'on' and 'off': result was the 
same
3. Gnome-tweak-tool - my default font size setting: 0,8 (I think that 0,8 - 0,9 
is ok. With value less than 0,8 text is too small and with bigger than 0,9 
..should be under "universal access"=is too big).

Problem:
1. The gnome topbar is too small (both size and text), time and date are barely 
visible.
2. The dash's texts are also too small (names of the apps - under app's icons)
3. The window titlebar's text is tiny, although it's size is fine

Temporary Workaround (old ones - from a dupplicate bug):
1. if restart environment (alt+f2, r + enter) --> this fixes topbar size but 
leave other apps like nautilus untouched (which is fine cause they are working 
fine already)
2. if change font size through gnome-tweak-tool --> this fixes topbar size but 
also changes nautilus font size, which is not good, because nautilus font is 
already ok

Temporary Workaround (NEW - fastest):
1. change font size in any value through gnome-tweak-tool. For me, change from 
0,80 to 0,81 and back to 0,8 solves the problem.

BUT: The workarounds mentioned above are temporary because the setting
is undone after reboot.

Other Issues:
1. with font size on 1.00 (through gnome-tweak-tool) everything is very big.
2. Many Topicons are very small (like viber, telegram, skype, mega) Others 
(variety, deluge) are fine.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1

[Desktop-packages] [Bug 1697450] Re: Gnome Shell hangs at login, while the "zoom" animation is being shown

** Summary changed:

- Installer freezes at session startup
+ Gnome Shell hangs at login, while the "zoom" animation is being shown

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Gnome Shell hangs at login, while the "zoom" animation is being shown

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.

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

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

[Desktop-packages] [Bug 1719128] Re: Automatic login works only for wayland session

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Automatic login works only for wayland session

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, Nvidia binary drivers, X11 session.
  Autologin feature doesn't work for X11, only for Wayland.

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

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

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

patchelf is not available in trusty, so that won't work to set the rpath
on the binary after the build. Will need to patch chromium to set the
rpath at build time.

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1719445] Re: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11

** Tags removed: need-duplicate-check

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

Title:
  package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h
  usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h
  usr/include/X11/Xregion.h usr/include/X11/Xutil.h] failed to
  install/upgrade: trying to overwrite shared '/usr/include/X11/Xcms.h',
  which is different from other instances of package libx11-dev:i386

Status in libx11 package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   libx11-dev: Install
   libx11-dev: Configure
   libx11-dev: Configure
   NULL: ConfigurePending
  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: Mon Sep 25 22:30:49 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-59-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
   broadcom-sta, 6.30.223.271, 4.4.0-59-generic, x86_64: installed
  DpkgHistoryLog:
   Start-Date: 2017-09-25  22:30:48
   Commandline: apt-get -f install
   Requested-By: adrien (1000)
   Upgrade: libx11-dev:i386 (2:1.4.99.1-0ubuntu2.3, 2:1.6.3-1ubuntu2)
  DpkgLog:
   2017-09-25 22:30:48 startup archives unpack
   2017-09-25 22:30:49 upgrade libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 
2:1.6.3-1ubuntu2
   2017-09-25 22:30:49 status half-installed libx11-dev:i386 
2:1.4.99.1-0ubuntu2.3
   2017-09-25 22:30:49 status unpacked libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
  DpkgTerminalLog:
   Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb ...
   Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/include/X11/Xcms.h', which is different 
from other instances of package libx11-dev:i386
  DuplicateSignature:
   package:libx11-dev:2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
   Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/include/X11/Xcms.h', which is different 
from other instances of package libx11-dev:i386
  ErrorMessage: trying to overwrite shared '/usr/include/X11/Xcms.h', which is 
different from other instances of package libx11-dev:i386
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics 
[1179:f840]
  InstallationDate: Installed on 2016-09-03 (387 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C55-C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=5a16cdbd-726a-45b9-944a-6b66f4f8e612 ro quiet splash radeon.audio=1 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: libx11
  Title: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h] failed to install/upgrade: trying to overwrite shared 
'/usr/include/X11/Xcms.h', which is different from other instances of package 
libx11-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F2
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55-C
  dmi.product.version: PSCPJU-00R011
  dmi.sys.vendor:

[Desktop-packages] [Bug 1719438] Re: gnome-shell crashed with SIGSEGV

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1715330, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956944/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956946/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956950/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956951/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956952/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956953/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719438/+attachment/4956954/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1715330
   gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  (Tested under wayland)

  Test Case:
  1. Launch gnome-boxes
  2. Create a new VM of Ubuntu Artful and run it
  3. Go the the live session in the VM
  4. Close gnome-boxes but keep the VM running
  5. Launch gnome-boxes again

  Expected result
  gnome-boxes is reattached to the VM

  Actual result 
  This crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 16:15:11 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9d310fc4af:mov0x8(%rdi),%eax
   PC (0x7f9d310fc4af) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-25 Thread Ubuntu Foundations Team Bug Bot

The attachment "fix_x11_font_dpi.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64

[Desktop-packages] [Bug 1719445] [NEW] package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X

2017-09-25 Thread Adrien Lacroix

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 libx11-dev: Install
 libx11-dev: Configure
 libx11-dev: Configure
 NULL: ConfigurePending
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: Mon Sep 25 22:30:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-36-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-59-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
 broadcom-sta, 6.30.223.271, 4.4.0-59-generic, x86_64: installed
DpkgHistoryLog:
 Start-Date: 2017-09-25  22:30:48
 Commandline: apt-get -f install
 Requested-By: adrien (1000)
 Upgrade: libx11-dev:i386 (2:1.4.99.1-0ubuntu2.3, 2:1.6.3-1ubuntu2)
DpkgLog:
 2017-09-25 22:30:48 startup archives unpack
 2017-09-25 22:30:49 upgrade libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 
2:1.6.3-1ubuntu2
 2017-09-25 22:30:49 status half-installed libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
 2017-09-25 22:30:49 status unpacked libx11-dev:i386 2:1.4.99.1-0ubuntu2.3
DpkgTerminalLog:
 Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb ...
 Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from 
other instances of package libx11-dev:i386
DuplicateSignature:
 package:libx11-dev:2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h]
 Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack):
  trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from 
other instances of package libx11-dev:i386
ErrorMessage: trying to overwrite shared '/usr/include/X11/Xcms.h', which is 
different from other instances of package libx11-dev:i386
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics 
[1179:f840]
InstallationDate: Installed on 2016-09-03 (387 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA Satellite C55-C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=5a16cdbd-726a-45b9-944a-6b66f4f8e612 ro quiet splash radeon.audio=1 
vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: libx11
Title: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h 
usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h 
usr/include/X11/Xutil.h] failed to install/upgrade: trying to overwrite shared 
'/usr/include/X11/Xcms.h', which is different from other instances of package 
libx11-dev:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.10
dmi.board.name: 06F2
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55-C
dmi.product.version: PSCPJU-00R011
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime:

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

And the following fixes the issue:

sudo patchelf --set-rpath "\$ORIGIN/." /usr/lib/chromium-browser
/chromium-browser

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1710350] Re: black screen after suspend

2017-09-25 Thread Fusion

I ran "sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" and I get 
the errors:
1) on terminal: Gtk-Message: GtkDialog mapped without a transient parent. This 
is discouraged.
2) on gtk window: Error('Incorrect padding',)

Although somehow, maybe after some recent update, problem was solved!

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

Title:
  black screen after suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 (gnome 3.24.2)
  4.11.0-13-generic
  GeForce GTX 1050 Ti/PCIe/SSE2 - 384.59
  AMD® Fx(tm)-4170 quad-core processor × 4
  monitor 3840x2160 (dvi)

  It happens on 1 of 3 times. I don't know what causes that.

  When I am going to leave my pc for several hours I put it first on
  suspend/sleep mode. At about one third of resumes (from suspend mode)
  a black screen occurs and there is nothing I could do about it (except
  from hard reset). If something is pressed by keyboard like
  'ctrl+alt+F1' or F2, screen starts again black (it searches for signal
  - backlight turned on - working mode). If nothing is pressed by
  keyboard, the screen closes after 1-2sec (backlight turned off -
  standby mode).

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

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

[Desktop-packages] [Bug 1718543] Re: gnome-shell-extension-prefs crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Summary changed:

- gnome-shell-extension-prefs crashed with SIGABRT in g_assertion_message()
+ gnome-shell-extension-prefs crashed with SIGABRT in 
g_assertion_message_expr() "assertion failed: (destination)" from 
ensure_surface_for_gicon()

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

Title:
  gnome-shell-extension-prefs crashed with SIGABRT in
  g_assertion_message_expr() "assertion failed: (destination)" from
  ensure_surface_for_gicon()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed when changing Dash to Dock settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 20 00:56:33 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2017-06-01 (110 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-shell-extension-prefs crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-06-10 (101 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-25 Thread Jeremy Soller

** Patch removed: "fix_x11_font_dpi.patch"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956941/+files/fix_x11_font_dpi.patch

** Patch added: "fix_x11_font_dpi.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956942/+files/fix_x11_font_dpi.debdiff

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

Title:
HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
Confirmed

Bug description:
After an upgrade this morning that took in the new version of this
package, and a suite of gnome-session/gnome-settings packages, which
may also be implicated, support for scaling on HiDPI screens seems to
have partially failed. Partially.

BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
when I got to the launchpad page it had pre-filled "gnome-session".
One presumes there's a reason for that so I've left it, especially as
this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
settings migrations utility in ubuntu-session which I wonder if it
might be implicated. (TBH looking at it it's not obvious why, though
it does reset scaling - that's not the problem, the problem is that it
can't be set back to a combination that works.)

Reminder all the stuff I'm reporting below as being wrongly-scaled was
scaled correctly before the update that just took place. Enpass got a
little help from having some QT env variables set, but that's it.

Logging in under session "Ubuntu" (Wayland - on a different machine as
this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
- also affects GNOME sessions:

* The fonts in the top bar, and the menus and indicators accessible
from there, are unscaled. The indicator icons *are* scaled correctly.

* The fonts in the applications view are unscaled, but the icons and
layout *are* scaled correctly.

* Menu titlebar *text* is unscaled. close/minimize/maximize widgets
*are* scaled correctly, as is the titlebar's size itself.

* The mouse pointer is unscaled.

* Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
client, hexchat, sublime text 3) are unscaled, or in some cases are a
bit confused, with some elements correctly scaled, but again fonts are
not.

* Also on a personal note, Java 9 JavaFX apps are no longer scaled.
(In Java 8 it was already broken; I was targeting Java 9 with my
development partly *because* its HiDPI support was working in Linux.)
FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

## What is working:

* Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
Gedit etc. etc.) are all fine. Although note those that use a "normal"
titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
show small titlebar text as mentioned above

* Google Chrome, Thunderbird, Firefox are fine (although the latter
two aren't being updated for Artful yet, just sayin' ;-)

## What happens if I try to fix it:

gsettings org.gnome.desktop.interface scaling-factor appears to no
longer be operational. Changing its value from 0 (default), 1 and 2
appears to have no effect on anything any more. It used to be setting
it to 2 fixed the few things that weren't right by having it set to
0... Correction, that *does* fix it for Java 9 JavaFX, it must be
reading that setting directly. But nothing else reported as broken
above is affected by changing this setting. Nor in fact does setting
it to 1 cause gnome apps to be unscaled.

gsettings org.gnome.desktop.interface cursor-size is working. I can
set it to 48, double its normal size, to get back normal-sized cursors
when the pointer is over newly-launched applications. But that's
obviously a workaround.

gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
also exposed in Gnome Tweaks, unsurprisingly makes text twice as
large. That "fixes" it for the applications that are reported as being
unscaled above, but it also doubles the size of text in gnome apps as
well, so those are now far too large for the windows they're in.
Google Chrome is unaffected by this, as is Java 9 JavaFX, but
Thunderbird *is* affected.

I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
it seems to have a nonsense-value "@a{si} {}". I have no idea if this
is anything in use or if it was an intended Unity 8 thing. I didn't
try anything with it.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-session 3.25.90-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug

[Desktop-packages] [Bug 1719438] [NEW] gnome-shell crashed with SIGSEGV

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

Public bug reported:

(Tested under wayland)

Test Case:
1. Launch gnome-boxes
2. Create a new VM of Ubuntu Artful and run it
3. Go the the live session in the VM
4. Close gnome-boxes but keep the VM running
5. Launch gnome-boxes again

Expected result
gnome-boxes is reattached to the VM

Actual result 
This crash

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 16:15:11 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2013-09-03 (1482 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9d310fc4af:  mov0x8(%rdi),%eax
 PC (0x7f9d310fc4af) ok
 source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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


** Tags: amd64 apport-crash artful wayland-session

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  (Tested under wayland)

  Test Case:
  1. Launch gnome-boxes
  2. Create a new VM of Ubuntu Artful and run it
  3. Go the the live session in the VM
  4. Close gnome-boxes but keep the VM running
  5. Launch gnome-boxes again

  Expected result
  gnome-boxes is reattached to the VM

  Actual result 
  This crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 16:15:11 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9d310fc4af:mov0x8(%rdi),%eax
   PC (0x7f9d310fc4af) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

2017-09-25 Thread Naël

Still affects xorg-lts-trusty for the users of releases < Trusty LTS,
but all of those releases e.g. Precise LTS are EOL now.

There is therefore no point in fixing this package, it won't be
installed by anybody any more.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-25 Thread Jeremy Soller

Here is a debdiff with the change, if Ubuntu would like to use it
sooner.

** Patch added: "fix_x11_font_dpi.patch"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956941/+files/fix_x11_font_dpi.patch

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

Title:
HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
Confirmed

Logging in under session "Ubuntu" (Wayland - on a different machine as
this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
- also affects GNOME sessions:

* The fonts in the top bar, and the menus and indicators accessible
from there, are unscaled. The indicator icons *are* scaled correctly.

* The fonts in the applications view are unscaled, but the icons and
layout *are* scaled correctly.

* Menu titlebar *text* is unscaled. close/minimize/maximize widgets
*are* scaled correctly, as is the titlebar's size itself.

* The mouse pointer is unscaled.

## What is working:

* Google Chrome, Thunderbird, Firefox are fine (although the latter
two aren't being updated for Artful yet, just sayin' ;-)

## What happens if I try to fix it:

[Desktop-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

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

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718671] Re: Gnome-Shell crashes after unlocking Lockscreen

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1714886, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1714886
   gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

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

Title:
  Gnome-Shell crashes after unlocking Lockscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  lsb_release  -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  gnome-shell:
Installed: 3.26.0-0ubuntu1
Candidate: 3.26.0-0ubuntu1
Version table:
   *** 3.26.0-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  When using Super+L to lock the screen first all is working as
  intended. After some time i want to unlock the Screen. I provide my
  credentials and now all application that were open before are closed.
  It looks like a new Session.

  This happens only after some Time has passed. If I lock the screen and
  immediately unlock it, all is working as intended

  I attached parts of journalctl:
  It seems a segfault causing parts of gnome getting killed by a SIGSEGV

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-25 Thread Jeremy Soller

I have recommended this patch to upstream, which is the simplest method
to fix the scaling issues described in detail above.

** Patch added: "fix_x11_font_dpi.patch"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956940/+files/fix_x11_font_dpi.patch

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

Title:
HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
Confirmed

Logging in under session "Ubuntu" (Wayland - on a different machine as
this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
- also affects GNOME sessions:

* The fonts in the top bar, and the menus and indicators accessible
from there, are unscaled. The indicator icons *are* scaled correctly.

* The fonts in the applications view are unscaled, but the icons and
layout *are* scaled correctly.

* Menu titlebar *text* is unscaled. close/minimize/maximize widgets
*are* scaled correctly, as is the titlebar's size itself.

* The mouse pointer is unscaled.

## What is working:

* Google Chrome, Thunderbird, Firefox are fine (although the latter
two aren't being updated for Artful yet, just sayin' ;-)

## What happens if I try to fix it:

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

Chromium 60 was built with is_component_build=true. Chromium 61 is built
with is_component_build=false, and in that configuration the rpath does
not contain the directory where shared libs (such as libffmpeg.so) are
built. There's a good explanation of why there:
https://cs.chromium.org/chromium/src/build/config/gcc/BUILD.gn?l=48.

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1718850] Re: System extensions appear off by default

I wonder if they appear off because we don't have package 'gnome-shell-
extensions' installed by default?

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

Title:
  System extensions appear off by default

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-tweak-tool package in Ubuntu:
  New

Bug description:
  Go to the Extensions panel in Tweaks.
  System extensions (dock and appindicators) appear off by default, where they 
are obviously not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-tweak-tool 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 08:02:59 2017
  ExecutablePath: /usr/bin/gnome-tweak-tool
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SourcePackage: gnome-tweak-tool
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

Fix committed for xenial:
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-xenial=312b9b8d36b90c6bae520722cf68e01b53832eeb

But I forgot to ask: Does the same fix exist in artful already? It's
part of the SRU process that the next release needs to have the fix
first, before xenial.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

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

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

[Desktop-packages] [Bug 1718927] Re: No hdmi sound after suspend/resume on 16.04

At a guess, your system is probably reverting back to the default audio
device on resume.

What does it look like in Settings after resuming? Can you change the
audio playback device back to HDMI by hand?

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

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Desktop-packages] [Bug 1718932] Re: Child windows do not have shadows

** Also affects: gnome-shell (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/1718932

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718932] Re: Child windows do not have shadows

Confirmed, but I think this was by design (chosen by upstream Gnome). We
have not yet changed it, or decided to change it.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Incomplete

** Summary changed:

- Child windows do not have shadows
+ Child windows do not have shadows in Gnome Shell

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

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718932] Re: Child windows do not have shadows

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

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

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718932] Re: Child windows do not have shadows

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

** Changed in: ubuntu-themes (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/1718932

Title:
  Child windows do not have shadows in Gnome Shell

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Some child windows do not have shadows.

  Test case:
  Open Thunderbird for the first time.
  A child window will appear to create a new account.
  It does not have shadows.

  Synaptic package manager also have the same issue.

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 14:20:26 2017
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719300] Re: chromedriver doesn't start without setting LD_LIBRARY_PATH

2017-09-25 Thread Jason Owen

I upgraded this morning, and my Selenium tests broke.

I was able to reproduce this problem with the Python getting started
script from https://sites.google.com/a/chromium.org/chromedriver
/getting-started (altered to set the path to `/usr/lib/chromium-
browser/chromedriver`):

```
virtualenv -p python3 venv
. venv/bin/activate
pip install selenium
python script.py
```

Running `ps aux | grep chrom` in another tab shows `Z+   15:51   0:00
[chromium-browse] `, and eventually the script times out with
`selenium.common.exceptions.WebDriverException: Message: unknown error:
Chrome failed to start: exited abnormally`.

Setting the LD_LIBRARY_PATH first fixes it: `export
LD_LIBRARY_PATH=/usr/lib/chromium-browser`.

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

Title:
  chromedriver doesn't start without setting LD_LIBRARY_PATH

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser won't start unless I set LD_LIBRARY_PATH=/usr/lib
  /chromium-browser.

  I think this is a recent change that and the problem is libffmpeg.so which is 
installed in /usr/lib/chromium-browser.
  Before, I could also launch chromium with 
/usr/lib/chromium-browser/chromium-browser but now I get the following error 
message:
  /usr/lib/chromium-browser/chromium-browser: error while loading shared 
libraries: libffmpeg.so: cannot open shared object file: No such file or 
directory

  The chromium-browser package installs a chromium-browser script in
  /usr/bin that sets LD_LIBRARY_PATH

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

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

[Desktop-packages] [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)

Confirmed, in chromium 60.0.3112.113 ldd was able to locate
libffmpeg.so:

$ ldd /usr/lib/chromium-browser/chromium-browser | grep ffmpeg
libffmpeg.so => /usr/lib/chromium-browser/./libffmpeg.so 
(0x7fec793cc000)

In chromium 61.0.3163.79, it can't locate it:

$ ldd /usr/lib/chromium-browser/chromium-browser | grep ffmpeg
libffmpeg.so => not found

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

Title:
  chromium doesn't start in guest session (xubuntu 16.04)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1719300] Re: chromedriver doesn't start without setting LD_LIBRARY_PATH

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

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

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

Title:
  chromedriver doesn't start without setting LD_LIBRARY_PATH

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser won't start unless I set LD_LIBRARY_PATH=/usr/lib
  /chromium-browser.

  I think this is a recent change that and the problem is libffmpeg.so which is 
installed in /usr/lib/chromium-browser.
  Before, I could also launch chromium with 
/usr/lib/chromium-browser/chromium-browser but now I get the following error 
message:
  /usr/lib/chromium-browser/chromium-browser: error while loading shared 
libraries: libffmpeg.so: cannot open shared object file: No such file or 
directory

  The chromium-browser package installs a chromium-browser script in
  /usr/bin that sets LD_LIBRARY_PATH

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

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

[Desktop-packages] [Bug 1719047] Re: Unable to resize window after snapped to half screen.

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

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

Title:
  Unable to resize window after snapped to half screen.

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Unable to resize window after snapped to half screen.  You can see the
  arrow, tempting you to just try and resize the window at the edge, but
  it's just toying with you.

  More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

  This used to work in z+Unity ;(.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 19:15:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-04-25 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

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

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

[Desktop-packages] [Bug 1719115] Re: gnome-shell crashed with signal 5 in _XIOError()

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1505409, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, dev branch
  Gnome-shell
  *** 3.26.0-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep 23 19:18:28 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2016-10-09 (348 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.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
  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/gnome-shell/+bug/1719115/+subscriptions

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

[Desktop-packages] [Bug 1719128] Re: Automatic login works only for wayland session

Have you enabled Wayland support by modifying your kernel command line?

Please attach a copy of your /proc/cmdline here, and also please run
this command to attach further details:

apport-collect 1719128

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

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

Title:
  Automatic login works only for wayland session

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, Nvidia binary drivers, X11 session.
  Autologin feature doesn't work for X11, only for Wayland.

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

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

[Desktop-packages] [Bug 1718215] Re: versions of cups-filters and libqpdf do not match

2017-09-25 Thread Bernard Banko

Update right now solved it for me.

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

Title:
  versions of cups-filters and libqpdf do not match

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  When I print a document it is sent to the printer (pdf, libreoffice,
  gedit, ...) but stops immediately and is not printed. It cannot be
  resumed and documents sent to the PDF driver result in a blank file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 16:07:01 2017
  InstallationDate: Installed on 2013-09-03 (1476 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  Lpstat:
   device for Deskjet: hp:/net/Deskjet_D5500_series?ip=192.168.1.50
   device for HP-Photosmart-5520-series: 
hp:/net/Photosmart_5520_series?zc=HPFC15B4E0E72B
   device for HP-Photosmart-C5200-series: 
usb://HP/Photosmart%20C5200%20series?serial=MY84AG220H0559=1
   device for MP210: usb://Canon/MP210%20series?serial=638BE0=1
   device for PDF: cups-pdf:/
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd', '/etc/cups/ppd/PDF.ppd', 
'/etc/cups/ppd/HP-Photosmart-C5200-series.ppd', '/etc/cups/ppd/Deskjet.ppd', 
'/etc/cups/ppd/MP210.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-Photosmart-5520-series.ppd: Permission denied
   grep: /etc/cups/ppd/PDF.ppd: Permission denied
   grep: /etc/cups/ppd/HP-Photosmart-C5200-series.ppd: Permission denied
   grep: /etc/cups/ppd/Deskjet.ppd: Permission denied
   grep: /etc/cups/ppd/MP210.ppd: Permission denied
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1717781] Re: Gnome session logs out unespectadly while using it

2017-09-25 Thread Carla Sella

Happened again. I had just logged back in, used Firefox and Thunderbird
a bit when it logged out all of a sudden again. This time, when I logged
back in my PC froze. Had to power off pressing the power button.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717781/+attachment/4956936/+files/syslog

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

Title:
  Gnome session  logs out unespectadly while using it

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  I have Ubuntu Ubuntu Artful Aardvark (development branch) installed.
  While I am logged on to my session, without any reason I can understand, 
Gnome session logs out.
  I log back in, after a while it just logs out again.
  This happened two or three times before Gnome shell freezed. Had to reboot my 
PC pressing power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 17 16:29:37 2017
  InstallationDate: Installed on 2017-06-01 (107 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (110 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-session 3.26.0-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1719408] [NEW] Application window outside of its frame in spread mode

Public bug reported:

Test Case:
1. On a workspace with no window, toggle spread mode (super key)
2. Open a terminal with its keybinding: CTRL+ALT+T

Expected result
The terminal opens in the center of the screen with a frame around it

Actual result
The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-bin 1.14.0-1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 15:00:29 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed
 virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:1507]
InstallationDate: Installed on 2013-09-03 (1482 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
MachineType: ASUSTeK COMPUTER INC. UX32VD
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
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.9.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

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


** Tags: amd64 apport-bug artful reproducible ubuntu wayland-session

** Attachment added: "Capture d’écran de 2017-09-25 14-59-10.png"
   
https://bugs.launchpad.net/bugs/1719408/+attachment/4956909/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202017-09-25%2014-59-10.png

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

Title:
  Application window outside of its frame in spread mode

Status in wayland package in Ubuntu:
  New

Bug description:
  Test Case:
  1. On a workspace with no window, toggle spread mode (super key)
  2. Open a terminal with its keybinding: CTRL+ALT+T

  Expected result
  The terminal opens in the center of the screen with a frame around it

  Actual result
  The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin 1.14.0-1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:00:29 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed
   virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1341351] Re: gnome-shell-extension-prefs crashed with signal 5 in g_settings_bind_with_mapping()

Per the upstream comment, the fault would be in the extension
'EasyScreenCast', so the status for gnome-shell itself is Invalid.

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

Title:
  gnome-shell-extension-prefs crashed with signal 5 in
  g_settings_bind_with_mapping()

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

Bug description:
  EasyScreenCast by IacopoDeeNosee

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-shell 3.12.2-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4
  Uname: Linux 3.16.0-3-lowlatency x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 13 17:29:04 2014
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell.location' b'max-accuracy-level' b"'off'"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2014-04-27 (77 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: gnome-shell-extension-prefs 
easyscreenc...@iacopodeenosee.gmail.com
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_bind_with_mapping () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_bind () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell-extension-prefs crashed with signal 5 in 
g_settings_bind_with_mapping()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717781] Re: Gnome session logs out unespectadly while using it

2017-09-25 Thread Carla Sella

Sorry for the delay, it didn't happen for a while until today.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717781/+attachment/4956907/+files/syslog

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

Title:
  Gnome session  logs out unespectadly while using it

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  I have Ubuntu Ubuntu Artful Aardvark (development branch) installed.
  While I am logged on to my session, without any reason I can understand, 
Gnome session logs out.
  I log back in, after a while it just logs out again.
  This happened two or three times before Gnome shell freezed. Had to reboot my 
PC pressing power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 17 16:29:37 2017
  InstallationDate: Installed on 2017-06-01 (107 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (110 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-session 3.26.0-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1719332] Re: nm-applet freezing/crashing with 802.1x on ethernet

2017-09-25 Thread Tiago Pimenta

This bug only happens with two or more connections configured (one
ethernet and another wireless) being at least one of them flagged not to
save password.

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

Title:
  nm-applet freezing/crashing with 802.1x on ethernet

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Enable 802.1x Security on Ethernet connection.
  Put authentication mode to PEAP.
  Mark to not require certificate.
  Enter the login.
  Flag the password to ask everytime.

  It does not prompt for the password and freezes, sometimes crashes,
  even after a reboot. Besides when you have an wireless connection with
  the same secutirity settings it prompts for the password, but the
  window freezes before showing the widgets.

  I have tried to input the password and flag it to save, it connects, I
  can see the IP via ifconfig, but the tray icon freezes anyway.

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

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

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

** Tags added: rls-aa-incoming

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1719390] gnome-control-center crashed with SIGSEGV

StacktraceTop:
 gcm_prefs_calib_apply_cb (widget=, prefs=0x5648b0251370) at 
cc-color-panel.c:316
 g_closure_invoke (closure=0x5648b0786a30, return_value=0x0, n_param_values=1, 
param_values=0x7ffcbbc97870, invocation_hint=0x7ffcbbc977f0) at 
../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5648b064a6f0, detail=detail@entry=0, 
instance=instance@entry=0x5648afeb97e0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffcbbc97870) at 
../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x5648afeb97e0, signal_id=, 
detail=0, var_args=var_args@entry=0x7ffcbbc97a30) at 
../../../../gobject/gsignal.c:3391
 g_signal_emit (instance=instance@entry=0x5648afeb97e0, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1719390] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719390/+attachment/4956902/+files/Stacktrace.txt

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1719390] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719390/+attachment/4956904/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1719390/+attachment/4956890/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1719390] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1719390/+attachment/4956903/+files/StacktraceSource.txt

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1539209] Update Released

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1562817] Update Released

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

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

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Released

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Find some headphones and/or microphone. Ensure you do not wear the
headphones during the test as it may be loud.
2. Set audio output/input volumes to maximum.
3. Unplug and replug the headphones/microphone.
4. Check that that pulseaudio process is still running, with a start time
older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would be
loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

I'm not sure it is related, but when i plug in a headset, the audio volume
goes through the roof, and a loud (painfully so) scratching sound is coming
from the headset until i press Vol+. Vol- does nothing till i have pressed up
at least once.
But the bug report thing does not pop up when the sound issue is there.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tbs 22776 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 28 12:39:45 2016
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2016-01-14 (73 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
pa_source_process_msg () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo
vboxusers
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 244743G
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn244743G:pvrThinkPadW530:rvnLENOVO:rn244743G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 244743G
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

  * debian/control: Update Vcs fields to launchpad git.
  * Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
  LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

 -- Daniel van Vugt   Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_proce

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

  * debian/control: Update Vcs fields to launchpad git.
  * Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
  LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

 -- Daniel van Vugt   Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_write_volume_cb() from source_set_port_cb() from
  pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
 headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
 older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  This error is there when i get back to the computer after a while of
  no use, and at login after restart. haven't seen this error while the
  system is "active"/in use.

  I have been unable to provoke the error to come.

  I'm not sure it is related, but when i plug in a headset, the audio volume 
goes through the roof, and a loud (painfully so) scratching sound is coming 
from the headset until i press Vol+. Vol- does nothing till i have pressed up 
at least once.
  But the bug report thing does not pop up when the sound issue is there.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  pulseaudio:
    Installed: 1:8.0-0ubuntu2
    Candidate: 1:8.0-0ubuntu2
    Version table:
   *** 1:8.0-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbs   22776 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 28 12:39:45 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-14 (73 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   pa_source_process_msg () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo 
vboxusers
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 244743G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn244743G:pvrThinkPadW530:rvnLENOVO:rn244743G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 244743G
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

[Desktop-packages] [Bug 1672171] Update Released

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

Title:
pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
from pa_bluetooth_transport_set_state() from profile_new_connection()
from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Released

Bug description:
[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
fidelity A2DP and the lower quality headset profiles).
2. Pair it with your machine and select the device in sound settings.
3. Turn the Bluetooth audio device off and on again, making sure it is
set to active if not automatically so.
4. Select the device in sound settings.
5. Check that that pulseaudio process is still running, with a start
time older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would
be loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

Bluetooth device keep disconnect and audio output tab is empty

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
Uname: Linux 4.10.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bikram14994 F pulseaudio
/dev/snd/controlC0: bikram14994 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Sun Mar 12 21:52:24 2017
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_bluetooth_transport_set_state () from
/usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0Y004V
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler()

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

* debian/control: Update Vcs fields to launchpad git.
* Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

-- Daniel van Vugt Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (Ubuntu Xenial)
Status: Fix Committed => Fix Released

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

Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Released

Bug description:
[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would
be loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

Bluetooth device keep disconnect and audio output tab is empty

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

[Desktop-packages] [Bug 1690028] Update Released

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

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_hand

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.4

---
pulseaudio (1:8.0-0ubuntu3.4) xenial; urgency=medium

  * debian/control: Update Vcs fields to launchpad git.
  * Cherrypick fixes for common crashes from upstream:
- cb78d6f5: SIGABRT in device_start_waiting_for_profiles (LP: #1690028,
  LP: #1672171)
- d985276c: SIGABRT in pa_alsa_path_set_volume (LP: #1539209, LP: #1562817)

 -- Daniel van Vugt   Fri, 11 Aug 2017
15:16:57 +0800

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color in artful

Thanks for your report. I confirm this error. 
On second try gnome-control-center crashes.

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

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

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

Title:
  Unable to calibrate monitors through Gnome Control Center->Color in
  artful

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

Bug description:
  Fresh install of Artful, using gnome-session to access vanilla GNOME
  session on Wayland (also tried on xorg).  Attempting to calibrate
  monitors through Gnome Control Center->Devices->Color.  All attempts
  ended at the point where I was asked to put the device onto the
  monitor, with the error:

  Calibration failed!
  An internal error occurred that could not be recovered. You can remove the 
calibration device.

  Syslog:
  Sep 24 12:19:31 desktop kernel: [  262.849675] usb 3-6: new full-speed USB 
device number 7 using xhci_hcd
  Sep 24 12:19:32 desktop kernel: [  262.990880] usb 3-6: New USB device found, 
idVendor=0971, idProduct=2007
  Sep 24 12:19:32 desktop kernel: [  262.990882] usb 3-6: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Sep 24 12:19:32 desktop kernel: [  262.990884] usb 3-6: Product: colormunki
  Sep 24 12:19:32 desktop kernel: [  262.990885] usb 3-6: Manufacturer: X-Rite
  Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
  Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with 
(Permission denied), drawing cursor with OpenGL from now on
  Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL 
warning: wayland-egl: could not open /dev/dri/card0 (Permission denied)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL 
warning: wayland-egl: could not open /dev/dri/card0 (Permission denied)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA 
error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva 
error: va_getDriverName() failed with unknown libva error,driver_name=(null)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva 
error: va_getDriverName() failed with unknown libva error,driver_name=(null)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA 
error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13)
  Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva 
error: va_getDriverName() failed with unknown libva error,driver_name=(null)

  
  I attempted to fix the permissions error for /dev/dri/card0.  Current 
permissions:
  rwh@desktop:~$ ls -l /dev/dri/card0
  crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0

  Tried adding my user to video group, which made no difference.  Then made 
file world r/w:
  rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0

  Which fixed that problem.  Now, in the calibrate wizard, on the second
  step (Display Type) I am offered three options (LCD, CRT, Projector)
  where I only saw LCD previously.  However, the calibration step failed
  the same as before.  Syslog:

  Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB 
device number 12 using xhci_hcd
  Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, 
idVendor=0971, idProduct=2007
  Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki
  Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite
  Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: 
[pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.]
  Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: 
Unable to initialize the Clutter backend: no available drivers found.
  Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: 
Unable to initialize the Clutter backend: no available drivers found.
  Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) 
dispatching to Wayland display.
  Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) 
dispatching to Wayland display.
  Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service 
name='org.freedesktop.ColorHelper' unit='colord-session.service'
  Sep 24 12:37:21 desktop systemd[3601]: Starting Color management helper...
  Sep 24 12:37:21 desktop dbus-daemon[4121]:

[Desktop-packages] [Bug 1719390] [NEW] gnome-control-center crashed with SIGSEGV

Public bug reported:

Crashed on second time trying to calibrate my monitor from control-
center.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 14:19:04 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-03 (1482 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/bin/gnome-control-center color
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5648add75047:  mov0x8(%rax),%rcx
 PC (0x5648add75047) ok
 source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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


** Tags: amd64 apport-crash artful need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed on second time trying to calibrate my monitor from control-
  center.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 14:19:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/bin/gnome-control-center color
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5648add75047:mov0x8(%rax),%rcx
   PC (0x5648add75047) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_proce

** Tags removed: rapport-crash
** Tags added: apport-crash

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

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Released

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

[Desktop-packages] [Bug 1719215] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  I was just switching between different settings sections and it
  crashed. Had just upgraded to artful.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 24 21:56:29 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-04-10 (167 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff0f2e2de8d :
movzbl 0x16(%rax),%edx
   PC (0x7ff0f2e2de8d) ok
   source "0x16(%rax)" (0x65646972706c6982) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.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
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-09-24 (0 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo

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

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

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

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Some Top Icons Disappear After Screen Locks - 17.10

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

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

  Thanks for all of your hard work!

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

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

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

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

You have been subscribed to a public bug:

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

Thanks for all of your hard work!

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

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


** Tags: amd64 apport-bug artful wayland-session
-- 
Some Top Icons Disappear After Screen Locks - 17.10
https://bugs.launchpad.net/bugs/1719192
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1719368] Re: gnome-shell crashed with signal 5 in _XIOError()

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

This looks like bug 1505409, AFAICT

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  My pc   ASUS GL753V  core I7 7700 
  this bug was present before the last update. 
  It's come on open desktop.  I use a conky desktop. Is there that

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep 23 01:18:02 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (220 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.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
  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/gnome-shell/+bug/1719368/+subscriptions

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

[Desktop-packages] [Bug 1270597] Re: package postgresql-client-9.3 9.3.2-1ubuntu1 failed to upgrade: alternative pg_basebackup.1.gz can't be slave of psql.1.gz

2017-09-25 Thread cracket

3 years have passed and bug is still impacting upgrade. As I understand
14.04 is still supported and bug should be fixed once again - hope
finally now.

Status should be still Not Fixed

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

Title:
  package postgresql-client-9.3 9.3.2-1ubuntu1 failed to upgrade:
  alternative pg_basebackup.1.gz can't be slave of psql.1.gz

Status in postgresql-common package in Ubuntu:
  Fix Released
Status in postgresql-common source package in Trusty:
  Fix Released

Bug description:
  crashed during upgrading from Ubuntu 12.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: postgresql-client-9.3 9.3.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-58.88-generic-pae 3.2.53
  Uname: Linux 3.2.0-58-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  Date: Sun Jan 19 16:27:59 2014
  DuplicateSignature: 
package:postgresql-client-9.3:9.3.2-1ubuntu1:ErrorMessage: subprocess installed 
post-installation script returned error exit status 2
  EcryptfsInUse: Yes
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 2
  InstallationDate: Installed on 2013-08-22 (150 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423.2)
  SourcePackage: postgresql-9.3
  Title: package postgresql-client-9.3 9.3.2-1ubuntu1 failed to 
install/upgrade: ErrorMessage: subprocess installed post-installation script 
returned error exit status 2
  UpgradeStatus: Upgraded to trusty on 2014-01-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1719372] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1719372/+attachment/4956876/+files/StacktraceSource.txt

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

Title:
  gnome-screensaver crashed with SIGSEGV

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Crash using Gource

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
  Uname: Linux 4.14.0-0-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Sep 25 13:20:02 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: Yes
  GnomeSessionInhibitors:
   1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
   2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
   3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2016-08-02 (418 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x55bbfd66f705:imul   
$0x6569766e,0x6f(%rbx),%esp
   PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
   source "$0x6569766e" ok
   destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
  SegvReason: executing writable VMA [mpx]
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ()
   XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1719368] Re: gnome-shell crashed with signal 5 in _XIOError()

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

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  My pc   ASUS GL753V  core I7 7700 
  this bug was present before the last update. 
  It's come on open desktop.  I use a conky desktop. Is there that

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep 23 01:18:02 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (220 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.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
  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/gnome-shell/+bug/1719368/+subscriptions

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

[Desktop-packages] [Bug 1719372] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719372/+attachment/4956877/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1719372/+attachment/4956857/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-screensaver crashed with SIGSEGV

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Crash using Gource

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
  Uname: Linux 4.14.0-0-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Sep 25 13:20:02 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: Yes
  GnomeSessionInhibitors:
   1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
   2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
   3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2016-08-02 (418 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x55bbfd66f705:imul   
$0x6569766e,0x6f(%rbx),%esp
   PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
   source "$0x6569766e" ok
   destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
  SegvReason: executing writable VMA [mpx]
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ()
   XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1719372] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1719372/+attachment/4956875/+files/Stacktrace.txt

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

Title:
  gnome-screensaver crashed with SIGSEGV

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Crash using Gource

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
  Uname: Linux 4.14.0-0-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Sep 25 13:20:02 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: Yes
  GnomeSessionInhibitors:
   1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
   2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
   3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2016-08-02 (418 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x55bbfd66f705:imul   
$0x6569766e,0x6f(%rbx),%esp
   PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
   source "$0x6569766e" ok
   destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
  SegvReason: executing writable VMA [mpx]
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ()
   XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1719372] gnome-screensaver crashed with SIGSEGV

StacktraceTop:
 ?? ()
 XForceScreenSaver (dpy=0x55bbfd5c1900, mode=mode@entry=0) at 
../../src/FSSaver.c:53
 XResetScreenSaver (dpy=) at ../../src/FSSaver.c:42
 gs_monitor_simulate_user_activity (monitor=0x55bbfd602740) at gs-monitor.c:195
 listener_simulate_user_activity_cb (listener=, 
monitor=0x55bbfd602740) at gs-monitor.c:287

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

Title:
  gnome-screensaver crashed with SIGSEGV

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Crash using Gource

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
  Uname: Linux 4.14.0-0-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Sep 25 13:20:02 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: Yes
  GnomeSessionInhibitors:
   1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
   2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
   3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2016-08-02 (418 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x55bbfd66f705:imul   
$0x6569766e,0x6f(%rbx),%esp
   PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
   source "$0x6569766e" ok
   destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
  SegvReason: executing writable VMA [mpx]
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ()
   XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

PulseAudio is what implements most of the Bluetooth audio logic (not
BlueZ, surprising I know). You can contact the developers a few
different ways, documented here:

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Community/

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Desktop-packages] [Bug 1719372] [NEW] gnome-screensaver crashed with SIGSEGV

2017-09-25 Thread Wellington Torrejais da Silva

Public bug reported:

Crash using Gource

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-screensaver 3.6.1-7ubuntu6
ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
Uname: Linux 4.14.0-0-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Sep 25 13:20:02 2017
ExecutablePath: /usr/bin/gnome-screensaver
GnomeSessionIdleInhibited: Yes
GnomeSessionInhibitors:
 1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
 2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
 3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'gnome'
 org.gnome.desktop.session idle-delay uint32 0
InstallationDate: Installed on 2016-08-02 (418 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
SegvAnalysis:
 Segfault happened at: 0x55bbfd66f705:  imul   $0x6569766e,0x6f(%rbx),%esp
 PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
 source "$0x6569766e" ok
 destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
SegvReason: executing writable VMA [mpx]
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
 ()
 XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-screensaver crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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


** Tags: amd64 apport-crash artful need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  gnome-screensaver crashed with SIGSEGV

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Crash using Gource

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.14.0-0.1-generic 4.14.0-rc1
  Uname: Linux 4.14.0-0-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Sep 25 13:20:02 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: Yes
  GnomeSessionInhibitors:
   1: AppId = firefox-trunk, Flags = 8, Reason = audio-playing
   2: AppId = org.gnome.gedit, Flags = 1, Reason = Há documentos não salvos
   3: AppId = user, Flags = 12, Reason = Inhibit by Caffeine
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2016-08-02 (418 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x55bbfd66f705:imul   
$0x6569766e,0x6f(%rbx),%esp
   PC (0x55bbfd66f705) in non-executable VMA region: 
0x55bbfd585000-0x55bbfd8e6000 rw-p [mpx]
   source "$0x6569766e" ok
   destination "0x6f(%rbx)" (0x55bbfd5c196f) ok
  SegvReason: executing writable VMA [mpx]
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ()
   XForceScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1719124] Re: gnome-shell crashed with signal 5 in g_settings_schema_get_value (..."opaque-background")