[Desktop-packages] [Bug 1518035] Re: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1

2015-11-20 Thread Cavsfan
I've been getting this error about libjpeg-progs for a while now.
I removed the package and left libjpeg-turbo-progs installled. It also took 
xscreensaver-data-extra with it when purged.
I re-installed libjpeg-turbo-progs and xscreensaver-data-extra.

setup an alias so the other updates would complete:

alias udf='sudo dpkg --configure -a'

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

Title:
  package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying
  to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in
  package libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg9 package in Ubuntu:
  Confirmed
Status in libjpeg9 package in Debian:
  Unknown

Bug description:
  just upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 1:9a-2ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 16 15:38:22 2015
  Dependencies:
   gcc-5-base 5.2.1-23ubuntu1
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-23ubuntu1
   libjpeg9 1:9a-2ubuntu1
   multiarch-support 2.21-0ubuntu4
  DuplicateSignature:
   Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-02-24 (633 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg9
  Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying 
to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1518035/+subscriptions

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


Re: [Desktop-packages] [Bug 1196251] Re: pacman crashed with SIGSEGV in is_bonus_dot()

2015-05-21 Thread Cavsfan
What how to?

On 05/12/2015 01:47 PM, eric tennant wrote:
 Hi, can you please advise me on the how to.
 Would appreciate it.
 Regards
 Eric Tennant


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

Title:
  pacman crashed with SIGSEGV in is_bonus_dot()

Status in xscreensaver package in Ubuntu:
  Fix Released

Bug description:
  I was just selecting which xscreensavers to allow and had not gotten
  to pacman yet when this occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xscreensaver-data-extra 5.15-2ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sun Jun 30 09:56:05 2013
  ExecutablePath: /usr/lib/xscreensaver/pacman
  InstallationDate: Installed on 2013-06-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130626)
  MarkForUpload: True
  ProcCmdline: pacman -root -window-id 0x1803DB5
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4084bf:  cmp0xdb8(%rdi),%esi
   PC (0x004084bf) ok
   source 0xdb8(%rdi) (0x01ed2004) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
  Title: pacman crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1298666] Re: Preferences option not present in Edit menu

2015-05-08 Thread Cavsfan
The solution in Wiley was to set
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
to {Gtk/ShellShowsAppMenu:0}

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

Title:
  Preferences option not present in Edit menu

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  I m running Ubuntu Gnome 64bit beta 2 in a VM. When running gedit...
  the menu edit does not include the option Preferences

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 27 15:38:07 2014
  InstallationDate: Installed on 2014-03-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 
(20140326.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1298666] Re: Preferences option not present in Edit menu

2015-05-07 Thread Cavsfan
I have installed wiley and in a gnome flashback (with compiz) session there is 
no option for preferences under the edit tab.
Therefore there is no option to not wrap lines, show line numbers, etc.

** Tags added: wiley

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

Title:
  Preferences option not present in Edit menu

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  I m running Ubuntu Gnome 64bit beta 2 in a VM. When running gedit...
  the menu edit does not include the option Preferences

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 27 15:38:07 2014
  InstallationDate: Installed on 2014-03-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 
(20140326.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1431041] Re: cups-browsed crashed with SIGSEGV in timeout_free()

2015-03-26 Thread Cavsfan
I got this errror at boot this morning.

** Attachment added: My /etc/cups/cups-browsed.conf file
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1431041/+attachment/4356970/+files/cups-browsed.conf

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

Title:
  cups-browsed crashed with SIGSEGV in timeout_free()

Status in avahi package in Ubuntu:
  Incomplete
Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  happened during update.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar 11 22:46:42 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2015-03-01 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
  Lpstat: device for WF-2530: 
dnssd://EPSON%20WF-2530%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-b0e89258fe55
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: WF-2530: Epson WF-2530 Series - epson-inkjet-printer 1.0.0-1lsb3.2 
(Seiko Epson Corporation LSB 3.2)
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=b98daf80-990b-45f5-aa26-844ab2d42789 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f03e1e4815a:movl   $0x1,0xa8(%rax)
   PC (0x7f03e1e4815a) ok
   source $0x1 ok
   destination 0xa8(%rax) (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/08/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: 970DE3/U3S3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/08/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1432886] Re: oneconf-service crashed with FileNotFoundError in __init__(): [Errno 2] No such file or directory: '/var/lib/dbus/machine-id'

2015-03-21 Thread Cavsfan
*** This bug is a duplicate of bug 1432138 ***
https://bugs.launchpad.net/bugs/1432138

I get this error daily. This time I awoke it from suspend and got the crqash 
report.
This is on Ubuntu Mate Vivid 15.04.

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

Title:
  oneconf-service crashed with FileNotFoundError in __init__(): [Errno
  2] No such file or directory: '/var/lib/dbus/machine-id'

Status in oneconf package in Ubuntu:
  Confirmed

Bug description:
  Fresh install + update + dist-upgrade + install vlc = Crash

  Description:  Ubuntu Vivid Vervet (development branch) dl today
  Release:  15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: oneconf 0.3.7
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 17 00:32:07 2015
  ExecutablePath: /usr/share/oneconf/oneconf-service
  ExecutableTimestamp: 1395675892
  InstallationDate: Installed on 2015-03-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150316)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/oneconf/oneconf-service
  ProcCwd: /
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  PythonArgs: ['/usr/share/oneconf/oneconf-service']
  SourcePackage: oneconf
  Title: oneconf-service crashed with FileNotFoundError in __init__(): [Errno 
2] No such file or directory: '/var/lib/dbus/machine-id'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1103456] Re: oneconf-query crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.186 was not provided by any .se

2015-03-16 Thread Cavsfan
Just got this error on a brand new install of Vivid Mate but got this:
 oneconf-query crashed with dbus.exceptions.DBusException in call_blocking(): 
org.freedesktop.DBus.Error.ServiceUnknown: The name :1.82 was not provided by 
any .service files

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

Title:
  oneconf-query crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name
  :1.186 was not provided by any .service files

Status in oneconf package in Ubuntu:
  Confirmed

Bug description:
  Just crashed. Not sure what caused this.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: oneconf 0.3.2
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jan 23 07:20:34 2013
  DbusErrorAnalysis: no service file providing :1.186
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/oneconf/oneconf-query
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/oneconf-query --async-update
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/oneconf-query', '--async-update']
  SourcePackage: oneconf
  Title: oneconf-query crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.186 was 
not provided by any .service files
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lp lpadmin sudo

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

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


[Desktop-packages] [Bug 1103456] Re: oneconf-query crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.186 was not provided by any .se

2015-03-16 Thread Cavsfan
Keep getting this same error over and over again.

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

Title:
  oneconf-query crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name
  :1.186 was not provided by any .service files

Status in oneconf package in Ubuntu:
  Confirmed

Bug description:
  Just crashed. Not sure what caused this.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: oneconf 0.3.2
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jan 23 07:20:34 2013
  DbusErrorAnalysis: no service file providing :1.186
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/oneconf/oneconf-query
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/oneconf-query --async-update
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/oneconf-query', '--async-update']
  SourcePackage: oneconf
  Title: oneconf-query crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.186 was 
not provided by any .service files
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lp lpadmin sudo

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-01-14 Thread Cavsfan
Those other workarounds are mentioning re-installing the driver. That
may prevent the error but during the next kernel installation you will
likely see the error again. Post #100 by dino99 is a modification that
you make for future kernels so they do not get the error. The error
message to me is bogus as the drivers do in fact install just fine
AFAIK. That is about all I know; I'm not a developer, I'm a tester...

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-01-14 Thread Cavsfan
Refer to post #111 for how to unsubscribe. Neolaser mentioned it once
there already.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-01-14 Thread Cavsfan
Refer to post #100 for the fix by dino99.
If you simply reinstall the driver it will happen the next time a kernel is in 
updates.
I believe dino99's fix should fix it once and for all.
I'm waiting on the next kernel to come along to verify that.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-01-14 Thread Cavsfan
I just got this again on Vivid 15.04 when 3.18.0-9-generic kernel installed.
Going to try the fix from post #100. I did it on Trusty now on Vivid.
Then the next kernel install will tell if it worked.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-01-14 Thread Cavsfan
Got a new kernel in Trusty 14.04 yesterday and got this error. Did the
steps in post #100 that dino99 suggested. Looked good rebooted and all
is fine. Will see if that fixes the problem from now on.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2014-12-19 Thread Cavsfan
I installed Vivid Alpha 1 from ISO yesterday and when I installed the 331.113 
drivers I did not get this error at all.
Everything was normal.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1380053] Re: package nvidia-prime 0.6.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

