[Desktop-packages] [Bug 1810771] Re: HPLIP hp-systray tray icon does not show dropdown menu in Unity Panel on 18.04 LTS

2019-01-10 Thread Khurshid Alam
It seems dbus realted issue, on unity it simply couldn't get the bus.
But dbus-launch works for me. Ask the maintainer (~till-kamppeter )to
upload new version of hplip.

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in Unity Panel
  on 18.04 LTS

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New
Status in ubuntu-unity-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS with `ubuntu-unity-desktop`  all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: hplip-gui 3.17.10+repack0-5
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CupsErrorLog:
   W [14/Aug/2018:13:47:13 +0300] Notifier for subscription 25 (dbus://) went 
away, retrying!
   W [07/Jan/2019:13:51:06 +0300] Notifier for subscription 39 (dbus://) went 
away, retrying!
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan  7 14:00:31 2019
  InstallationDate: Installed on 2018-04-28 (253 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b7cab74d-ae3c-460b-95fe-5f8e8a45ff56 ro quiet splash
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Desktop-packages] [Bug 1716264] Re: Cannot change theme to Radiance in 3.25.x

2019-01-10 Thread Jeremy Bicha
To rephrase:

GNOME prefers people use the GNOME Tweaks app to change their theme.
Currently, the Ubuntu Desktop team agrees enough with GNOME's decision
on this issue to not want to try to override it in Ubuntu.

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

Title:
  Cannot change theme to Radiance in 3.25.x

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I cannot find the panel to change the theme to Radiance in the new
  g-c-c 3.25.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-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: ubuntu:GNOME
  Date: Sun Sep 10 19:41:35 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-09 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  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/1716264/+subscriptions

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


[Desktop-packages] [Bug 1802512] Re: xorg does not work

2019-01-10 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  xorg does not work

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  I;m usin geforce 8800GT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..1c.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:1c:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Fri Nov  9 14:40:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd MS-7C02
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=a037c8bc-adce-4a23-9b98-d6cd7b029fe0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 TOMAHAWK (MS-7C02)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd07/02/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C02
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1778919] Re: package firefox 60.0.1+build2-0ubuntu0.18.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127

2019-01-10 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package firefox 60.0.1+build2-0ubuntu0.18.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 127

Status in firefox package in Ubuntu:
  Expired

Bug description:
  happened on an update proposed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0.1+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fred   1460 F pulseaudio
   /dev/snd/controlC2:  fred   1460 F pulseaudio
   /dev/snd/controlC0:  fred   1460 F pulseaudio
  BuildID: 20180517114003
  Channel: Unavailable
  Date: Wed Jun 27 15:18:08 2018
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 127
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-29 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.74 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 60.0.1+build2-0ubuntu0.18.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.14
  dmi.board.name: Eureka3
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd11/13/2009:svnHP-Pavilion:pnVN433AA-ABFp6235fr:pvr:rvnPEGATRONCORPORATION:rnEureka3:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: VN433AA-ABF p6235fr
  dmi.sys.vendor: HP-Pavilion

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

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


[Desktop-packages] [Bug 1786796] Re: click on menu button doesn't work with firefox 61

2019-01-10 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  click on menu button doesn't work with firefox 61

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I can't click on several icons with Firefox 61 on Ubuntu 16.04 (Xenial).
  For example, a click on the menu button doesn't work. None comboboxs work.

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

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


[Desktop-packages] [Bug 1802609] Re: alot of freezing

2019-01-10 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  alot of freezing

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Ubuntu worked perfectly with me twice only i don't know why its
  freezing when i open any app cant even access ctrl alt f1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 02:14:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1802696] Re: Laptop suspends on login with external screen and lid closed

2019-01-10 Thread Launchpad Bug Tracker
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Laptop suspends on login with external screen and lid closed

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  Release:  18.10
  with latest updates installed.

  I have mouse, keyboard and external screen connected to the laptop, lid is 
closed.
  Right after boot I'm selecting user, typing password, pressing enter and 
after a few seconds laptop suspends (fan stopped, keyboard lights turned off). 
Pressing space on a keyboard wakes it up.

  MSI GL72 7RD, nvidia drivers installed 390.87, X11 ubuntu desktop
  session selected in login screen.

  Could be resolved if sleep is disabled on systemd side:
  sudo systemctl mask sleep.target suspend.target hibernate.target 
hybrid-sleep.target

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

-- 
Mailing list: https://launchpad.net/~desktop-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 contents revealed briefly on resume, before even unlocking

2019-01-10 Thread Dan Dascalescu
I still see this issue in a configuration very similar to comment #33:

* ThinkPad X1 Carbon 6th Gen with integrated Intel Graphics
* Ubuntu 18.04.1 fresh install

-- 
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 contents revealed briefly on resume, before even unlocking

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

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

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

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  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

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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 1795342] Re: High Power Consumption

2019-01-10 Thread Daniel van Vugt
Some notable CPU users from that file:

16:57   0:42 /usr/lib/snapd/snapd
16:57   3:01 /usr/sbin/preload -s /var/lib/preload/preload.state
16:57   0:30 [irq/125-iwlwifi]   <---  this is the Intel Wifi driver
16:57   0:21 /usr/bin/tor --defaults-torrc 
/usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
16:58   0:30 /usr/bin/gnome-shell

But I can't see any very high power users so maybe we're looking in the
wrong place. And maybe we need to be more scientific about this...

To be more scientific about the problem we need to display the current
power usage in watts. You can do that using either 'sudo powertop' or in
the Power Statistics app looking at your battery information.

Next, now that you can see the exact power usage watts, try changing
things like running a different shell. For example Unity:  sudo apt
install unity-session

You may also then want to try different kernel versions (older and newer) and 
compare the power usage of those:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

Title:
  High Power Consumption

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.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-power-consumption/+bug/1795342/+subscriptions

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


[Desktop-packages] [Bug 1591535] Re: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds.

2019-01-10 Thread Daniel van Vugt
** Description changed:

+ https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618
+ 
+ ---
+ 
  My built-in internal mic on my Toshiba Satellite-A215 will not pick up
  sounds. The external speakers work just fine, but once again the mic
  can't record any sounds. I have an Ubuntu 14.04.4 LTS.
  
  Below is a link of my ALSA "info" that may be useful:
  
  http://www.alsa-
  project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d
  
  I've tried the ALSA DKMS update recommended to me by an ubuntuforums.org
  user from this link:
  
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
  
  However after following the instructions from the above link, the mic
  still has not worked.
  
  The same Ubuntu forum user suggested I file a bug. He/she provided me
  with a link from "an old report from an A215 with the same ALC268
  codec":
  
  https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353
  
  I provided this because it may be helpful in the debug process.
  
  The version of ALSA I have is shown below:
  Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic.
  
  Any help would be appreciated, please let me know if you need any
  additional info.
  
- PS 
+ PS
  I've also provided a link below of the ongoing forum discussion I've been 
