[Desktop-packages] [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ...

[Timo Aaltonen]

15.10 isn't supported anymore, and fglrx is not available in 16.04 and
should get removed on upgrade

kernel 4.3 is not in any ubuntu release, so building the driver against
it isn't supported either

** Changed in: fglrx-installer (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Won't Fix
Status in fglrx-installer-updates package in Ubuntu:
  Won't Fix

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+subscriptions

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

[Desktop-packages] [Bug 1686077] Re: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

[Bug Watch Updater]

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

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

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

Title:
  Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

Status in gnome-settings-daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in gnome-settings-daemon source package in Yakkety:
  Triaged
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Triaged
Status in unity-settings-daemon source package in Zesty:
  Triaged
Status in gnome-settings-daemon package in Debian:
  Unknown

Bug description:
  Impact
  ==
  This bugfix enabled gnome-settings-daemon's multimedia key support to work 
according to what the API has said for years (in addition to the way it's been 
commonly used).

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?h=gnome-3-24=42f75ed4cdc86498d6e02e511a1314b8916bd4aa

  https://mail.gnome.org/archives/desktop-devel-
  list/2017-April/msg00069.html

  The SRU justification is that newer versions of apps will be switching
  to the D-Bus name in the API documentation. If someone installs the
  newer version from a PPA or a Flatpak or Snap, the multimedia key
  support should continue working.

  Test Case
  =
  ?

  Regression Potential
  
  This should just make gnome(unity)-settings-daemon own both the commonly used 
D-Bus name and the one actually defined in the API docs.

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

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

[Desktop-packages] [Bug 1686243] Re: NVIDIA driver

[Timo Aaltonen]

you're using an unofficial ppa which could mess things up, besides your
machine is a hybrid machine so you need to use prime-select in order to
switch to nvidia

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

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

Title:
  NVIDIA driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Trying for days to install an nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
  Uname: Linux 4.8.0-49-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 26 01:19:29 2017
  DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
   nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-04-24 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 
root=UUID=65af2065-0769-48de-9408-1d7d5313f54e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-25 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80+git20170420.691a2157-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 26 01:05:56 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

[Sachin Bawoor]

** Changed in: dnsmasq (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => Sachin Bawoor (bawoor)

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

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

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

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

[Olivier Tilloy]

@James: are you still seeing this issue with recent releases of
chromium?

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

Title:
  chromium-browser crashed with SIGSEGV in
  content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in libdrm-2.4.23 package in Ubuntu:
  Confirmed

Bug description:
  I was using Google Maps and Chromium froze up and crashed.  After
  this, rendering of the new Google Maps page causes jagged lines to
  appear in the browser page display section, until I reboot the
  computer.  Killing and relaunching Chromium doesn't fix the problem.
  The jagged lines still appear after computer reboot if I visit Google
  Maps again, and again won't disappear until I restart the computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ChromiumPrefs: can't open profile 
/home/jamesmaz/.config/chromium/Default/Preferences
  Date: Mon Nov 11 13:10:09 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ 
--channel=4656.10.459810737\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=0,6,18\ --gpu-vendor-id=0x8086\ 
--gpu-device-id=0x0106\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=9.1.7
  ProcEnviron:

  SegvAnalysis:
   Segfault happened at: 0x7f82c62ad43e:movl   $0x1337,0x0
   PC (0x7f82c62ad43e) ok
   source "$0x1337" ok
   destination "0x0" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   base::MessageLoop::RunTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from 
/usr/lib/chromium-browser/libs/libbase.so
   ?? () from /usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default:
   CHROMIUM_FLAGS=""
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
  mtime.conffile..etc.chromium.browser.default: 2013-11-10T15:09:15.272458

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

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

[Desktop-packages] [Bug 1343081] Re: chromium: missing "http://" in URL bar on non-ssl http URLs

[Olivier Tilloy]

I’ve verified that this works as expected with recent releases of chromium.
Now closing, please re-open if you're still affected by the issue (note that 
the http:// prefix being hidden in the first place is by design, so not 
considered a bug).

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

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

Title:
  chromium: missing "http://; in URL bar on non-ssl http URLs

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

  On http URLs (non-ssl), the url bar misses the "http://; prefix.
  This is especially ugly when copying URLs.

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

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

[Desktop-packages] [Bug 1309759] Re: Chromium min, max, close at upper right

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1097125
   chromium-browser has min/max/close buttons at upper right

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

Title:
  Chromium min, max, close at upper right

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Again, this cluster appears at the upper right corner of the browser
  window instead of the upper left as required.

  This seems to be a recurring problem in this package.

  Please fix asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  ChromiumPrefs: can't open profile 
/home/peterzay/.config/chromium/Default/Preferences
  CurrentDesktop: Unity
  Date: Fri Apr 18 17:18:06 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1355591] Re: chromium-browser crashed with SIGSEGV in ShCompile()

[Olivier Tilloy]

Now closing per last comment.

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

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

Title:
  chromium-browser crashed with SIGSEGV in ShCompile()

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Upgrade and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 36.0.1985.125-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 12 00:02:02 2014
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  Disassembly: => 0x0:  No se puede acceder a la memoria en la dirección 0x0
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-04-27 (106 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3586.0.1567776759\ --disable-breakpad\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,10,14\ --gpu-vendor-id=0x8086\ 
--gpu-device-id=0x0116\ --gpu-driver-vendor\ --gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x0:   No se puede acceder a la memoria en la 
dirección 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/chromium-browser/libs/libtranslator.so
   ?? () from /usr/lib/chromium-browser/libs/libtranslator.so
   ShCompile () from /usr/lib/chromium-browser/libs/libtranslator.so
   gpu::gles2::ShaderTranslator::Translate(char const*) () from 
/usr/lib/chromium-browser/libs/libgpu.so
  Title: chromium-browser crashed with SIGSEGV in ShCompile()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-27T17:58:46.529285

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

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

[Desktop-packages] [Bug 1222718] Re: Using fglrx, chromium tabs not displaying titles

[Olivier Tilloy]

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

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

Title:
  Using fglrx, chromium tabs not displaying titles

Status in Chromium Browser:
  Unknown
Status in fglrx:
  New
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Invalid

Bug description:
  Hello,

  My problem is that Chrome/Chromium (have both installed) are not displaying 
page titles rendering many pages.
  Actually, because of bug of keybindings in Gnome 3.9 I can't create 
screenshot, but with most pages I have favicon displayed and not any text like 
page title.

  It doesn't matter if GPU rendering is enabled or disabled.

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

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

[Desktop-packages] [Bug 1248745] Re: chromedriver needs to be upgraded to v2 to work with current chromium-browser builds.

[Olivier Tilloy]

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

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

Title:
  chromedriver needs to be upgraded to v2 to work with current chromium-
  browser builds.

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  While using selenium code that worked fine with chromedriver v2.3 and
  v30 Chrome on x86 (but trying to run on an armhf system) I hit an
  error that looks very similar to
  https://code.google.com/p/chromedriver/issues/detail?id=471

  Exception:
  WebDriverException: Message: u"Unknown command 'WaitForAllTabsToStopLoading'. 
Options: AcceptOrDismissAppModalDialog, ActionOnSSLBlockingPage, ActivateTab, 
AddBookmark, AddDomEventObserver, AppendTab, ApplyAccelerator, 
BringBrowserToFront, ClearEventQueue, CloseBrowserWindow, CloseTab, 
CreateNewAutomationProvider, DeleteCookie, DeleteCookieInBrowserContext, 
DoesAutomationObjectExist, DragAndDropFilePaths, ExecuteJavascript, 
ExecuteJavascriptInRenderView, GetActiveTabIndex, GetAppModalDialogMessage, 
GetBookmarkBarStatus, GetBookmarksAsJSON, GetBrowserInfo, 
GetBrowserWindowCount, GetChromeDriverAutomationVersion, GetCookies, 
GetCookiesInBrowserContext, GetDownloadDirectory, GetExtensionsInfo, 
GetIndicesFromTab, GetLocalStatePrefsInfo, GetMultiProfileInfo, GetNextEvent, 
GetPrefsInfo, GetProcessInfo, GetSecurityState, GetTabCount, GetTabIds, 
GetTabInfo, GetViews, GoBack, GoForward, InstallExtension, 
IsDownloadShelfVisible, IsFindInPageVisible, IsMenuCommandEnabled, 
IsPageActionVisible,
  IsTabIdValid, MaximizeView, NavigateToURL, OpenFindInPage, 
OpenNewBrowserWindow, OpenNewBrowserWindowWithNewProfile, OpenProfileWindow, 
OverrideGeoposition, RefreshPolicies, Reload, RemoveBookmark, 
RemoveEventObserver, ReparentBookmark, RunCommand, SendWebkitKeyEvent, 
SetBookmarkTitle, SetBookmarkURL, SetCookie, SetCookieInBrowserContext, 
SetDownloadShelfVisible, SetExtensionStateById, SetLocalStatePrefs, SetPrefs, 
SetViewBounds, SimulateAsanMemoryBug, TriggerBrowserActionById, 
TriggerPageActionById, UninstallExtensionById, UpdateExtensionsNow, 
WaitForBookmarkModelToLoad, WaitUntilNavigationCompletes, 
WebkitMouseButtonDown, WebkitMouseButtonUp, WebkitMouseClick, 
WebkitMouseDoubleClick, WebkitMouseDrag, WebkitMouseMove, 
AcceptCurrentFullscreenOrMouseLockRequest, AddOrEditSearchEngine, 
AddSavedPassword, CloseNotification, DenyCurrentFullscreenOrMouseLockRequest, 
DisablePlugin, EnablePlugin, FindInPage, GetAllNotifications, GetDownloadsInfo, 
GetFPS, GetHistoryInfo, GetInitialLoadTimes
 , GetNTPInfo, GetNavigationInfo, GetOmniboxInfo, GetPluginsInfo, 
GetSavedPasswords, GetSearchEngineInfo, GetV8HeapStats, ImportSettings, 
IsFullscreenBubbleDisplayed, IsFullscreenBubbleDisplayingButtons, 
IsFullscreenForBrowser, IsFullscreenForTab, IsFullscreenPermissionRequested, 
IsMouseLockPermissionRequested, IsMouseLocked, KillRendererProcess, LaunchApp, 
LoadSearchEngineInfo, OmniboxAcceptInput, OmniboxMovePopupSelection, 
PerformActionOnDownload, PerformActionOnInfobar, PerformActionOnSearchEngine, 
RemoveNTPMostVisitedThumbnail, RemoveSavedPassword, 
RestoreAllNTPMostVisitedThumbnails, SaveTabContents, SetAppLaunchType, 
SetOmniboxText, SetWindowDimensions, WaitForAllDownloadsToComplete, 
WaitForNotificationCount, "

  The solution in the bug is "ChromeDriver 1 does not work with Chrome
  29."  Which means for Chromium v29 and above chromedriver2 code must
  be used to make the chromium-chromedriver package.  I'm trying to run
  on armhf, so can't use the packaged version from Google.

  I assume the new code could be grabbed from
  https://sites.google.com/a/chromium.org/chromedriver/contributing
  (took a bit of poking around through invalid links to find).

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

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

[Desktop-packages] [Bug 1676431] Update Released

[Andy Whitcroft]

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

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

Title:
   Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  Calculator key doesn't launch the calculator in Zesty

  This is because gnome-calculator 3.24 renamed its .desktop.

  Test Case
  -
  Run Unity.
  Install the update.
  If you have a keyboard with a Calculator key, press that key.

  Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
  Click the row that says Launch calculator. Type something else (How about 
Super+C). Once it's set, press that key combination.

  In either case, the Calculator should start.

  Regression Potential
  
  This is the same fix applied in gnome-settings-daemon.

  https://launchpadlibrarian.net/312312021/gnome-settings-
  daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?id=ace15f5dc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+subscriptions

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

[Desktop-packages] [Bug 1676431] Re: Calculator key doesn't launch the calculator

[Launchpad Bug Tracker]

This bug was fixed in the package unity-settings-daemon -
15.04.1+17.04.20170418-0ubuntu1

---
unity-settings-daemon (15.04.1+17.04.20170418-0ubuntu1) zesty; urgency=medium

  * Fix calculator keyboard key by adapting to gnome-calculator 3.24
.desktop rename (LP: #1676431)

 -- Jeremy Bicha   Tue, 18 Apr 2017 11:58:34 +

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
   Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  Calculator key doesn't launch the calculator in Zesty

  This is because gnome-calculator 3.24 renamed its .desktop.

  Test Case
  -
  Run Unity.
  Install the update.
  If you have a keyboard with a Calculator key, press that key.

  Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
  Click the row that says Launch calculator. Type something else (How about 
Super+C). Once it's set, press that key combination.

  In either case, the Calculator should start.

  Regression Potential
  
  This is the same fix applied in gnome-settings-daemon.

  https://launchpadlibrarian.net/312312021/gnome-settings-
  daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?id=ace15f5dc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+subscriptions

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

[Desktop-packages] [Bug 1400206] Re: Chromium hangs: GPU process hung

[Olivier Tilloy]

@Chris: are you seeing the same errors in stderr as reported by Richard
("The GPU process hung" and "Lost UI shared context")?

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

Title:
  Chromium hangs: GPU process hung

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Starting with a recent update to either my graphics card, or to
  chromium, it (chromium) will seem to hang after resuming from a lock
  screen. By hang, I mean it seems to refuse to redraw since it still
  responds to mouse clicks on the close button. Here's the stderr output
  on console:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates
  [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed 
to establish GPU channel.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI 
shared context.
  [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  7 22:21:35 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  --- 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-02-16 (1083 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Tags:  utopic
  Uname: Linux 3.11.0-14-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  modified.conffile..etc.chromium.browser.default:
   # Default settings for chromium-browser. This file is sourced by /bin/sh from
   # /usr/bin/chromium-browser
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
   # Options to pass to chromium-browser
   CHROMIUM_FLAGS=""
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190

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

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

[Desktop-packages] [Bug 1664259] Re: /usr/bin/deja-dup-preferences:11:gtk_widget_accessible_get_attributes:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit

[Launchpad Bug Tracker]

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  /usr/bin/deja-dup-
  
preferences:11:gtk_widget_accessible_get_attributes:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit

Status in deja-dup package in Ubuntu:
  Expired

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1664259/+subscriptions

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

[Desktop-packages] [Bug 1686275] [NEW] System message indicated a bug on reboot. Shows on reboot always.

[Justin Ngan]

Public bug reported:

System message indicated a bug on reboot. Shows on reboot always.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 25 22:02:42 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
InstallationDate: Installed on 2017-03-12 (44 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: Hewlett-Packard 550-009
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-49-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2015
dmi.bios.vendor: AMI
dmi.bios.version: 80.06
dmi.board.name: 2B2C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.01
dmi.chassis.asset.tag: MXX52512YG
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr80.06:bd04/01/2015:svnHewlett-Packard:pn550-009:pvr1.00:rvnHewlett-Packard:rn2B2C:rvr1.01:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 550-009
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Apr 25 21:58:26 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/628593

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

Title:
  System message indicated a bug on reboot. Shows on reboot always.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  System message indicated a bug on reboot. Shows on reboot always.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 25 22:02:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
  InstallationDate: Installed on 2017-03-12 (44 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Hewlett-Packard 550-009
  ProcEnviron:
   LANGUAGE=en_CA:en

[Desktop-packages] [Bug 1524963] Re: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'

[Launchpad Bug Tracker]

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

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

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

Title:
  Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4',
  unhandled serial type'

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  I see these warnings in the journalctl after every boot, on Ubuntu
  15.10:

  
  ```
  Dec 11 09:18:08 M2 ModemManager[816]:   Could not grab port 
(tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
  Dec 11 09:18:08 M2 ModemManager[816]:   Couldn't create modem for 
device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port
  Dec 11 09:18:08 M2 ModemManager[816]:   Modem couldn't be initialized: 
Couldn't check unlock status: SIM not inserted
  ```

  Any clues what this could be and why modem can't be initialized?
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-05-22 (202 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: modemmanager 1.4.10-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ...

[KitchM]

Once more.  During normal updates again.

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Confirmed
Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+subscriptions

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

[Desktop-packages] [Bug 1685272] Re: gnome-shell: no window border

[Daniel van Vugt]

Yes, what Amr said...

$ dpkg -s light-themes | grep Source
Source: ubuntu-themes


** Changed in: light-themes (Ubuntu Artful)
   Status: Confirmed => Invalid

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions

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

[Desktop-packages] [Bug 1685272] Re: gnome-shell: no window border

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions

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

[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

[Mathew Hodson]

** No longer affects: mesa (Ubuntu Xenial)

** No longer affects: mesa (Ubuntu)

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Released
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Released

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note: "Download updates while installing Ubuntu" doesn't currently
  seem to be working. If after installing 16.04 on effected Skylake
  hardware you find that Unity/Compiz is broken, switch to a VT with
  Control+Alt+F1, login, and then run:

  sudo apt-get update
  sudo apt-get dist-upgrade

  You should see the `libllvm3.8` package get updated. After a reboot,
  Unity/Compiz should be working.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which
  has a bug that results in invalid JIT code generation when using the
  mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISOs. It will be included on the 16.04.1
  ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions

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

[Desktop-packages] [Bug 1686254] [NEW] OpenVPN auto-connect options greyed out or missing for no reason

[Paul]

Public bug reported:

"Automatically connect to this network..." and "Automatically connect to
VPN when..." are greyed out or missing from the GUI, the former is also
"checked" however this is not true as it never attempts to auto connect.

There's no reason for these to be unavailable, especially when personal
encrypted passwords and keys are used.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: plasma-nm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: openvpn

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: plasma-nm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  OpenVPN auto-connect options greyed out or missing for no reason

Status in network-manager package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in plasma-nm package in Ubuntu:
  New

Bug description:
  "Automatically connect to this network..." and "Automatically connect
  to VPN when..." are greyed out or missing from the GUI, the former is
  also "checked" however this is not true as it never attempts to auto
  connect.

  There's no reason for these to be unavailable, especially when
  personal encrypted passwords and keys are used.

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

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

[Desktop-packages] [Bug 1686247] [NEW] Firefox should Suggests libavcodec

[Mathew Hodson]

Public bug reported:

Firefox needs libav to play MP3 music and MP4 videos on the web. The
firefox package should Suggests the corresponding libavcodec package so
there is a clue for the user about which package they need to install to
get the full multimedia functionality in Firefox.

In Zesty, Firefox would need
Suggests: libavcodec57

** Affects: firefox (Ubuntu)
 Importance: Low
 Status: New


** Tags: packaging trusty xenial zesty

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

Title:
  Firefox should Suggests libavcodec

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox needs libav to play MP3 music and MP4 videos on the web. The
  firefox package should Suggests the corresponding libavcodec package
  so there is a clue for the user about which package they need to
  install to get the full multimedia functionality in Firefox.

  In Zesty, Firefox would need
  Suggests: libavcodec57

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

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

[Desktop-packages] [Bug 272772] Re: packages that Depend/Recommend/Suggest firefox (meta-package) must alternatively Depend/Recommend/Suggest abrowser

[Mathew Hodson]

** No longer affects: firefox-3.0 (Ubuntu Intrepid)

** No longer affects: firefox-3.0 (Ubuntu)

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

Title:
  packages that Depend/Recommend/Suggest firefox (meta-package) must
  alternatively Depend/Recommend/Suggest abrowser

Status in adblock-plus package in Ubuntu:
  Fix Released
Status in all-in-one-sidebar package in Ubuntu:
  Fix Released
Status in amsn package in Ubuntu:
  Fix Released
Status in beagle package in Ubuntu:
  Fix Released
Status in biofox package in Ubuntu:
  Fix Released
Status in classpath package in Ubuntu:
  Fix Released
Status in ctxextensions package in Ubuntu:
  Fix Released
Status in firefox-sage package in Ubuntu:
  Fix Released
Status in firefox-showcase package in Ubuntu:
  Fix Released
Status in flashblock package in Ubuntu:
  Fix Released
Status in foxyproxy package in Ubuntu:
  Fix Released
Status in gnome-chemistry-utils package in Ubuntu:
  Fix Released
Status in greasemonkey package in Ubuntu:
  Fix Released
Status in httrack package in Ubuntu:
  Fix Released
Status in imagezoom package in Ubuntu:
  Fix Released
Status in lastfm package in Ubuntu:
  Fix Released
Status in libjibx-java package in Ubuntu:
  Fix Released
Status in livehttpheaders package in Ubuntu:
  Fix Released
Status in mediatomb package in Ubuntu:
  Fix Released
Status in mozgest package in Ubuntu:
  Fix Released
Status in mozilla-bonobo package in Ubuntu:
  Fix Released
Status in mozilla-noscript package in Ubuntu:
  Fix Released
Status in mozilla-stumbleupon package in Ubuntu:
  Fix Released
Status in nip2 package in Ubuntu:
  Fix Released
Status in nukeimage package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Fix Released
Status in pcmanx-gtk2 package in Ubuntu:
  Fix Released
Status in rapache package in Ubuntu:
  Fix Released
Status in scrapbook package in Ubuntu:
  Fix Released
Status in speeddial package in Ubuntu:
  Fix Released
Status in stanford-pwdhash package in Ubuntu:
  Fix Released
Status in tiemu package in Ubuntu:
  Fix Released
Status in tilp package in Ubuntu:
  Fix Released
Status in torbutton package in Ubuntu:
  Fix Released
Status in tuxguitar package in Ubuntu:
  Fix Released
Status in ubufox package in Ubuntu:
  Fix Released
Status in ubuntu-docs package in Ubuntu:
  Fix Released
Status in ubuntu-it-menu package in Ubuntu:
  Fix Released
Status in useragentswitcher package in Ubuntu:
  Fix Released
Status in venkman package in Ubuntu:
  Fix Released
Status in webdeveloper package in Ubuntu:
  Fix Released
Status in wmnetselect package in Ubuntu:
  Fix Released
Status in wysihtml package in Ubuntu:
  Fix Released
Status in xfig package in Ubuntu:
  Fix Released
Status in zekr package in Ubuntu:
  Fix Released
Status in adblock-plus source package in Intrepid:
  Fix Released
Status in all-in-one-sidebar source package in Intrepid:
  Fix Released
Status in amsn source package in Intrepid:
  Fix Released
Status in beagle source package in Intrepid:
  Fix Released
Status in biofox source package in Intrepid:
  Fix Released
Status in classpath source package in Intrepid:
  Fix Released
Status in ctxextensions source package in Intrepid:
  Fix Released
Status in firefox-sage source package in Intrepid:
  Fix Released
Status in firefox-showcase source package in Intrepid:
  Fix Released
Status in flashblock source package in Intrepid:
  Fix Released
Status in foxyproxy source package in Intrepid:
  Fix Released
Status in gnome-chemistry-utils source package in Intrepid:
  Fix Released
Status in greasemonkey source package in Intrepid:
  Fix Released
Status in httrack source package in Intrepid:
  Fix Released
Status in imagezoom source package in Intrepid:
  Fix Released
Status in lastfm source package in Intrepid:
  Fix Released
Status in libjibx-java source package in Intrepid:
  Fix Released
Status in livehttpheaders source package in Intrepid:
  Fix Released
Status in mediatomb source package in Intrepid:
  Fix Released
Status in mozgest source package in Intrepid:
  Fix Released
Status in mozilla-bonobo source package in Intrepid:
  Fix Released
Status in mozilla-noscript source package in Intrepid:
  Fix Released
Status in mozilla-stumbleupon source package in Intrepid:
  Fix Released
Status in nip2 source package in Intrepid:
  Fix Released
Status in nukeimage source package in Intrepid:
  Fix Released
Status in openoffice.org source package in Intrepid:
  Fix Released
Status in pcmanx-gtk2 source package in Intrepid:
  Fix Released
Status in rapache source package in Intrepid:
  Fix Released
Status in scrapbook source package in Intrepid:
  Fix Released
Status in speeddial source package in Intrepid:
  Fix Released
Status in stanford-pwdhash source package in Intrepid:
  Fix Released
Status in tiemu source package in Intrepid:
  Fix Released
Status in tilp source package in 

[Desktop-packages] [Bug 1686243] [NEW] NVIDIA driver

[Sebastian Carter]

Public bug reported:

Trying for days to install an nvidia driver

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
Uname: Linux 4.8.0-49-lowlatency x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Apr 26 01:19:29 2017
DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
 nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2017-04-24 (1 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 
root=UUID=65af2065-0769-48de-9408-1d7d5313f54e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2017-04-25 (0 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.80+git20170420.691a2157-0ubuntu0ricotz~xenial
version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 26 01:05:56 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


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

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

Title:
  NVIDIA driver

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying for days to install an nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
  Uname: Linux 4.8.0-49-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 26 01:19:29 2017
  DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
   nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-04-24 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 

[Desktop-packages] [Bug 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

[Nastooh]

Got this working, based on the comments above (Thank you all), using the 
following steps:
1- Disable PRIME in BIOS
2- Select Discrete Graphics in BIOS
3- Update /etc/default/grub to include
GRUB_CMDLINE_LINUX_DEFAULT="thinkpad-acpi.brightness_enable=1 
acpi_backlight=vendor"
4- update-grub
5- apt-get remove --purge "nvidia*"
6- Add https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers PPA
7- apt update && apt -y upgrade
8- Select Nouveau as display driver, under Software & Updates, Additional 
Drivers tab

After reboot, I am able to use LVDS, VGA and DVI. The only snag is that 
contrast cannot be controlled via keyboard, due to Step 3, above. As a work 
around, I do:
echo x | sudo tee /sys/class/backlight/nv_backlight/brightness, where x is 
between 0 to cat /sys/class/backlight/nv_backlight/max_brightness.
So far, it has been a very good experience, with glxgear showing 60 fps and fan 
running quieter. Cheers,

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Desktop-packages] [Bug 1642967] Re: Processing triggers for tex-common => E: Sub-process /usr/bin/dpkg returned an error code (1)

[i2000s]

Do you mean the lines in /usr/share/texmf/web2c/fmtutil.cnf ? I don't
have the file under /var/lib/texmf shown in your last comment. Anyway,
commenting out the two lines didn't solve my problem...

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

Title:
  Processing triggers for tex-common => E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  After dist-upgrading from 16.04 to 16.10 then running apt-get dist-
  upgrade

  Processing triggers for tex-common (6.05) ...

  
  Warning: Old configuration style found in /etc/texmf/updmap.d
  Warning: For now these files have been included, 
  Warning: but expect inconsistencies.
  Warning: These packages should be rebuild with tex-common.
  Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
  Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg

  texlive-base is not ready, delaying updmap-sys call
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20160819-2) ...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... 
  mktexlsr: Updating /var/lib/texmf/ls-R... 
  mktexlsr: Done.
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Processing triggers for tex-common (6.05) ...

  
  Warning: Old configuration style found in /etc/texmf/updmap.d
  Warning: For now these files have been included, 
  Warning: but expect inconsistencies.
  Warning: These packages should be rebuild with tex-common.
  Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
  Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg

  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
  This may take some time... 
  fmtutil failed. Output has been stored in
  /tmp/fmtutil.VnoTRmP0
  Please include this file if you report a bug.

  dpkg: error processing package tex-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of 
texlive-generic-recommended:
   texlive-generic-recommended depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-generic-recommended (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-base:
   texlive-latex-base depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-base (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-base-doc:
   texlive-latex-base-doc depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-base-doc (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-pstricks:
   texlive-pstricks depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
   texlive-pstricks depends on texlive-generic-recommended (>= 2016); however:
Package texlive-generic-recommended is not configured yet.

  dpkg: error processing package texlive-pstricks (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-recommended:
   texlive-latex-recommended depends on texlive-latex-base (>= 2016); however:
Package texlive-latex-base is not configured yet.
   texlive-latex-recommended depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-recommended (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-extra-utils:
   texlive-extra-utils depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
   texlive-extra-utils depends on texlive-latex-base (>= 2016); however:
Package texlive-latex-base is not configured yet.

  dpkg: error processing package texlive-extra-utils (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-pictures-doc:
   texlive-pictures-doc depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-pictures-doc (--configure):
   dependency problems - leaving unconfigured
  dpkg: 

[Desktop-packages] [Bug 1642967] Re: Processing triggers for tex-common => E: Sub-process /usr/bin/dpkg returned an error code (1)

[Launchpad Bug Tracker]

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

** Changed in: tex-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  Processing triggers for tex-common => E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  After dist-upgrading from 16.04 to 16.10 then running apt-get dist-
  upgrade

  Processing triggers for tex-common (6.05) ...

  
  Warning: Old configuration style found in /etc/texmf/updmap.d
  Warning: For now these files have been included, 
  Warning: but expect inconsistencies.
  Warning: These packages should be rebuild with tex-common.
  Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
  Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg

  texlive-base is not ready, delaying updmap-sys call
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20160819-2) ...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... 
  mktexlsr: Updating /var/lib/texmf/ls-R... 
  mktexlsr: Done.
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Processing triggers for tex-common (6.05) ...

  
  Warning: Old configuration style found in /etc/texmf/updmap.d
  Warning: For now these files have been included, 
  Warning: but expect inconsistencies.
  Warning: These packages should be rebuild with tex-common.
  Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
  Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg

  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
  This may take some time... 
  fmtutil failed. Output has been stored in
  /tmp/fmtutil.VnoTRmP0
  Please include this file if you report a bug.

  dpkg: error processing package tex-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of 
texlive-generic-recommended:
   texlive-generic-recommended depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-generic-recommended (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-base:
   texlive-latex-base depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-base (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-base-doc:
   texlive-latex-base-doc depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-base-doc (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-pstricks:
   texlive-pstricks depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
   texlive-pstricks depends on texlive-generic-recommended (>= 2016); however:
Package texlive-generic-recommended is not configured yet.

  dpkg: error processing package texlive-pstricks (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-latex-recommended:
   texlive-latex-recommended depends on texlive-latex-base (>= 2016); however:
Package texlive-latex-base is not configured yet.
   texlive-latex-recommended depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-latex-recommended (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-extra-utils:
   texlive-extra-utils depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
   texlive-extra-utils depends on texlive-latex-base (>= 2016); however:
Package texlive-latex-base is not configured yet.

  dpkg: error processing package texlive-extra-utils (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-pictures-doc:
   texlive-pictures-doc depends on tex-common (>= 6); however:
Package tex-common is not configured yet.

  dpkg: error processing package texlive-pictures-doc (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of prosper:
   

[Desktop-packages] [Bug 1564778] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in package libsane:i386 1.0.

[Nish Aravamudan]

I followed the same path and dist-upgraded all the way to yakkety and
saw no errors with the package in proposed. I'm not sure, though, if
that really qualifies as a v-d-y, given that I didn't reproduce the
original issue in that path.

# apt policy libsane libsane-common
libsane:
  Installed: 1.0.25+git20150528-1ubuntu2.16.10.1
  Candidate: 1.0.25+git20150528-1ubuntu2.16.10.1
  Version table:
 *** 1.0.25+git20150528-1ubuntu2.16.10.1 500
500 http://archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.25+git20150528-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
libsane-common:
  Installed: 1.0.25+git20150528-1ubuntu2.16.10.1
  Candidate: 1.0.25+git20150528-1ubuntu2.16.10.1
  Version table:
 *** 1.0.25+git20150528-1ubuntu2.16.10.1 500
500 http://archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.25+git20150528-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

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

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is
  also in package libsane:i386 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [ Impact ]

  This is a packaging error when upgrading from trusty to xenial.  You
  may see a file conflict error because a file moved from libsane to
  libsane-common.  This is fairly common, as you can see from the dupes
  and affect-count.

  As described in comment #4, only xenial really needs to be patched.
  But since it shares the same version of sane-backends as yakkety and
  zesty, it's nice to update both of those so that upgraders get a clean
  path.

  [ Test Case ]

  Install libsane and libsane-common on trusty.  Upgrade to xenial.

  [ Regression Potential ]

  Tiny.  This is just a Breaks/Conflict packaging error.  No code
  changes.

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

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

[Desktop-packages] [Bug 26472] Re: Rhythmbox Freezes Upon WiFi Net Drop...

[Raj Reddy]

** Changed in: juniperopenstack/r3.2
   Status: In Progress => Invalid

** Changed in: juniperopenstack/trunk
   Status: In Progress => Invalid

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

Title:
  Rhythmbox Freezes Upon WiFi Net Drop...

Status in Juniper Openstack:
  Invalid
Status in Juniper Openstack r3.2 series:
  Invalid
Status in Juniper Openstack trunk series:
  Invalid
Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Rhythmbox 0.9.0 tends to freeze when my wifi connection drops out. Sometimes 
my
  WiFi connection drops and when it does, Rhythmbox does not recover in grace 
but
  instead freezes up and leaves me with no choice but to kill it. This has
  happened on 386/686 5.10 Breezy Badger while connected and streaming music 
from
  ShoutCast (http://shoutcast.com). To try and reproduce this bug (most likely
  possible even from a lan line) is to disconnect from the net while streaming 
music.

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

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

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

[Desktop-packages] [Bug 1236951] Re: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[i2000s]

Encountered this error when I tried reinstalling the texlive 2015 from
the official source. TeX-common stopped me to reinstall, but I have
tried removing tex-common completely, I think.

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

Title:
  package tex-common 4.04 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

Status in Release Notes for Ubuntu:
  Fix Released
Status in tex-common package in Ubuntu:
  Triaged
Status in tex-common source package in Trusty:
  Triaged

Bug description:
  While updating from 13.04 to 13.10, I was prompted with a crash
  dialog, then a "will automatically revert (?)" dialogue...

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.8.0-31.23-lowlatency 3.8.13.8
  Uname: Linux 3.8.0-31-lowlatency x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  8 12:11:33 2013
  DuplicateSignature: package:tex-common:4.04:ErrorMessage: subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2012-06-12 (482 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1236951/+subscriptions

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

[Desktop-packages] [Bug 1206060] Re: xrandr-tool depends on py3, not py2

[Bryan Quigley]

This was fixed at least in 16.04.

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

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

Title:
  xrandr-tool depends on py3, not py2

Status in xdiagnose package in Ubuntu:
  Fix Released

Bug description:
  Using Ubuntu 13.04, type "xrandr-tool outputs" and watch it crash with
  the following message:

   Traceback (most recent call last):
 File "./xrandr-tool", line 82, in 
   for line in str(xrandr_stdout, encoding='utf8').split("\n"):
   TypeError: str() takes at most 1 argument (2 given)

  in /usr/bin/xrandr-tool, line 82, the str() builtin does not accept a second 
argument. So, this  is wrong.
  Side question: why not port it to Python3 ASAP?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xdiagnose 3.5.1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Mon Jul 29 11:20:04 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-30 (28 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: xdiagnose
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1619407] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Launchpad Bug Tracker]

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I don'y know which details?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Aug 29 16:45:32 2016
  DuplicateSignature:
   package:gconf2:3.2.6-3ubuntu6
   Removing python3-apport (2.20.1-0ubuntu2) ...
   dpkg: error processing package python3-problem-report (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-08-23 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1686188] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[sveinn]

Public bug reported:


Failed on upgrade from 14.04 LTS to 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Apr 25 07:15:33 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-04-06 (1480 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.20
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  
  Failed on upgrade from 14.04 LTS to 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr 25 07:15:33 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-06 (1480 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.20
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1686187] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[sveinn]

Public bug reported:

Failed on upgrade from 14.04 LTS to 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Apr 25 07:15:33 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-04-06 (1480 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.20
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Failed on upgrade from 14.04 LTS to 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr 25 07:15:33 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-06 (1480 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.20
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1686189] [NEW] External monitor connecting problem

[naveenkumarmula]

Public bug reported:

I am facing a problem with Intel Graphics driver. I have external
monitor and in display settings the second monitor is detecting but it's
not working, so could you email me a solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.4.25-040425-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 25 21:45:16 2017
DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
InstallationDate: Installed on 2017-04-25 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 3537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 03JPPR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Inspiron 3537
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Apr 25 21:37:24 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17900 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  External monitor connecting problem

Status in xorg package in Ubuntu:
  New

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: 

[Desktop-packages] [Bug 1400206] Re: Chromium hangs: GPU process hung

[Chris Carlin]

@Richard: what graphics card showed the error and what did not? Did you
ever notice hard drive thrashing while the window was refusing to
redraw?

I MIGHT still be seeing this bug, but I'm not positive it's the one I've
been seeing.

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

Title:
  Chromium hangs: GPU process hung

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Starting with a recent update to either my graphics card, or to
  chromium, it (chromium) will seem to hang after resuming from a lock
  screen. By hang, I mean it seems to refuse to redraw since it still
  responds to mouse clicks on the close button. Here's the stderr output
  on console:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates
  [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed 
to establish GPU channel.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI 
shared context.
  [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  7 22:21:35 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  --- 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-02-16 (1083 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Tags:  utopic
  Uname: Linux 3.11.0-14-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  modified.conffile..etc.chromium.browser.default:
   # Default settings for chromium-browser. This file is sourced by /bin/sh from
   # /usr/bin/chromium-browser
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
   # Options to pass to chromium-browser
   CHROMIUM_FLAGS=""
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190

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

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

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Julian Andres Klode]

(rewording from IRC:) Apparently this needs to go in via security, as
the upgrade would not automatically enable -updates, and we really need
this picked up. Since I can't do security stuff, it'd be best if someone
who can handles the updates.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1681679] Re: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[mohan]

thanks

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

Title:
  package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in deja-dup package in Ubuntu:
  New

Bug description:
  system gets hang whenever multiple apps are running simultaneously, i
  have to remove the battery to make it again work..

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   file-roller:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr 11 12:18:26 2017
  DpkgTerminalLog:
   Preparing to unpack .../file-roller_3.22.1-0ubuntu1_amd64.deb ...
   Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ...
   dpkg: error processing package deja-dup (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:deja-dup:34.2-0ubuntu3.1
   Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ...
   dpkg: error processing package deja-dup (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-10 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: deja-dup
  Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1681679/+subscriptions

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

[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

[jefferson]

Okay, before reverting out of curiousity I did try the recently updates
packages and can confirm the issue is resolved, and everything seems
stable, no regressions.

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in gnome-settings-daemon:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800,
  login screen is too tiny to read. GDM login screen doesn't reflect
  changes to org.gnome.desktop.interface scaling-factor or text-scaling-
  factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

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

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

[Desktop-packages] [Bug 46586] Re: Logitech Media Keyboard Elite not fully supported

[Gunnar Hjalmarsson]

It would be great if somebody who is affected by this could file an
upstream bug.

https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-config

This kind of addition wouldn't be reasonable to patch in Ubuntu only.

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

Title:
  Logitech Media Keyboard Elite not fully supported

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  The media keys on the Logitech Media Keyboard Elite are not supported
  properly - the layout appears to be different than the others already
  included and the kernel does not recognise many of the media/extra
  keys. Currently I have the keyboard hooked up through the USB port.

  I have made the following changes to my system to attempt to support
  this keyboard. Caution: Pressing the key I have mapped as XF86LaunchC
  (F11 with the F-mode light off) will reliably crash and reboot the
  system - I have no idea why.

  At boot time, the following script is run to map the scancodes to the
  console level codes.  I assume that this keyboard really requires
  fixes in the kernel code to recognise this keyboard without the use of
  extra scan codes.

  # Kernel level keycode mappings for the Logitech Media Keyboard Elite USB
  # 6a   190   Zoom In
  # e004 191   Zoom Out
  # 6b   192   Zoom Reset
  # e011 193   Messenger
  # e05a 194   Mode F (switch function keys)
  # e03b 195   (F1 )Help
  # e03c 196   (F2 )Word
  # e03d 197   (F3 )Excel
  # e03e 198   (F4 )Powerpoint
  # e03f 199   (F5 )Undo
  # e040 200   (F6 )Redo
  # e041 201   (F7 )Print
  # e042 202   (F8 )Save
  # e043 203   (F9 )Box A
  # e044 204   (F10)Box B
  # e057 205   (F11)Box C
  # e058 206   (F12)Box D

  setkeycodes \
  6a 190 \
  e004 191   \
  6b 192 \
  e011 193   \
  e05a 194   \
  e03b 195   \
  e03c 196   \
  e03d 197   \
  e03e 198   \
  e03f 199   \
  e040 200   \
  e041 201   \
  e042 202   \
  e043 203   \
  e044 204   \
  e057 205   \
  e058 206
  # ---

  I also made the following alterations to the symbols in
  /etc/X11/xkb/symbols/inet:

  --- inet.20060516   2006-05-16 20:44:30.0 -0400
  +++ inet2006-05-16 20:59:41.0 -0400
  @@ -1244,6 +1244,39 @@
   key   {   [ XF86AudioRaiseVolume  ]   };
   };

  +// Logitech Media Keyboard Elite
  +partial alphanumeric_keys
  +xkb_symbols "logimedelite" {
  +include "inet(logitech_base)"
  +
  +key   {   [ XF86ZoomIn]   };
  +key   {   [ XF86ZoomOut   ]   };
  +key   {   [ XF86Clear ]   };
  +key   {   [ XF86AudioPlay, XF86AudioPause ]   };
  +key   {   [ XF86AudioStop ]   };
  +key   {   [ XF86AudioNext ]   };
  +key   {   [ XF86Messenger ]   };
  +key   {   [ XF86Calculator]   };
  +key   {   [ XF86ModeLock  ]   };
  +
  +key   {   [ XF86Help  ]   };
  +key   {   [ XF86Word  ]   };
  +key   {   [ XF86Excel ]   };
  +key   {   [ XF86Finance   ]   };
  +
  +key   {   [ XF86Back  ]   };
  +key   {   [ XF86Forward   ]   };
  +key   {   [ XF86Book  ]   };
  +key   {   [ XF86Save  ]   };
  +
  +key   {   [ XF86LaunchA   ]   };
  +key   {   [ XF86LaunchB   ]   };
  +key   {   [ XF86LaunchC   ]   };
  +key   {   [ XF86LaunchD   ]   };
  +
  +};
  +
  +
   partial alphanumeric_keys
   xkb_symbols "logiultrax" {
   include "inet(logitech_base)"

  
  Then the three rules files in /etc/X11/xkb/rules were updated as follows:

  toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.20060516 base
  --- base.20060516   2006-05-16 21:00:45.0 -0400
  +++ base2006-05-16 21:01:43.0 -0400
  @@ -38,7 +38,7 @@
 honeywell_euroboard \
 rapidaccess rapidaccess2 rapidaccess2a \
 ltcd logiaccess logicdp logicdpa logicdit logicink logiciink \
  -  logiinkse logiinkseusb logiitc logiik itouch logiultrax \
  +  logiinkse logiinkseusb logiitc logiik itouch logimedelite 
logiultrax \
 mx1998 mx2500 mx2750 \
 microsoftinet microsoftpro microsoftprousb microsoftprooem 
microsoftprose \
 microsoftoffice microsoftmult \

  toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.lst.20060516 base.lst
  --- 

[Desktop-packages] [Bug 1564778] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in package libsane:i386 1.0.

[Nish Aravamudan]

I setup a Trusty LXD, installed libsane and  libsane-common and then
manually updated source.list with the xenial repositories, including
xenial-proposed. I then did `sudo apt-get update; sudo apt-get dist-
upgrade` and the upgrade completed successfully (no error) with the
following versions of libsane and libsane-common.

$ apt policy libsane libsane-common
libsane:
  Installed: 1.0.25+git20150528-1ubuntu2.16.04.1
  Candidate: 1.0.25+git20150528-1ubuntu2.16.04.1
  Version table:
 *** 1.0.25+git20150528-1ubuntu2.16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.0.25+git20150528-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libsane-common:
  Installed: 1.0.25+git20150528-1ubuntu2.16.04.1
  Candidate: 1.0.25+git20150528-1ubuntu2.16.04.1
  Version table:
 *** 1.0.25+git20150528-1ubuntu2.16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.0.25+git20150528-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

** Tags added: verification-needed-yakkety

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

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is
  also in package libsane:i386 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [ Impact ]

  This is a packaging error when upgrading from trusty to xenial.  You
  may see a file conflict error because a file moved from libsane to
  libsane-common.  This is fairly common, as you can see from the dupes
  and affect-count.

  As described in comment #4, only xenial really needs to be patched.
  But since it shares the same version of sane-backends as yakkety and
  zesty, it's nice to update both of those so that upgraders get a clean
  path.

  [ Test Case ]

  Install libsane and libsane-common on trusty.  Upgrade to xenial.

  [ Regression Potential ]

  Tiny.  This is just a Breaks/Conflict packaging error.  No code
  changes.

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

[Alfonso]

Seeing this on a 17.04 fresh install on LibreOffice Calc as well.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 946490] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  chromium-browser crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 17.0.963.56~r121963-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Sun Mar  4 20:55:59 2012
  Desktop-Session:
   DESKTOP_SESSION = gnome-fallback
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-fallback:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/gnome-fallback:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb3cbee5d:mov(%eax),%edx
   PC (0xb3cbee5d) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: Upgraded to precise on 2012-02-10 (23 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
nopasswdlogin plugdev sambashare tape video
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1015430] Re: chromium-browser crashed with SIGSEGV in IA__gdk_x11_window_get_drawable_impl()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in
  IA__gdk_x11_window_get_drawable_impl()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Seems similar to bug 652481, but that one is quite old...

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic i686
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: i386
  Date: Wed Jun 13 12:44:48 2012
  Desktop-Session:
   DESKTOP_SESSION = gnome-fallback
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-fallback:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/gnome-fallback:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  ExecutableTimestamp: 1335856200
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ 
https://mail.google.com/mail/
  ProcCwd: /home/mandriver
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xcbf974 : mov
0xc(%eax),%eax
   PC (0x00cbf974) ok
   source "0xc(%eax)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   gdk_x11_window_get_drawable_impl () from 
/usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  Title: chromium-browser crashed with SIGSEGV in 
gdk_x11_window_get_drawable_impl()
  UpgradeStatus: Upgraded to precise on 2012-02-09 (124 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
nopasswdlogin plugdev sambashare tape video
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1686163] [NEW] Nu am sonor in difuzoare sau este distorsionat

[iulian]

Public bug reported:

Sonorul în difuzoare, este dat la maximum, dar se aude încet și
distorsionat!

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 25 20:24:51 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
 virtualbox, 5.1.18, 4.10.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1858]
InstallationDate: Installed on 2017-04-13 (12 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP 650 Notebook PC
ProcEnviron:
 LANGUAGE=ro
 PATH=(custom, no user)
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=c8fbd7b6-341a-46dc-8f79-c5b887b27f94 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1858
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.33
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd10/19/2012:svnHewlett-Packard:pnHP650NotebookPC:pvr088412005B10002600010:rvnHewlett-Packard:rn1858:rvr65.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 650 Notebook PC
dmi.product.version: 088412005B10002600010
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Apr 25 20:20:14 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Nu am sonor in difuzoare sau este distorsionat

Status in xorg package in Ubuntu:
  New

Bug description:
  Sonorul în difuzoare, este dat la maximum, dar se aude încet și
  distorsionat!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 25 20:24:51 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.10.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1858]
  InstallationDate: Installed on 2017-04-13 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: Hewlett-Packard HP 650 Notebook PC
  ProcEnviron:
   LANGUAGE=ro
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=c8fbd7b6-341a-46dc-8f79-c5b887b27f94 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

@bill - you might try 'sudo dpkg --configure -a' and see if that
resolves the situation.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1686157] [NEW] External Displays Turn Off After Only A Few Seconds Of Inactivity

[Dane Mutters]

Public bug reported:

OS VERSION
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"

UPOWER VERSION
upower:
  Installed: 0.99.4-4
  Candidate: 0.99.4-4
  Version table:
 *** 0.99.4-4 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

EXPECTED BEHAVIOR
Expected displays to stay on while idle, for at least a few minutes (per Power 
Settings).

WHAT HAPPENED INSTEAD (and hardware information)
I just upgraded from a fully-updated Ubuntu 16.10 64-bit Desktop installation 
to 17.04, using the update manager.  In 16.10 and 16.04 LTS, this issue did not 
exist for me.

I'm using a MacBook Pro with Ubuntu installed in a dual-boot
configuration.  I have two attached monitors: one via the mini
DisplayPort and one via HDMI.  I normally keep the laptop lid closed
while working.  Since the upgrade (persisting through several reboots),
whenever I have the notebook lid closed, if I don't touch the keyboard
or mouse for about 5 seconds, both external displays go into power-
saving mode.  When I touch the keyboard/mouse, again, they instantly
come back up (no delay), indicating that the computer had probably not
been suspended.  If I then don't touch the keyboard/mouse for another 5
seconds, they immediately go back into power saving mode.  (Repeat...)

Going into Display Settings and changing "Built-in Display" to on or off
doesn't seem to have any effect.  When I close the lid, it changes
itself back to "OFF"; and when I open the lid, it changes itself back to
"ON".  (This seems like a sensible behavior.)  Notably, the on/off
switch doesn't seem to move unless I exit and re-enter Display Settings.

I found a workaround to this problem on a forum post:
In "/etc/UPower/UPower.conf", change "IgnoreLid=false" to "IgnoreLid=true".

After doing this, the Built-in Display switch stays on whatever I set it
to, regardless of whether the laptop lid is open or closed (which
probably isn't ideal); but more importantly, the external displays no
longer turn off when idle for a few seconds.  They now obey the settings
I explicitly define in Power Settings.

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

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

Title:
  External Displays Turn Off After Only A Few Seconds Of Inactivity

Status in upower package in Ubuntu:
  New

Bug description:
  OS VERSION
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04
  DISTRIB_CODENAME=zesty
  DISTRIB_DESCRIPTION="Ubuntu 17.04"

  UPOWER VERSION
  upower:
Installed: 0.99.4-4
Candidate: 0.99.4-4
Version table:
   *** 0.99.4-4 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  EXPECTED BEHAVIOR
  Expected displays to stay on while idle, for at least a few minutes (per 
Power Settings).

  WHAT HAPPENED INSTEAD (and hardware information)
  I just upgraded from a fully-updated Ubuntu 16.10 64-bit Desktop installation 
to 17.04, using the update manager.  In 16.10 and 16.04 LTS, this issue did not 
exist for me.

  I'm using a MacBook Pro with Ubuntu installed in a dual-boot
  configuration.  I have two attached monitors: one via the mini
  DisplayPort and one via HDMI.  I normally keep the laptop lid closed
  while working.  Since the upgrade (persisting through several
  reboots), whenever I have the notebook lid closed, if I don't touch
  the keyboard or mouse for about 5 seconds, both external displays go
  into power-saving mode.  When I touch the keyboard/mouse, again, they
  instantly come back up (no delay), indicating that the computer had
  probably not been suspended.  If I then don't touch the keyboard/mouse
  for another 5 seconds, they immediately go back into power saving
  mode.  (Repeat...)

  Going into Display Settings and changing "Built-in Display" to on or
  off doesn't seem to have any effect.  When I close the lid, it changes
  itself back to "OFF"; and when I open the lid, it changes itself back
  to "ON".  (This seems like a sensible behavior.)  Notably, the on/off
  switch doesn't seem to move unless I exit and re-enter Display
  Settings.

  I found a workaround to this problem on a forum post:
  In "/etc/UPower/UPower.conf", change "IgnoreLid=false" to "IgnoreLid=true".

  After doing this, the Built-in Display switch stays on whatever I set
  it to, regardless of whether the laptop lid is open or closed (which
  probably isn't ideal); but more importantly, the external displays no
  longer turn off when idle for a few seconds.  They now obey the
  settings I explicitly define in Power Settings.

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

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

[Desktop-packages] [Bug 1683512] Re: No libcuda.so.1 after upgrading to 381-driver

[n1k31t4]

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  No libcuda.so.1 after upgrading to 381-driver

Status in nvidia-graphics-drivers package in Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  New
Status in theano package in Ubuntu:
  New

Bug description:
  I had a problem with window edges after waking from suspend - see
  here: https://askubuntu.com/questions/896221/strange-artifacts-along-
  window-borders-after-waking-computer-from-sleep-mode/

  For this reason I upgraded to the newer driver, from 375.39 to 381.09.

  I have posted this question on AskUbuntu, with some extra information!
  
https://askubuntu.com/questions/905993/missing-libcuda-so-1-file-after-upgrading-to-newest-nvidia-driver

  Since upgrading, I have had to reinstall the Cuda Toolkit 8.0 (and CUDNN 
v5.1), however there seems to be a driver file missing, which prevents me from 
installing both Tensorflow and the gputools package in R, which build upon the 
Cuda Toolkit, which in turn needs the missing libcuda.so.1 file.
  Neither Tensorflow no gputools are able to locate the file: libcuda.so.1.
  Here is a similar issue, but with older drivers involved:  
https://github.com/tensorflow/tensorflow/issues/4078

  I have read that I could possibly create this file as it is a symlink, 
however I would prefer not to, as I do not know what other dependencies exist.
  Example of possible workaround:   
http://stackoverflow.com/questions/41890549/tensorflow-cannot-open-libcuda-so-1

  I am running Ubuntu 16.04.

  Can somebody see why this file is missing or propose a stable
  solution?

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

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

[Desktop-packages] [Bug 1277454] Re: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  In synaptic, I clicked on "open web site" button of a package.
  Chromium crashed when starting (it was not running yet.)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 31.0.1650.63-0ubuntu1~20131204.1
  ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Fri Feb  7 12:04:40 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins: (no entry found in the Preferences file)
  DiskUsage:
   b'File systemTipo  Dim. Usati Dispon. Uso% Montato su\n/dev/sda13
 ext4   31G   16G 13G  56% /\nnone   tmpfs 4,0K 0
4,0K   0% /sys/fs/cgroup\nudev   devtmpfs  1,9G  4,0K1,9G   1% 
/dev\ntmpfs  tmpfs 386M  1,3M385M   1% /run\nnone   
tmpfs 5,0M 05,0M   0% /run/lock\nnone   tmpfs 1,9G  
216K1,9G   1% /run/shm\nnone   tmpfs 100M   36K100M   1% 
/run/user\n'
   
   Inodes:
   b'File systemInode IUsati ILiberi IUso% Montato su\n/dev/sda13  2,0M 
  287K1,7M   15% /\nnone483K  2483K1% 
/sys/fs/cgroup\nudev480K543479K1% /dev\ntmpfs   
483K595482K1% /run\nnone483K  3483K1% 
/run/lock\nnone483K  8483K1% /run/shm\nnone
483K 24483K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-28 (40 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131228)
  ProcCmdline: chromium-browser\ https://launchpad.net/mugshot
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   base::debug::BreakDebugger() () from 
/usr/lib/chromium-browser/libs/libbase.so
   ?? ()
   ?? ()
   ?? ()
   content::BrowserMainLoop::PreCreateThreads() () from 
/usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Pontus]

I'll add that I've got the same issue; the settings slider has no effect
on the mouse speed (ThinkPad USB Laser Mouse).

I solved it by removing the following package (NOT RECOMMENDED, MAY BREAK YOUR 
SYSTEM):
  xserver-xorg-input-libinput

This introduced a new issue described here:
https://askubuntu.com/questions/904707/sound-indicator-system-slider-
jumps-in-steps-of-10

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xinput package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

[Adam Jacobs]

Yes.  I'm running 17.04 and Unity.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1686155] [NEW] Trackpoint sensitivity on Dell Latitude 5470 is insane

[Alexey]

Public bug reported:

Hello. I've tried to write on askUbuntu and to the Dell Support but got no 
answers.
My problem is that I can setup my trackpoint properly on Ubuntu. It works 
awesome on Windows with or without drivers installed. 
I've come across this thread 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590
which says that trackpoint is not recognized by ubuntu on 16.04 and it was 
fixed in 17.04
So I thought that 5470 and 7470 are pretty close and tried new 17.04 ubuntu but 
the result is the same.

with xinput on 16.04 command I was able to set up 3 parameters but on
17.04 there are no such parameters:

xinput list-props 13
Device 'AlpsPS/2 ALPS DualPoint Stick':
Device Enabled (140):   1
Coordinate Transformation Matrix (142): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Accel Speed (309): 0.00
libinput Accel Speed Default (310): 0.00
libinput Accel Profiles Available (311):1, 1
libinput Accel Profile Enabled (312):   1, 0
libinput Accel Profile Enabled Default (313):   1, 0
libinput Natural Scrolling Enabled (314):   0
libinput Natural Scrolling Enabled Default (315):   0
libinput Send Events Modes Available (260): 1, 0
libinput Send Events Mode Enabled (261):0, 0
libinput Send Events Mode Enabled Default (262):0, 0
libinput Left Handed Enabled (316): 0
libinput Left Handed Enabled Default (317): 0
libinput Scroll Methods Available (318):0, 0, 1
libinput Scroll Method Enabled (319):   0, 0, 1
libinput Scroll Method Enabled Default (320):   0, 0, 1
libinput Button Scrolling Button (321): 2
libinput Button Scrolling Button Default (322): 2
libinput Middle Emulation Enabled (323):0
libinput Middle Emulation Enabled Default (324):0
Device Node (263):  "/dev/input/event6"
Device Product ID (264):2, 8
libinput Drag Lock Buttons (325):   
libinput Horizontal Scroll Enabled (326):   1

and this is a 16.04 parameters:
https://askubuntu.com/questions/908477/configure-trackpoint-on-dell-latitude-5470

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Trackpoint sensitivity on Dell Latitude 5470 is insane

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Hello. I've tried to write on askUbuntu and to the Dell Support but got no 
answers.
  My problem is that I can setup my trackpoint properly on Ubuntu. It works 
awesome on Windows with or without drivers installed. 
  I've come across this thread 
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590
  which says that trackpoint is not recognized by ubuntu on 16.04 and it was 
fixed in 17.04
  So I thought that 5470 and 7470 are pretty close and tried new 17.04 ubuntu 
but the result is the same.

  with xinput on 16.04 command I was able to set up 3 parameters but on
  17.04 there are no such parameters:

  xinput list-props 13
  Device 'AlpsPS/2 ALPS DualPoint Stick':
Device Enabled (140):   1
Coordinate Transformation Matrix (142): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Accel Speed (309): 0.00
libinput Accel Speed Default (310): 0.00
libinput Accel Profiles Available (311):1, 1
libinput Accel Profile Enabled (312):   1, 0
libinput Accel Profile Enabled Default (313):   1, 0
libinput Natural Scrolling Enabled (314):   0
libinput Natural Scrolling Enabled Default (315):   0
libinput Send Events Modes Available (260): 1, 0
libinput Send Events Mode Enabled (261):0, 0
libinput Send Events Mode Enabled Default (262):0, 0
libinput Left Handed Enabled (316): 0
libinput Left Handed Enabled Default (317): 0
libinput Scroll Methods Available (318):0, 0, 1
libinput Scroll Method Enabled (319):   0, 0, 1
libinput Scroll Method Enabled Default (320):   0, 0, 1
libinput Button Scrolling Button (321): 2
libinput Button Scrolling Button Default (322): 2
libinput Middle Emulation Enabled (323):0
libinput Middle Emulation Enabled Default (324):0
Device Node (263):  "/dev/input/event6"
Device Product ID (264):2, 8
libinput Drag Lock Buttons (325):   
libinput Horizontal Scroll Enabled (326):   1

  and this is a 16.04 

[Desktop-packages] [Bug 1677327] Re: SRU request: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]

[Andy Whitcroft]

** Tags added: kernel-adt-failure kernel-adt-failure-hwe-edge-4.10

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

Title:
  SRU request: dkms build fails with zesty hwe kernel [error: too few
  arguments to function ‘NV_GET_USER_PAGES’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  The patch for Linux 4.9 in nvidia-340 in Ubuntu 16.04 does not match the one 
in 17.04. As a result, the module fails to build against the hwe 4.10 kernel.

  [Test Case]
  1) Enable the xenial-proposed repository, and install 
linux-headers-generic-hwe-16.04-edge, linux-image-generic-hwe-16.04-edge, and 
nvidia-340.

  2) Check that DKMS builds the module, then restart the system, and see
  if it boots correctly. If unsure, please attach your /var/log/gpu-
  manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the exact same patch is already available in the package in 17.04.

  
  _
  ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz

  We need to backport build fixes for 4.9/4.10 kernels.

  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function 
‘os_lock_user_pages’:
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing 
argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast 
[-Wint-conversion]
   page_count, write ? FOLL_WRITE : 0, user_pages, 
NULL);
   ^
  In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0:
  /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected 
‘int’ but argument is of type ‘struct page **’
   static inline long NV_GET_USER_PAGES(unsigned long start,
  ^
  /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few 
arguments to function ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,

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

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

[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Jeremy Bicha]

** Description changed:

  I'm splitting this issue off from LP: #1685542 (which made xserver-xorg-
  input-all no longer recommend xserver-xorg-input-synaptics) for tracking
  the remaining issues.
  
  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which haven't
  been ported to libinput yet), synaptics overrides libinput. That makes
  gnome-control-center's Mouse & Touchpad settings panel only show basic
  settings and important configurations don't work.
  
  Questions
  -
  1. Which desktops/apps still need -synaptics?
+ - Unity
+ - Xfce?
+ - LXDE? LXQt?
+ All the other major desktops have already been ported (LP: #1417980)
  
  2. Can these apps be ported or removed before 18.04 LTS is released?
  
  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?
  
  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?
  
  5. Is there any other way we can fix this conflict?

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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

[Desktop-packages] [Bug 1685683] Re: Update evolution to 3.24.1

[Jeremy Bicha]

** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
  I made a few packaging changes we should review with Debian.
  
  1. I dropped https://sources.debian.net/src/evolution-data-
  server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries depend
  on it.
  
  2. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
  3. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.
  
  To Do
  =
- 4. https://bugzilla.gnome.org/show_bug.cgi?id=781645
- 
- 5. Hook up the new installed-tests packages to be ran as autopkgtests
+ 4. Hook up the new installed-tests packages to be ran as autopkgtests

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

Title:
  Update evolution to 3.24.1

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.

  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages

  I made a few packaging changes we should review with Debian.

  1. I dropped https://sources.debian.net/src/evolution-data-
  server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries
  depend on it.

  2. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not
  directly apply to cmake and it doesn't seem needed. The soname hasn't
  been bumped in 5 years. I had to have libevolution Breaks/Replaces
  evolution-dev since there are no .so symlinks any more.

  3. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.

  To Do
  =
  4. Hook up the new installed-tests packages to be ran as autopkgtests

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

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

[Desktop-packages] [Bug 1606959] Re: DPI setting is not correctly calculated on Ubuntu GNOME

[Olivier Tilloy]

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

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

Title:
  DPI setting is not correctly calculated on Ubuntu GNOME

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser,
  unlike any other app I've found, gets the wrong DPI, and starts up
  unscaled.

  On investigation, this appears to be because of a bug in
  desktop_screen_x11.cc (I checked this only in the sources for the
  currently shipped version of Chromium, against which I'm reporting
  this bug).

  The hardware is *correctly* queried via the GTK2 back-end in
  gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of
  desktop_screen_x11.cc.

  However, this is then unconditionally overridden lower down. In line
  356, density_indicator is set to 8 (this corresponds to a scale factor
  of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to
  read a value from the gsettings key /com/ubuntu/user-interface/scale-
  factor.

  Aside: Under Unity, I understand that this setting is populated with
  information about the connected displays (I did try to find where this
  happens, but I can only find references to the setting in unity-
  control-center, while presumably it must also be set whenever a new
  display is plugged or unplugged); under GNOME it seems not to be.

  The problem is that when the gsettings key /com/ubuntu/user-interface
  /scale-factor is empty, or absent, the default value of
  density_indicator is still used, overriding the hardware-provided
  value. The only circumstances in which the hardware-provided value
  will be used are when the key for the relevant display is explicitly
  set to 0.

  This means that scaling won't work on a GNOME system, which is ironic
  considering that the correct information has already been obtained
  from Gtk!

  As far as I can see, the fix is to change the setting of 8 in line 356
  to 0, so that if no gsettings value can be obtained, then the
  hardware-supplied value, which has already been calculated, is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM=
   dpms: On
   modes: 2560x1600
   enabled: enabled
   status: connected
  Date: Wed Jul 27 15:14:57 2016
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  Env:
   'None'
   '/home/rrt/.local/lib/x86_64-linux-gnu'
  InstallationDate: Installed on 2015-12-28 (212 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Load-Avg-1min: 0.49
  Load-Processes-Running-Percent:   0.1%
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-07-25 (2 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

[Ads20000]

Is this also occurring with Unity too then? What about GNOME Shell? I
get it in the Snap (and the original report was me seeing it on GNOME
Flashback on 16.10) but I haven't seen it in the Deb on Unity or GNOME
Shell yet.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1171674] Re: Chromium renders Korean text (Hangul) illegibly

[Olivier Tilloy]

According to
https://bugs.chromium.org/p/chromium/issues/detail?id=233851 this was a
bug in the font itself, and has been fixed since then.

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

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

Title:
  Chromium renders Korean text (Hangul) illegibly

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Install chromium-browser and visit a page with Korean text, e.g.:

  
http://ko.wikipedia.org/wiki/%EC%84%A0%ED%92%8D%EA%B8%B0_%EC%82%AC%EB%A7%9D%EC%84%A4

  Hangul text inside the rendering area (but not outside it, e.g. tabs)
  is smashed together; see attached screenshot.

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

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

[Desktop-packages] [Bug 1417980] Re: Add support for unified Xorg input driver

[Timo Aaltonen]

Pretty sure this is a wontfix for Unity by now.

** Changed in: cinnamon-settings-daemon (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Won't Fix

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

** No longer affects: cinnamon-control-center (Ubuntu)

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

Title:
  Add support for unified Xorg input driver

Status in cinnamon-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in mate-control-center package in Ubuntu:
  Fix Released
Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  xserver-xorg-input-libinput driver will eventually replace current
  input drivers (evdev, synaptics at first, wacom later). This needs
  changes to the desktop configuration tools.

  
  background info:
  http://www.x.org/wiki/Events/XDC2014/XDC2014HuttererLibInput/xdc-2014.html
  
https://fosdem.org/2015/schedule/event/libinput/attachments/slides/591/export/events/attachments/libinput/slides/591/libinput_xorg.pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinnamon-settings-daemon/+bug/1417980/+subscriptions

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

[Desktop-packages] [Bug 1009614] Re: Launcher-icon shown twice when running

[Olivier Tilloy]

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

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

Title:
  Launcher-icon shown twice when running

Status in Unity:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Invalid
Status in software-center package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Chromium's icon in Unity's launcher is added to the starter a second
  time when Chromium is running.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Wed Jun  6 19:09:48 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1400206] Re: Chromium hangs: GPU process hung

[Richard Eames]

@Olivier: No, I haven't seen this bug in a while since I changed my
video cards. (I do still see the tooltip graphical artefacts when
hovering over the tabs, but it doesn't lock my browser.)

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

Title:
  Chromium hangs: GPU process hung

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Starting with a recent update to either my graphics card, or to
  chromium, it (chromium) will seem to hang after resuming from a lock
  screen. By hang, I mean it seems to refuse to redraw since it still
  responds to mouse clicks on the close button. Here's the stderr output
  on console:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates
  [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed 
to establish GPU channel.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI 
shared context.
  [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  7 22:21:35 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  --- 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-02-16 (1083 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Tags:  utopic
  Uname: Linux 3.11.0-14-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  modified.conffile..etc.chromium.browser.default:
   # Default settings for chromium-browser. This file is sourced by /bin/sh from
   # /usr/bin/chromium-browser
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
   # Options to pass to chromium-browser
   CHROMIUM_FLAGS=""
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190

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

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

[Desktop-packages] [Bug 1303034] Re: crashed

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  crashed

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  I don't know what caused the crash

  L14.04 all updates installed including latest bios

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 33.0.1750.152-0ubuntu1~pkg995.1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Apr  5 14:30:40 2014
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/Lubuntu:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-04-03 (1 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140401)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser --enable-pinch
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 953353] Re: chromium-browser crashed with SIGSEGV in type_check_is_value_type_U()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in type_check_is_value_type_U()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Broke whilst visiting http://www.srcf.net/webdesktop/ Crash report
  automatically generated.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 17.0.963.79~r125985-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar 12 19:44:04 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so\ 
--lang=en-GB\ --channel=5243.0x7faaab785230.2003420797
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f49d0e8835e :
testb  $0x8,0x16(%rbx)
   PC (0x7f49d0e8835e) ok
   source "$0x8" ok
   destination "0x16(%rbx)" (0xaabe) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   g_type_check_is_value_type () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_value_init () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_plug_new_for_display () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: chromium-browser crashed with SIGSEGV in g_type_check_is_value_type()
  UpgradeStatus: Upgraded to precise on 2012-03-10 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in apport package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Test Case
  -
  1) Set your default browser to Chromium.
  2) Launch synaptic
  3) Click on the home page url for a package.
  4) Observe chromium-browser not launch
  5) Receive apport crash dialog
  5) Also notice the apport crash dialog refers to upstart / systemd

  none

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:

  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

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

[Desktop-packages] [Bug 966054] Re: chromium-browser crashed with SIGSEGV in gtk_gc_key_hash()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in gtk_gc_key_hash()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  have no description

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 17.0.963.83~r127885-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 12:17:11 2012
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so\ 
--lang=en-GB\ --channel=7907.0x7fc05e5a6370.743642940
  ProcEnviron:
   
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  Title: chromium-browser crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 981826] Re: chromium-browser crashed with SIGABRT in __assert_fail_base()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGABRT in __assert_fail_base()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  I was watching a flash video on a website.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 14 21:12:26 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/flashplugin-installer/libflashplayer.so\ --lang=en-US\ 
--channel=25012.0x7f1fa0c30280.1228555870
  ProcEnviron:
   
  Signal: 6
  SourcePackage: chromium-browser
  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
   __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: chromium-browser crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1058304] Re: Pepper Flash 11.3.31.232 crashes on Chromium 20.0 (Precise)

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Pepper Flash 11.3.31.232 crashes on Chromium 20.0 (Precise)

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Hi, when running Pepper Flash on Chromium it crashed at:
  http://sverigesradio.se/sida/artikel.aspx?programid=2327=5286854

  See also: Re: Chromium Flash Pepper on precise, how?
  http://ubuntuforums.org/showpost.php?p=12072504=13

  I'm using Lubuntu 12.04 which is based on Ubuntu 12.04 LTS (Precise
  Pangolin), but Lubuntu 12.04 is not a LTS. Chromium Version
  20.0.1132.47 Ubuntu 12.04 (144678)

  Result of chrome://plugins

  Flash - Version: 11.3.31.232
  Shockwave Flash 11.3 r31
  Namn: Shockwave Flash
  Beskrivning:  Shockwave Flash 11.3 r31
  Version:  11.3.31.232
  Plats:/usr/lib/chromium-browser/libpepflashplayer.so
  Typ:  PPAPI (utanför process)
 Inaktivera
  MIME-typer:   
  MIME-typ  Beskrivning Filtillägg
  application/x-shockwave-flash Shockwave Flash 
  .swf
  application/futuresplash  FutureSplash Player 
  .spl

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 28 21:32:17 2012
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = /etc/xdg/lubuntu/:/etc/xdg/xdg-Lubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/share/Lubuntu:/usr/local/share/:/usr/share/:/usr/share:/usr/share/gdm:/var/lib/menu-xdg
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: 
CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
 --ppapi-flash-version=11.3.31.232"
  modified.conffile..etc.chromium.browser.default:
   # Default settings for chromium-browser. This file is sourced by /bin/sh from
   # /usr/bin/chromium-browser
   
   # Options to pass to chromium-browser
   
CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
 --ppapi-flash-version=11.3.31.232"
  mtime.conffile..etc.chromium.browser.default: 2012-09-25T23:47:40.370395

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

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

[Desktop-packages] [Bug 719183] Re: chromium-browser hangs when webgl is enabled

[Olivier Tilloy]

According to the upstream chromium bug, this was an issue in Modernizr.

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

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

Title:
  chromium-browser hangs when webgl is enabled

Status in Mesa:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: chromium

  chromium-browser fails to open sourceforge.net pages when webgl is enabled 
(default). I also filed a chromium bug:
  http://code.google.com/p/chromium/issues/detail?id=72737

  Here what happens when starting chromium from the commandline:
  fritz@jfh00:~$ chromium-browser http://sourceforge.net/projects/pidgin/
  libEGL warning: unable to load st_GL.so
  /usr/lib/chromium-browser/chromium-browser --type=gpu-process 
--channel=2862.0xba19c650.558368832: symbol lookup error: 
/usr/lib/egl/egl_gallium.so: undefined symbol: drmGetMagic

  sourceforge.net pages load when started with --disable-webgl

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

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

[Desktop-packages] [Bug 574740] Re: No sound on YouTube only in Chromium (Firefox works fine)

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report issues occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

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

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

Title:
  No sound on YouTube only in Chromium (Firefox works fine)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: chromium-browser

  I'm using the Chromium Browser installed from the Software Center, and
  when I visit YouTube (any video) the video plays fine, but there's no
  sound at all. Visiting the same videos with Firefox plays sound with
  no problems.

  I'm using Chromium package 5.0.342.9~r43360-0ubuntu2 on lucid. Also,
  I'm using ALSA to play sound on my Creative X-Fi sound card.

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

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

[Desktop-packages] [Bug 529758] Re: Extension to install a flash provider

[Olivier Tilloy]

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

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

Title:
  Extension to install a flash provider

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in Baltix:
  New

Bug description:
  Binary package hint: chromium-browser

  I would be nice if chromium have a application to install flash
  plugin, like Firefox have to install the closed source plugin, or a
  free alternative.

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

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

[Desktop-packages] [Bug 755036] Re: chrome plugin crashes when calling javascript function

[Olivier Tilloy]

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

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

Title:
  chrome plugin crashes when calling javascript function

Status in Iced Tea:
  Invalid
Status in chromium-browser package in Ubuntu:
  Invalid
Status in icedtea-web package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: icedtea6-plugin

  Working with chrome on ubuntu, have a basic java applet and javascript
  interaction.  The javascript to java goes fine, but when I try having
  the java fire a javascript method, the chrome java plugin crashes.
  This all works fine in Fire Fox.

  The Error:

  The following plug-in has crashed: icedTea NPR Web Broweser Plugin
  (using IcedTea6 1.9.7 (6b20-1.9.7-0ubuntu1~10.04.1))

  
  The HTML:
  
  
   
   
   
  
 
  The Javascript:
  
  function updateWebPage(){
  alert("java is touching me");
  document.thisappletawesome.setText("hihihi")
  }

  
  The Java:
   
  import java.applet.*;
  import java.awt.*;
  import netscape.javascript.*;
  import javax.swing.*;

  public class JSHelloWorld extends JApplet {
  JTextArea txt = new JTextArea(100,100);
  
  public void init(){
JSObject jso = JSObject.getWindow(this);
try {
jso.call("updateWebPage", new String[] {"Hihi"});
  }
  catch (Exception ex) {
 ex.printStackTrace();
  }
  }
  
  public JSHelloWorld() {
  txt.setText("Hello World");
  getContentPane().add(txt);
  }
  
  public void setText(String s)
  {
  txt.setText(s);
  }
   

  
  The problem looks like it was with OpenJDK.
   sudo aptitude remove icedtea6-plugin
   sudo aptitude install sun-java6-plugin
  Fixed the problem.

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

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

[Desktop-packages] [Bug 1374222] Re: path for policy files changed

[Olivier Tilloy]

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

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

Title:
  path for policy files changed

Status in apparmor package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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

[Desktop-packages] [Bug 1393902] Re: GOOG search credit flag isn't always in search queries

[Olivier Tilloy]

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

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

Title:
  GOOG search credit flag isn't always in search queries

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  We expect "client=ubuntu" or "client=browser-ubuntu" in every GOOG
  search query URL.

  It isn't in every search, but is in some. The user-profile's age
  (probably in versions, not time) seems to be a factor, or whether one
  is logged-in to Google for sync seems to be a factor too.

  data:

  who:
  (ntpf|loc)  New Tab Page Form or Location
  L=logged in too G Apps
  N=profile created with this version
  (nn) = version
  "client=value"

  cm: ntpf  N (37.0.2062.94=utopicrel) "client=ubuntu-browser"
  cm: loc   N (37.0.2062.94=utopicrel) "client=ubuntu-browser"
  cm: ntpf LN (37.0.2062.94=utopicrel) "client=ubuntu-browser"
  cm: loc  LN (37.0.2062.94=utopicrel) "client=ubuntu-browser"
  cm: ntpf  N (34.0.1847.116=trustyrel) "client=ubuntu-browser"
  cm: loc   N (34.0.1847.116=trustyrel) "client=ubuntu-browser"
  cm: ntpf LN (38.0.2125.111) "client=ubuntu-browser"
  cm: ntpf  N (38.0.2125.111) "client=ubuntu-browser"
  cm: ntpf L  (38.0.2125.111) "client=ubuntu-browser"
  cm: ntpf(38.0.2125.111) "client=ubuntu-browser"
  cm: loc  LN (38.0.2125.111) "client=ubuntu-browser"
  cm: loc   N (38.0.2125.111) "client=ubuntu-browser"
  cm: loc  L  (38.0.2125.111) "client=ubuntu-browser"
  cm: loc (38.0.2125.111) "client=ubuntu-browser"

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

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

[Desktop-packages] [Bug 1584506] Re: Chromium

[Olivier Tilloy]

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

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

Title:
  Chromium

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  In certain site flashes the screen.
  Both Chromium and stable Chrome 
  Chromium  50.0.2661.102 (Versão do desenvolvedor) Ubuntu 16.04 64 bits
  Revisão   496034c629901db4564ba5613e2d736635eeb082
  SOLinux 
  Blink 537.36 (@496034c629901db4564ba5613e2d736635eeb082)
  JavaScriptV8 5.0.71.48
  Flash 21.0.0.216
  Agente do usuário Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 
(KHTML, like Gecko) Ubuntu Chromium/50.0.2661.102 Chrome/50.0.2661.102 
Safari/537.36
  Linha de comando  /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=21.0.0.216 --enable-pinch 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=21.0.0.216 --enable-pinch --window-depth=24 
--flag-switches-begin --flag-switches-end
  Caminho do executável /usr/lib/chromium-browser/chromium-browser
  Caminho de perfil /home/leandro/.config/chromium/Default
  Variações 16e0dd70-3f4a17df
  f19a86b5-55d854e7
  930c120f-3f4a17df
  cf5ed6e1-3f4a17df
  775ebbd7-3f4a17df
  dd4da2fc-3f4a17df
  64cbdfc2-3f4a17df
  f5dd6118-2f5721af
  4ea303a6-3f4a17df
  fa99bb73-3f4a17df
  dbffab5d-f51b51
  30e679f-3f4a17df
  c8b9b12d-d93a0620
  867c4c68-3f4a17df
  12a73824-3f4a17df

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

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

[Desktop-packages] [Bug 1661245] Re: chromium-browser 55 version on Zesty : FTBFS

[Olivier Tilloy]

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

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

Title:
  chromium-browser 55 version on Zesty : FTBFS

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Perhaps this bug should be reported against the current Zesty state but the 
chromium-browser in Zesty is stuck at version 53 which is practically unusable 
with many HTTPS sites because of erroneous security warnings. The same thin 
happened on Yakkety and a version bump to 55 solved the issues.
  Please bump the version on Zesty.

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

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

[Desktop-packages] [Bug 1365524] Re: Nach Neuinstall alles gut, nach Aktualisierung nicht mehr zu öffnen

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Nach Neuinstall alles gut, nach Aktualisierung nicht mehr zu öffnen

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Ich sprach von  >pdfshuffler<, lässt sich nicht öffnen nach
  Aktualiesierung?!

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep  4 15:35:15 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3724.0.1298319176\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x1002\ --gpu-device-id=0x6899\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

[Adam Jacobs]

I see it on upgrade from 16.10.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.18.9-1ubuntu3.3

---
gtk+3.0 (3.18.9-1ubuntu3.3) xenial; urgency=medium

  * Backport upstream patch to fix lagging and visual issues in Nautilus
(toggled-not-clicked.patch, LP: #1562002).

 -- Dmitry Shachnev   Thu, 23 Mar 2017 22:44:18
+0300

** Changed in: gtk+3.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Nautilus: lag after choosing action in top right menu

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released

Bug description:
  # Impact
  This is known to affect Nautilus, but can potentially affect other 
applications too (the upstream bug has an example test app attached).

  See also the duplicate bug 1644393, which is another appearance of the
  same bug but with other symptoms.

  # Proposed Fix
  The proposed fix is an upstream commit taken from gtk-3-20 branch:
  https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1

  # Test Case
  https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case.

  # Regression Potential
  The bug is fixed in GTK+ 3.20.9, so the fix was already present in the 
version that shipped with Yakkety. I am not aware of any regressions.

  -
  choosing action like New Tab, New Folder, Select Items Matching, will make 
nautilus lag (unresponsive)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 25 20:52:21 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+685+36'"
  InstallationDate: Installed on 2016-03-24 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1286902] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  lsb_release -rd
  Description:Ubuntu Trusty Tahr (development branch)
  Release:14.04

  
  apt-cache policy chromium-browser
  chromium-browser:
Installed: 32.0.1700.107-0ubuntu1~20140204.977.1
Candidate: 32.0.1700.107-0ubuntu1~20140204.977.1
Version table:
   *** 32.0.1700.107-0ubuntu1~20140204.977.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 32.0.1700.107-0ubuntu1~20140204.977.1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  3 04:54:15 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins: (no entry found in the Preferences file)
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2012-09-30 (518 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  ProcCmdline: chromium-browser\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=12.0.0.70
  SegvAnalysis:
   Segfault happened at: 0x7f0b2a73157d:mov0x10(%rax),%rdx
   PC (0x7f0b2a73157d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (112 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  mtime.conffile..etc.chromium.browser.default: 2014-02-24T07:07:20.065993

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

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

[Desktop-packages] [Bug 1309348] Re: chromium-browser crashed with SIGSEGV in size()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in size()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  this happens when you try to sign in to your google account.

  apt-cache policy chromium-browser
  chromium-browser:
    Installed: 34.0.1847.116-0ubuntu2
    Candidate: 34.0.1847.116-0ubuntu2
    Version table:
   *** 34.0.1847.116-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  Uname: Linux 3.14.0-999-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Apr 18 13:56:21 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2012-09-30 (564 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  ProcCmdline: chromium-browser\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=12.0.0.77\ --enable-pinch
  SegvAnalysis:
   Segfault happened at: 0x7fd672296361 
<_ZNK3net19HttpResponseHeaders10FindHeaderEmRKN4base16BasicStringPieceISsEE+17>:
mov0x10(%rdi),%rax
   PC (0x7fd672296361) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   net::HttpResponseHeaders::FindHeader(unsigned long, 
base::BasicStringPiece const&) const () from 
/usr/lib/chromium-browser/libs/libnet.so
   net::HttpResponseHeaders::HasHeader(base::BasicStringPiece 
const&) const () from /usr/lib/chromium-browser/libs/libnet.so
   ?? ()
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV in 
net::HttpResponseHeaders::FindHeader()
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (158 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-03-23T05:34:43.487383

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

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

[Desktop-packages] [Bug 1311169] Re: Chromium crashed with SIGSEGV in aura::rootWindow()::CanDispatchToConsumer() [happens while using with touchscreen]

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Chromium crashed with SIGSEGV in
  aura::rootWindow()::CanDispatchToConsumer() [happens while using with
  touchscreen]

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Chromium crashed while I was trying to use it with a touch screen
  laptop.

  maybe related bug:
  https://code.google.com/p/chromium/issues/detail?id=342040

  Also attached .crash file.

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

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

[Desktop-packages] [Bug 1573408] Re: GNOME Software does not install third-party .deb packages

[Luis Alvarado]

This affects Ubuntu 17.04 32 / 64. I just noticed this error when trying
to install google chrome, virtualbox, sublime, atom, basically
everything I had prepared. So I see it's being worked on which is
excellent news.

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

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1360463] Re: chromium-browser crashed with SIGSEGV in printing::PrintingContextLinux::PrintDocument()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in
  printing::PrintingContextLinux::PrintDocument()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  I had 3 tabs open in Chromium and tried to print a page and chromium-
  browser closed with this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 36.0.1985.143-0ubuntu1~pkg1042
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Aug 22 18:17:19 2014
  Desktop-Session:
   DESKTOP_SESSION = gnome-fallback-compiz
   XDG_CONFIG_DIRS = 
/etc/xdg/xdg-gnome-fallback-compiz:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/gnome-fallback-compiz:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda5  
ext4   15G  9.3G  4.7G  67% /\nudev   devtmpfs  1.9G 0  1.9G   
0% /dev\ntmpfs  tmpfs 396M  6.1M  390M   2% /run\ntmpfs  
tmpfs 2.0G  496K  2.0G   1% /dev/shm\ntmpfs  tmpfs 2.0G 0  
2.0G   0% /sys/fs/cgroup\ntmpfs  tmpfs 100M   60K  100M   1% 
/run/user\ntmpfs  tmpfs 5.0M  4.0K  5.0M   1% /run/lock\n/dev/sdb1  
fuseblk   932G  593G  340G  64% /media/cavsfan/Fantom\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda5959K  
312K  647K   33% /\nudev 484K   557  483K1% /dev\ntmpfs 
   495K   660  494K1% /run\ntmpfs495K 9  495K1% 
/dev/shm\ntmpfs495K15  495K1% /sys/fs/cgroup\ntmpfs 
   495K39  495K1% /run/user\ntmpfs495K 6  495K1% 
/run/lock\n/dev/sdb1340M  125K  340M1% /media/cavsfan/Fantom\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-03-10 (165 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
  ProcCmdline: chromium-browser\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=14.0.0.145\ --enable-pinch
  SegvAnalysis:
   Segfault happened at: 0x7f2cf0464724 
<_ZN8printing20PrintingContextLinux13PrintDocumentEPKNS_8MetafileE+20>: mov
0x18(%rcx),%rcx
   PC (0x7f2cf0464724) ok
   source "0x18(%rcx)" (0xc836201b1981) not located in a known VMA region 
(needed readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   printing::PrintingContextLinux::PrintDocument(printing::Metafile const*) () 
from /usr/lib/chromium-browser/libs/libprinting.so
   printing::PrintedDocument::RenderPrintedPage(printing::PrintedPage const&, 
printing::PrintingContext*) const () from 
/usr/lib/chromium-browser/libs/libprinting.so
   ?? ()
   ?? ()
   base::MessageLoop::RunTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in 
printing::PrintingContextLinux::PrintDocument()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b'false\n'/desktop/gnome/interface/icon_theme = 
b''/desktop/gnome/interface/gtk_theme = b''
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-07-30T15:35:40.819664

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

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

[Desktop-packages] [Bug 1224451] Re: chromium-browser crashed with SIGSEGV in UnityWebappsIndicatorCallback_dispatcher()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in
  UnityWebappsIndicatorCallback_dispatcher()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  There was one unread message in the messaging indicator, I clicked it.
  Chromium's Facebook window was raised and the message displayed, but a
  top bar appeared stating that Unity Webapps plugin has crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu1
  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
  CrashCounter: 1
  Date: Thu Sep 12 15:14:01 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-09-03 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  LocalLibraries: 
/home/menesis/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.7_0/libunity_npapi_plugin.so
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=plugin\ 
--plugin-path=/home/username/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.7_0/libunity_npapi_plugin.so\
 --lang=lt\ --channel=6379.18.6103503
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   UnityWebappsIndicatorCallback_dispatcher (context=, 
user_data=) at unity-webapps-binding.c:2371
   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: chromium-browser crashed with SIGSEGV in 
UnityWebappsIndicatorCallback_dispatcher()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b'compiz\n'/apps/metacity/general/compositing_manager = 
b'true\n'/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1218354] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  This crash occurred while I restarted my laptop after updating the
  software from automatic update...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 28.0.1500.71-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Thu Aug 29 17:53:12 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda1  
ext4   92G  8.8G   79G  11% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1.8G  4.0K  1.8G   1% /dev\ntmpfs   
   tmpfs 362M  1.3M  361M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 1.8G  744K  1.8G   1% 
/run/shm\nnone   tmpfs 100M   32K  100M   1% /run/user\n/dev/sda5   
   ext4  366G  158G  190G  46% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda15.9M  
343K  5.5M6% /\nnone 209K 2  209K1% 
/sys/fs/cgroup\nudev 204K   524  204K1% /dev\ntmpfs
209K   543  208K1% /run\nnone 209K 5  209K1% 
/run/lock\nnone 209K 9  209K1% /run/shm\nnone 
209K24  209K1% /run/user\n/dev/sda5 24M  221K   24M1% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-05-28 (92 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  LocalLibraries: 
/home/sundaravenkataraman/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.7_0/libunity_npapi_plugin.so
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=plugin\ 
--plugin-path=/home/username/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.7_0/libunity_npapi_plugin.so\
 --lang=en-US\ --channel=2437.15.7580659
  Signal: 11
  SourcePackage: chromium-browser
  Stacktrace:
   #0  0xb4a5eb45 in ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   No symbol table info available.
   Cannot access memory at address 0xaf70e144
  StacktraceTop: ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-08-19 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1228824] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Nothing more

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  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: Sun Sep 22 11:58:31 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-09-14 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/flashplugin-installer/libflashplayer.so\ --lang=es\ 
--channel=6055.30.4186137
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=unknown
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc8847a88d8:mov0x20(%rax),%rbx
   PC (0x7fc8847a88d8) ok
   source "0x20(%rax)" (0x7fc8855877d0) in non-readable VMA region: 
0x7fc885118000-0x7fc885d58000 ---p None
   destination "%rbx" ok
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy fuse games 
lpadmin plugdev sambashare saned scanner src sudo tape tty users video voice
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1553592] Re: 16.04 casper 15_autologin file contains obsolete lightdm configuration

[Sebastien Bacher]

** Tags added: rls-z-incoming

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

Title:
  16.04 casper 15_autologin file contains obsolete lightdm configuration

Status in accountsservice package in Ubuntu:
  Triaged
Status in casper package in Ubuntu:
  Triaged

Bug description:
  /usr/share/initramfs-tools/scripts/casper-bottom/15autologin

  the lightdm section of the file contains a lightdm configuration that
  is incorrect for 15.10 and later

  for example it writes out /root/etc/lightdm/lightdm.conf

  according to the lightdm wiki this should be
  /root/etc/lightdm/lightdm.conf.d/xyz.conf

  Additionally using [SeatDefaults] is wrong.  Again according the wiki
  [SeatDefaults] is obsolete and should be [Seat:*]

  Think this is probably why manual live CD creators and those who use
  Pinguy ISO Builder cannot create a lightdm autologin live CD

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Mar  5 21:07:13 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1400206] Re: Chromium hangs: GPU process hung

[Olivier Tilloy]

@Richard: is that bug still affecting you with recent releases of
chromium?

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

Title:
  Chromium hangs: GPU process hung

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Starting with a recent update to either my graphics card, or to
  chromium, it (chromium) will seem to hang after resuming from a lock
  screen. By hang, I mean it seems to refuse to redraw since it still
  responds to mouse clicks on the close button. Here's the stderr output
  on console:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates
  [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process 
hung. Terminating after 1 ms.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed 
to establish GPU channel.
  [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI 
shared context.
  [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  7 22:21:35 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  --- 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-02-16 (1083 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Tags:  utopic
  Uname: Linux 3.11.0-14-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  modified.conffile..etc.chromium.browser.default:
   # Default settings for chromium-browser. This file is sourced by /bin/sh from
   # /usr/bin/chromium-browser
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
   # Options to pass to chromium-browser
   CHROMIUM_FLAGS=""
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190

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

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

[Desktop-packages] [Bug 1234874] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Apport say Chromium crashed but chromium steel working witouth any
  bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2 [modified: 
usr/share/applications/chromium-browser.desktop]
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Oct  3 20:48:55 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = /usr/lib32
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-09-14 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914)
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3033.6.314873525\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=0,19\ --gpu-vendor-id=0x1002\ 
--gpu-device-id=0x6741\ --gpu-driver-vendor=ATI\ /\ AMD\ 
--gpu-driver-version=13.1
  SegvAnalysis:
   Segfault happened at: 0x7fbdde50a51f:mov0x44(%rax),%edx
   PC (0x7fbdde50a51f) ok
   source "0x44(%rax)" (0x0044) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
   ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
   ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
   ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
   ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default:
   CHROMIUM_FLAGS=""
   . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  mtime.conffile..etc.chromium.browser.default: 2013-09-29T23:52:15.416172

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

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

[Desktop-packages] [Bug 1200566] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  várias vezes

  ProblemType: Crash
  DistroRelease: elementary OS 0.2
  Package: chromium-browser 28.0.1500.52-0ubuntu1.12.04.2 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 3.2.0-50.76-generic 3.2.48
  Uname: Linux 3.2.0-50-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3+elementary3~precise1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Fri Jul 12 07:09:17 2013
  Desktop-Session:
   DESKTOP_SESSION = pantheon
   XDG_CONFIG_DIRS = /etc/xdg/xdg-pantheon:/etc/xdg
   XDG_DATA_DIRS = /usr/share/pantheon:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: elementary OS 0.2 "Luna" - Beta 2 amd64 (20130506)
  MarkForUpload: True
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/flashplugin-installer/libflashplayer.so\ --lang=pt-BR\ 
--channel=23439.5.2135927796
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f7d20c51e8e:cmp%rax,(%rdx)
   PC (0x7f7d20c51e8e) ok
   source "%rax" ok
   destination "(%rdx)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
   ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
  ThirdParty: True
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1223455] Re: chromium-browser crashed with SIGABRT

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Crashed while launching 2 instances of chromium in background

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
  Uname: Linux 3.11.0-6-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep 10 12:40:05 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-09-03 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --window-size=400,200\ 
--window-position=100,100\ --user-data-dir=profile_storage
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/firefox 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1308229] Re: chromium-browser crashed with SIGSEGV in BrowserContextKeyedServiceFactory::GetServiceForBrowserContext()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in
  BrowserContextKeyedServiceFactory::GetServiceForBrowserContext()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  the browser just suddenly stop responding to mouse and keyboard; just closed 
your window — crashed.
   
  apt-cache policy chromium-browser
  chromium-browser:
Installed: 34.0.1847.116-0ubuntu2
Candidate: 34.0.1847.116-0ubuntu2
Version table:
   *** 34.0.1847.116-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  Uname: Linux 3.14.0-999-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 16 03:34:37 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2012-09-30 (562 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  ProcCmdline: chromium-browser\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=12.0.0.77\ --enable-pinch
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   
BrowserContextKeyedServiceFactory::GetServiceForBrowserContext(content::BrowserContext*,
 bool) () from 
/usr/lib/chromium-browser/libs/libbrowser_context_keyed_service.so
   ?? ()
   ?? ()
   base::MessageLoop::RunTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in 
BrowserContextKeyedServiceFactory::GetServiceForBrowserContext()
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (156 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-03-23T05:34:43.487383

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

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

[Desktop-packages] [Bug 1045823] Re: chromium-browser crashed with SIGSEGV in slab_allocator_alloc_chunk()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in slab_allocator_alloc_chunk()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  I opened the bookmarks!

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu5
  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
  ChromiumPrefs:
   browser/check_default_browser = False
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  Date: Tue Sep  4 15:29:35 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda1  
ext4  9,5G  7,1G  2,0G  79% /\nudev   devtmpfs  489M  4,0K  489M   
1% /dev\ntmpfs  tmpfs 200M  780K  199M   1% /run\nnone   
tmpfs 5,0M 0  5,0M   0% /run/lock\nnone   tmpfs 498M  216K  
498M   1% /run/shm\n/dev/sdb5  ext4  101G   16G   81G  16% 
/media/adri/80bab25a-23c8-4e7a-9a84-70c3c11824a82\n/dev/sdb2  ext4  
193G  106G   78G  58% /media/adri/Adatok4\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1614K  
236K  378K   39% /\nudev 123K   499  122K1% /dev\ntmpfs 
   125K   421  124K1% /run\nnone 125K 3  125K1% 
/run/lock\nnone 125K 8  125K1% /run/shm\n/dev/sdb5
6,4M  187K  6,3M3% 
/media/adri/80bab25a-23c8-4e7a-9a84-70c3c11824a82\n/dev/sdb2 13M  6,9K  
 13M1% /media/adri/Adatok4\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f4fb00884ea:mov(%rax),%rsi
   PC (0x7f4fb00884ea) ok
   source "(%rax)" (0x1584ddbef281c327) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   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
   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: chromium-browser crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1056330] Re: chromium-browser crashed with SIGSEGV in real_queue_resize()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in real_queue_resize()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Trying to attach a screenshot to a bug report here, and both Chrome
  and Chromium crash Since yesterday's update, a lot is broken in
  Ubuntu.. thank you very much.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Tue Sep 25 12:06:08 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f5ab06a6c7b:mov0x38(%rbp),%rdx
   PC (0x7f5ab06a6c7b) ok
   source "0x38(%rbp)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_cclosure_marshal_VOID__BOXEDv () 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: chromium-browser crashed with SIGSEGV in 
g_cclosure_marshal_VOID__BOXEDv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1229021] Re: chromium-browser crashed with SIGSEGV because too much pre-rendered graphics ongoing

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV because too much pre-rendered
  graphics ongoing

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE
  1. Using the Chromium web-browser, go to 
.
  2. Resize the map for a while.

  EXPECTED BEHAVIOUR
  - The map to resize normally.

  REAL BEHAVIOUR
  - The Chromium web-browser can crash, depending on the graphic processor 
being used, because too much pre-rendered graphics ongoing.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  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: Mon Sep 23 14:14:44 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda1  
ext4  443G  139G  282G  34% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  7.8G  4.0K  7.8G   1% /dev\ntmpfs   
   tmpfs 1.6G  1.2M  1.6G   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 7.8G  2.3M  7.8G   1% 
/run/shm\nnone   tmpfs 100M   48K  100M   1% /run/user\n'

   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 29M  
648K   28M3% /\nnone 2.0M11  2.0M1% 
/sys/fs/cgroup\nudev 2.0M   535  2.0M1% /dev\ntmpfs
2.0M   560  2.0M1% /run\nnone 2.0M 5  2.0M1% 
/run/lock\nnone 2.0M16  2.0M1% /run/shm\nnone 
2.0M28  2.0M1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2012-03-27 (544 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=11058.45.1644192592\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=0,6,19\ --gpu-vendor-id=0x8086\ 
--gpu-device-id=0x0102\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=9.2
  SegvAnalysis:
   Segfault happened at: 0x7ff2a2506188:movl   $0x1337,0x0
   PC (0x7ff2a2506188) ok
   source "$0x1337" ok
   destination "0x0" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-09-14 (8 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1194241] Re: chromium-browser crashed with SIGSEGV in content::NPObjectProxy::NPInvokePrivate()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in
  content::NPObjectProxy::NPInvokePrivate()

Status in WebApps: libunity-webapps:
  New
Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Unity webapp plugin crashed during usual navigation.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 25.0.1364.160-0ubuntu3
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Jun 24 21:00:10 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sdb1  
ext4   30G   28G  299M  99% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  3.9G  4.0K  3.9G   1% /dev\ntmpfs   
   tmpfs 789M  1.2M  788M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 3.9G  3.3M  3.9G   1% 
/run/shm\nnone   tmpfs 100M   36K  100M   1% /run/user\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdb11.9M  
688K  1.2M   36% /\nnone 987K11  987K1% 
/sys/fs/cgroup\nudev 984K   519  984K1% /dev\ntmpfs
987K   545  986K1% /run\nnone 987K 3  987K1% 
/run/lock\nnone 987K14  987K1% /run/shm\nnone 
987K24  987K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-01-05 (170 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  LocalLibraries: 
/home/andrea/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.6_0/libunity_npapi_plugin.so
  MarkForUpload: True
  ProcCmdline: chromium-browser\ --type=plugin\ 
--plugin-path=/home/username/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.6_0/libunity_npapi_plugin.so\
 --lang=en-US\ --channel=4319.5.8261013
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   UnityWebappsContextPrepareCallback_dispatcher (context=, 
user_data=) at unity-webapps-binding.c:221
   ?? () from /usr/lib/libunity-webapps.so.0
   g_main_dispatch (context=0x7f2a0d445b40) at 
/build/buildd/glib2.0-2.37.2/./glib/gmain.c:3058
  Title: chromium-browser crashed with SIGSEGV in 
UnityWebappsContextPrepareCallback_dispatcher()
  UpgradeStatus: Upgraded to saucy on 2013-05-28 (27 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo tilp
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1194241/+subscriptions

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

[Desktop-packages] [Bug 934806] Re: chromium-browser crashed with SIGABRT in raise()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGABRT in raise()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Happened when I closed chromium.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: chromium-browser 16.0.912.77~r118311-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
(no entry found in the Preferences file)
  Date: Sat Feb 18 08:18:30 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  Signal: 6
  SourcePackage: chromium-browser
  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/libgio-2.0.so.0
  Title: chromium-browser crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (126 days ago)
  UserGroups: adm admin cdrom chipcard dialout lpadmin plugdev sambashare 
vboxusers
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 973375] Re: chromium-browser crashed with SIGSEGV in g_pattern_match()

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV in g_pattern_match()

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  I started an Java Browser Game while this error occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.142~r129054-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  4 15:32:55 2012
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so\ 
--lang=de\ --channel=2084.0x7ff87336fc80.41062962
  ProcEnviron:
   
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  Title: chromium-browser crashed with SIGSEGV in g_pattern_match()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1272461] Re: djvu search doesn't list results

[hife]

** Description changed:

  Evince version 3.10.0-0ubuntu2
  Ubuntu 13.10
  
  When searching .djvu files, the sidebar appears, but stays empty instead of 
showing a list of results.
  (If it is not possible to list results, I would prefer the sidebar to stay 
hidden.)
+ 
+ Update: This issue still stands in version 3.18.2.

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

Title:
  djvu search doesn't list results

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Evince version 3.10.0-0ubuntu2
  Ubuntu 13.10

  When searching .djvu files, the sidebar appears, but stays empty instead of 
showing a list of results.
  (If it is not possible to list results, I would prefer the sidebar to stay 
hidden.)

  Update: This issue still stands in version 3.18.2.

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

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

[Desktop-packages] [Bug 1064250] Re: chromium-browser crashed with SIGSEGV

[Olivier Tilloy]

Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  simply letting gmail open in chromium and locking my session before
  leaving.

  On the morrow, chromium has crashed.

  regards.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct  9 10:38:12 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f6b2ecbe61c:mov0x150(%rax),%r12
   PC (0x7f6b2ecbe61c) ok
   source "0x150(%rax)" (0x0150) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  Stacktrace:
   #0  0x7f6b2ecbe61c in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fff0e6dce98
  StacktraceTop: ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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