2014-12-19 Thread Cavsfan
I tried to install systemd-sysv which wanted to uninstall upstart and 
nvidia-prime and got this.
Nvidia-prime could not be removed due to dependency issues.

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

Title:
  package nvidia-prime 0.6.6 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 5

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  This just happened when trying to upgrade on utopic

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-prime 0.6.6
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  Date: Sat Oct 11 11:58:01 2014
  DuplicateSignature: package:nvidia-prime:0.6.6:subprocess new pre-removal 
script returned error exit status 5
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2014-06-24 (108 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.6.6 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1403110] [NEW] nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

2014-12-16 Thread Cavsfan
Public bug reported:

Got the checksum error when DKMS modules were being built for nvidia
driver 331.113 when kernel 3.16.0-28-generic was added.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.113-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.15-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.16.0-28-generic
Date: Tue Dec 16 10:26:34 2014
InstallationDate: Installed on 2014-11-16 (29 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
PackageVersion: 331.113-0ubuntu2
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package systemd-boot vivid

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

Title:
  nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Got the checksum error when DKMS modules were being built for nvidia
  driver 331.113 when kernel 3.16.0-28-generic was added.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15-0ubuntu3
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-28-generic
  Date: Tue Dec 16 10:26:34 2014
  InstallationDate: Installed on 2014-11-16 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.113-0ubuntu2
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu2: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1401251] [NEW] nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

2014-12-10 Thread Cavsfan
Public bug reported:

I have no further information. 
Still getting the same error during dkms updates for 331.113-0ubuntu1, which 
was installed today.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.113-0ubuntu1
Uname: Linux 3.18.0-031800-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
DKMSKernelVersion: 3.18.0-031800-lowlatency
Date: Wed Dec 10 15:13:37 2014
InstallationDate: Installed on 2014-11-16 (24 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
PackageVersion: 331.113-0ubuntu1
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package systemd-boot vivid

** Tags added: systemd-boot

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

Title:
  nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I have no further information. 
  Still getting the same error during dkms updates for 331.113-0ubuntu1, which 
was installed today.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu1
  Uname: Linux 3.18.0-031800-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-031800-lowlatency
  Date: Wed Dec 10 15:13:37 2014
  InstallationDate: Installed on 2014-11-16 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.113-0ubuntu1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1401251] Re: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

2014-12-10 Thread Cavsfan
Installed the 3,18 kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.18-vivid/ not sure if that matters.

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

Title:
  nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I have no further information. 
  Still getting the same error during dkms updates for 331.113-0ubuntu1, which 
was installed today.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu1
  Uname: Linux 3.18.0-031800-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-031800-lowlatency
  Date: Wed Dec 10 15:13:37 2014
  InstallationDate: Installed on 2014-11-16 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.113-0ubuntu1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1401251] Re: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

2014-12-10 Thread Cavsfan
nvidia-331 331.113-0ubuntu2 as well as all of the previously mentioned
components just upgraded and no errors occurred so this bug may be moot.

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

Title:
  nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I have no further information. 
  Still getting the same error during dkms updates for 331.113-0ubuntu1, which 
was installed today.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu1
  Uname: Linux 3.18.0-031800-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-031800-lowlatency
  Date: Wed Dec 10 15:13:37 2014
  InstallationDate: Installed on 2014-11-16 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.113-0ubuntu1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1401251] Re: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

2014-12-10 Thread Cavsfan
This might matter: I just checked for updates and libcuda1-331,
nvidia-331, nvidia-331-uvm, nvidia-opencl-icd-331, are now being
installed after the error. I thought nvidia-331 updates once just before
this.

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

Title:
  nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  I have no further information. 
  Still getting the same error during dkms updates for 331.113-0ubuntu1, which 
was installed today.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.113-0ubuntu1
  Uname: Linux 3.18.0-031800-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 3.18.0-031800-lowlatency
  Date: Wed Dec 10 15:13:37 2014
  InstallationDate: Installed on 2014-11-16 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.113-0ubuntu1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2014-12-01 Thread Cavsfan
I guess it's up to you. I don't think most people want to see bug 
reports popping up on a final releases, especially LTS versions which 
most of mine are. That is what I have always seen in the past. Disable 
Apport Error Reporting in Ubuntu 14.10 
http://ubuntuhandbook.org/index.php/2014/09/disable-apport-error-reporting-ubuntu-14-10/
There is one link that states Reporting bugs is important, it helps 
improving system stability, but if you’re constantly getting crash 
report popups, you may want to disable it.
I've got 7 operating systems on my computer and one of them is 15.04 
development. But for Precise 12.04 and the others I turned error 
reporting off. So, while a system is in development I definitely leave 
bug reporting on then once it hits final release I usually replace that 
OS with the next development release.

I do not rely on short term releases, I mainly stick with LTS versions. 
So, I guess it is a matter of preference.
What's the difference between a Long Term Support Release and a Normal 
Release? 
http://askubuntu.com/questions/16366/whats-the-difference-between-a-long-term-support-release-and-a-normal-release
 
provides some more information.
But, the bottom line is that is up to you.
On 12/01/2014 12:16 AM, İsmail Arılık wrote:
 Thanks for your reply. But I did not understand why may I want to turn off
 the bug reports. Why is it customary? It is exactly possible a final
 release may have bugs. Who is apport them?
 30 Kas 2014 23:30 tarihinde Cavsfan 1268...@bugs.launchpad.net yazdı:

 I agree that this error is not really an error and does not affect the
 DKMS modules at all.
 I get the error when a new kernel is installed but the nvidia-331 and
 nvidia-331-uvm DKMS modules are successfully built.
 This can be seen when the kernel is subsequently removed and the DKMS
 modules are successfully removed.

 Also, in 14.10 since it is in final release you probably want to turn off
 the bug reports as I did and I believe is customary after a version release
 with this command:
 sudo sh -c 'echo enabled=0  /etc/default/apport'

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1397071).
 https://bugs.launchpad.net/bugs/1268257

 Title:
nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
failed to build, with only error: objdump: '... .tmp_nv.o': No such
file

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed

 Bug description:
Nvidia kernel module failed to build on kernel 3.13.0-2
Yesterday when the new kernel was pushed, the dkms process failed.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.13.0-2-generic
Date: Sun Jan 12 01:28:35 2014
InstallationDate: Installed on 2013-11-03 (69 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
 (20131016.1)
PackageVersion: 331.20-0ubuntu9
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel
 module failed to build
UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions


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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2014-11-30 Thread Cavsfan
I agree that this error is not really an error and does not affect the DKMS 
modules at all.
I get the error when a new kernel is installed but the nvidia-331 and 
nvidia-331-uvm DKMS modules are successfully built.
This can be seen when the kernel is subsequently removed and the DKMS modules 
are successfully removed.

Also, in 14.10 since it is in final release you probably want to turn off the 
bug reports as I did and I believe is customary after a version release with 
this command:
sudo sh -c 'echo enabled=0  /etc/default/apport'

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1396249] [NEW] nvidia-331 331.89-0ubuntu6: nvidia-331 kernel module failed to build

2014-11-25 Thread Cavsfan
Public bug reported:

Exactly like bug #1298016 but 331.89 instead of 331.88.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.89-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
DKMSKernelVersion: 3.16.0-25-generic
Date: Tue Nov 25 11:49:05 2014
InstallationDate: Installed on 2014-11-16 (9 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
PackageVersion: 331.89-0ubuntu6
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu6: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package vivid

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

Title:
  nvidia-331 331.89-0ubuntu6: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Exactly like bug #1298016 but 331.89 instead of 331.88.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331 331.89-0ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Tue Nov 25 11:49:05 2014
  InstallationDate: Installed on 2014-11-16 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141115)
  PackageVersion: 331.89-0ubuntu6
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu6: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe

2014-11-06 Thread Cavsfan
I just got this again with Utopic Mate Remix and I have 331.89 Nvidia
drivers installed.

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

Title:
  init: Error while reading from descriptor: Broken pipe

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed

Bug description:
  [   16.934379] init: Error while reading from descriptor: Broken pipe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: init 1.20ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep  2 17:23:15 2014
  InstallationDate: Installed on 2014-04-27 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370859] Re: Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)

2014-10-17 Thread Cavsfan
I just got this error when kernel 3.16.0-23-generic was installed.

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

Title:
  Error! Bad return status for module build on kernel: 3.16.0-16-generic
  (x86_64)

Status in The Linux Kernel:
  New
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  Installing a new kernel 3.16.0.16 from a running gnome-shell session
  using the kernel 3.16.014, i'm getting:

  
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic 
/boot/vmlinuz-3.16.0-16-generic
  Error! Bad return status for module build on kernel: 3.16.0-16-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
  *

  As apport also fails to report that issue (it simply does nothing, it
  even does not start and does not warns either), i'm joining the crash
  file and make.log for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 18 07:13:23 2014
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1379985] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-10-11 Thread Cavsfan
I got this error but I'm also getting an error about nvidia-prime not
installing correctly.

The following packages will be upgraded:
  nvidia-prime
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/11.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 280128 files and directories currently installed.)
Preparing to unpack .../nvidia-prime_0.6.7_amd64.deb ...
Failed to issue method call: Unit nvidia-prime.service not loaded.
invoke-rc.d: initscript nvidia-prime, action stop failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
Failed to issue method call: Unit nvidia-prime.service not loaded.
invoke-rc.d: initscript nvidia-prime, action stop failed.
dpkg: error processing archive 
/var/cache/apt/archives/nvidia-prime_0.6.7_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 5
Failed to issue method call: Unit nvidia-prime.service failed to load: No such 
file or directory.
invoke-rc.d: initscript nvidia-prime, action start failed.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 6
Errors were encountered while processing:
 /var/cache/apt/archives/nvidia-prime_0.6.7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  dist-upgrade throws the error. nvidia driver is can not be installed

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 05:22:55 2014
  InstallationDate: Installed on 2013-01-14 (634 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-09-14 (26 days ago)

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

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


[Desktop-packages] [Bug 1374460] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-09-27 Thread Cavsfan
I just got this exact error after installing 3.16.0-18-generic kernel and 
rebooting.
This is on Utopic Unicorn 14.10 Mate Remix.

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  get that issue with each new kernel installation

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  DKMSKernelVersion: 3.16.0-18-generic
  Date: Fri Sep 26 13:30:34 2014
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1374460] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-09-27 Thread Cavsfan
Same thing on Utopic Unicorn 14.10 after installing 3.16.0-18-generic
kernel and rebooting.

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  get that issue with each new kernel installation

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  DKMSKernelVersion: 3.16.0-18-generic
  Date: Fri Sep 26 13:30:34 2014
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1373498] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-09-24 Thread Cavsfan
I got this exact error when I removed kernel 3.16.0-14-generic as I had 3 
kernels installed.
Although when that kernel was removed and when it was installed it gave an 
error like it didn't properly install the nvidia driver but this is what was in 
the output indicating that the driver was indeed successfully installed on both 
both the nvidia-331 module and nvidia-331-uvm. See the text file below.

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  I get the crash file everytime I start the machine.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-16-generic
  Date: Fri Sep 19 19:35:19 2014
  InstallationDate: Installed on 2014-07-31 (54 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140730)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1373498] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-09-24 Thread Cavsfan
Attachment text file for the above.

** Attachment added: DKMS removed the nvidia modules from 3.16.0-14-generic 
although there was an error when it was installed
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1373498/+attachment/4213817/+files/DKMS%20removed%20the%20nvidia%20modules%20from%203.16.0-14-generic%20although%20there%20was%20an%20error%20when%20it%20was%20installed

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  I get the crash file everytime I start the machine.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-16-generic
  Date: Fri Sep 19 19:35:19 2014
  InstallationDate: Installed on 2014-07-31 (54 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140730)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1372753] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-09-23 Thread Cavsfan
I received this nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module 
failed to build.
Same error only with nvidia-331-uvm instead of nvidia-331.

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  nvidia-331 kernel module failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  DKMSKernelVersion: 3.16.0-17-generic
  Date: Tue Sep 23 08:28:46 2014
  InstallationDate: Installed on 2014-07-19 (65 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-09-21 (1 days ago)

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

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


[Desktop-packages] [Bug 1370890] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

2014-09-18 Thread Cavsfan
I received this same error after rebooting when kernel 3.16.0-16-generic
was installed.

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed

Bug description:
  Got an error while installing the kernel 3.16.0.16, the make.log warns
  about:

  
  WARNING: could not find 
/var/lib/dkms/nvidia-331/331.89/build/.nv-kernel.o.cmd for 
/var/lib/dkms/nvidia-331/331.89/build/nv-kernel.o
  

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  DKMSKernelVersion: 3.16.0-16-generic
  Date: Thu Sep 18 08:13:51 2014
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-07 Thread Cavsfan
I got this again today on Utopic when 3.16.0-14-generic was installed.
Although when I deleted the 3.16.0-12-generic kernel the 
/lib/modules/3.16.0-12-generic/updates/dkms/nvidia_331.ko was deleted so it was 
installed even though it had gotten the error when it was installed.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-05 Thread Cavsfan
I got this error but it's the same thing: nvidia-331 331.89-0ubuntu3: 
nvidia-331 kernel module failed to build
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-13-generic 
/boot/vmlinuz-3.16.0-13-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-13-generic 
/boot/vmlinuz-3.16.0-13-generic
Error! Bad return status for module build on kernel: 3.16.0-13-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
However /var/lib/dkms/nvidia-331/331.89/build/make.log does not exist.

I have the following nvidia files installed and it does 2 DKMS updates to the 
kernel and the 2nd one does not get this error.
cavsfan@cavsfan-MS-7529:~$ dpkg -l | grep nvidia
ii  nvidia-331331.89-0ubuntu3   
 amd64NVIDIA binary driver - version 331.89
ii  nvidia-331-uvm331.89-0ubuntu3   
 amd64NVIDIA Unified Memory kernel module
ii  nvidia-libopencl1-331 331.89-0ubuntu3   
 amd64NVIDIA OpenCL Driver and ICD Loader library
ii  nvidia-opencl-icd-331 331.89-0ubuntu3   
 amd64NVIDIA OpenCL ICD
ii  nvidia-prime  0.6.6 
 amd64Tools to enable NVIDIA's Prime
ii  nvidia-settings   331.20-0ubuntu8   
 amd64Tool for configuring the NVIDIA graphics 
driver

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-05 Thread Cavsfan
Same thing on Utopic Mate:
nvidia-331 331.89-0ubuntu3: nvidia-331 kernel module failed to build.
See my previous comment for the exact same details Mate gave.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-02 Thread Cavsfan
I got this after a reboot when 3.16.0-12-generic kernel was installed. I also 
noticed this in the output:
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-12-generic 
/boot/vmlinuz-3.16.0-12-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-12-generic 
/boot/vmlinuz-3.16.0-12-generic
Error! Bad return status for module build on kernel: 3.16.0-12-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
But the make.log does not exist.
It performed 2 DKMS processes and the 2nd one didn't get the error just the 
first one.
This is what is installed:
cavsfan@cavsfan-MS-7529:~$ dpkg -l | grep nvidia
ii  nvidia-331331.89-0ubuntu2   
 amd64NVIDIA binary driver - version 331.89
ii  nvidia-331-uvm331.89-0ubuntu2   
 amd64NVIDIA Unified Memory kernel module
ii  nvidia-libopencl1-331 331.89-0ubuntu2   
 amd64NVIDIA OpenCL Driver and ICD Loader library
ii  nvidia-opencl-icd-331 331.89-0ubuntu2   
 amd64NVIDIA OpenCL ICD
ii  nvidia-prime  0.6.6 
 amd64Tools to enable NVIDIA's Prime
ii  nvidia-settings   331.20-0ubuntu8   
 amd64Tool for configuring the NVIDIA graphics 
driver

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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


[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-08-28 Thread Cavsfan
I got this error:
nvidia-331 331.89-0ubuntu2: nvidia-331 kernel module failed to build
This is on Utopic Mate 14.10

** Tags added: utopic

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Triaged

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] chromium-browser crashed with SIGSEGV in printing::PrintingContextLinux::PrintDocument()

2014-08-22 Thread Cavsfan
Public bug reported:

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

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


** Tags: amd64 apport-crash need-amd64-retrace systemd-boot utopic

** Information type changed from Private to Public

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

Title:
  chromium-browser crashed with SIGSEGV in
  printing::PrintingContextLinux::PrintDocument()

Status in “chromium-browser” package in Ubuntu:
  New

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

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

2014-08-19 Thread Cavsfan
This occurs daily for me in Utopic also. Although the application is slow to 
start; a transparent window appears and then the bug report. It asks if I want 
to leave it closed or relaunch it. Clicking on either does nothing. Then I go 
about using Chromium for several hours without any apparent problems. It 
doesn't really use a lot of CPU and it is not slow. So except for the startup, 
it seems to run ok for me.
I'm running gnome flashback with compiz.

-- 
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:
  Confirmed

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 1351647] [NEW] compiz crashed with SIGSEGV