having at ubuntuforums.org below:
  
  http://ubuntuforums.org/showthread.php?t=2323851
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  richard1533 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  richard1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jun 11 10:49:01 2016
  InstallationDate: Installed on 2016-01-06 (156 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  richard1533 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  richard1533 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.10
  dmi.board.name: IALAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.10:bd05/23/2007:svnTOSHIBA:pnSatelliteA215:pvrPSAEGU-01700U:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite A215
  dmi.product.version: PSAEGU-01700U
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-06T05:53:22.078529

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

Title:
  [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My
  built-in internal mic won't record sounds.

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618

  ---

  My built-in internal mic on my Toshiba Satellite-A215 will not pick up
  sounds. The external speakers work just fine, but once again the mic
  can't record any sounds. I have an Ubuntu 14.04.4 LTS.

  Below is a link of my ALSA "info" that may be useful:

  http://www.alsa-
  project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d

  I've tried the ALSA DKMS update recommended to me by an
  ubuntuforums.org user from this link:

  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

  However after following the instructions from the above link, the mic
  still has not worked.

  The same Ubuntu forum user suggested I file a bug. He/she provided me
  with a link from "an old report from an A215 with the same ALC268
  codec":

  https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353

  I provided this because it may be helpful in the debug process.

  The version of ALSA I have is shown below:
  Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic.

  Any help would be appreciated, please let me know if you need any
  additional info.

  PS
  I've also provided a link below of the ongoing forum discussion I've been 
having at ubuntuforums.org below:

  http://ubuntuforums.org/showthread.php?t=2323851

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  

[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode

2019-01-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201

One of the benefits of Launchpad over other bug trackers is that we can
spread a single bug over multiple components. And those different
components have different Status values within a single bug. Bug 1424201
does that.

/Sometimes/ separate bugs do get created for different components, but
in this particular case I think it is illustrative for all the
information about multiple browsers to be visible on a single page.

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

Title:
  Enable v4l2 hardware accelerated video decode

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

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

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


[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

2019-01-10 Thread Carlos Yanez
/metoo

>uname -a
Linux ubuntu-W520 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Unlocking the  screen takes 5 seconds in Xorg sessions (not so much in
  Wayland sessions)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-01-10 Thread Pe4enko
Should it work on ubuntu 18.10? I try to install 390 driver. After this i run 
command 
sudo prime-select nvidia and restart system. But GUI no work anymore. In kernel 
log i see errors.
My video card is geforce 750M

Jan 11 02:38:17 lblack kernel: [  121.613281] nvidia: loading out-of-tree 
module taints kernel.
Jan 11 02:38:17 lblack kernel: [  121.613290] nvidia: module license 'NVIDIA' 
taints kernel.
Jan 11 02:38:17 lblack kernel: [  121.613290] Disabling lock debugging due to 
kernel taint
Jan 11 02:38:17 lblack kernel: [  121.616641] nvidia: module verification 
failed: signature and/or required key missing - tainting kernel
Jan 11 02:38:17 lblack kernel: [  121.623093] nvidia-nvlink: Nvlink Core is 
being initialized, major device number 238
Jan 11 02:38:17 lblack kernel: [  121.623677] NVRM: loading NVIDIA UNIX x86_64 
Kernel Module  390.87  Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
Jan 11 02:38:17 lblack kernel: [  121.625479] NVRM: API mismatch: the client 
has the version 410.66, but
Jan 11 02:38:17 lblack kernel: [  121.625479] NVRM: this kernel module has the 
version 390.87.  Please
Jan 11 02:38:17 lblack kernel: [  121.625479] NVRM: make sure that this kernel 
module and all NVIDIA driver
Jan 11 02:38:17 lblack kernel: [  121.625479] NVRM: components have the same 
version.

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

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

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

  3) Update the list of packages:

  sudo apt-get update

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

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed 

[Desktop-packages] [Bug 1806385]

2019-01-10 Thread Raal
This seems to have begun at the below commit.
Adding Cc: to Andrzej J.R. Hunt ; Could you possibly take a look at this one?
Thanks

Implemented in this commit

bc2d7d4d0ac466a92703f7ba85cf75c19488aa70 is the first bad commit
commit bc2d7d4d0ac466a92703f7ba85cf75c19488aa70
Author: Matthew Francis 
Date:   Sat Sep 5 22:43:10 2015 +0800

source-hash-61a20e43b1ec7641bed073244c988e3ea981f086

commit 61a20e43b1ec7641bed073244c988e3ea981f086
Author: Andrzej J.R. Hunt 
AuthorDate: Sat Oct 26 17:10:52 2013 +0100
Commit: Caolán McNamara 
CommitDate: Fri Nov 8 10:25:49 2013 -0600

SlideSorter: insert new slide on double-click.

Previously inserting a new slide required using a context menu
(via right-click) or the main menu-bar. It is now possible
to insert a blank slide by double-clicking in an empty area
of the slide sorter.

Change-Id: Id7ac5f9d3befd02d0a89ad5e1631885c0493ad3d
Reviewed-on: https://gerrit.libreoffice.org/6442
Reviewed-by: Caolán McNamara 
Tested-by: Caolán McNamara 

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

Title:
  Creating a new slide by double click not working correctly

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

Bug description:
  Version: 6.1.3.2
  Build-ID: libreoffice-6.1.3.2-snap1

  You can create new slides in impress by double clicking on the empty
  part of the slides pane (below the existing slide). However, this
  works only as expected while the slides pane actually has empty space
  at the bottom.

  As soon as I have created a few slides, the slides pane is completely
  filled, and two things happen:

  (1) Improvement: It is very hard to double click on the thin white
  space at the bottom of the filled slides pane. This could be improved
  by always letting a few pixels at the bottom to click on.

  (2) Bug: You can actually manage to double click there and this
  creates a new slide. However, this new slide is not filed at the end
  of slides (as it should) but appears at a strange location somewhere
  in the middle of slides. This is definitely wrong.

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

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


[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2019-01-10 Thread Jesse
OK, I just experienced the issue again after resuming from suspend with
the new package installed. (Not sure whether the package version number
was updated for the candidate, but I'm using the one with SHA1
e51a7f3a77c2643714b9ca68b6707584c82784ce.)

I've attached the journalctl output.

There's a very faint chance I didn't restart yesterday after
reinstalling this package, but I've certainly restarted gnome-shell
quite a few times, so I'm fairly certain the problem is recurring even
with the fix.

Devs: please let me know if there's something else I can do to help test
or resolve this problem.

** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769383/+attachment/5228409/+files/journalctl.txt

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2019-01-10 Thread Kendon Bell
I am also seeing this problem:

```
[Jabra MOVE v2.5.0]# info 74:5C:4B:2A:E3:BE
Device 74:5C:4B:2A:E3:BE (public)
Name: Jabra MOVE v2.5.0
Alias: Jabra MOVE v2.5.0
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
[Jabra MOVE v2.5.0]# 
```

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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


[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2019-01-10 Thread Michel-Ekimia
FYI Fedora has now included the VAAPI

https://src.fedoraproject.org/rpms/chromium/c/278c62709d1dba5883c3b69047706837bb402bd7?branch=master

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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


[Desktop-packages] [Bug 955926] Re: No pop down menus on "Archivo Editar Ver Ir Ayuda" after fresh install

2019-01-10 Thread Tedesco
I don't know if the problem has been resolved by changes in the software or a 
new version results in a correct functionality.
If the fact that we reached end-of-life of the version 12.04, results in "no 
more action on software maintenance" the bug report could be closed without 
resolving the problem.
And this is not "Fix Released". Or "close the bug-report" always is indicated 
with "Fix Released".

Once again thank you very much to all the people working on ubuntu
I'm very happy with the ubuntu-server with KVM/QEMU libvirt

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

Title:
  No pop down menus on "Archivo Editar Ver Ir Ayuda" after fresh install

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  After "fresh install" you login with key ENTER to confirm.
  With the mouse over "Escritorio de Ubuntu" (top menu line) you get the change 
to "Archivo Editar Ver Ir Ayuda" menus.
  With a click on any of this menu items there is NO drop down menu visible. 
(no effect)

  Click on the ubuntu simble of the side menu, the corresponding
  "window" open, click outside of this "window" to close it.

  Now you will get the pop down menus mentioned before.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.91-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Thu Mar 15 12:23:50 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120315)
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 841821] Re: Color manager shows [invalid UTF-8]

2019-01-10 Thread Sebastien Bacher
the bug has seen no activity in years and upstream closed, doing the
same, feel free to reopen a bug if you still get issues in newer
versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Color manager shows [invalid UTF-8]

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Settings manager -> Color -> monitor name shows with invalid UTF-8:

  [Invalid UTF-8] - VBOX monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  Date: Mon Sep  5 16:30:41 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (3 days ago)

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

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


[Desktop-packages] [Bug 863425] Re: Running system-settings again sometimes does not bring existing window to foreground

2019-01-10 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: gnome-control-center (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Running  system-settings again sometimes does not bring existing
  window to foreground

Status in gnome-control-center:
  Unknown
Status in compiz package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in compiz source package in Oneiric:
  Invalid
Status in gnome-control-center source package in Oneiric:
  Won't Fix
Status in compiz source package in Precise:
  Invalid
Status in gnome-control-center source package in Precise:
  Won't Fix

Bug description:
  Testing with Oneiric 11.10 I have found that if I have the system-
  settings window already open then clicking the indicator menu item
  'System-Settings...' does not bring the existing window to the
  foreground.

  It does work as expected if you simply open system-settings and then
  change focus to another open window but if you open any of the options
  then it stops working.

  gnome-control-center:  1:3.2.0-0ubuntu3

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

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


[Desktop-packages] [Bug 1810168] Re: Move the Keyboard repeat settings back to the Keyboard settings

2019-01-10 Thread Dan Dascalescu
Already reported at https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/79

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

Title:
  Move the Keyboard repeat settings back to the Keyboard settings

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I've just installed Ubuntu 18.04 and wanted to set the keyboard repeat
  delay and speed. So I type "Keyboard", hoping to land in the same
  place I would on Ubuntu 16, but the Keyboard settings in 18 only have
  shortcuts. Huh?

  I had to Google "how to set the keyboard repeat rate Ubuntu 18", which
  is already a big red flag.

  I'm sure there was a reason for that setting to be moved under
  "Universal Access", but was there a user acceptance test? Maybe it
  makes some logical or architectural sense to have Keyboard Repeat
  Settings under "Universal Access", but to me and to many other
  users[1] it makes no sense at all.

  To quote one user:

  "Great UI design. Why would you put keyboard settings in
  Settings->Keyboard? Haha that'd be stupid! We should hide them in
  accessibility under what looks like a toggle-button but isn't
  instead... Edit: Speed is backwards? Oh my god someone *designed*
  this??"

  [1]: https://askubuntu.com/questions/846030/how-to-set-keyboard-
  repeat-delay-and-speed-in-ubuntu-gnome-16-10

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

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


[Desktop-packages] [Bug 868018] Re: "Suspend when inactive for.." doesn't actually suspend

2019-01-10 Thread Sebastien Bacher
that's an old bug without activity in years, closing, feel free to open
a new report if you have issues in newer versions though

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

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

Title:
  "Suspend when inactive for.." doesn't actually suspend

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

Bug description:
  1. Ubuntu 11.10 Beta 2
  2. gnome-control-center 1:3.2.0-0ubuntu4
  3. Under Power I expect the "Suspend when inactive for.." value to do pretty 
much what it says it'll do. I've been on battery power, and the Battery Power 
option set to 5 minutes, and it doesn't suspend when I leave it sitting. 
Overnight I had it set to "Never" When Plugged In, and I'd wake up with it 
suspended.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Tue Oct  4 21:09:59 2011
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-29 (5 days ago)
  usr_lib_gnome-control-center:
   deja-dup   20.0-0ubuntu3
   gnome-bluetooth3.2.0-0ubuntu1
   indicator-datetime 0.3.0-0ubuntu1

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

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


[Desktop-packages] [Bug 599783] Re: proxy capplet is not IPv6 aware

2019-01-10 Thread Sebastien Bacher
The issue has been fixed in newer versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  proxy capplet is not IPv6 aware

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-control-center

  Entering valid ipv6 address's in the network proxy settings form
  fields results in truncation at first instance of colon, feild parser
  needs to be rewritten to support v6 address's.

  i.e [ c001:d00d:dead:feed::1]:3128

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-control-center 1:2.30.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-4.5-generic-pae 2.6.35-rc3
  Uname: Linux 2.6.35-4-generic-pae i686
  Architecture: i386
  Date: Wed Jun 30 00:49:24 2010
  ExecutablePath: /usr/bin/gnome-network-properties
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1407): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-terminal:1678): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed

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

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


[Desktop-packages] [Bug 1233498] Re: [region]: gnome-control-center crashed with SIGSEGV in append_sections_from_gsettings()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [region]: gnome-control-center crashed with SIGSEGV in
  append_sections_from_gsettings()

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

Bug description:
  Happened when using Libreoffice

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu40
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  1 08:18:11 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-07-27 (65 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f99b524d13e:mov(%rax),%rdi
   PC (0x7f99b524d13e) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libregion.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libregion.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: [region]: gnome-control-center crashed with SIGSEGV in 
gdk_display_get_event()
  UpgradeStatus: Upgraded to saucy on 2013-09-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1

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

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


[Desktop-packages] [Bug 1234304] Re: gnome-control-center crashed with SIGSEGV in update_outputs()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in update_outputs()

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

Bug description:
  ubuntustudio 13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu40
  ProcVersionSignature: Ubuntu 3.11.0-2.1-lowlatency 3.11.0-rc5
  Uname: Linux 3.11.0-2-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 15:42:40 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-08-28 (35 days ago)
  InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Alpha amd64 
(20130824)
  MarkForUpload: True
  ProcCmdline: gnome-control-center deja-dup
  SegvAnalysis:
   Segfault happened at: 0x7fdebfeea146:mov0x10(%rbx),%ecx
   PC (0x7fdebfeea146) ok
   source "0x10(%rbx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.12
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.12
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.12
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.12
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev pulse 
pulse-access sambashare scanner sudo video

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

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


[Desktop-packages] [Bug 1228481] Re: [color]: gnome-control-center crashed with SIGSEGV in gcm_prefs_remove_device()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [color]: gnome-control-center crashed with SIGSEGV in
  gcm_prefs_remove_device()

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

Bug description:
  I just was using the Gnome Control Center and suddenly, it crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu38
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 21 04:30:03 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-09-14 (371 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f23bdd369ba:mov0x38(%r14),%rdi
   PC (0x7f23bdd369ba) ok
   source "0x38(%r14)" (0xaae2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libcolor.so
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [color]: gnome-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to saucy on 2013-09-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers www-data
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1

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

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


[Desktop-packages] [Bug 1231403] Re: gnome-control-center crashed with SIGSEGV in do_winsys_init()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in do_winsys_init()

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

Bug description:
  unkown cause

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu38
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 26 21:39:07 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-22 (96 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f537aeed549 : mov
(%rax),%r8d
   PC (0x7f537aeed549) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   radeon_drm_winsys_create () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: gnome-control-center crashed with SIGSEGV in radeon_drm_winsys_create()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1225193] Re: [color]: gnome-control-center crashed with SIGSEGV in gcm_prefs_add_device()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [color]: gnome-control-center crashed with SIGSEGV in
  gcm_prefs_add_device()

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

Bug description:
  i accessed backup section from settings , chose some fetures and
  suddently the system was crashed for 2 minutes

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu36
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Fri Sep 13 23:52:13 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-13 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f06128f26fc:mov0x18(%r13),%rsi
   PC (0x7f06128f26fc) ok
   source "0x18(%r13)" (0xaac2) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libcolor.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libcolor.so
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [color]: gnome-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 8357] Re: Allow to set DPI resolution

2019-01-10 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Allow to set DPI resolution

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  Computer -> System Configuration -> Screen Resolution should not only allow to
  set widht, height, and frequency, but also the physical resolution of the
  monitor. A friend of mine got 1600x1200 as default resolution, which makes
  characters far too small to be readable.

  Instead of specifying a DPI number directly (which is somewhat abstract), 
there
  should be two rulers displayed; either the user measures them with a "hardware
  ruler" and enters the lengths of the displayed rulers (much like GIMP does), 
or
  there is a slider for each direction which scale the displayed rulers until 
they
  match the hardware ruler.

  http://bugzilla.gnome.org/show_bug.cgi?id=153634:
  http://bugzilla.gnome.org/show_bug.cgi?id=153634

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

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


[Desktop-packages] [Bug 1520984] Re: Replace Software Updater with built-in version - feature request

2019-01-10 Thread Sebastien Bacher
The features requests like that make more sense upstream, Ubuntu isn't
going to add that in a distribution specific way

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Replace Software Updater with built-in version - feature request

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  As everything else is more or less built-into the GNOME Control Center
  it would be really good if the Software Updater was replaced with a
  built-in one which is built-into the GNOME Control Center. I am
  running Ubuntu GNOME 15.10 with GNOME 3.18.

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

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


[Desktop-packages] [Bug 1235979] Re: gnome-control-center crashed with SIGSEGV in gnome_control_center_show()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  gnome_control_center_show()

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

Bug description:
  __---

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu41
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Oct  6 16:30:22 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-10-01 (5 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x8050d76 :  mov
0x10(%ebx),%eax
   PC (0x08050d76) ok
   source "0x10(%ebx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Stacktrace:
   #0  0x08050d76 in gnome_control_center_show ()
   No symbol table info available.
   #1  0x0804d80a in _start ()
   No symbol table info available.
  StacktraceTop:
   gnome_control_center_show ()
   _start ()
  Title: gnome-control-center crashed with SIGSEGV in 
gnome_control_center_show()
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131004-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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


[Desktop-packages] [Bug 1235773] Re: [printers]: gnome-control-center crashed with SIGSEGV in __GI___libc_free()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  __GI___libc_free()

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

Bug description:
  attempt to install this printer : samsung SCX-3405.
  it's reconize materially but installation crashed with gnome-control-center 
in Printer Tab

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu41
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 22:23:52 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-08-27 (39 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130826)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f5bb370691c <__GI___libc_free+28>:  mov
-0x8(%rdi),%rax
   PC (0x7f5bb370691c) ok
   source "-0x8(%rdi)" (0xfffb) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x3) at malloc.c:2892
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_widget_path_unref () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
__GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1325274] Re: Wacom Control Panel GUI doesn't work on Xubuntu 14.04

2019-01-10 Thread Sebastien Bacher
old bug without recent activity, closing

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: In Progress => Invalid

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Invalid

** Changed in: wacom-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Wacom Control Panel GUI doesn't work on Xubuntu 14.04

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in wacom-tools package in Ubuntu:
  Invalid

Bug description:
  Wacom Control Panel doesn't work at all with Xubuntu 14.04 LTS (it's
  not available in the Settings even if 'Wacom Tablet' package is
  installed)

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

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


[Desktop-packages] [Bug 1031474] Re: add a option to define the preferred instant messaging app

2019-01-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  add a option to define the preferred instant messaging app

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I would like to have an additional field in the part where the preferred apps 
are set for:
  * RSS app
  * Podcast app
  * Twitter app (Gwibber is just buggy)

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

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


[Desktop-packages] [Bug 1232480] Re: [printers]: gnome-control-center crashed with SIGSEGV in memset()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in memset()

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

Bug description:
  Can't add printer because it won't install.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu39
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 17:05:23 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-25 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f37bf2f78b6 <__memset_sse2+230>:mov
%rdx,-0x10(%rdi)
   PC (0x7f37bf2f78b6) ok
   source "%rdx" ok
   destination "-0x10(%rdi)" (0x7f37c0ee6664) in non-writable VMA region: 
0x7f37c0b4-0x7f37c1007000 r-xp /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.800.4
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.800.4
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 947323] Re: nm-applet should change icon to indicate Airplane Mode

2019-01-10 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  nm-applet should change icon to indicate Airplane Mode

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  When an ubuntu user enables "Airplane Mode" (System Settings >
  Network: Airplane Mode = On), the Network Status Indicator should
  change its appearance/icon to indicate that this special mode is
  enabled. Perhaps it should change to the icon of an airplane.

  The user needs some form of communication (some form of indication) of
  the Airplane Mode status in the panel.

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

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


[Desktop-packages] [Bug 1031474] Re: add a option to define the preferred instant messaging app

2019-01-10 Thread Sebastien Bacher
The features requests like that make more sense upstream, Ubuntu isn't
going to add that in a distribution specific way

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  add a option to define the preferred instant messaging app

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I would like to have an additional field in the part where the preferred apps 
are set for:
  * RSS app
  * Podcast app
  * Twitter app (Gwibber is just buggy)

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

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


[Desktop-packages] [Bug 1521778] Re: gnome-control-center.real crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center.real crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  crashed when opening the mouse panel

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Dec  2 09:02:34 2015
  ExecutablePath: /usr/bin/gnome-control-center.real
  ExecutableTimestamp: 1448432673
  InstallationDate: Installed on 2012-09-23 (1164 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  ProcCmdline: /usr/bin/gnome-control-center.real --overview
  ProcCwd: /home/darkness
  SegvAnalysis:
   Segfault happened at: 0x7f6b3a03f920 :
mov(%r10),%rbp
   PC (0x7f6b3a03f920) ok
   source "(%r10)" (0x0005) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast (type_instance=0x18082b0, iface_type=80) at 
/build/glib2.0-ZjeN9o/glib2.0-2.47.1/./gobject/gtype.c:4065
   () at /usr/lib/x86_64-linux-gnu/libupower-glib.so.3

(instance=instance@entry=0x1bd82b0, signal_id=, 
detail=) at 
/build/glib2.0-ZjeN9o/glib2.0-2.47.1/./gobject/gsignal.c:3439
   g_object_dispatch_properties_changed (object=0x1bd82b0 [UpClientGlueProxy], 
n_pspecs=, pspecs=) at 
/build/glib2.0-ZjeN9o/glib2.0-2.47.1/./gobject/gobject.c:1061
   g_object_notify (pspec=0x113dde0 [GParamString], object=0x1bd82b0 
[UpClientGlueProxy]) at 
/build/glib2.0-ZjeN9o/glib2.0-2.47.1/./gobject/gobject.c:1154
  Title: gnome-control-center.real crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo systemd-journal www-data

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

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


[Desktop-packages] [Bug 1235141] Re: gnome-control-center assert failure: gnome-control-center: tpp.c:65: __pthread_tpp_change_priority: asserzione \"previous_prio == -1 || (previous_prio >= __sched_f

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center assert failure: gnome-control-center: tpp.c:65:
  __pthread_tpp_change_priority: asserzione \"previous_prio == -1 ||
  (previous_prio >= __sched_fifo_min_prio && previous_prio <=
  __sched_fifo_max_prio)\" non riuscita.

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

Bug description:
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10
  gnome-control-center:
Installato: 1:3.6.3-0ubuntu41
Candidato:  1:3.6.3-0ubuntu41
Tabella versione:
   *** 1:3.6.3-0ubuntu41 0
  500 http://it.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu41
  Uname: Linux 3.11.3-031103-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AssertionMessage: gnome-control-center: tpp.c:65: 
__pthread_tpp_change_priority: asserzione \"previous_prio == -1 || 
(previous_prio >= __sched_fifo_min_prio && previous_prio <= 
__sched_fifo_max_prio)\" non riuscita.
  Date: Fri Oct  4 10:28:23 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2011-10-02 (732 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __assert_fail_base (fmt=0xb6290eee , 
assertion=assertion@entry=0xb6cb7738 "previous_prio == -1 || (previous_prio >= 
__sched_fifo_min_prio && previous_prio <= __sched_fifo_max_prio)", 
file=file@entry=0xb6cb76b8 "tpp.c", line=line@entry=65, 
function=function@entry=0xb6cb76be <__PRETTY_FUNCTION__.8004> 
"__pthread_tpp_change_priority") at assert.c:92
   __GI___assert_fail (assertion=assertion@entry=0xb6cb7738 "previous_prio == 
-1 || (previous_prio >= __sched_fifo_min_prio && previous_prio <= 
__sched_fifo_max_prio)", file=file@entry=0xb6cb76b8 "tpp.c", 
line=line@entry=65, function=function@entry=0xb6cb76be 
<__PRETTY_FUNCTION__.8004> "__pthread_tpp_change_priority") at assert.c:101
   __pthread_tpp_change_priority (previous_prio=previous_prio@entry=318, 
new_prio=new_prio@entry=-1) at tpp.c:63
   __pthread_mutex_unlock_full (mutex=0x9c1fd60, decr=) at 
pthread_mutex_unlock.c:281
   __gmon_start__@plt ()
  Title: gnome-control-center assert failure: gnome-control-center: tpp.c:65: 
__pthread_tpp_change_priority: asserzione \"previous_prio == -1 || 
(previous_prio >= __sched_fifo_min_prio && previous_prio <= 
__sched_fifo_max_prio)\" non riuscita.
  UpgradeStatus: Upgraded to saucy on 2013-10-03 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1232485] Re: [printers]: gnome-control-center crashed with SIGSEGV in magazine_chain_pop_head()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  magazine_chain_pop_head()

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

Bug description:
  Adding new printer causes crash. Cannot add a new printer. Continually
  crashes every time I attempt to add new printer.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu39
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Sep 28 09:38:07 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-22 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f525162e9c7 :mov
(%rbx),%rax
   PC (0x7f525162e9c7) ok
   source "(%rbx)" (0x656c6269736976) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape vboxusers video
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1589052] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The issue is similar to https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/93 which has been fixed in 3.30 and indeed
https://errors.ubuntu.com/problem/1f92fe5794bfb1ca26fd9d7b1a974953f3a4da21
shows no report for that version

(note that restarting network-manager is not a normal use scenario and
not that common so it doesn't really qualify as a SRU candidate at this
point)

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  1. Open the network panel in g-c-c
  2. Run `sudo service network-manager restart`

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Jun  4 03:00:24 2016
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-05-19 (381 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc283b5691b :
movzbl 0x16(%rdx),%eax
   PC (0x7fc283b5691b) ok
   source "0x16(%rdx)" (0x7001e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" 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
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () 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 xenial on 2016-04-23 (41 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sbuild sudo

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

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


[Desktop-packages] [Bug 1230415] Re: [printers]: gnome-control-center crashed with SIGSEGV in magazine_chain_pop_head()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  magazine_chain_pop_head()

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

Bug description:
  gnome settings crash when I try to install my printer

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu38
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 25 18:59:28 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-21 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130919)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=it:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdbb19c5ad7 :mov
(%rbx),%rax
   PC (0x7fdbb19c5ad7) ok
   source "(%rbx)" (0x202000646c696863) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1233835] Re: [printers]: gnome-control-center crashed with SIGSEGV in g_slist_append()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  g_slist_append()

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

Bug description:
  Ubuntu GNOME 13.10
  Gnome 3.8.4
  No PPAs
  Fully updated (Tues Oct 1, 2013)

  Whenever I try to add a network printer, the entire system settings
  menu crashes without warning.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu39
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct  1 16:13:03 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-10-01 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 
(20130930)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0225062ca9 :mov
%rbp,(%rax)
   PC (0x7f0225062ca9) ok
   source "%rbp" ok
   destination "(%rax)" (0x7f02266d3998) in non-writable VMA region: 
0x7f02262ef000-0x7f02267b6000 r-xp /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.800.4
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.800.4
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slist_append () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_object_class_install_property () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slist_append()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1271896] Re: add gnome-session-properties to control-center