2014-08-02 Thread Cavsfan
Public bug reported:

compiz crashed with SIGSEGV is the only error I received.
I opened Additional Drivers and tried to resize the window when the screen 
froze completely.
Then the bug report appeared.
I booted using systemd.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
 GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-3ubuntu2)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Aug  2 13:05:31 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.16.0-5-generic, x86_64: installed
 bbswitch, 0.7, 3.16.0-6-generic, x86_64: installed
 nvidia-331, 331.89, 3.16.0-5-generic, x86_64: installed
 nvidia-331, 331.89, 3.16.0-6-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. Device [3842:c988]
InstallationDate: Installed on 2014-03-10 (145 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash 
init=/lib/systemd/systemd
SegvAnalysis:
 Segfault happened at: 0x7f51fadb7b35:  movaps 0x10(%rdx),%xmm0
 PC (0x7f51fadb7b35) ok
 source 0x10(%rdx) (0x0010) not located in a known VMA region (needed 
readable region)!
 destination %xmm0 ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.89
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.89
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.89
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.89
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.89
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31M3-L V2(MS-7529)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7529
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Aug  2 10:09:28 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUVC Camera (046d:081a) KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu9

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


** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace systemd-boot 

[Desktop-packages] [Bug 1334353] [NEW] compiz crashed with SIGSEGV

2014-06-25 Thread Cavsfan
Public bug reported:

On Utopic that was the only error message I received while resizing a
terminal window. The system hung for a few seconds and then the report
bug apport-gtk popped up.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: compiz-core 1:0.9.11+14.10.20140606-0ubuntu2
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.79  Sun May 18 03:55:59 
PDT 2014
 GCC version:  gcc version 4.8.3 (Ubuntu 4.8.3-3ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Jun 25 11:35:25 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.15.0-5-generic, x86_64: installed
 bbswitch, 0.7, 3.15.0-6-generic, x86_64: installed
 nvidia-331, 331.79, 3.15.0-5-generic, x86_64: installed
 nvidia-331, 331.79, 3.15.0-6-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. Device [3842:c988]
InstallationDate: Installed on 2014-03-10 (107 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro 
init=/lib/systemd/systemd
SegvAnalysis:
 Segfault happened at: 0x7f6165632b35:  movaps 0x10(%rdx),%xmm0
 PC (0x7f6165632b35) ok
 source 0x10(%rdx) (0x0010) not located in a known VMA region (needed 
readable region)!
 destination %xmm0 ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.79
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.79
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.79
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.79
 ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.79
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31M3-L V2(MS-7529)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7529
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Jun 25 11:23:47 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUVC Camera (046d:081a) KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu6

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


** Tags: amd64 apport-crash compiz-0.9 ubuntu utopic

** Information type changed from Private to Public

-- 
You received this bug 

[Desktop-packages] [Bug 1327555] [NEW] package compiz-plugins 1:0.9.11+14.10.20140606-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/compiz/cube/images/freedesktop.png', which is

2014-06-07 Thread Cavsfan
Public bug reported:

This happened at bootup today. Yesterday I got some compiz updates and
got a dpkg error but sudo apt-get -f install seemed to fix the problem.
This is the 1st reboot after that.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: compiz-plugins 1:0.9.11+14.10.20140606-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
Uname: Linux 3.15.0-5-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.3 (Ubuntu 4.8.3-2ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 2.14.3-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
Date: Fri Jun  6 17:28:06 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.15.0-4-generic, x86_64: installed
 bbswitch, 0.7, 3.15.0-5-generic, x86_64: installed
 nvidia-331, 331.38, 3.15.0-4-generic, x86_64: installed
 nvidia-331, 331.38, 3.15.0-5-generic, x86_64: installed
DuplicateSignature: 
package:compiz-plugins:1:0.9.11+14.10.20140606-0ubuntu1:trying to overwrite 
'/usr/share/compiz/cube/images/freedesktop.png', which is also in package 
compiz-core 1:0.9.11+14.04.20140423-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/compiz/cube/images/freedesktop.png', which is also in package 
compiz-core 1:0.9.11+14.04.20140423-0ubuntu1
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. Device [3842:c988]
InstallationDate: Installed on 2014-03-10 (88 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
SourcePackage: compiz
Title: package compiz-plugins 1:0.9.11+14.10.20140606-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/compiz/cube/images/freedesktop.png', which is also in package 
compiz-core 1:0.9.11+14.04.20140423-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31M3-L V2(MS-7529)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7529
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Jun  7 09:23:37 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUVC Camera (046d:081a) KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.15.1-0ubuntu5

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


** Tags: amd64 apport-package compiz-0.9 need-duplicate-check package-conflict 
ubuntu utopic

** Description changed:

- This happened at bootup today. Yesterday I got come compiz updates and
+ This happened at bootup today. Yesterday I got some compiz updates and
  got a dpkg error but sudo apt-get -f install seemed to fix the problem.
  This is the 1st reboot after that.
  
  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: compiz-plugins 1:0.9.11+14.10.20140606-0ubuntu1
  

[Desktop-packages] [Bug 1312159] Re: ** (gksu:xxxx): CRITICAL **: fcntl error

2014-05-22 Thread Cavsfan
gksu is completely broken and this bug is incomplete and medium
security? That is odd.

** Attachment added: terminal screenshot
   
https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1312159/+attachment/4117769/+files/Screenshot%20from%202014-05-22%2015%3A30%3A25.png

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Incomplete

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1312159] Re: ** (gksu:xxxx): CRITICAL **: fcntl error

2014-05-22 Thread Cavsfan
I meant medium importance.

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Incomplete

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1319433] Re: package xscreensaver-data 5.15-3ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/xscreensaver/xlyap', which is also in package xscreensaver-data-ex

2014-05-14 Thread Cavsfan
Got the same error during apt-get upgrade on 
xscreensaver-data_5.26-1ubuntu1_amd64.deb.
But I too ran apt-get -f upgrade afterward and it worked.

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

Title:
  package xscreensaver-data 5.15-3ubuntu1 failed to install/upgrade:
  trying to overwrite '/usr/lib/xscreensaver/xlyap', which is also in
  package xscreensaver-data-extra 5.15-3ubuntu1

Status in “xscreensaver” package in Ubuntu:
  Confirmed

Bug description:
  Just ran apt-get -f upgrade afterward and it worked, problem was
  updating xscreensaver and xscreensave-data at same time.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: xscreensaver-data 5.15-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Wed May 14 10:44:57 2014
  DuplicateSignature: package:xscreensaver-data:5.15-3ubuntu1:trying to 
overwrite '/usr/lib/xscreensaver/xlyap', which is also in package 
xscreensaver-data-extra 5.15-3ubuntu1
  ErrorMessage: trying to overwrite '/usr/lib/xscreensaver/xlyap', which is 
also in package xscreensaver-data-extra 5.15-3ubuntu1
  InstallationDate: Installed on 2014-02-24 (78 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: xscreensaver
  Title: package xscreensaver-data 5.15-3ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/lib/xscreensaver/xlyap', which is also in package 
xscreensaver-data-extra 5.15-3ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1152656] Re: compiz crashed with SIGSEGV

2014-03-30 Thread Cavsfan
I just got this same error again while editing a conky file with gedit.
The screen messed up a bit and then went back to normal.

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

Title:
  compiz crashed with SIGSEGV

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  nautilus crashed on opening, nvidia tegra graphics card

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: compiz-core 1:0.9.9~daily13.03.06-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar  8 15:58:34 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-03-08 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130308)
  Lsusb:
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=5f1101a4-6b85-4305-ad3d-0fb59d5547a1 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0xb7556e00:movdqu (%eax),%xmm0
   PC (0xb7556e00) ok
   source (%eax) (0x66bc6350) not located in a known VMA region (needed 
readable region)!
   destination %xmm0 ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
  Title: compiz crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Fri Mar  8 15:57:38 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse TOUCHSCREEN, id 7
   inputVMware VMware Virtual USB Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   No surface to present from.
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual3Virtual4Virtual5Virtual6Virtual7
Virtual8
  xserver.version: 2:1.13.2-0ubuntu3
  xserver.video_driver: vmware

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

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

[Desktop-packages] [Bug 1296053] [NEW] compiz crashed with SIGSEGV

2014-03-22 Thread Cavsfan
Public bug reported:

This morning I booted into Gnome Flashback w/Compiz and faced a Unity
session. I logged out a few times and there was no difference between a
Unity session and a Gnome Flashback w/Compiz session until I Unchecked
in CCSM the Unity MT Grab handles checkbox and the Ubuntu Unity plugin
checkbox. CCSM had reset to default so while setting it back up it got
this error. My Gnome Flashback w/Compiz came back though after making
the above changes.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: compiz-core 1:0.9.11+14.04.20140320.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Mar 22 09:04:34 2014
Disassembly: = 0x7fbb87cbc770: Cannot access memory at address 0x7fbb87cbc770
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed
 bbswitch, 0.7, 3.13.0-18-generic, x86_64: installed
 nvidia-331, 331.38, 3.13.0-18-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. Device [3842:c988]
InstallationDate: Installed on 2014-03-10 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7fbb87cbc770:  Cannot access memory at address 
0x7fbb87cbc770
 PC (0x7fbb87cbc770) ok
 SP (0x7fffccfd11d0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31M3-L V2(MS-7529)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7529
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Mar 22 09:03:30 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUVC Camera (046d:081a) KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.0-1ubuntu7

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


** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace trusty ubuntu

** Information type changed from Private to Public

-- 
You received this bug notification because you are a 

[Desktop-packages] [Bug 1152656] Re: compiz crashed with SIGSEGV

2014-03-22 Thread Cavsfan
Opened Audacious then went to import a playlist and the playlist froze
semi-transparent. After about 20 seconds it unfroze and popped up the
error reporting.

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

Title:
  compiz crashed with SIGSEGV

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  nautilus crashed on opening, nvidia tegra graphics card

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: compiz-core 1:0.9.9~daily13.03.06-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar  8 15:58:34 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-03-08 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130308)
  Lsusb:
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=5f1101a4-6b85-4305-ad3d-0fb59d5547a1 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0xb7556e00:movdqu (%eax),%xmm0
   PC (0xb7556e00) ok
   source (%eax) (0x66bc6350) not located in a known VMA region (needed 
readable region)!
   destination %xmm0 ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
  Title: compiz crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Fri Mar  8 15:57:38 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse TOUCHSCREEN, id 7
   inputVMware VMware Virtual USB Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   No surface to present from.
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual3Virtual4Virtual5Virtual6Virtual7
Virtual8
  xserver.version: 2:1.13.2-0ubuntu3
  xserver.video_driver: vmware

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1282780] Re: compiz crashed with SIGSEGV

2014-03-02 Thread Cavsfan
I get this error when resizing windows. The whole system freezes and
then apport pops up when it comes back up. The windows decoration check
mark is gone at this time too.

** Changed in: compiz (Ubuntu)
   Status: Invalid = New

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

Title:
  compiz crashed with SIGSEGV

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I got this yesterday and didn't report it because there were compiz
  updates. Today I got all of the updates and after the new kernel
  3.13.0-11-generic was installed and I rebooted. I got this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140218-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  CurrentDesktop: GNOME
  CurrentDmesg:
   [   19.258926] nvidia :01:00.0: irq 45 for MSI/MSI-X
   [   19.859039] r8169 :03:00.0 eth0: link up
   [   19.859047] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   69.652374] show_signal_msg: 183 callbacks suppressed
   [   69.652380] compiz[2152]: segfault at 10 ip 7f2d5edb8845 sp 
7fff49306ba0 error 4 in libnvidia-glcore.so.331.38[7f2d5d7f2000+1b67000]
  Date: Thu Feb 20 16:10:18 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-10-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-11-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-10-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-11-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:c988]
  InstallationDate: Installed on 2014-01-08 (43 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7f2d5edb8845:movaps 0x10(%rdx),%xmm0
   PC (0x7f2d5edb8845) ok
   source 0x10(%rdx) (0x0010) not located in a known VMA region (needed 
readable region)!
   destination %xmm0 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38
   ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38
   ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38
   ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38
   ?? () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38
  Title: compiz crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31M3-L V2(MS-7529)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7529
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.2.0~git20140213.0320ba99-0ubuntu0sarvatt2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Desktop-packages] [Bug 1284266] Re: compizconfig-settings-manager doesn't allow Windows Decoration to stay checked

2014-02-28 Thread Cavsfan
Just by opening CCSM, the window decorator goes away and the check box
becomes unchecked.

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

Title:
  compizconfig-settings-manager doesn't allow Windows Decoration to stay
  checked

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Every bootup or login the Windows Decoration checkbox is unchecked. I click 
to check it and it's good for a while. The system is up to date.
  But, it will become unchecked on it's own at any time. It will simply not 
stay in effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140218-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: GNOME
  Date: Mon Feb 24 14:08:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-11-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-12-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-11-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-12-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:c988]
  InstallationDate: Installed on 2014-01-08 (46 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31M3-L V2(MS-7529)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7529
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
  xserver.bootTime: Mon Feb 24 12:36:10 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUVC Camera (046d:081a) KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.15.0-1ubuntu6

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1284201] [NEW] pacman crashed with SIGSEGV in __libc_start_main()

2014-02-24 Thread Cavsfan
*** This bug is a duplicate of bug 1196251 ***
https://bugs.launchpad.net/bugs/1196251

Public bug reported:

Woke Trusty from suspend and it a few minutes later I wondered why the
screen was blank. Then apport popped up.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xscreensaver-data-extra 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 24 11:26:52 2014
ExecutablePath: /usr/lib/xscreensaver/pacman
InstallationDate: Installed on 2014-01-08 (46 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
ProcCmdline: pacman -root
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4084bf:cmp0xdb8(%rdi),%esi
 PC (0x004084bf) ok
 source 0xdb8(%rdi) (0x0201e004) not located in a known VMA region (needed 
readable region)!
 destination %esi ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x4027f0, argc=2, argv=0x7fff9808fd08, init=optimized 
out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fff9808fcf8) at libc-start.c:287
Title: pacman crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash third-party-packages trusty

** Information type changed from Private to Public

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

Title:
  pacman crashed with SIGSEGV in __libc_start_main()

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  Woke Trusty from suspend and it a few minutes later I wondered why the
  screen was blank. Then apport popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xscreensaver-data-extra 5.15-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 24 11:26:52 2014
  ExecutablePath: /usr/lib/xscreensaver/pacman
  InstallationDate: Installed on 2014-01-08 (46 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  ProcCmdline: pacman -root
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4084bf:  cmp0xdb8(%rdi),%esi
   PC (0x004084bf) ok
   source 0xdb8(%rdi) (0x0201e004) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x4027f0, argc=2, argv=0x7fff9808fd08, 
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fff9808fcf8) at libc-start.c:287
  Title: pacman crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1256961] Re: new glib (2.39.1) causes some indicators nautilus to not load promptly