2019-01-10 Thread Sebastien Bacher
The features requests like that make more sense upstream, Ubuntu isn't
going to add that in a distribution specific way

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  add gnome-session-properties to control-center

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  Please add gnome-session-properties to gnome(unity)-control-center

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu50
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 23 13:20:57 2014
  InstallationDate: Installed on 2014-01-05 (17 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2014-01-06 (17 days ago)

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

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


[Desktop-packages] [Bug 1224202] Re: [color]: gnome-control-center crashed with SIGSEGV in gcm_prefs_device_changed_cb()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [color]: gnome-control-center crashed with SIGSEGV in
  gcm_prefs_device_changed_cb()

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

Bug description:
  This occurred just after I downloaded and imported a colour profile
  from System76.  It seems to have imported the profile, but did not
  enable it - re-visiting the settings pane and enabling the profile
  succeeded.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu36
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Thu Sep 12 01:22:45 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-11 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f38ae2acb95:mov0x38(%rdx),%rdi
   PC (0x7f38ae2acb95) ok
   source "0x38(%rdx)" (0xaae2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libcolor.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libcolord.so.1
  Title: [color]: gnome-control-center crashed with SIGSEGV in 
g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1237899] Re: gnome-control-center crashed with SIGSEGV in thread_memory_magazine2_free()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  thread_memory_magazine2_free()

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

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu41
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Fri Oct  4 16:41:06 2013
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1380729441
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  ProcCwd: /home/yura
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=uk_UA:en
   PATH=(custom, user)
   LANG=uk_UA.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb6cf5203 :movl   
$0x0,0x4(%ebp)
   PC (0xb6cf5203) ok
   source "$0x0" ok
   destination "0x4(%ebp)" (0x0047) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_free1 () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_slice_free1()
  UpgradeStatus: Upgraded to saucy on 2013-10-04 (0 days ago)
  UserGroups: adm admin cdrom debian-tor dialout dip fax floppy fuse libvirtd 
lpadmin plugdev sambashare tape video
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1

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

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


[Desktop-packages] [Bug 1233401] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in g_type_check_instance()

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

Bug description:
  Failed when I was changing security to shut off logging

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu40
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 30 17:44:32 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-29 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f07cccd45b9 : mov
(%rax),%rdi
   PC (0x7f07cccd45b9) ok
   source "(%rax)" (0x30007400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm barry cdrom dip lpadmin plugdev sambashare staff sudo users 
util
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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


[Desktop-packages] [Bug 340422] Re: introduce automatic antialiasing/hinting mode and make gnome honour fontconfig

2019-01-10 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: gtk+2.0 (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  introduce automatic antialiasing/hinting mode and make gnome honour
  fontconfig

Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix
Status in gtk+2.0 package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gnome-settings-daemon

  this bug is forked from bug 332172

  Currently gtk and settings daemon override the fontconfig default wrt
  to hinting/antialiasing by setting xdefaults: Xft/*

  The fix involves:
   1. make gtk honour the monitor settings (which are already detected by cairo 
and libxft2 atm) if we are in "automatic" mode.
   2. make gnome-settings-daemon aware of automatic mode and stop setting the 
Xft/* overrides if automatic mode is used
   3. add UI to opt-out from automatic mode in font appearence dialog of 
gnome-control-center.

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

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


[Desktop-packages] [Bug 1235839] Re: [display]: gnome-control-center crashed with SIGABRT in _g_log_abort()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [display]: gnome-control-center crashed with SIGABRT in _g_log_abort()

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

Bug description:
  trying to open system settings and it keeps crashing - please let me
  know if you need help / additional detals

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu41
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  5 21:05:05 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-07-28 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac 
(20130725)
  MarkForUpload: True
  ProcCmdline: gnome-control-center display
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gnome_rr_config_load_current () from /usr/lib/libgnome-desktop-3.so.7
   gnome_rr_config_new_current () from /usr/lib/libgnome-desktop-3.so.7
  Title: [display]: gnome-control-center crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131004-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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


[Desktop-packages] [Bug 1029965] Re: Add chat client selection

2019-01-10 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1031474 ***
https://bugs.launchpad.net/bugs/1031474

** This bug has been marked a duplicate of bug 1031474
   add a option to define the preferred instant messaging app

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

Title:
  Add chat client selection

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

Bug description:
  This is almost but not quite an enhancement request.

  I'm tripping over bugs in Empathy that I don't encounter with Pidgin.
  I'd like Pidgin to be the default chat client, at least until I can
  get those bugs resolved.  Currently control panel doesn't offer a way
  to make that switch.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.3
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  Date: Fri Jul 27 10:23:01 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to precise on 2012-05-01 (87 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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


[Desktop-packages] [Bug 1238821] Re: [printers]: gnome-control-center crashed with SIGSEGV in magazine_chain_pop_head() while trying to install a network printer

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  magazine_chain_pop_head() while trying to install a network printer

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

Bug description:
  Tryed to install an Epson Stylus Photo PX830 connected via LAN. Printer 
Manager found printer and i clicked install.  Then i have seen the printer 
overview with the text "Installing Printer" in Status field. Then the 
control-center chrashed.
  I tried this several times and it always happens. Also after a few reboots.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu43
  ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct 11 17:35:24 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-30 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: gnome-control-center printers
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6b285359c7 :mov
(%rbx),%rax
   PC (0x7f6b285359c7) ok
   source "(%rbx)" (0x0055) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_widget_path_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1232566] Re: [keyboard]: gnome-control-center crashed with SIGSEGV in g_strdup()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [keyboard]: gnome-control-center crashed with SIGSEGV in g_strdup()

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

Bug description:
  I opened gnome-control-center on the Saucy final beta and it crashed
  with the above error. Backtrace and other apport data attached.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu39
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 17:24:25 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-03 (268 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: gnome-control-center keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fb65ee5d5f1 <__strlen_sse2_pminub+17>:  movdqu 
(%rdi),%xmm1
   PC (0x7fb65ee5d5f1) ok
   source "(%rdi)" (0x000a) not located in a known VMA region 
(needed readable region)!
   destination "%xmm1" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
  Title: [keyboard]: gnome-control-center crashed with SIGSEGV in g_strdup()
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild src sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130924.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1

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

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


[Desktop-packages] [Bug 1107662] Re: Cannot add week number to calendar

2019-01-10 Thread Sebastien Bacher
The features requests like that make more sense upstream, Ubuntu isn't
going to add that in a distribution specific way

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot add week number to calendar

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  In Ubuntu 12.04 LTS, week numbers cannot be added to the gnome
  calendar.

  When you try to date and time panel in settings you don't have that
  option. This can be seen in the screenshot of the question at:

  http://askubuntu.com/questions/182489/how-do-i-enable-week-numbers-in-
  calendar-applet-when-settings-are-missing

  
  Please re-enable calendar week numbering.

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

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


[Desktop-packages] [Bug 808512] Re: No way to configure screensaver

2019-01-10 Thread Sebastien Bacher
The features requests like that make more sense upstream, Ubuntu isn't
going to add that in a distribution specific way

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  No way to configure screensaver

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  There is no UI to configure the screensaver hack in Oneiric.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
  Uname: Linux 3.0-3-generic i686
  Architecture: i386
  Date: Sun Jul 10 23:15:37 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-06-27 (13 days ago)

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

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


[Desktop-packages] [Bug 1631434] Re: gnome-control-center crashed with SIGSEGV in _cogl_check_extension()

2019-01-10 Thread Sebastien Bacher
** Package changed: gnome-control-center (Ubuntu) => cogl (Ubuntu)

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

Title:
  gnome-control-center crashed with SIGSEGV in _cogl_check_extension()

Status in cogl package in Ubuntu:
  Confirmed

Bug description:
  I tried to open the gnome settings application in the latest version
  of ubuntu gnome 16.10, and the tab came up along the top window, but
  then no window opened and the crash report generator came up.

  output of lsb_release -rd:

  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  version of package I'm using:

  apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.20.1-2ubuntu3
Candidate: 1:3.20.1-2ubuntu3
Version table:
   *** 1:3.20.1-2ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu yakkety/universe amd64 
Packages
  100 /var/lib/dpkg/status

  What I expected to happen:

  I expected the settings window to open

  What actually happened:

  The window tab at the top showed up, and the mouse cursor turned into
  the working circle symbol, the window didn't open.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-control-center 1:3.20.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 12:28:35 2016
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-10-07 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fab239edb59:mov(%rsi),%rsi
   PC (0x7fab239edb59) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 972349] Re: [network]: gnome-control-center crashed with SIGSEGV in __GI___libc_free()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  __GI___libc_free()

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

Bug description:
  [network]: gnome-control-center crashed with SIGSEGV in
  __GI___libc_free()

  Try open gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic i686
  ApportVersion: 2.0-0ubuntu3
  Architecture: i386
  Date: Tue Apr  3 14:56:27 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100913)
  ProcCmdline: gnome-control-center --overview
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
__GI___libc_free()
  UpgradeStatus: Upgraded to precise on 2012-03-21 (13 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-control-center/+bug/972349/+subscriptions

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


[Desktop-packages] [Bug 1093130] Re: [printers]: gnome-control-center crashed with SIGSEGV in jobs_dialog_response_cb()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  jobs_dialog_response_cb()

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

Bug description:
  On using the "close" button in

  System Settings -> Printers -> jobs

  the program crashed.

  Steps to reproduce(not tested):

  1.Send a print job from firefox(html)
  2.Send a second print job from evince(pdf)
  3.Call System Settings -> Printers -> Jobs
  4.Try to stop the second not started print job with the buttons for that
  5.See that failing
  6.Have a not wanted print.
  7.Switch off the power of the printer
  8.Use the close button in the job dialog
  9.Have the crasher

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sat Dec 22 17:11:21 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-07-22 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fba28e64734:mov0x78(%rax),%rdi
   PC (0x7fba28e64734) ok
   source "0x78(%rax)" (0x0078) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libprinters.so
   g_closure_invoke (closure=0x7fba5253b220, return_value=0x0, 
n_param_values=2, param_values=0x7fffce4b1ab0, invocation_hint=0x7fffce4b1a50) 
at /build/buildd/glib2.0-2.34.3/./gobject/gclosure.c:777
   signal_emit_unlocked_R (node=node@entry=0x7fba52043670, 
detail=detail@entry=0, instance=instance@entry=0x7fba5251e220, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffce4b1ab0) at 
/build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3551
   g_signal_emit_valist (instance=0x7fba5251e220, signal_id=, 
detail=0, var_args=var_args@entry=0x7fffce4b1d08) at 
/build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3300
   g_signal_emit (instance=, signal_id=, 
detail=) at /build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3356
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_closure_invoke()
  UpgradeStatus: Upgraded to raring on 2012-11-15 (36 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   indicator-datetime  12.10.3daily12.11.23-0ubuntu1

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

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


[Desktop-packages] [Bug 1070858] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in active_input_update()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [soundnua]: gnome-control-center crashed with SIGSEGV in
  active_input_update()

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

Bug description:
  If I launch the Sound properties via the dash, sound menu, or gnome-
  control-center, the window shows for a short period before crashing. I
  have tried with a new user account. I have tried purging and then
  reinstalling pulseaudio.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct 24 11:16:06 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: gnome-control-center sound-nua
  ProcCwd: /home/andrew
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0a09bfb9f2 :  mov%eax,-0x528(%rbp)
   PC (0x7f0a09bfb9f2) ok
   source "%eax" ok
   destination "-0x528(%rbp)" (0x7fff885d1f98) not located in a known VMA 
region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
   g_cclosure_marshal_VOID(unsigned int0_t, void) () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [soundnua]: gnome-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID()
  UpgradeStatus: Upgraded to quantal on 2012-08-19 (65 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo vboxusers
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3

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

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


[Desktop-packages] [Bug 1034321] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

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

Bug description:
  I tried to add a Facebook account to GNOME Online Accounts.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Wed Aug  8 12:07:32 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.0
  Title: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-04-17 (112 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-control-center/+bug/1034321/+subscriptions

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


[Desktop-packages] [Bug 1219993] Re: [sound]: gnome-control-center assert failure: *** Error in `gnome-control-center': double free or corruption (fasttop): 0x0000000001683200 ***

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [sound]: gnome-control-center assert failure: *** Error in `gnome-
  control-center': double free or corruption (fasttop):
  0x01683200 ***

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

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu33
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `gnome-control-center': double free or 
corruption (fasttop): 0x01683200 ***
  Date: Tue Sep  3 01:39:29 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-02 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130902.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f5516f776a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x1683200, str=0x7f5516f77868 "double free or 
corruption (fasttop)", action=3) at malloc.c:4902
   _int_free (av=, p=0x16831f0, have_lock=0) at malloc.c:3758
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libsound.so
   g_cclosure_marshal_VOID__STRINGv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [sound]: gnome-control-center assert failure: *** Error in 
`gnome-control-center': double free or corruption (fasttop): 0x01683200 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1051531] Re: [bluetooth]: trying to browse files via bluetooth on my nokia 6300s, segfault in device_changed()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [bluetooth]: trying to browse files via bluetooth on my nokia 6300s,
  segfault in device_changed()

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

Bug description:
  Connected device, clicked on Browse Files on the panel bluetooth
  applet, and voila!

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Sun Sep 16 19:19:23 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6d729ca :  mov
(%esi),%eax
   PC (0xb6d729ca) ok
   source "(%esi)" (0x1e1e1e1e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_instance_get_private () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgnome-bluetooth.so.11
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_instance_get_private()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.15-0ubuntu2
   indicator-datetime  12.10.0-0ubuntu2

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

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


[Desktop-packages] [Bug 1160116] Re: [printers]: gnome-control-center crashed with SIGSEGV in magazine_chain_pop_head()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  magazine_chain_pop_head()

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

Bug description:
  Installed 64-bit drivers for Lexmark Prospect Pro 205 printer. Trying
  to set up printer when crash occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar 25 20:39:46 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130325)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fcbcc4190cf :mov
(%rbx),%rax
   PC (0x7fcbcc4190cf) ok
   source "(%rbx)" (0x37887c74800) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1

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

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


[Desktop-packages] [Bug 975404] Re: gnome-control-center crashed with SIGSEGV in _dbus_pthread_mutex_lock()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _dbus_pthread_mutex_lock()

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

Bug description:
  trying to connect my Nokia E7 via bluetooth

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 03:01:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcCmdline: gnome-control-center bluetooth
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: gnome-control-center crashed with SIGSEGV in dbus_connection_get_data()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1035653] Re: gnome-control-center crashed with SIGSEGV in dun_cleanup()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in dun_cleanup()

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

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu8
  Uname: Linux 3.6.0-030600rc1-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  CrashCounter: 1
  Date: Sat Aug 11 11:44:57 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1)
  ProcCmdline: gnome-control-center bluetooth
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xa3c11f04:mov0x0(%ebp),%eax
   PC (0xa3c11f04) ok
   source "0x0(%ebp)" (0x0014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
   ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
   ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1205588] Re: [keyboard]: gnome-control-center crashed with SIGSEGV in update_custom_shortcut()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [keyboard]: gnome-control-center crashed with SIGSEGV in
  update_custom_shortcut()

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

Bug description:
  I assigned some keyboard custom shortcuts. Left the settings windows
  open for a while.

  Then I closed the Keyboard settings window while the Custom Shortcut
  window was still open. Closed that afterwards. Crash.

  I tried to reproduce but couldn't. You have to close the Custom
  Shortcut window first.  So not really sure how I managed to do that
  the first time.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu30
  Uname: Linux 3.11.0-031100rc2-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Sat Jul 27 01:06:09 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2011-10-08 (657 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111006)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7ff164030be4:cmpb   $0x0,(%rax)
   PC (0x7ff164030be4) ok
   source "$0x0" ok
   destination "(%rax)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [keyboard]: gnome-control-center crashed with SIGSEGV in 
g_closure_invoke()
  UpgradeStatus: Upgraded to saucy on 2013-05-04 (83 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130725-0ubuntu1

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

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


[Desktop-packages] [Bug 1216623] Re: [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

2019-01-10 Thread Sebastien Bacher
the error report shows that the issue has been fixed in newer versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Fix Released

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

Title:
  [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  crashed when I tried to tune "Text entry settings" - "Using custom
  fonts"

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu31
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sun Aug 25 20:33:30 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-07-26 (29 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130726)
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ibus_config_get_value () from /usr/lib/i386-linux-gnu/libibus-1.0.so.5
   ?? () from /usr/lib/i386-linux-gnu/control-center-1/panels/libregion.so
  Title: [region]: gnome-control-center crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130822.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1198687] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_is_a()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

Bug description:
  gnome-contol-center crashed on user account creation.


  Steps to reproduce(not tested- just performed one time which causes the 
crasher):
  1.Start system configuration -> user -> unlock -> create new account
  2.Give in the full name field "angela"
  3.See the automatically filling of the filed user name with "angela"
  4.Press ok and have the crash.

  Additional:

  This was a standard account creation.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu24.1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.2
  Architecture: amd64
  Date: Sun Jul  7 17:47:37 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-13 (175 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fa3472cc67c :
testb  $0x4,0x16(%rdi)
   PC (0x7fa3472cc67c) ok
   source "$0x4" ok
   destination "0x16(%rdi)" (0x2e66c3010796) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to raring on 2013-04-18 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 969972] Re: [network]: gnome-control-center crashed with SIGSEGV in _nm_remote_settings_ensure_inited()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  _nm_remote_settings_ensure_inited()

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

Bug description:
  problem occured after starting networking preferences

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Mar 31 13:46:06 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
nm_remote_settings_list_connections()
  UpgradeStatus: Upgraded to precise on 2012-03-28 (2 days ago)
  UserGroups: adm admin audio cdrom chipcard clamav cyberjack davfs2 disk 
floppy fuse libvirtd lpadmin mythtv netdev plugdev sambashare saned scanner 
syslog users video videos
  usr_lib_gnome-control-center:
   deja-dup22.0-0ubuntu1
   gnome-bluetooth 3.2.2-0ubuntu4

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

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


[Desktop-packages] [Bug 1132407] Re: Unable to connect to VPN while on a network connection that is not managed by network manager

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to connect to VPN while on a network connection that is not
  managed by network manager

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

Bug description:
  I needed to use my network connection before login, so I had to
  disable it in network manager and set it up using
  /etc/network/interfaces instead. However, I would still like to use
  VPN connections which I have already stored in Network Manager. But as
  I have tried to do it, "something" crashed. Ubuntu error reporting
  says it was gnome-control-center, I don't know, haven't looked much
  into it.

  Apparently, there is a problem with activating VPN connections in
  network manager while not being connected to any network via network
  manager (but of course, being connected to some network using other
  methods). The fact that it is not possible is ridiculous. Why? The VPN
  connection itself should only be dependent on whether the underlying
  interface is connected to some network or not... There should be no
  ties with network-manager-specific status of connections regarding
  this interface. It is absolutely irrelevant.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Sun Feb 24 12:31:27 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-13 (42 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130112)
  MarkForUpload: True
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2ddd2b8b80:mov0x8(%rax),%edx
   PC (0x7f2ddd2b8b80) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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


[Desktop-packages] [Bug 1103196] Re: [bluetooth]: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [bluetooth]: gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  Using the bluethoot manager, click on "Browse files"

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Tue Jan 22 22:57:09 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-11-02 (81 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: gnome-control-center bluetooth
  SegvAnalysis:
   Segfault happened at: 0x7fc1eaf19c3c :
mov(%rax),%rbp
   PC (0x7fc1eaf19c3c) ok
   source "(%rax)" (0x000b) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast (type_instance=0x7fc1edd97df0, 
iface_type=140470891014608) at 
/build/buildd/glib2.0-2.34.1/./gobject/gtype.c:3997
   bluetooth_client_connect_service () from /usr/lib/libgnome-bluetooth.so.11
   ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
   g_closure_invoke (closure=0x7fc1edd52a20, return_value=0x0, 
n_param_values=2, param_values=0x7fff307872a0, invocation_hint=0x7fff30787240) 
at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:777
   signal_emit_unlocked_R (node=node@entry=0x7fc1ed8cb590, 
detail=detail@entry=1088, instance=instance@entry=0x7fc1edc301e0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff307872a0) at 
/build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3551
  Title: [bluetooth]: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk kismet libvirtd lpadmin plugdev sambashare src 
sudo vboxusers
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4.2
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3.1

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

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


[Desktop-packages] [Bug 971615] Re: [color]: gnome-control-center crashed with SIGSEGV in g_strdup()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [color]: gnome-control-center crashed with SIGSEGV in g_strdup()

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

Bug description:
  Received error messages while installing Brother Linux printer drivers
  (MFC-5895cw) downloaded directly from Brother site, but driver imstall
  then proceeded.  Regards   Mike

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
  Uname: Linux 3.2.0-21-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu2
  Architecture: i386
  Date: Mon Apr  2 10:57:06 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: [color]: gnome-control-center crashed with SIGSEGV in g_strdup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1216637] Re: [network]: gnome-control-center crashed with SIGABRT in _g_log_abort()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGABRT in _g_log_abort()

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

Bug description:
  AFTER UPDATE AND WAKING UP FROM SUSPEND THEN RESTARTING THE ERROR
  OCCURED

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu31
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Mon Aug 26 05:10:20 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-03-24 (519 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/control-center-1/panels/libnetwork.so
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to saucy on 2013-07-18 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130822.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1044100] Re: [background]: gnome-control-center crashed with SIGSEGV in cc_background_xml_load_xml_internal()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [background]: gnome-control-center crashed with SIGSEGV in
  cc_background_xml_load_xml_internal()

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

Bug description:
  I was looking at the Change Desktop Background dialog while updating
  ubuntu-wallpaper package.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Aug 31 00:36:13 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: gnome-control-center background
  SegvAnalysis:
   Segfault happened at: 0x7f66bb2d6222:mov(%rax),%rdi
   PC (0x7f66bb2d6222) ok
   source "(%rax)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libbackground.so
   ?? () from /usr/lib/control-center-1/panels/libbackground.so
   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_va () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [background]: gnome-control-center crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: Upgraded to quantal on 2012-07-25 (35 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.13-0ubuntu1
   indicator-datetime  12.10.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1158047] Re: [display]: gnome-control-center crashed with SIGABRT in g_assertion_message()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [display]: gnome-control-center crashed with SIGABRT in
  g_assertion_message()

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

Bug description:
  It happens when i click display in ubuntu raring with latest updates
  install as of today.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu16
  Uname: Linux 3.9.0-999-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 20 17:24:12 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-20 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130117)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gnome_rr_config_load_current () from /usr/lib/libgnome-desktop-3.so.4
  Title: [display]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.3bzr13.02.20-0ubuntu1

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

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


[Desktop-packages] [Bug 1222341] Re: [keyboard]: gnome-control-center crashed with SIGSEGV in cc_keyboard_option_get_current_value_description() while closing the window

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [keyboard]: gnome-control-center crashed with SIGSEGV in
  cc_keyboard_option_get_current_value_description() while closing the
  window

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

Bug description:
  Opened the keyboard configuration (via the new "Text entry setting..."
  menu option), went a bit through the different configurations, closed
  the window, and boom.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu33
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 09:14:52 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-03-14 (542 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  SegvAnalysis:
   Segfault happened at: 0x7f7b21595fa6:cmp%rax,(%rdx)
   PC (0x7f7b21595fa6) ok
   source "%rax" ok
   destination "(%rdx)" (0x2) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_hash_table_foreach (hash_table=0x306a180, func=0x7f7b5342b4f0, 
user_data=0x7fffe55d4a10) at /build/buildd/glib2.0-2.37.6/./glib/ghash.c:1526
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: [keyboard]: gnome-control-center crashed with SIGSEGV in 
g_hash_table_foreach()
  UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1

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

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


[Desktop-packages] [Bug 1057764] Re: [bluetooth]: gnome-control-center crashed with SIGABRT in cc_bluetooth_panel_update_visibility()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [bluetooth]: gnome-control-center crashed with SIGABRT in
  cc_bluetooth_panel_update_visibility()

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

Bug description:
  Going to report this, although not 100% sure what action caused it.

  Only bluetooth device I use is a mouse, which is working.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Thu Sep 27 12:38:36 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: gnome-control-center bluetooth
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
  Title: [bluetooth]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to quantal on 2012-09-27 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

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

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


[Desktop-packages] [Bug 974867] Re: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  gtk_widget_size_allocate()

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

Bug description:
  actieons 
  1/ install 

  load Nvidia recommended driver

  make dual screen with Nvidia Cenerama

  Update 
  Reboot 

  with system => displays try to set de launcher on one screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr  6 07:58:46 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcCmdline: gnome-control-center --overview
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1054275] Re: [network]: gnome-control-center crashed with SIGSEGV in get_selected_object()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  get_selected_object()

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

Bug description:
  Crashes when trying to adjust wifi network from within dialog

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Fri Sep 21 14:32:44 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  ProcCmdline: gnome-control-center network connect-8021x-wifi 
/org/freedesktop/NetworkManager/Devices/0 
/org/freedesktop/NetworkManager/AccessPoint/0
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f91b756afc5:mov0x10(%rax),%rdi
   PC (0x7f91b756afc5) ok
   source "0x10(%rax)" (0xaaba) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
g_closure_invoke()
  UpgradeStatus: Upgraded to quantal on 2012-09-19 (1 days ago)
  UserGroups: adm cdrom debian-tor dip lpadmin netdev plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

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

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


[Desktop-packages] [Bug 974253] Re: [online-accounts] gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [online-accounts] gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  When i try to change the state of different google-services (switch
  mail, calendar etc on/off) the control-center crashes on ubunru 12.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Thu Apr  5 10:19:17 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcCmdline: gnome-control-center online-accounts
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1167377] Re: [printers]: gnome-control-center crashed with SIGSEGV in g_object_notify_queue_add()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  g_object_notify_queue_add()

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

Bug description:
  the gnome ubuntu 4.13 does not recognize my printer

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu19
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr 10 10:44:55 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-04-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130402.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7f3a15c160 :  cmp
%rsi,(%rax)
   PC (0x7f7f3a15c160) ok
   source "%rsi" ok
   destination "(%rax)" (0x6e617078652d6261) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_container_child_notify () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in g_slist_find()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1

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

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


[Desktop-packages] [Bug 1186585] Re: gnome-control-center crashed after log in to google

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed after log in to google

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

Bug description:
  this happened after loggin in to google using two-step authentication

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu24
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat Jun  1 12:06:47 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-04-06 (421 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  ProcCmdline: gnome-control-center credentials
  SegvAnalysis:
   Segfault happened at: 0x7f7965bb71a9 :   mov
(%rdi),%rax
   PC (0x7f7965bb71a9) ok
   source "(%rdi)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   tp_proxy_pending_call_cancel () from 
/usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.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
  Title: gnome-control-center crashed with SIGSEGV in g_object_ref()
  UpgradeStatus: Upgraded to raring on 2013-04-26 (36 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1
   gnome-control-center-unity  1.2daily13.04.09-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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


[Desktop-packages] [Bug 1044230] Re: gnome-control-center crashed with SIGSEGV in adapter_changed()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in adapter_changed()

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

Bug description:
  I changed the bluetooth settings and devices. Than I have the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug 31 08:50:07 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcCmdline: gnome-control-center bluetooth
  SegvAnalysis:
   Segfault happened at: 0xb6d4f57a :  mov
(%esi),%eax
   PC (0xb6d4f57a) ok
   source "(%esi)" (0x1060) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_instance_get_private () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgnome-bluetooth.so.11
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_instance_get_private()
  UpgradeStatus: Upgraded to quantal on 2012-08-14 (16 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.13-0ubuntu1
   indicator-datetime  12.10.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1219272] Re: [screen]: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [screen]: gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  Happened when I went to "Brightness & Lock" and then tried going back
  by clicking "All Settings". Happens reproducibly.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu33
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sat Aug 31 21:45:30 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-08-31 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130830)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f55b141926c :
mov(%rax),%rdi
   PC (0x7f55b141926c) ok
   source "(%rax)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" 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/control-center-1/panels/libscreen.so
   g_simple_async_result_complete () 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_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: [screen]: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130828.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1197199] Re: system crashed when attempting to set default browser to chromium

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  system crashed when attempting to set default browser to chromium

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

Bug description:
  Unable to change default browser

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jul  2 20:27:37 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-16 (47 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130514)
  MarkForUpload: True
  ProcCmdline: gnome-control-center info
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fc681de7767 :mov
(%rbx),%rax
   PC (0x7fc681de7767) ok
   source "(%rbx)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1193764] Re: [color]: gnome-control-center crashed with SIGSEGV in cd_device_connect()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [color]: gnome-control-center crashed with SIGSEGV in
  cd_device_connect()

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

Bug description:
  It crashes in the Systems Settings application

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sun Jun 23 02:06:00 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130622)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xaca57ca1 :mov
(%edi),%edx
   PC (0xaca57ca1) ok
   source "(%edi)" (0xe8e8ffe8) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   cd_device_connect () from /usr/lib/i386-linux-gnu/libcolord.so.1
   cd_device_connect_sync () from /usr/lib/i386-linux-gnu/libcolord.so.1
   ?? () from /usr/lib/control-center-1/panels/libcolor.so
   ?? () from /usr/lib/control-center-1/panels/libcolor.so
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [color]: gnome-control-center crashed with SIGSEGV in 
cd_device_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3daily13.06.19-0ubuntu1

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

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


[Desktop-packages] [Bug 1048098] Re: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()

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

Bug description:
  The Network Properties page in Gnome Control Centre crashed when the
  wireless interface was enabled via rfkill in the terminal.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 04:22:05 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7f2e707860b5:mov0x34(%rbx),%eax
   PC (0x7f2e707860b5) ok
   source "0x34(%rbx)" (0x0034) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.14-0ubuntu1
   indicator-datetime  12.10.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1216192] Re: [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

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

Bug description:
  Was switching back and forth between the different keyboard and region
  panels when the control center crashed and this popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu31
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Fri Aug 23 23:20:51 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2011-09-24 (699 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   _g_log_abort () at /build/buildd/glib2.0-2.37.6/./glib/gmessages.c:255
   g_assertion_message (domain=domain@entry=0x7fd5986f0154 "IBUS", 
file=file@entry=0x7fd5986f4961 "ibusconfig.c", line=line@entry=394, 
func=func@entry=0x7fd5986f4cd0 "ibus_config_get_value", 
message=message@entry=0x7fd5bf7a24d0 "assertion failed: (IBUS_IS_CONFIG 
(config))") at /build/buildd/glib2.0-2.37.6/./glib/gtestutils.c:2278
   g_assertion_message_expr (domain=0x7fd5986f0154 "IBUS", file=0x7fd5986f4961 
"ibusconfig.c", line=394, func=0x7fd5986f4cd0 "ibus_config_get_value", 
expr=) at /build/buildd/glib2.0-2.37.6/./glib/gtestutils.c:2293
   ibus_config_get_value () from /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libregion.so
  Title: [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()
  UpgradeStatus: Upgraded to saucy on 2013-06-08 (77 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130822.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1052132] Re: [sound]: gnome-control-center crashed with SIGSEGV in _int_malloc()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [sound]: gnome-control-center crashed with SIGSEGV in _int_malloc()

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

Bug description:
  Crashed while I was changing the systems sounds (bark, drop, etc.).
  Froze before crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 20:32:02 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120913)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc33d314c5f:mov0x10(%r14),%r8
   PC (0x7fc33d314c5f) ok
   source "0x10(%r14)" (0x53555f6e75) not located in a known VMA region (needed 
readable region)!
   destination "%r8" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   malloc () from /lib/x86_64-linux-gnu/libc.so.6
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdupv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: [sound]: gnome-control-center crashed with SIGSEGV in malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.15-0ubuntu2
   indicator-datetime  12.10.0-0ubuntu2

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

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


[Desktop-packages] [Bug 1216260] Re: [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [region]: gnome-control-center crashed with SIGABRT in _g_log_abort()

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

Bug description:
  Seen on up to date Saucy. To replicate:
  Open Region and Language settings, Text Entry tab. Click Show Input 
Candidates dropdown (currently empty) and select Horizontal (or Vertical). It 
crashes immediately.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu31
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Sat Aug 24 10:36:12 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-08-12 (11 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130812)
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_config_get_value () from /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libregion.so
  Title: [region]: gnome-control-center crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130822.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1201899] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  crash on ubuntu 13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu30
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 16 19:16:38 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-10 (186 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130110)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fc32d034fec :
mov(%rax),%rdi
   PC (0x7fc32d034fec) ok
   source "(%rax)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Stacktrace:
   #0  0x7fc32d034fec in g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   No symbol table info available.
   Cannot access memory at address 0x7fff8edc8cd8
  StacktraceTop: g_type_check_instance_cast () 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu3
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130716-0ubuntu1

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

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


[Desktop-packages] [Bug 1155435] Re: [printers]: gnome-control-center crashed with SIGSEGV in __memset_x86_64()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  __memset_x86_64()

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

Bug description:
  Was trying to add a printer to a new installation of Ubuntu GNOME
  13.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 15 00:00:20 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130313)
  MarkForUpload: True
  ProcCmdline: gnome-control-center printers
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5ecf1d4826:mov%rdx,-0x10(%rdi)
   PC (0x7f5ecf1d4826) ok
   source "%rdx" ok
   destination "-0x10(%rdi)" (0x7f5ed115cb92) in non-writable VMA region: 
0x7f5ed0e27000-0x7f5ed12d2000 r-xp /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.600.4
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.600.4
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
g_slice_alloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  usr_lib_gnome-control-center:
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1

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

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


[Desktop-packages] [Bug 1064862] Re: [bluetooth]: gnome-control-center crashed with SIGSEGV in get_iter_from_path()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gnome-control-center (Ubuntu)
 Assignee: Tony (toekneemi) => (unassigned)

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

Title:
  [bluetooth]: gnome-control-center crashed with SIGSEGV in
  get_iter_from_path()

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

Bug description:
  While fiddling with Bluetooth & Sound..

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.6.1-0ubuntu2
  Architecture: i386
  CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
  CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
  Date: Wed Oct 10 12:07:34 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center bluetooth
  SegvAnalysis:
   Segfault happened at: 0xa854de8a:mov0x8(%esi),%ecx
   PC (0xa854de8a) ok
   source "0x8(%esi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/libgnome-bluetooth.so.11
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to quantal on 2012-09-21 (18 days ago)
  UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin netdev plugdev 
pulse pulse-access sambashare video
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3

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

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


[Desktop-packages] [Bug 975994] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in _IO_vfprintf_internal()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [soundnua]: gnome-control-center crashed with SIGSEGV in
  _IO_vfprintf_internal()

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

Bug description:
  Launching sound preferences from the indicator. pavucontrol works
  fine.

  if launched from gnome-control-center the STERR output is:

  $ gnome-control-center

  (gnome-control-center:4558): Gtk-WARNING **: Attempting to add a
  widget with type GtkBox to a container of type GtkScrolledWindow, but
  the widget is already inside a container of type GtkAlignment, please
  use gtk_widget_reparent()

  (gnome-control-center:4558): Gtk-WARNING **: Attempting to add a
  widget with type GtkBox to a container of type GtkScrolledWindow, but
  the widget is already inside a container of type GtkBox, please use
  gtk_widget_reparent()

   get server info

   update server
   1 profiles supported on port HDMI / DisplayPort 

   SET PROFILES HDMI / DisplayPort
   Add output ui entry with id : 1 

   create_ui_device_from_port, direction 1 
   description HDMI / DisplayPort 
   origin Built-in Audio 
   port available 1 
   

   15 profiles supported on port Analog Output

   7 profiles supported on port iec958-stereo-input

   3 profiles supported on port Digital Output (S/PDIF)

   SET PROFILES Digital Output (S/PDIF)
   Add output ui entry with id : 2 

   create_ui_device_from_port, direction 1 
   description Digital Output (S/PDIF) 
   origin ICE1712 [Envy24] PCI Multi-Channel I/O Controller 
   port available 1 
   

   SET PROFILES iec958-stereo-input
   Add input ui entry with id : 3 

   create_ui_device_from_port, direction 0 
   description iec958-stereo-input 
   origin ICE1712 [Envy24] PCI Multi-Channel I/O Controller 
   port available 1 
   

   SET PROFILES Analog Output
   Add output ui entry with id : 4 

   create_ui_device_from_port, direction 1 
   description Analog Output 
   origin ICE1712 [Envy24] PCI Multi-Channel I/O Controller 
   port available 1 
   

   update sink - is new

   Match device with stream 
   We have a match with description : HDMI / DisplayPort  
   origin : Built-in Audio 
   cached already with device id 1, 
   => set stream id to 1 

   
   
   lookup-device-from-stream found device  
   device description HDMI / DisplayPort 
   device port = hdmi-output-0 
   device stream id 1 
   AND 
   stream port = hdmi-output-0 stream id 1 and stream description Built-in 
Audio Digital Stereo (HDMI) 
  active_sink change 

  
   active output update - device id = 1 


   on_output_selection_changed - active 1

  
   active_output_update HDMI / DisplayPort 

   update sink - is new

   Match device with stream 
   We have a match with description : Analog Output  
   origin : ICE1712 [Envy24] PCI Multi-Channel I/O Controller 
   cached already with device id 4, 
   => set stream id to 2 

   
   update sink - is new 

   
   software device 

   Add output ui entry with id : 5 
  just detected a network sink
   
   Bluetooth device 
   

   Add input ui entry with id : 3

   lookup device from stream - ICE1712 [Envy24] PCI Multi-Channel I/O
  Controller Analog Stereo - it is a network_stream

   active_input_update ICE1712 [Envy24] PCI Multi-Channel I/O Controller
  Analog Stereo

   Did we try to move to a software/bluetooth source ?

  [last message repeated hundreds of times..]

  Segmentation fault (core dumped)


  pactl list out is:

  Module #0
Name: module-device-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "1.1"

  Module #1
Name: module-stream-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "1.1"

  Module #2
Name: module-card-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "1.1"

  Module #3
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
  

[Desktop-packages] [Bug 1054865] Re: display : gnome-control-center crashed with SIGSEGV in gtk_widget_get_toplevel

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
   display : gnome-control-center crashed with SIGSEGV in
  gtk_widget_get_toplevel

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

Bug description:
  Displays pane could not handle rotating the screen. of course I'm
  working with a Citizen LCD monitor that does 1440 x 900, which I had
  to force. The monitor is not recognized automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Sun Sep 23 01:56:04 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: gnome-control-center display
  SegvAnalysis:
   Segfault happened at: 0xb750830d :   mov
(%esi),%edx
   PC (0xb750830d) ok
   source "(%esi)" (0x47470047) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_widget_get_toplevel () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/control-center-1/panels/libdisplay.so
   ?? () from /usr/lib/control-center-1/panels/libdisplay.so
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: [display]: gnome-control-center crashed with SIGSEGV in 
gtk_widget_get_toplevel()
  UpgradeStatus: Upgraded to quantal on 2012-08-18 (35 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1189034] Re: gnome-control-center crashed with SIGSEGV in gtk_hbox_get_type()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in gtk_hbox_get_type()

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

Bug description:
  Privacy setting fails to start.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu24
  ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13
  Uname: Linux 3.8.0-24-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sat Jun  8 17:05:54 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-04-25 (44 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: gnome-control-center activity-log-manager
  SegvAnalysis:
   Segfault happened at: 0x7f841b98237a :movabs 
%rax,0x245c8948c35b10c4
   PC (0x7f841b98237a) ok
   source "%rax" ok
   destination "0x245c8948c35b10c4" (0x245c8948c35b10c4) not located in a known 
VMA region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_hbox_get_type () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_hbox_get_type()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1
   gnome-control-center-unity  1.2daily13.04.09-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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


[Desktop-packages] [Bug 1056149] Re: gnome-control-center crashed with SIGSEGV in _shell_remove_all_custom_widgets()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _shell_remove_all_custom_widgets()

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

Bug description:
  gnome-control-center crashed with SIGSEGV in _start()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep 25 15:11:46 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0xb77a2db8:mov0x4(%ecx),%ebp
   PC (0xb77a2db8) ok
   source "0x4(%ecx)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   _start ()
  Title: gnome-control-center crashed with SIGSEGV in _start()
  UpgradeStatus: Upgraded to quantal on 2012-09-12 (13 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev root sambashare sudo www-data
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

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

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


[Desktop-packages] [Bug 1193955] Re: gnome-control-center crashed with SIGABRT in __assert_fail_base()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-center crashed with SIGABRT in __assert_fail_base()

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

Bug description:
  hm, optical is nothing crashed. Occured while I set new system
  language to English(UK) than apply settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.11
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic-pae 3.2.46
  Uname: Linux 3.2.0-48-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: i386
  Date: Mon Jun 24 01:51:13 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu4
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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


[Desktop-packages] [Bug 1153505] Re: [network]: gnome-control-center crashed with SIGSEGV in stop_shared_connection()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  stop_shared_connection()

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

Bug description:
  dont knw what happen

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  Date: Sun Mar 10 20:03:59 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-08 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130308)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0xa1c3fa18:mov0x4(%edi),%edx
   PC (0xa1c3fa18) ok
   source "0x4(%edi)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   g_cclosure_marshal_VOID(int0_t) () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.07-0ubuntu1

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

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


[Desktop-packages] [Bug 1157983] Re: [printers]: gnome-control-center crashed with SIGSEGV in pango_item_free()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in
  pango_item_free()

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

Bug description:
  Plugged in my Canon M600 Printer. Going to System settings > Printer > Add 
new printer.
  Then selected my printer from list and pressed "add" - then 
gnome-control-center crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 20 19:50:52 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-17 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130316)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe93ca33209 :mov
0x38(%rdi),%rdi
   PC (0x7fe93ca33209) ok
   source "0x38(%rdi)" (0x10039) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   pango_item_free () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   pango_layout_line_unref () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
  Title: [printers]: gnome-control-center crashed with SIGSEGV in 
pango_item_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare shadow sudo vboxusers
  usr_lib_gnome-control-center:
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.3bzr13.02.20-0ubuntu1

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

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


[Desktop-packages] [Bug 1041921] Re: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed()

2019-01-10 Thread Sebastien Bacher
The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _gtk_widget_set_alloc_needed()

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

Bug description:
  Tried scrolling down in the main window after openning a couple of
  settings

  Description:  Ubuntu quantal (development branch)
  Release:  12.10
  gnome-control-center:
Installed: 1:3.4.2-0ubuntu11
Candidate: 1:3.4.2-0ubuntu11
Version table:
   *** 1:3.4.2-0ubuntu11 0
  500 http://gb.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu11
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Date: Sun Aug 26 20:05:15 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f0e2b69bb8a:movzbl 0x4(%rdx),%eax
   PC (0x7f0e2b69bb8a) ok
   source "0x4(%rdx)" (0xaaae) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_image_set_from_gicon () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_image_set_from_gicon()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.13-0ubuntu1
   indicator-datetime  12.10.0-0ubuntu1

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

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


  1   2   3   4   >