2013-12-06 Thread Cavsfan
I just logged out and back in then timed it to see when the panel
date/time etc. appeared and it took 1 minute 30 seconds for it to come
up all the way. Once I clicked on Cairo Dock from the menu on the top
panel in flashback as it is immediately available. Then when it did
finish starting up I had 2 instances of Cairo Dock running.

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

Title:
  new glib (2.39.1) causes some indicators  nautilus to not load
  promptly

Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  updated 14.04 install with glib (2.39.1)  default installed 
indicator-applet-complete
  Log into either flashback session
  indicators session, datetime  sound will not be present
  additionally  nautilus will have not been started (handling the Desktop), can 
be seen by absence of r. click on Desktop

  Wait 1-2 min, then the indicators will load  nautilus will have started
  (nautilus can be started prior to from places

  With previous glib (2.38+) none of this occurs

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-flashback (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-4.12-generic 3.12.1
  Uname: Linux 3.12.0-4-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  2 10:29:31 2013
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1199074] Re: Saucy - cannot uninstall gnome-screensaver because it wants to uninstall gnome-session-flashback also.

2013-11-20 Thread Cavsfan
This currently affects Trusty 14.04 as well as Saucy 13.10. But, the
workaround above works well.

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

Title:
  Saucy - cannot uninstall gnome-screensaver because it wants to
  uninstall gnome-session-flashback also.

Status in “gnome-panel” package in Ubuntu:
  Triaged

Bug description:
  I wanted to uninstall gnome-screensaver and have xscreensaver work
  but, when I attempt to remove gnome-screensaver, it wants to take
  gnome-session-flashback. That is not what I want to do.

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

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


[Desktop-packages] [Bug 1199074] Re: Saucy - cannot uninstall gnome-screensaver because it wants to uninstall gnome-session-flashback also.

2013-11-06 Thread Cavsfan
Found a workaround to leave gnome-screensaver installed while running 
xscreensaver:
Create a script to run at startup with these commands. Anything less than 60 
seconds is less likely to work.

#! /bin/bash
sleep 60
killall gnome-screensaver

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

Title:
  Saucy - cannot uninstall gnome-screensaver because it wants to
  uninstall gnome-session-flashback also.

Status in “gnome-panel” package in Ubuntu:
  Triaged

Bug description:
  I wanted to uninstall gnome-screensaver and have xscreensaver work
  but, when I attempt to remove gnome-screensaver, it wants to take
  gnome-session-flashback. That is not what I want to do.

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

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


[Desktop-packages] [Bug 1227770] Re: gvfsd-mtp crashed with SIGSEGV in ptp_property_issupported() (when plugging in android phone via USB port)

2013-09-24 Thread Cavsfan
** Summary changed:

- gvfsd-mtp crashed with SIGSEGV in ptp_property_issupported()
+ gvfsd-mtp crashed with SIGSEGV in ptp_property_issupported() (when plugging 
in android phone via USB port)

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

Title:
  gvfsd-mtp crashed with SIGSEGV in ptp_property_issupported() (when
  plugging in android phone via USB port)

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  On Saucy 13.10:
  I plugged in my andriod phone via USB to get a picture off of it and it said 
it failed to mount but did. I was able to get the picture.
  Then when I clicked unmount in Places, it also said failed to dismount but 
did and this error popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 19 12:03:36 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2013-06-30 (80 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130630)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fc5def4f14c:cmp%cx,-0x2(%rax)
   PC (0x7fc5def4f14c) ok
   source %cx ok
   destination -0x2(%rax) (0x7fc5cc0ca000) in non-writable VMA region: 
0x7fc5cc0ca000-0x7fc5d000 ---p None
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing VMA None
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Friendlyname () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   ?? ()
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1227770] Re: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()

2013-09-19 Thread Cavsfan
** Information type changed from Private Security to Public Security

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

Title:
  gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  On Saucy 13.10:
  I plugged in my andriod phone via USB to get a picture off of it and it said 
it failed to mount but did. I was able to get the picture.
  Then when I clicked unmount in Places, it also said failed to dismount but 
did and this error popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 19 12:03:36 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2013-06-30 (80 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130630)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fc5def4f14c:cmp%cx,-0x2(%rax)
   PC (0x7fc5def4f14c) ok
   source %cx ok
   destination -0x2(%rax) (0x7fc5cc0ca000) in non-writable VMA region: 
0x7fc5cc0ca000-0x7fc5d000 ---p None
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing VMA None
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Friendlyname () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   ?? ()
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1227770] Re: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()

2013-09-19 Thread Cavsfan
** Information type changed from Private to Public Security

** Information type changed from Public Security to Private Security

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

Title:
  gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  On Saucy 13.10:
  I plugged in my andriod phone via USB to get a picture off of it and it said 
it failed to mount but did. I was able to get the picture.
  Then when I clicked unmount in Places, it also said failed to dismount but 
did and this error popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 19 12:03:36 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2013-06-30 (80 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130630)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fc5def4f14c:cmp%cx,-0x2(%rax)
   PC (0x7fc5def4f14c) ok
   source %cx ok
   destination -0x2(%rax) (0x7fc5cc0ca000) in non-writable VMA region: 
0x7fc5cc0ca000-0x7fc5d000 ---p None
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing VMA None
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Friendlyname () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   ?? ()
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Friendlyname()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

2013-07-30 Thread Cavsfan
I just tested the amd64 deb and got this:
cavsfan@cavsfan-desktop:~/Downloads$ sudo dpkg -i 
gnome-panel_3.6.2-0ubuntu12_amd64.deb[sudo] password for cavsfan: 
(Reading database ... 236597 files and directories currently installed.)
Preparing to replace gnome-panel 1:3.4.1-0ubuntu1.1 (using 
gnome-panel_3.6.2-0ubuntu12_amd64.deb) ...
Unpacking replacement gnome-panel ...
dpkg: dependency problems prevent configuration of gnome-panel:
 gnome-panel depends on libdconf1 (= 0.14.0); however:
  Package libdconf1 is not installed.
 gnome-panel depends on libecal-1.2-15 (= 3.5.91); however:
  Package libecal-1.2-15 is not installed.
 gnome-panel depends on libedataserver-1.2-17 (= 3.5.91); however:
  Package libedataserver-1.2-17 is not installed.
 gnome-panel depends on libglib2.0-0 (= 2.37.3); however:
  Version of libglib2.0-0 on system is 2.32.3-0ubuntu1.
 gnome-panel depends on libgnome-desktop-3-7 (= 3.2.0); however:
  Package libgnome-desktop-3-7 is not installed.
 gnome-panel depends on libgweather-3-3 (= 3.7.91); however:
  Package libgweather-3-3 is not installed.
 gnome-panel depends on libical1 (= 1.0); however:
  Package libical1 is not installed.
 gnome-panel depends on libpango-1.0-0 (= 1.18.0); however:
  Package libpango-1.0-0 is not installed.
 gnome-panel depends on gnome-panel-data (= 1:3.6.2-0ubuntu12); however:
  Version of gnome-panel-data on system is 1:3.4.1-0ubuntu1.1.
dpkg: error processing gnome-panel (--install):
 dependency problems - leaving unconfigured
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for man-db ...
Errors were encountered while processing:
 gnome-panel

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

Title:
  Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

Status in Compiz:
  Confirmed
Status in Desktop panel for GNOME:
  New
Status in Themes for Ubuntu:
  New
Status in “gnome-panel” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  White squares appears in blank sections of gnome panel at Ubuntu Startup and 
during window Minimize / Maximize Actions. Gnome-Flashback with Compiz 
(Effects) only.

  Distribution:

  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  Packages:

  compiz:
    Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Version table:
   *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10:
    Installed: 1:3.6.2-0ubuntu11
    Candidate: 1:3.6.2-0ubuntu11
    Version table:
   *** 1:3.6.2-0ubuntu11 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

  How to Reproduce:

  Normally after distro-upgrade or a clean install, since the 1st Boot
  you'll see a white square in unussed portion of gnome panels (totally
  white if the panel is clean)

  Steps:

  1.- Launch some application (firefox in this case)
  2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox 
to Panel)
  3.- At this Step, maybe the White panell has disappeared ( Now the color is 
normal according to Ambiance Theme )
  4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and 
the White Square in Gnome Panel appears Again. If its not, repeat the Minimize 
and Maximize actios to rise up the bug)

  Temporary WorkArround:

  Enable Show Hide Buttons under Panel Properties. This will
  transfer the buggy white color effect to the sidebuttons in the
  panel.

  How to Reproduce with Adwaita theme:
  1) Open file for edit:
  /usr/share/themes/Adwaita/gtk-3.0/gtk.css

  2) Add these lines end of file:
  .gnome-panel-menu-bar,
  PanelApplet  GtkMenuBar.menubar,
  PanelToplevel,
  PanelWidget,
  PanelAppletFrame,
  PanelApplet {
  background-image: -gtk-gradient(linear, left top, left bottom, 
from(shade(#3c3b37, 1.5)), to(shade(#3c3b37, 1.05)));
  }

  3. Switch gtk theme to Adwaita. If already using it, restart gnome-
  panel.

  4. gnome-panel has black background instead of gradient. menu bar and
  indicator applet complete looks like it should.

  5. Opening panel properties and switching background from none to
  solid color and back will bring gradient to whole panel.

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

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

[Desktop-packages] [Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

2013-07-30 Thread Cavsfan
Ignore the above post.
I just tried the amd64 deb and got these errors:

cavsfan@cavsfan-MS-7529:~/Downloads$ sudo dpkg -i 
gnome-panel_3.6.2-0ubuntu12_amd64.deb[sudo] password for cavsfan: 
(Reading database ... 209648 files and directories currently installed.)
Preparing to replace gnome-panel 1:3.6.2-0ubuntu11 (using 
gnome-panel_3.6.2-0ubuntu12_amd64.deb) ...
Unpacking replacement gnome-panel ...
dpkg: dependency problems prevent configuration of gnome-panel:
 gnome-panel depends on gnome-panel-data (= 1:3.6.2-0ubuntu12); however:
  Version of gnome-panel-data on system is 1:3.6.2-0ubuntu11.

dpkg: error processing gnome-panel (--install):
 dependency problems - leaving unconfigured
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus ...
Processing triggers for desktop-file-utils ...
Processing triggers for mime-support ...
Processing triggers for man-db ...
Errors were encountered while processing:
 gnome-panel

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

Title:
  Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

Status in Compiz:
  Confirmed
Status in Desktop panel for GNOME:
  New
Status in Themes for Ubuntu:
  New
Status in “gnome-panel” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  White squares appears in blank sections of gnome panel at Ubuntu Startup and 
during window Minimize / Maximize Actions. Gnome-Flashback with Compiz 
(Effects) only.

  Distribution:

  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  Packages:

  compiz:
    Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Version table:
   *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10:
    Installed: 1:3.6.2-0ubuntu11
    Candidate: 1:3.6.2-0ubuntu11
    Version table:
   *** 1:3.6.2-0ubuntu11 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

  How to Reproduce:

  Normally after distro-upgrade or a clean install, since the 1st Boot
  you'll see a white square in unussed portion of gnome panels (totally
  white if the panel is clean)

  Steps:

  1.- Launch some application (firefox in this case)
  2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox 
to Panel)
  3.- At this Step, maybe the White panell has disappeared ( Now the color is 
normal according to Ambiance Theme )
  4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and 
the White Square in Gnome Panel appears Again. If its not, repeat the Minimize 
and Maximize actios to rise up the bug)

  Temporary WorkArround:

  Enable Show Hide Buttons under Panel Properties. This will
  transfer the buggy white color effect to the sidebuttons in the
  panel.

  How to Reproduce with Adwaita theme:
  1) Open file for edit:
  /usr/share/themes/Adwaita/gtk-3.0/gtk.css

  2) Add these lines end of file:
  .gnome-panel-menu-bar,
  PanelApplet  GtkMenuBar.menubar,
  PanelToplevel,
  PanelWidget,
  PanelAppletFrame,
  PanelApplet {
  background-image: -gtk-gradient(linear, left top, left bottom, 
from(shade(#3c3b37, 1.5)), to(shade(#3c3b37, 1.05)));
  }

  3. Switch gtk theme to Adwaita. If already using it, restart gnome-
  panel.

  4. gnome-panel has black background instead of gradient. menu bar and
  indicator applet complete looks like it should.

  5. Opening panel properties and switching background from none to
  solid color and back will bring gradient to whole panel.

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

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


[Desktop-packages] [Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

2013-07-30 Thread Cavsfan
I installed both debs and still have the white top and bottom middle
panels.

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

Title:
  Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

Status in Compiz:
  Confirmed
Status in Desktop panel for GNOME:
  New
Status in Themes for Ubuntu:
  New
Status in “gnome-panel” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  White squares appears in blank sections of gnome panel at Ubuntu Startup and 
during window Minimize / Maximize Actions. Gnome-Flashback with Compiz 
(Effects) only.

  Distribution:

  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  Packages:

  compiz:
    Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Version table:
   *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10:
    Installed: 1:3.6.2-0ubuntu11
    Candidate: 1:3.6.2-0ubuntu11
    Version table:
   *** 1:3.6.2-0ubuntu11 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

  How to Reproduce:

  Normally after distro-upgrade or a clean install, since the 1st Boot
  you'll see a white square in unussed portion of gnome panels (totally
  white if the panel is clean)

  Steps:

  1.- Launch some application (firefox in this case)
  2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox 
to Panel)
  3.- At this Step, maybe the White panell has disappeared ( Now the color is 
normal according to Ambiance Theme )
  4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and 
the White Square in Gnome Panel appears Again. If its not, repeat the Minimize 
and Maximize actios to rise up the bug)

  Temporary WorkArround:

  Enable Show Hide Buttons under Panel Properties. This will
  transfer the buggy white color effect to the sidebuttons in the
  panel.

  How to Reproduce with Adwaita theme:
  1) Open file for edit:
  /usr/share/themes/Adwaita/gtk-3.0/gtk.css

  2) Add these lines end of file:
  .gnome-panel-menu-bar,
  PanelApplet  GtkMenuBar.menubar,
  PanelToplevel,
  PanelWidget,
  PanelAppletFrame,
  PanelApplet {
  background-image: -gtk-gradient(linear, left top, left bottom, 
from(shade(#3c3b37, 1.5)), to(shade(#3c3b37, 1.05)));
  }

  3. Switch gtk theme to Adwaita. If already using it, restart gnome-
  panel.

  4. gnome-panel has black background instead of gradient. menu bar and
  indicator applet complete looks like it should.

  5. Opening panel properties and switching background from none to
  solid color and back will bring gradient to whole panel.

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

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


[Desktop-packages] [Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

2013-07-30 Thread Cavsfan
I had installed each deb separately and that caused problems. I
installed both debs with sudo dpkg -i gnome-panel*.deb this time and  I
can confirm that this did fix this problem.

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

Title:
  Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

Status in Compiz:
  Confirmed
Status in Desktop panel for GNOME:
  New
Status in Themes for Ubuntu:
  New
Status in “gnome-panel” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  White squares appears in blank sections of gnome panel at Ubuntu Startup and 
during window Minimize / Maximize Actions. Gnome-Flashback with Compiz 
(Effects) only.

  Distribution:

  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  Packages:

  compiz:
    Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Version table:
   *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10:
    Installed: 1:3.6.2-0ubuntu11
    Candidate: 1:3.6.2-0ubuntu11
    Version table:
   *** 1:3.6.2-0ubuntu11 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

  How to Reproduce:

  Normally after distro-upgrade or a clean install, since the 1st Boot
  you'll see a white square in unussed portion of gnome panels (totally
  white if the panel is clean)

  Steps:

  1.- Launch some application (firefox in this case)
  2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox 
to Panel)
  3.- At this Step, maybe the White panell has disappeared ( Now the color is 
normal according to Ambiance Theme )
  4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and 
the White Square in Gnome Panel appears Again. If its not, repeat the Minimize 
and Maximize actios to rise up the bug)

  Temporary WorkArround:

  Enable Show Hide Buttons under Panel Properties. This will
  transfer the buggy white color effect to the sidebuttons in the
  panel.

  How to Reproduce with Adwaita theme:
  1) Open file for edit:
  /usr/share/themes/Adwaita/gtk-3.0/gtk.css

  2) Add these lines end of file:
  .gnome-panel-menu-bar,
  PanelApplet  GtkMenuBar.menubar,
  PanelToplevel,
  PanelWidget,
  PanelAppletFrame,
  PanelApplet {
  background-image: -gtk-gradient(linear, left top, left bottom, 
from(shade(#3c3b37, 1.5)), to(shade(#3c3b37, 1.05)));
  }

  3. Switch gtk theme to Adwaita. If already using it, restart gnome-
  panel.

  4. gnome-panel has black background instead of gradient. menu bar and
  indicator applet complete looks like it should.

  5. Opening panel properties and switching background from none to
  solid color and back will bring gradient to whole panel.

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

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


[Desktop-packages] [Bug 1189309] Re: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()

2013-07-17 Thread Cavsfan
I just logged into Unity after logging out of Gnome Fallback and
immediately got this and other errors.

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

Title:
  nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()

Status in “network-manager-applet” package in Ubuntu:
  Confirmed

Bug description:
  crashed on login.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
  Uname: Linux 3.9.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jun 10 12:34:25 2013
  ExecutablePath: /usr/bin/nm-applet
  ExecutableTimestamp: 1362762982
  InstallationDate: Installed on 2012-09-23 (260 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: nm-applet
  ProcCwd: /home/darkness
  RfKill:
   
  SegvAnalysis:
   Segfault happened at: 0x7fe676a5f87c gtk_status_icon_set_visible+28:   
cmp%rax,(%rdx)
   PC (0x7fe676a5f87c) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   gtk_status_icon_set_visible (status_icon=0x265c300, visible=0) at 
/build/buildd/gtk+3.0-3.8.2/./gtk/gtkstatusicon.c:2057
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libappindicator3.so.1
   g_object_unref (_object=0x25999b0) at 
/build/buildd/glib2.0-2.37.1/./gobject/gobject.c:3152
   ?? ()
  Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0.14vlan  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  
   test   vlan  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunmanaged 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
disabled   enabled disabled

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

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


[Desktop-packages] [Bug 1196251] [NEW] pacman crashed with SIGSEGV in is_bonus_dot()

2013-06-30 Thread Cavsfan
Public bug reported:

I was just selecting which xscreensavers to allow and had not gotten to
pacman yet when this occurred.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xscreensaver-data-extra 5.15-2ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Sun Jun 30 09:56:05 2013
ExecutablePath: /usr/lib/xscreensaver/pacman
InstallationDate: Installed on 2013-06-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130626)
MarkForUpload: True
ProcCmdline: pacman -root -window-id 0x1803DB5
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4084bf:cmp0xdb8(%rdi),%esi
 PC (0x004084bf) ok
 source 0xdb8(%rdi) (0x01ed2004) not located in a known VMA region (needed 
readable region)!
 destination %esi ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
Title: pacman crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: xscreensaver (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash saucy third-party-packages

** Information type changed from Private to Public

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

Title:
  pacman crashed with SIGSEGV in is_bonus_dot()

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  I was just selecting which xscreensavers to allow and had not gotten
  to pacman yet when this occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xscreensaver-data-extra 5.15-2ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sun Jun 30 09:56:05 2013
  ExecutablePath: /usr/lib/xscreensaver/pacman
  InstallationDate: Installed on 2013-06-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130626)
  MarkForUpload: True
  ProcCmdline: pacman -root -window-id 0x1803DB5
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4084bf:  cmp0xdb8(%rdi),%esi
   PC (0x004084bf) ok
   source 0xdb8(%rdi) (0x01ed2004) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
  Title: pacman crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1196177] Re: Compiz - Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

2013-06-30 Thread Cavsfan
Every time I boot into Saucy the middle section of the top and bottom panels 
are a light color close to white.
I have found that if I hold ALT+Super+right click the mouse on each panel, go 
to properties, click background,
change it to solid color and then back to none (use system theme) then it 
straightens out and the color matches the rest of the panels. I used to have to 
do this multiple times per session but, recently it appears I can do it once 
after login but, not absolutely sure.

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

Title:
  Compiz - Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)

Status in Compiz:
  New
Status in Compiz Core:
  New
Status in Compiz Core Ubuntu:
  New
Status in Compiz Workarounds Plugins:
  New
Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  White squares appears in blank sections of gnome panel at Ubuntu Startup and 
during window Minimize / Maximize Actions. Gnome-Flashback with Compiz 
(Effects) only.

  Distribution:

  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  Packages:

  compiz:
    Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
    Version table:
   *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10:
    Installed: 1:3.6.2-0ubuntu11
    Candidate: 1:3.6.2-0ubuntu11
    Version table:
   *** 1:3.6.2-0ubuntu11 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

  How to Reproduce:

  Normally after distro-upgrade or a clean install, since the 1st Boot
  you'll see a white square in unussed portion of gnome panels (totally
  white if the panel is clean)

  Steps:

  1.- Launch some application (firefox in this case)
  2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox 
to Panel)
  3.- At this Step, maybe the White panell has disappeared ( Now the color is 
normal according to Ambiance Theme )
  4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and 
the White Square in Gnome Panel appears Again. If its not, repeat the Minimize 
and Maximize actios to rise up the bug)

  Temporary WorkArround:

  Enable Show Hide Buttons under Panel Properties. This will
  transfer the buggy white color effect to the sidebuttons in the
  panel.

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

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


[Desktop-packages] [Bug 796076] Re: When run as root [gksudo gedit whatever] gedit tries to open a 2nd 'untitled document 1'

2013-06-05 Thread Cavsfan
This annoying little quirk just started happening in Ubuntu 12.04 LTS, however 
it always has occurred in 12.10, 13.04, 13.10 as well as Mint 13 and 15.
I added the workaround samuel mentioned as I only ever use this in terminal.

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

Title:
  When run as root [gksudo gedit whatever]  gedit  tries to open a 2nd
  'untitled document 1'

Status in Light-Weight Text Editor for Gnome:
  Fix Released
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Ex.
  gksudo gedit /etc/fstab will open fstab successfully but will also try to 
open Untitled Document 1 at the same time
  If just running gksudo gedit than you'll get Untitled Document 1 that never 
does fully open (become writable

  == Regression details ==
  Discovered in version: 3.0.4-0ubuntu2
  Last known good version: 2.30.4-2ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gedit 3.0.4-0ubuntu2 [modified: usr/share/applications/gedit.desktop]
  ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7
  Uname: Linux 2.6.38-9-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sat Jun 11 19:11:08 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.utf8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1105102] Re: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

2013-01-25 Thread Cavsfan
I just installed the daily iso and was preparing to copy files and got
this error.

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

Title:
  dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

Status in “glib2.0” package in Ubuntu:
  Fix Committed

Bug description:
  Occured after the raring desktop amd64 installation on 20130125 on a
  VM based on qemu-kvm usign virt-manager

  1. Boot a VM to raring desktop amd64 live session with the image of 20130125 
  2. Start the installer from the live session
  3. Perform manual partition (with 3 ext4 partitions and a swap)
  4. Reboot after the installation
  5. This crash was observed after the first reboot

  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: dconf-service 0.15.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Fri Jan 25 13:57:33 2013
  ExecutablePath: /usr/lib/dconf/dconf-service
  InstallationDate: Installed on 2013-01-25 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125)
  MarkForUpload: True
  ProcCmdline: /usr/lib/dconf/dconf-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fdfa0181520:mov0x20(%rdi),%eax
   PC (0x7fdfa0181520) ok
   source 0x20(%rdi) (0x0020) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: d-conf
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+subscriptions

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


[Desktop-packages] [Bug 1019995] Re: gksu nautilus will not display icons correctly or at all

2012-08-11 Thread Cavsfan
In terminal entering sudo -s, entering password and then nautilus is the 
work around I have read.
It also does not give any errors like gksu nautilus does.

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

Title:
  gksu nautilus will not display icons correctly or at all

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  nautulus 3.5.3 will not display  icons when using gksu nautilus in
  terminal

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

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
  Uname: Linux 3.5.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.2.5-0ubuntu1
  Architecture: i386
  Date: Mon Jul  2 04:50:02 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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