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

2014-10-11 Thread starkus
Public bug reported:

error through upgrading from 14.04 to 14.10 without having had purged
some ppa i guess...

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
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 07:45:47 2014
InstallationDate: Installed on 2014-08-23 (48 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
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-10-11 (0 days ago)

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


** Tags: amd64 apport-package 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/1380006

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

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

Bug description:
  error through upgrading from 14.04 to 14.10 without having had purged
  some ppa i guess...

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 07:45:47 2014
  InstallationDate: Installed on 2014-08-23 (48 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  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-10-11 (0 days ago)

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

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


[Desktop-packages] [Bug 1380014] [NEW] modemmanager should blacklist Freetronics devices

2014-10-11 Thread Ben Stanley
Public bug reported:

In a similar vein to Bug #910736, there are more Arduino related devices
that must be blacklisted.

For the LeoStick, the following is required:
-- /etc/udev/rules.d/77-modem-manager-freetronics.rules 
--
ATTRS{idVendor}==26ba, ENV{ID_MM_DEVICE_IGNORE}=1
ATTRS{idVendor}==20a0, ENV{ID_MM_DEVICE_IGNORE}=1
---
See http://www.freetronics.com/pages/leostick-getting-started-guide in the 
section Problems Uploading on Linux.

There are also some additional devices listed on the end of Bug #910736
after it was marked as FixedReleased.

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

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

Title:
  modemmanager should blacklist Freetronics devices

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  In a similar vein to Bug #910736, there are more Arduino related
  devices that must be blacklisted.

  For the LeoStick, the following is required:
  -- /etc/udev/rules.d/77-modem-manager-freetronics.rules 
--
  ATTRS{idVendor}==26ba, ENV{ID_MM_DEVICE_IGNORE}=1
  ATTRS{idVendor}==20a0, ENV{ID_MM_DEVICE_IGNORE}=1
  
---
  See http://www.freetronics.com/pages/leostick-getting-started-guide in the 
section Problems Uploading on Linux.

  There are also some additional devices listed on the end of Bug
  #910736 after it was marked as FixedReleased.

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

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


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

2014-10-11 Thread Thierry Leiber
Public bug reported:

v??

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 08:12:05 2014
InstallationDate: Installed on 2014-04-08 (185 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140403)
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-10-06 (4 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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


** Tags: amd64 apport-package 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/1380018

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

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

Bug description:
  v??

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 08:12:05 2014
  InstallationDate: Installed on 2014-04-08 (185 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140403)
  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-10-06 (4 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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


[Desktop-packages] [Bug 1059872] Re: Error formatting disk using disk utility

2014-10-11 Thread Mupfelzitze
Fresh Ubuntu 14.04.1 LTS. Disk utility fails in formatting empty
partition on usb-disk:

Error formatting partition
Error synchronizing after initial wipe: Timed out waiting for object 
(udisks-error-quark, 0)

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

Title:
  Error formatting disk using disk utility

Status in “udisks2” package in Ubuntu:
  Invalid
Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “udisks2” source package in Trusty:
  Invalid
Status in “util-linux” source package in Trusty:
  Triaged
Status in “util-linux” package in Debian:
  Fix Released

Bug description:
  Formatting a SD card using the disk utility fails with an error
  message

  Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)

  Steps to repro:
  Launch the disk utility
  Plug a SD card into the computer
  Select the SD card and click on the gears icon at the top right of the 
application
  From the drop down menu, select Format Disk
  maintain the default setting and select Format
  Acknowledge warnings
  After format process has been going for a while, the error message shown 
above pops up

  Workaround: 
  After selecting the SD card, instead of clicking the gear icon to format, 
click the partition in the Volumes section.
  Delete the partition (minus icon)
  Create a new partition

  -

  The underlying problem is that the wipefs tool from util-linux does
  not work any more.

  === TEST CASE ===
  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat EOF | sudo sfdisk /dev/sdb
  # partition table of /dev/sdb
  unit: sectors

  /dev/sdb1 : start=   32, size=   409568, Id=83
  /dev/sdb2 : start=0, size=0, Id= 0
  /dev/sdb3 : start=0, size=0, Id= 0
  /dev/sdb4 : start=0, size=0, Id= 0
  EOF

  # now create an ext4 file system:
  $ sudo mkfs.ext4 /dev/sdb1

  # check contents:
  $ sudo blkid -p /dev/sdb /dev/sdb1
  /dev/sdb: PTTYPE=dos
  /dev/sdb1: UUID=4bd1c542-a61f-43c4-a7e5-cc50e66e6b5a VERSION=1.0 
TYPE=ext4 USAGE=filesystem PART_ENTRY_SCHEME=dos PART_ENTRY_TYPE=0x83 
PART_ENTRY_NUMBER=1 PART_ENTRY_OFFSET=32 PART_ENTRY_SIZE=409568 
PART_ENTRY_DISK=8:16

  # wipe:
  $ sudo wipefs -a /dev/sdb

  # now check contents again
  $ sudo blkid -p /dev/sdb /dev/sdb1

  # in the broken case, you will still see a dos partition table and
  the ext4 partition; in the working case, /dev/sdb won't show anything
  and /dev/sdb1 does not exist any more

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: udisks 1.0.4-6
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CustomUdevRuleFiles: 51-android.rules 51-android.rules~
  Date: Mon Oct  1 15:07:46 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120720.1)
  MachineType: FOXCONN NT-A2400NT-A3500
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic 
root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7
  SourcePackage: udisks
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: NT-A2400NT-A3500
  dmi.board.vendor: FOXCONN
  dmi.board.version: FAB 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: FOXCONN
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.:
  dmi.product.name: NT-A2400NT-A3500
  dmi.product.version: FAB 1.0
  dmi.sys.vendor: FOXCONN

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

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


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

2014-10-11 Thread Brian Smith
Public bug reported:

Failed to build on update to Kernel 3.16.0.22

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 10:17:57 2014
InstallationDate: Installed on 2014-07-11 (91 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709)
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)

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


** Tags: amd64 apport-package 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/1380028

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

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

Bug description:
  Failed to build on update to Kernel 3.16.0.22

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 10:17:57 2014
  InstallationDate: Installed on 2014-07-11 (91 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709)
  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/1380028/+subscriptions

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


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

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

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Status: New = Confirmed

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

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

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

Bug description:
  This incident occured while system updates were being applied.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 00:01:13 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates 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-updates/+bug/1380001/+subscriptions

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


[Desktop-packages] [Bug 1253620]

2014-10-11 Thread Sbergman
(In reply to Björn Michaelsen from comment #68)
 Scoping this bug clearly only on the missing deps for KDE thanks to the
 excellent summary in comment 59.

...which has become moot with
http://cgit.freedesktop.org/libreoffice/core/commit/?id=f9f9aa9873c5851da86d33ca75e937ac022206a3
Remove smb from X-KDE-Protocols lines, see
http://lists.freedesktop.org/archives/libreoffice/2014-October/063904.html
Re: X-KDE-Protocols=...,smb,...

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

Title:
  Can't open a LibreOffice native file via CIFS share

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  Problem description: 
  Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 
12.04 and LibreOffice 4.1.3.2 (from ppa).

  System informations:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04
  Codename: precise

  LibreOffice package from ppa:libreoffice/ppa: 
  1:4.1.3~rc2-0ubuntu1~precise1~ppa1

  Steps to reproduce:
  1. Open LibreOffice
  2. Select Open File from file menu
  3. Select the remote share folder
  4. Click to open the file

  Current behavior:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior:
  LibreOffice opens the remote file correctly.

  Alternatives steps:
  1. Open the remote path via Nautilus
  2. Double click on remote LibreOffice native files

  Current behavior2:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior2:
  LibreOffice opens the remote file correctly.

  Notes: 
  * Remote and local MS files are opened correctly.
  * The problems with LibreOffice native files disappear if copying the remote 
files in a local path

  Here a workaround:
  sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' 
/usr/share/applications/libreoffice-*

  No problem present on:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  with LibreOffice:
  1:4.1.3~rc2-0ubuntu1~saucy1~ppa3

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

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


[Desktop-packages] [Bug 1253620] Re: Can't open a LibreOffice native file via CIFS share

2014-10-11 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed = Fix Released

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

Title:
  Can't open a LibreOffice native file via CIFS share

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  Problem description: 
  Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 
12.04 and LibreOffice 4.1.3.2 (from ppa).

  System informations:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04
  Codename: precise

  LibreOffice package from ppa:libreoffice/ppa: 
  1:4.1.3~rc2-0ubuntu1~precise1~ppa1

  Steps to reproduce:
  1. Open LibreOffice
  2. Select Open File from file menu
  3. Select the remote share folder
  4. Click to open the file

  Current behavior:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior:
  LibreOffice opens the remote file correctly.

  Alternatives steps:
  1. Open the remote path via Nautilus
  2. Double click on remote LibreOffice native files

  Current behavior2:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior2:
  LibreOffice opens the remote file correctly.

  Notes: 
  * Remote and local MS files are opened correctly.
  * The problems with LibreOffice native files disappear if copying the remote 
files in a local path

  Here a workaround:
  sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' 
/usr/share/applications/libreoffice-*

  No problem present on:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  with LibreOffice:
  1:4.1.3~rc2-0ubuntu1~saucy1~ppa3

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

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


[Desktop-packages] [Bug 1374771] Re: black background in resources tab

2014-10-11 Thread netanelf
This bug seems to be fixed in one of the last utopic updates.

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

Title:
  black background in resources tab

Status in “gnome-system-monitor” package in Ubuntu:
  New

Bug description:
  after updating to ubuntu 14.10 (from ubuntu 14.04)
  in the system monitor the graphs look bad as the background has became black 
instead of the usual bright one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-system-monitor 3.8.2.1-2ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 27 17:30:12 2014
  InstallationDate: Installed on 2014-05-19 (131 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to utopic on 2014-09-26 (0 days ago)

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

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


[Desktop-packages] [Bug 1380046] [NEW] [AV200 - Xonar STX, playback] Loud pop when switching to headphones

2014-10-11 Thread Michael Lawton
Public bug reported:

When switching the port to either headphone ports from the speaker port
there is a loud pop in the headphones. When I am playing music through
the speakers at 100% volume and then switch, I can hear the music at a
very loud volume through the headphones for a fraction of a second
before dropping to the proper headphones volume which is much lower.
Even if I mute the output before switching ports there is still a pop
although not nearly as loud.

I believe this is a driver issue (oxygen/virtuoso). The Essense STX uses
a relay to switch between the speaker and headphones ports. I am
guessing the the power for the speaker (line out) port is much higher
than that used for the headphones port and the drivers need to mute the
sound at a hardware level before switching to elmininate the pop. On
Windows when switching to and from speaker and headphones port the
output would be muted for almost a second as the port was switched so
there was no pop. On Ubuntu there is no delay when switching ports. I
have looked at the driver source code and there is an anti_pop_delay of
800 milliseconds used on the Xonar init method. I think this same delay
should probably be added when switching to the headphone ports.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  michael   20842 F pulseaudio
 /dev/snd/controlC0:  michael   20842 F pulseaudio
 /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
 /dev/snd/controlC1:  michael   20842 F pulseaudio
CurrentDesktop: Unity
Date: Sat Oct 11 22:50:15 2014
InstallationDate: Installed on 2014-10-07 (3 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [AV200 - Xonar STX, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  

[Desktop-packages] [Bug 1377007] Re: Delay in response to user actions in Ubuntu 14.10 on cards AMD

2014-10-11 Thread Tamir
on the kernel 3.16.0-21-generic # 28-Ubuntu SMP Mon Oct 6 16:00:43 UTC
2014 x86_64 x86_64 x86_64 GNU / Linux to normal  :) - no delay/

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

Title:
  Delay in response to user actions in Ubuntu 14.10 on cards AMD

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Constant periodic belated response of the system to the user. Evident even 
when you drive across the screen just with the mouse.
  When you turn off the laptop weighs a welcome screen for a long time until 
the power goes off.
  Perhaps the problem is in the other modules of the operating system, such as 
the open source driver for AMD graphics cards in the kernel 3.16
  P.S. In Ubuntu 14.04 no such problem.
  P.S.S. Graphics: GLX Renderer: Gallium 0.4 on AMD ARUBA
  Card-1: Advanced Micro Devices [AMD/ATI] Radeon HD 7520G
  Card-2: Advanced Micro Devices [AMD/ATI] Radeon HD 7670M
  Resolution: 1366x768@60.1hz 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.344
  CurrentDesktop: Unity
  Date: Fri Oct  3 04:45:14 2014
  LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141002)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 33883] Re: hidden files not included in directory 'properties'

2014-10-11 Thread marco.pallotta
Confirmed on 14.04 too.

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

Title:
  hidden files not included in directory 'properties'

Status in Nautilus:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  Nautilus 2.13.91 under Dapper Flyer 4 and Nautilus 2.12.1 under
  Breezy.

  Expected behaviour
  * upon right clicking a directory and choosing properties the numbers in the 
'contents' will include all files and folders.

  Actual behaviour:
  * lists only non-hidden files

  Workaround
  * open the directory, set 'show hidden files' to 'yes', choose select all, 
select properties.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-11 Thread dino99
Still getting that error:

cd /var/lib/dkms/nvidia-331/331.89/build; make module 
SYSSRC=/lib/modules/3.16.0-22-generic/build 
SYSOUT=/lib/modules/3.16.0-22-generic/build 
KBUILD_EXTMOD=/var/lib/dkms/nvidia-331/331.89/build
make[1]: Entering directory '/var/lib/dkms/nvidia-331/331.89/build'
NVIDIA: calling KBUILD...
make[2]: Entering directory '/usr/src/linux-headers-3.16.0-22-generic'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo 2;   \
echo 2   ERROR: Kernel configuration is invalid.;   \
echo 2  include/generated/autoconf.h or include/config/auto.conf are 
missing.;\
echo 2  Run 'make oldconfig  make prepare' on kernel src to fix 
it.;  \
echo 2 ;  

Could not this be fixed ? That issue is met by many users.

Devtalk: https://devtalk.nvidia.com/default/topic/769055/dkms-fails-to-
compile-nvidia-modules-340-32-343-13-during-kernel-3-16-1-compile-
process-on-debia/

-- 
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 “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/ubuntu/+source/nvidia-graphics-drivers-331/+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 1379431] Re: Eclipse crashes very often because of problems with GTK

2014-10-11 Thread JPTTEST
see https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736

** Bug watch added: Eclipse bugs #430736
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736

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

Title:
  Eclipse crashes very often because of problems with GTK

Status in “eclipse” package in Ubuntu:
  New

Bug description:
  Especially when clicking buttons Eclipse crashes.

  This is regardless of 
  - the Java version (tried openjava 7 and oracle java 7)
  - the eclipse version (tried the ubuntu delivered 3.8 and 4.4 download from 
eclipse.org)

  They say the cause is that eclipse loads a mix of GTK2 and GTK3 libs.
  (cannot find the source now)

  Solution: simply add the env var 
  export SWT_GTK3=1

  
  Ubuntu 14.04.1 LTS

  Package: eclipse
  Architecture: all
  Version: 3.8.1-5.1

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

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


[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%

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

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

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

Title:
  Initial zoom level is slightly under 100%

Status in Eye of GNOME:
  New
Status in “eog” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  When opening an image, the zoom level is displayed as 100%, but the
  image is visibly blurry from being slightly zoomed out. There are a
  few pixels of black bar on the right and left edges of the image.
  Expanding the window vertically lets the image display at 1:1 zoom.

  This occurs with images that should be small enough to be displayed at
  100% zoom. For example: a 960x540 image on a 1920x1080 display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eog 3.10.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 23 18:06:29 2014
  InstallationDate: Installed on 2014-02-16 (35 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%

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

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

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

Title:
  Initial zoom level is slightly under 100%

Status in Eye of GNOME:
  New
Status in “eog” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  When opening an image, the zoom level is displayed as 100%, but the
  image is visibly blurry from being slightly zoomed out. There are a
  few pixels of black bar on the right and left edges of the image.
  Expanding the window vertically lets the image display at 1:1 zoom.

  This occurs with images that should be small enough to be displayed at
  100% zoom. For example: a 960x540 image on a 1920x1080 display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eog 3.10.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 23 18:06:29 2014
  InstallationDate: Installed on 2014-02-16 (35 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%

2014-10-11 Thread Nobuto MURATA
** Package changed: light-themes (Ubuntu) = ubuntu-themes (Ubuntu)

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

Title:
  Initial zoom level is slightly under 100%

Status in Eye of GNOME:
  New
Status in “eog” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  When opening an image, the zoom level is displayed as 100%, but the
  image is visibly blurry from being slightly zoomed out. There are a
  few pixels of black bar on the right and left edges of the image.
  Expanding the window vertically lets the image display at 1:1 zoom.

  This occurs with images that should be small enough to be displayed at
  100% zoom. For example: a 960x540 image on a 1920x1080 display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eog 3.10.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 23 18:06:29 2014
  InstallationDate: Installed on 2014-02-16 (35 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 874283]

2014-10-11 Thread Vincent Fortier
Issue still present using Ubuntu 14.04.  While this may be related to a
wrong behaviour from the server side it works flawlessly using pidgin.

Related launchpad bug: https://bugs.launchpad.net/ubuntu/+source
/telepathy-gabble/+bug/874283

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

Title:
  Empathy IM Client does not connect to Zimbra via XMPP

Status in Jabber/XMPP connection manager:
  Incomplete
Status in “telepathy-gabble” package in Ubuntu:
  Triaged

Bug description:
  This is the error from the debug log:

  on_connection_ready: got error:
  WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error:
  -12: GNUTLS_E_FATAL_ALERT_RECEIVED

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 14 16:31:45 2011
  ExecutablePath: /usr/bin/empathy
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:cs_CZ:cs:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions

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


[Desktop-packages] [Bug 874283]

2014-10-11 Thread Vincent Fortier
And may be related or duplicate of this as well:
https://bugs.freedesktop.org/show_bug.cgi?id=39931

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

Title:
  Empathy IM Client does not connect to Zimbra via XMPP

Status in Jabber/XMPP connection manager:
  Incomplete
Status in “telepathy-gabble” package in Ubuntu:
  Triaged

Bug description:
  This is the error from the debug log:

  on_connection_ready: got error:
  WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error:
  -12: GNUTLS_E_FATAL_ALERT_RECEIVED

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 14 16:31:45 2011
  ExecutablePath: /usr/bin/empathy
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:cs_CZ:cs:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions

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


[Desktop-packages] [Bug 727041] Re: unity-window-decorator crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Christopher
It seems to have resurfaced in 14.10. Mine crashes on boot, then
restores itself.

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

Title:
  unity-window-decorator crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: compiz

  I was scanning my music library in Banshee. There was a problem with
  the scanning and Banshee hanged. The crash happened when I forced a
  close of Banshee.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: compiz-gnome 1:0.9.4-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 09:57:12 2011
  ExecutablePath: /usr/bin/unity-window-decorator
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110228.1)
  ProcCmdline: /usr/bin/unity-window-decorator
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x415c70:  mov0x310(%rax),%rdi
   PC (0x00415c70) ok
   source 0x310(%rax) (0x0310) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/libgobject-2.0.so.0
  Title: unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (nautilus:5119): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed
   (unknown:5117): dee-WARNING **: Transaction from 
com.canonical.Unity.ApplicationsPlace.SectionsModel is in the past. Ignoring 
transaction.
   (unknown:5117): dee-WARNING **: Transaction from 
com.canonical.Unity.ApplicationsPlace.GroupsModel is in the past. Ignoring 
transaction.

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

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


[Desktop-packages] [Bug 1380051] [NEW] characters in svg images wiggle

2014-10-11 Thread Andreas E.
Public bug reported:

When zooming an SVG image that contains texts, the positions of
characters wiggle. The characters move sidewards closer together or
farer away, as if the kerning would be different at every zoom level.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: eog 3.10.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 11 12:51:15 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-02 (250 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: video showing the issue
   
https://bugs.launchpad.net/bugs/1380051/+attachment/4231424/+files/eog-svg-text.mp4

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

Title:
  characters in svg images wiggle

Status in “eog” package in Ubuntu:
  New

Bug description:
  When zooming an SVG image that contains texts, the positions of
  characters wiggle. The characters move sidewards closer together or
  farer away, as if the kerning would be different at every zoom level.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eog 3.10.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 12:51:15 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (250 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1380050] [NEW] Ubuntu boots to a black screen

2014-10-11 Thread Paolo
Public bug reported:

Ubuntu boots to a black screen. I can hear the opening chimes, but I
cannot see anything until I switch my screen off and on again. Then I
can see the login screen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Oct 11 12:49:21 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041]
InstallationDate: Installed on 2014-09-26 (14 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: HP-Pavilion KA869AA-ABZ a6335.it
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.13
dmi.board.name: NARRA2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnKA869AA-ABZa6335.it:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: KA869AA-ABZ a6335.it
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Oct 11 12:48:11 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMLK Trust Keyboard 14909 KEYBOARD, id 8
 inputMLK Trust Keyboard 14909 KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: radeon

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


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

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

Title:
  Ubuntu boots to a black screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Ubuntu boots to a black screen. I can hear the opening chimes, but I
  cannot see anything until I switch my screen off and on again. Then I
  can see the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 11 12:49:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] 
[1002:94c3] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041]
  InstallationDate: Installed on 2014-09-26 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: HP-Pavilion KA869AA-ABZ a6335.it
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.13
  dmi.board.name: NARRA2
  dmi.board.vendor: 

[Desktop-packages] [Bug 874283] Re: Empathy IM Client does not connect to Zimbra via XMPP

2014-10-11 Thread Bug Watch Updater
** Bug watch added: freedesktop.org Bugzilla #39931
   https://bugs.freedesktop.org/show_bug.cgi?id=39931

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

Title:
  Empathy IM Client does not connect to Zimbra via XMPP

Status in Jabber/XMPP connection manager:
  Incomplete
Status in “telepathy-gabble” package in Ubuntu:
  Triaged

Bug description:
  This is the error from the debug log:

  on_connection_ready: got error:
  WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error:
  -12: GNUTLS_E_FATAL_ALERT_RECEIVED

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 14 16:31:45 2011
  ExecutablePath: /usr/bin/empathy
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:cs_CZ:cs:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions

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


[Desktop-packages] [Bug 859560] Re: Gedit line number margin doesn't scale with font size

2014-10-11 Thread Joseph Mansigian
I can confirm the Gedit line number does not scale with font size
problem reported by Paul Duke.  This is a serious issue that forces me
to keep a magnifying glass by my machine when I work.   There has been
insensitivity to this problem.

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

Title:
  Gedit line number margin doesn't scale with font size

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

Bug description:
  Machine: 64bit Ubuntu Ocelot with all updates applied as of
  26/09/2011.

  The width of the Gedit line number margin (enabled in preferences)
  doesn't scale with the font size. I am visually impaired and thus have
  my gedit font size set to 16. However when I do this and press enter a
  few times (so I have more than 9 lines in a file) the margin isn't
  expanded to fit the new two digit number. When we have more than 99
  lines (three digits), the margin scales correctly once more.

  This happens on a new setup with fresh configuration files.

  Steps to reproduce:
  1). Open gedit
  2). Change font size to 16 (probably also has issues at other sizes too).
  3). Make more than 9 lines in the file.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] package nvidia-prime 0.6.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

2014-10-11 Thread Jamie Lawler
Public bug reported:

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)

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

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 1380053] Re: package nvidia-prime 0.6.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

2014-10-11 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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:
  New

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 1380054] [NEW] On mako, when you have a big circle about activity in a day, it's show in the pin unlock screen

2014-10-11 Thread Riccardo Padovani
Public bug reported:

I'm running rtm 04 on mako.

When I have a big circle on a day on the right of the screen (first
screenshot) and I swype to the left to unlock the screen, part of the
circle is shown in the screen  (second screenshot)

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: 1.png
   https://bugs.launchpad.net/bugs/1380054/+attachment/4231435/+files/1.png

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

Title:
  On mako, when you have a big circle about activity in a day, it's show
  in the pin unlock screen

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  I'm running rtm 04 on mako.

  When I have a big circle on a day on the right of the screen (first
  screenshot) and I swype to the left to unlock the screen, part of the
  circle is shown in the screen  (second screenshot)

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

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


[Desktop-packages] [Bug 1380054] Re: On mako, when you have a big circle about activity in a day, it's show in the pin unlock screen

2014-10-11 Thread Riccardo Padovani
** Attachment added: 2.png
   
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1380054/+attachment/4231436/+files/2.png

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

Title:
  On mako, when you have a big circle about activity in a day, it's show
  in the pin unlock screen

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  I'm running rtm 04 on mako.

  When I have a big circle on a day on the right of the screen (first
  screenshot) and I swype to the left to unlock the screen, part of the
  circle is shown in the screen  (second screenshot)

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

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


[Desktop-packages] [Bug 1380057] [NEW] dual buoting Ubuntu 7.04 and Ubuntu 14, 04

2014-10-11 Thread Ljubomir
Public bug reported:

http://paste.ubuntu.com/8538362?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Oct 11 11:22:03 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
   Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
MachineType: ASUSTeK Computer INC. 900HA
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 900HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd07/06/2009:svnASUSTeKComputerINC.:pn900HA:pvrx.x:rvnASUSTeKComputerINC.:rn900HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 900HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
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.1
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 Oct 11 11:13:11 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 805 
 vendor HSD
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  dual buoting Ubuntu 7.04 and Ubuntu 14,04

Status in “xorg” package in Ubuntu:
  New

Bug description:
  http://paste.ubuntu.com/8538362?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 11 11:22:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
  LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
  MachineType: ASUSTeK Computer INC. 900HA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 900HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 

[Desktop-packages] [Bug 727041] Re: unity-window-decorator crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Stephen M. Webb
It's highly unlikely you're seeing a three-year-old bug resurface in a
component that has not been shipped for at least two years.

It's more likely you're seeing bug #1366351.

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

Title:
  unity-window-decorator crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: compiz

  I was scanning my music library in Banshee. There was a problem with
  the scanning and Banshee hanged. The crash happened when I forced a
  close of Banshee.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: compiz-gnome 1:0.9.4-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 09:57:12 2011
  ExecutablePath: /usr/bin/unity-window-decorator
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110228.1)
  ProcCmdline: /usr/bin/unity-window-decorator
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x415c70:  mov0x310(%rax),%rdi
   PC (0x00415c70) ok
   source 0x310(%rax) (0x0310) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/libgobject-2.0.so.0
  Title: unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (nautilus:5119): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed
   (unknown:5117): dee-WARNING **: Transaction from 
com.canonical.Unity.ApplicationsPlace.SectionsModel is in the past. Ignoring 
transaction.
   (unknown:5117): dee-WARNING **: Transaction from 
com.canonical.Unity.ApplicationsPlace.GroupsModel is in the past. Ignoring 
transaction.

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

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


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

2014-10-11 Thread Danieljf1983
Public bug reported:

Crash on boot

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 07:38:25 2014
InstallationDate: Installed on 2014-10-10 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
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)

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


** Tags: amd64 apport-package 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/1380059

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

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

Bug description:
  Crash on boot

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 07:38:25 2014
  InstallationDate: Installed on 2014-10-10 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  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/1380059/+subscriptions

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


[Desktop-packages] [Bug 1380060] [NEW] nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

2014-10-11 Thread Bill Turner, wb4alm
Public bug reported:

failed again, again.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.38-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
DKMSKernelVersion: 3.13.0-37-generic
Date: Sat Oct 11 07:30:33 2014
InstallationDate: Installed on 2014-05-11 (153 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageVersion: 331.38-0ubuntu7.1
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.38-0ubuntu7.1: 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 trusty

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

Title:
  nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

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

Bug description:
  failed again, again.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-37-generic
  Date: Sat Oct 11 07:30:33 2014
  InstallationDate: Installed on 2014-05-11 (153 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.38-0ubuntu7.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.38-0ubuntu7.1: 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/1380060/+subscriptions

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


[Desktop-packages] [Bug 1380060] Re: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

2014-10-11 Thread Bill Turner, wb4alm
Why not re-release the 331 driver with the bug fixed?

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

Title:
  nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

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

Bug description:
  failed again, again.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-37-generic
  Date: Sat Oct 11 07:30:33 2014
  InstallationDate: Installed on 2014-05-11 (153 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageVersion: 331.38-0ubuntu7.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.38-0ubuntu7.1: 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/1380060/+subscriptions

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


[Desktop-packages] [Bug 1380061] [NEW] Firefox doesn't respect transition in minified .css

2014-10-11 Thread Sławomir Domagała
Public bug reported:

An example css file is in attachments. There are transition rules. 
I've checked this css in Chrome. Transitions are respected, in firefox not. 
Non-minified file doesn't cause problems.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 32.0.3+build1-0ubuntu0.14.04.1
Uname: Linux 3.13.5-031305-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  slawomir   2863 F pulseaudio
 /dev/snd/controlC1:  slawomir   2863 F pulseaudio
BuildID: 20140924083558
Channel: Unavailable
CurrentDesktop: Unity
Date: Sat Oct 11 13:04:46 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions:
 Global Menu Bar integration - globalm...@ubuntu.com
 Polski Language Pack - langpack...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2014-03-03 (221 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
IpRoute:
 default via 192.168.25.1 dev wlan0  proto static 
 192.168.25.0/24 dev wlan0  proto kernel  scope link  src 192.168.25.126  
metric 9
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=32.0.3/20140924083558 (In use)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RelatedPackageVersions:
 google-talkplugin 5.4.2.0-1
 rhythmbox-mozilla 3.0.2-0ubuntu2
 icedtea-6-plugin  1.5-1ubuntu1
 totem-mozilla 3.10.1-1ubuntu4
 adobe-flashplugin 11.2.202.261-0precise1
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to trusty on 2014-03-04 (220 days ago)
dmi.bios.date: 11/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 00385M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/06/2013:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn00385M:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Vostro 5470
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

** Attachment added: all.css
   https://bugs.launchpad.net/bugs/1380061/+attachment/4231462/+files/all.css

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

Title:
  Firefox doesn't respect transition in minified .css

Status in “firefox” package in Ubuntu:
  New

Bug description:
  An example css file is in attachments. There are transition rules. 
  I've checked this css in Chrome. Transitions are respected, in firefox not. 
Non-minified file doesn't cause problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 32.0.3+build1-0ubuntu0.14.04.1
  Uname: Linux 3.13.5-031305-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slawomir   2863 F pulseaudio
   /dev/snd/controlC1:  slawomir   2863 F pulseaudio
  BuildID: 20140924083558
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat Oct 11 13:04:46 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Global Menu Bar integration - globalm...@ubuntu.com
   Polski Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-03-03 (221 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  IpRoute:
   default via 192.168.25.1 dev wlan0  proto static 
   192.168.25.0/24 dev wlan0  proto kernel  scope link  src 192.168.25.126  
metric 9
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=32.0.3/20140924083558 (In use)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   google-talkplugin 5.4.2.0-1
   rhythmbox-mozilla 3.0.2-0ubuntu2
   icedtea-6-plugin  1.5-1ubuntu1
  

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

2014-10-11 Thread Eddy Beaupré
Public bug reported:

I don't have much to add, i didn't saw any error while installing but
this error popped up after a few reboots.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Fri Oct 10 19:40:03 2014
InstallationDate: Installed on 2014-10-09 (1 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141009)
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)

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


** Tags: amd64 apport-package 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/1380065

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

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

Bug description:
  I don't have much to add, i didn't saw any error while installing but
  this error popped up after a few reboots.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Fri Oct 10 19:40:03 2014
  InstallationDate: Installed on 2014-10-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141009)
  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/1380065/+subscriptions

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


[Desktop-packages] [Bug 1380021] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1366351 ***
https://bugs.launchpad.net/bugs/1366351

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231291/+files/CoreDump.gz

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231305/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231307/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231308/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231309/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380021/+attachment/4231310/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1366351
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  by start up

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu5
  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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Oct 11 09:38:34 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: 2014-09-27 18:03:09,095 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1642]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1642]
  InstallationDate: Installed on 2014-09-10 (30 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: ASUSTeK Computer Inc. N53SV
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=nl_NL
   XDG_RUNTIME_DIR=set
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic 
root=UUID=4448cf3f-e041-4b11-b2bb-fabc4d116307 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-27 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N53SV.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N53SV
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN53SV.215:bd01/09/2012:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N53SV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 

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

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1378627 ***
https://bugs.launchpad.net/bugs/1378627

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231350/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231352/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231355/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231356/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231357/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231360/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380033/+attachment/4231361/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1378627
   chromium-browser crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGSEGV

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

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Oct 11 10:40:26 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (292 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=12037.0.568132389\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7ff73cb3b63f:mov0x1f8(%rax),%r15
   PC (0x7ff73cb3b63f) ok
   source 0x1f8(%rax) (0x01f8) not located in a known VMA region (needed 
readable region)!
   destination %r15 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/chromium-browser/libs/libgpu.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577

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

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


[Desktop-packages] [Bug 1379961] Re: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1370955 ***
https://bugs.launchpad.net/bugs/1370955

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231119/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231121/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231123/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231124/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231125/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231126/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1379961/+attachment/4231127/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1370955

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()

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

Bug description:
  Desconozco

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: evolution-data-server 3.12.6-0ubuntu4
  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
  CurrentDesktop: GNOME
  Date: Fri Oct 10 18:51:55 2014
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2014-10-06 (4 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141005)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libedata-cal-1.2.so.23
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libedata-cal-1.2.so.23
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 1001902] [NEW] xdg-open is not mate compatible

2014-10-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
replace /gnome/mate/. Some applications like chrome/chromium open their
file using xdg-open.

Linux Mint 13 RC mate edition

** Affects: linuxmint
 Importance: Undecided
 Status: New

** Affects: ubuntu-mate
 Importance: Undecided
 Status: Confirmed

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: patch
-- 
xdg-open is not mate compatible
https://bugs.launchpad.net/bugs/1001902
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xdg-utils in Ubuntu.

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


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

2014-10-11 Thread jerrylamos
BTW, same or similar bug occurs on Google Chrome which is not a Ubuntu
program hence un-reportable on launchpad.

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

Title:
  chromium-browser crashed with SIGSEGV

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

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Oct  8 07:12:48 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3043.0.199670400\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7fc0e6b1963f:mov0x1f8(%rax),%r15
   PC (0x7fc0e6b1963f) ok
   source 0x1f8(%rax) (0x01f8) not located in a known VMA region (needed 
readable region)!
   destination %r15 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/chromium-browser/libs/libgpu.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577

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

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


[Desktop-packages] [Bug 1001902] Re: xdg-open is not mate compatible

2014-10-11 Thread bedfojo
** Package changed: ubuntu = xdg-utils (Ubuntu)

** Bug watch added: Debian Bug tracker #754219
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219

** Also affects: xdg-utils via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219
   Importance: Unknown
   Status: Unknown

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Confirmed
Status in Xdg-utils:
  Unknown
Status in “xdg-utils” package in Ubuntu:
  Confirmed

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

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

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


[Desktop-packages] [Bug 1308105]

2014-10-11 Thread Alexander Schmidt
Created attachment 5681
HDMI power cycling patch

Created and attached a small patch that fixes the issue for me. It
applies to any xfce4-settings version starting from
dbd76eb58bd9d7a55de753daa5572ef24867d924 (contained in 4.11.1), up to
the current origin/master.

Can anybody confirm this patch fixing the issue while not introducing
undesirable side effects?

As I understand, it is indeed a suitable solution (cf. the
implementation in 641c6c4d7dda4ac41f811c8c0f9e26738f12a732 which used a
corresponding approach) but it might conceal another underlying problem:

g_ptr_array_unref(GPtrArray*) is expected to have the same effect as
g_ptr_array_free(GPtrArray*, TRUE) in case there is exactly one
reference to the given argument. However, in the case at hand, the
effects differ, which leads to the conclusion that there is more that
just one reference left to the given argument, prior to calling
g_ptr_array_unref. This could indicate some bug/leak -- but as I
understand, calling g_ptr_array_free with free_seg=TRUE deals with that
(somebody correct me if I'm wrong).

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Invalid
Status in “xfce4-settings” package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode NULL

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello supe...@ubuntu.com

  OUTPUT=HDMI-0
  BAD_MODE=1280x720
  GOOD_MODE=1920x1080

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

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

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


[Desktop-packages] [Bug 1379531] Re: Combine sides should be combine pages?

2014-10-11 Thread Akerbeltz
Try this direct link to the Gaelic localization pages
https://translations.launchpad.net/ubuntu/utopic/+source/simple-scan/+pots/simple-scan/gd/+translate?show=untranslated

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

Title:
  Combine sides should be combine pages?

Status in Ubuntu Translations:
  Invalid
Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  Combine sides
  and
  Combine sides (reverse)

  look like a German speaker with poor English mistranslated 'Seiten' as
  'sides' rather than 'pages'?

   Located in ../src/ui.vala:1204 
   Located in ../src/ui.vala:1214

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

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


[Desktop-packages] [Bug 1380072] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1366351 ***
https://bugs.launchpad.net/bugs/1366351

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231506/+files/CoreDump.gz

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231521/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231523/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231524/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231525/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380072/+attachment/4231526/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1366351
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  driver: fglrx
  version: 2:14.201-0ubuntu1
  graphic card: R260X

  Compiz crashed just after logging-in.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct 11 14:37:12 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 14.201, 3.16.0-22-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-20-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-21-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-22-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X] 
[1002:6658] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:2274]
  InstallationDate: Installed on 2014-07-01 (101 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=debd7fa5-7267-4c5e-824e-f5c21e3340c2 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  

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

2014-10-11 Thread henry adler
Public bug reported:

Running Software Updater

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
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 08:08:35 2014
InstallationDate: Installed on 2012-04-02 (921 days ago)
InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
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)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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


** Tags: amd64 apport-package 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/1380077

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

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

Bug description:
  Running Software Updater

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 08:08:35 2014
  InstallationDate: Installed on 2012-04-02 (921 days ago)
  InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 
(20120328)
  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)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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


[Desktop-packages] [Bug 1380075] Re: Brasero won't accept FLAC files for audio disc project

2014-10-11 Thread Elbarbudo
Brasero .log

** Attachment added: brasero-session.log
   
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1380075/+attachment/4231541/+files/brasero-session.log

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

Title:
  Brasero won't accept FLAC files for audio disc project

Status in “brasero” package in Ubuntu:
  New

Bug description:
  Slightly different behaviour :

  Steps to reproduce:
1) Launch 'brasero'
2) Create a new audio project
3) Drag a FLAC file into the project from nautilus
4) Try to create a disk image : ends with  Impossible de lier les 
interfaces des greffons

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: brasero 3.10.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 14:56:31 2014
  InstallationDate: Installed on 2014-05-24 (139 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1380075] [NEW] Brasero won't accept FLAC files for audio disc project

2014-10-11 Thread Elbarbudo
Public bug reported:

Slightly different behaviour :

Steps to reproduce:
  1) Launch 'brasero'
  2) Create a new audio project
  3) Drag a FLAC file into the project from nautilus
  4) Try to create a disk image : ends with  Impossible de lier les interfaces 
des greffons

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: brasero 3.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 11 14:56:31 2014
InstallationDate: Installed on 2014-05-24 (139 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Brasero won't accept FLAC files for audio disc project

Status in “brasero” package in Ubuntu:
  New

Bug description:
  Slightly different behaviour :

  Steps to reproduce:
1) Launch 'brasero'
2) Create a new audio project
3) Drag a FLAC file into the project from nautilus
4) Try to create a disk image : ends with  Impossible de lier les 
interfaces des greffons

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: brasero 3.10.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 14:56:31 2014
  InstallationDate: Installed on 2014-05-24 (139 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with chromium

2014-10-11 Thread Ekimia
Hi mateo,  I've been to the same point as you and compared working
chrome and chromium.

Chrome works when disabling nativeclient , so we are sure that the
plugin is rellay ppapi and does not use native client.

When you disable the Widevineadapatater plugin in chrome you get a
M7357-1003 and chromium return the M7354 error which is kind of weird
then 

we need help from the chromium team 

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

Title:
  Unable to use the widevine plugin with chromium

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

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  it seems widevine support is only activated when branding=chrome

  as seen in

  
  
https://github.com/scheib/chromium/blob/master/third_party/widevine/cdm/widevine_cdm.gyp

  Widevine support would enable EME playing such as Netflix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1380093] [NEW] autologin prevents the lock from working

2014-10-11 Thread Shiu Fun
Public bug reported:

After upgrade to 14.04, I notice I can no longer lock my screen.  After
more debugging, it was due to the fact that I have autologin enabled.

Autologin is needed, so when my machine starts up due to whatever
reason.  But I would like to be able to lock the screen, and thus
require a password to unlock (per configuration) if needed (or when it
goes idle).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu10.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 11 09:49:21 2014
InstallationDate: Installed on 2013-08-29 (407 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
SourcePackage: evince
UpgradeStatus: Upgraded to trusty on 2014-09-23 (17 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  autologin prevents the lock from working

Status in “evince” package in Ubuntu:
  New

Bug description:
  After upgrade to 14.04, I notice I can no longer lock my screen.
  After more debugging, it was due to the fact that I have autologin
  enabled.

  Autologin is needed, so when my machine starts up due to whatever
  reason.  But I would like to be able to lock the screen, and thus
  require a password to unlock (per configuration) if needed (or when it
  goes idle).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 09:49:21 2014
  InstallationDate: Installed on 2013-08-29 (407 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-23 (17 days ago)

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

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


[Desktop-packages] [Bug 1380087] Re: gnome-system-monitor crashed with signal 5 in _XReply()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1275322 ***
https://bugs.launchpad.net/bugs/1275322

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231568/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231570/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231571/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231572/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231573/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231574/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380087/+attachment/4231575/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1275322

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-system-monitor crashed with signal 5 in _XReply()

Status in “gnome-system-monitor” package in Ubuntu:
  New

Bug description:
  It hppend while debigung a wifi issue.
  intel 7260 dropes wifi if bluetooth is enable and used.
  And wifi is the only network, so monitor has only wifi to display for 
networking.
  The crash could  be related to restarting (modprobe) ths wifi drivers... ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-system-monitor 3.8.2.1-2ubuntu4
  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
  CurrentDesktop: GNOME
  Date: Sat Oct 11 15:37:15 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2014-07-08 (94 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-system-monitor crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to utopic on 2014-10-04 (6 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo wireshark

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

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


[Desktop-packages] [Bug 1380092] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1366351 ***
https://bugs.launchpad.net/bugs/1366351

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231578/+files/CoreDump.gz

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231592/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231594/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231595/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231596/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380092/+attachment/4231597/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1366351
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I just switched to another user without logout.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu5
  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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Oct 11 15:49:23 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: 2014-09-30 21:52:24,663 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.14, 3.16.0-21-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-22-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Installed on 2013-10-10 (365 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUS All Series
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=59777031-18fb-48a0-8496-f8631f11e961 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-30 (10 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd12/05/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  

[Desktop-packages] [Bug 1380095] [NEW] Gnome Fallback[s] don't work in 14.04. Work once ONLY if reinstalled

2014-10-11 Thread Peter-and-Crazybear
Public bug reported:

While the computer is saying its a problem with gnome-panel, I keep re-
installing gnome-session-fallback. It will work [in either flavor of
fallback (no idea why there are now two!) ONE TIME - but the next time I
get a screen with NO panels and NO keyboard shortcuts are recognized (so
I can't even get a terminal). All I can do is hard shut-down of
computer; restart into gnome or unity or some others (which I do NOT
like to use!). I have done this MANY times now. It never stays 'done'.
Am going back to my  copy ov 12.04 until someone can tell me why or how
to make one of the fallbacks (hopefully both) work every time I sign in
to 14.04. Thank you. Anyone else having similar problems? The only other
thing I can think of is that I upgraded from 12.04 in which fallback
operated just fine and was stable.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-session-fallback 1:3.8.0-1ubuntu12.1
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 11 15:50:02 2014
GsettingsChanges:
 b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true'
 b'org.gnome.gnome-panel.run-dialog' b'history' b'[\'gksu gedit 
/etc/apt/sources.list\', OED.EXE 
\'/home/peter-and-crazybear/Wine/(OED)/Bin/oedcd_v3.exe\', \'warrick/\', 
\'warrick.pl\', \'warrick/\', \'skype\', \'env PULSE_LATENCY_MSEC=60 skype \', 
\'/usr/bin/xsensors\', \'alacarte\', \'gconf-editor\', \'nautilus -q\', 
\'xkill\', \'warrick/\']'
InstallationDate: Installed on 2013-12-02 (312 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
PackageArchitecture: all
SourcePackage: gnome-panel
UpgradeStatus: Upgraded to trusty on 2014-09-28 (13 days ago)

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


** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty

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

Title:
  Gnome Fallback[s] don't work in 14.04. Work once ONLY if reinstalled

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

Bug description:
  While the computer is saying its a problem with gnome-panel, I keep
  re-installing gnome-session-fallback. It will work [in either flavor
  of fallback (no idea why there are now two!) ONE TIME - but the next
  time I get a screen with NO panels and NO keyboard shortcuts are
  recognized (so I can't even get a terminal). All I can do is hard
  shut-down of computer; restart into gnome or unity or some others
  (which I do NOT like to use!). I have done this MANY times now. It
  never stays 'done'. Am going back to my  copy ov 12.04 until someone
  can tell me why or how to make one of the fallbacks (hopefully both)
  work every time I sign in to 14.04. Thank you. Anyone else having
  similar problems? The only other thing I can think of is that I
  upgraded from 12.04 in which fallback operated just fine and was
  stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-fallback 1:3.8.0-1ubuntu12.1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 15:50:02 2014
  GsettingsChanges:
   b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true'
   b'org.gnome.gnome-panel.run-dialog' b'history' b'[\'gksu gedit 
/etc/apt/sources.list\', OED.EXE 
\'/home/peter-and-crazybear/Wine/(OED)/Bin/oedcd_v3.exe\', \'warrick/\', 
\'warrick.pl\', \'warrick/\', \'skype\', \'env PULSE_LATENCY_MSEC=60 skype \', 
\'/usr/bin/xsensors\', \'alacarte\', \'gconf-editor\', \'nautilus -q\', 
\'xkill\', \'warrick/\']'
  InstallationDate: Installed on 2013-12-02 (312 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to trusty on 2014-09-28 (13 days ago)

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

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


[Desktop-packages] [Bug 1001902] Re: xdg-open is not mate compatible

2014-10-11 Thread Bug Watch Updater
** Changed in: xdg-utils
   Status: Unknown = New

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Confirmed
Status in Xdg-utils:
  New
Status in “xdg-utils” package in Ubuntu:
  Confirmed

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

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

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


[Desktop-packages] [Bug 1300821] Re: compiz crashed with SIGSEGV in CompWindow::move()

2014-10-11 Thread Dimitry
May be it will help:
Happened with me both on 14.04 and 14.10
What's most interesting, it seems crash taking place only with nvidia graphics 
- I've used nvidia card for a year while suffering crash couple times a week, 
then assemble new computer with Intel graphics and the same OS (14.04, fresh 
install) and can't recall that bug occur. Recently I've bought Nvidia video 
card to that PC, updated to 14.10 (fresh install) and last week I have already 
2 crashes.

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

Title:
  compiz crashed with SIGSEGV in CompWindow::move()

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  I was attempting to move Files from one workspace to another while a
  lot of file IO was occurring (was firing up a VM with vagrant). I
  could not release Files and keep it on the second workspace, it kept
  attempting to move with my mouse and eventually compiz crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Apr  1 17:12:45 2014
  DistUpgraded: 2014-03-04 03:38:53,219 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1860]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 7690M [103c:1860]
  InstallationDate: Installed on 2014-03-01 (30 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=a3e6c361-4b43-43b0-b258-f50c42041898 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fb11ed0d8f7 _ZN10CompWindow4moveEiib+71:  mov
%cl,0x3f0(%rax)
   PC (0x7fb11ed0d8f7) ok
   source %cl ok
   destination 0x3f0(%rax) (0x7fb11cd47900) in non-writable VMA region: 
0x7fb11cccd000-0x7fb11cdd3000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0
  SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   CompWindow::move(int, int, bool) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
   ExpoScreen::donePaint() () from /usr/lib/compiz/libexpo.so
   CompositeScreen::donePaint() () from /usr/lib/compiz/libcomposite.so
   CompositeScreen::donePaint() () from /usr/lib/compiz/libcomposite.so
   CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so
  Title: compiz crashed with SIGSEGV in CompWindow::move()
  UpgradeStatus: Upgraded to trusty on 2014-03-04 (28 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1807
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.58
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/24/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr06902120471620100:rvnHewlett-Packard:rn1807:rvr33.58:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 06902120471620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140328-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.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: Tue Apr  1 16:25:32 2014
  

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

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

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: New = Confirmed

-- 
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 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 1301083] Re: Drag and Drop File Auto Opens Folders

2014-10-11 Thread Teo
How can this even be importance low? Doesn't anybody realize the huge
SECURITY RISK this bug involves?

You drag a file onto a folder, for just a fraction of a second more than
the time it takes for the folder to auto-open. Then you drop it, but
when you do, the folder has just opened and you have accidentally
dropped the file onto a subfolder within the folder. Unless you double
check, you may not realize where you have moved the file and you may
loose it forever. You may have moved it (without realizing) into a
subfolder that you will later delete, without knowing it contains a file
that you never intended to move into it.

This is DISASTROUS.

We already know that Nautilus development has degenerated into complete
dementia, and that until it gets repleced with something else in Ubuntu,
it constantly needs patching to revert regressions like this one (which
are made on purpose, because of demential design). But an issue like
this should be considered high importance, if not critical, as it can
lead to DATA LOSS.

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

Title:
  Drag and Drop File Auto Opens Folders

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  When dragging and dropping a file, if the mouse hovers over a folder
  for a split second, the folder opens.

  This behaviour is quite jarring.  Whether or not you intended to drop
  into that folder, you may not have intended to open that folder.

  The hover time can't be set.  And the behaviour can't be disabled.

  It's a very significant usability issue for Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr  1 20:21:16 2014
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'1144x859+1331+77'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'140'
  InstallationDate: Installed on 2014-03-18 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=set
   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/1301083/+subscriptions

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


[Desktop-packages] [Bug 1380095] Re: Gnome Fallback[s] don't work in 14.04. Work once ONLY if reinstalled

2014-10-11 Thread Alberts Muktupāvels
1. gnome-session-fallback is build from gnome-panel source code that is why 
your computer is saying problem is with gnome-panel.
2. reinstalling gnome-session-fallback should not solve anything. It is 
transitional package and does not contain anyting. Problem is somewhere else. 
This package can be removed.
3. GNOME Fallback is now called GNOME Flashback.

Have you tried to re-select session from login screen? GNOME Flashback
(Metacity) and/or GNOME Flashback (Compiz). Maybe there is some problems
upgrading from 12.04 to 14.04.

Are you using extra ppa? In tags there is gnome3-ppa. Not sure, but this
might cause problems if there is installed newer GNOME components.

Can you right click on desktop?  Is nautilus autostarted or you are
getting completly empty screen.

Can you attach extra log file? I would like to see ~/.cache/upstart
/gnome-session-Unity.log. After you fail to login, restart PC and then
login in GNOME session (not in Unity), then attach asked file. Yes, I
need gnome-session-Unity.log, don't ask why.

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

Title:
  Gnome Fallback[s] don't work in 14.04. Work once ONLY if reinstalled

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

Bug description:
  While the computer is saying its a problem with gnome-panel, I keep
  re-installing gnome-session-fallback. It will work [in either flavor
  of fallback (no idea why there are now two!) ONE TIME - but the next
  time I get a screen with NO panels and NO keyboard shortcuts are
  recognized (so I can't even get a terminal). All I can do is hard
  shut-down of computer; restart into gnome or unity or some others
  (which I do NOT like to use!). I have done this MANY times now. It
  never stays 'done'. Am going back to my  copy ov 12.04 until someone
  can tell me why or how to make one of the fallbacks (hopefully both)
  work every time I sign in to 14.04. Thank you. Anyone else having
  similar problems? The only other thing I can think of is that I
  upgraded from 12.04 in which fallback operated just fine and was
  stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-fallback 1:3.8.0-1ubuntu12.1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 11 15:50:02 2014
  GsettingsChanges:
   b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true'
   b'org.gnome.gnome-panel.run-dialog' b'history' b'[\'gksu gedit 
/etc/apt/sources.list\', OED.EXE 
\'/home/peter-and-crazybear/Wine/(OED)/Bin/oedcd_v3.exe\', \'warrick/\', 
\'warrick.pl\', \'warrick/\', \'skype\', \'env PULSE_LATENCY_MSEC=60 skype \', 
\'/usr/bin/xsensors\', \'alacarte\', \'gconf-editor\', \'nautilus -q\', 
\'xkill\', \'warrick/\']'
  InstallationDate: Installed on 2013-12-02 (312 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to trusty on 2014-09-28 (13 days ago)

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

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


[Desktop-packages] [Bug 1379728] Re: gnome-keyring crashes in using GNOME-Shell 3.14

2014-10-11 Thread Fran Diéguez
Fixed

Thanks for the quick response and your work!

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

Title:
  gnome-keyring crashes in using GNOME-Shell 3.14

Status in “gnome-keyring” package in Ubuntu:
  New

Bug description:
  While using gnome3-staging ppa in U-G 14.10 gnome-keyring crashes
  echoing this message:

  WARNING: gnome-keyring:: couldn't connect to: 
/run/user/1000/keyring-oCHwf5/pkcs11: Connection refused
  p11-kit: skipping module 'gnome-keyring' whose initialization failed: An 
error occurred on the device

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-keyring 3.10.1-1ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 10 11:54:33 2014
  InstallationDate: Installed on 2014-09-19 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140917)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2014-10-11 Thread Fran Diéguez
Fixed with latest updates in gnome3-staging

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

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

Status in Ubuntu GNOME:
  New
Status in “deja-dup” package in Ubuntu:
  New

Bug description:
  g-c-c 3.14 crashes when loading the Backup panel

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-control-center 1:3.14.0-1ubuntu1~utopic1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Oct  9 19:30:35 2014
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2014-09-19 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140917)
  ProcCmdline: /usr/bin/gnome-control-center.real --overview
  SegvAnalysis:
   Segfault happened at: 0x7faac2be3743 gtk_lock_button_set_permission+99:
cmp%rax,(%rdx)
   PC (0x7faac2be3743) ok
   source %rax ok
   destination (%rdx) (0x6a65643a706c6568) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_lock_button_set_permission () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in 
gtk_lock_button_set_permission()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu1

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

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


[Desktop-packages] [Bug 986412] Re: Need to add support for PDF Portfolios

2014-10-11 Thread Paul Ortyl
Reading protfolio as a bunch of attachments is only a workaround. The UI
should be able to show these subpdfs as a single continuous one.

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

Title:
  Need to add support for PDF Portfolios

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  I recently ran into something I haven't seen before when someone sent
  me a PDF Portfolio
  (http://help.adobe.com/en_US/Acrobat/9.0/Standard/WSA2872EA8-9756
  -4a8c-9F20-8E93D59D91CE.html). Evince doesn't know what to do with the
  file and seems to open it incorrectly. I just get an onscreen message
  to install Adobe Acrobat 9 (attached image).

  Looks like Ocular is on the way to a solution:
  http://www.linuxquestions.org/questions/linux-software-2/pdf-
  portfolio-833748/ and http://ubuntuforums.org/showthread.php?p=9981196

  (Adobe Reader 9 installed via Software Center doesn't seem to open
  more than the first embedded PDF)

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

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


[Desktop-packages] [Bug 1300821] Re: compiz crashed with SIGSEGV in CompWindow::move()

2014-10-11 Thread JoshuaStrobl
This is not a Nvidia specific issue, I've had this issue on AMD.

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

Title:
  compiz crashed with SIGSEGV in CompWindow::move()

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  I was attempting to move Files from one workspace to another while a
  lot of file IO was occurring (was firing up a VM with vagrant). I
  could not release Files and keep it on the second workspace, it kept
  attempting to move with my mouse and eventually compiz crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Apr  1 17:12:45 2014
  DistUpgraded: 2014-03-04 03:38:53,219 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1860]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 7690M [103c:1860]
  InstallationDate: Installed on 2014-03-01 (30 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=a3e6c361-4b43-43b0-b258-f50c42041898 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fb11ed0d8f7 _ZN10CompWindow4moveEiib+71:  mov
%cl,0x3f0(%rax)
   PC (0x7fb11ed0d8f7) ok
   source %cl ok
   destination 0x3f0(%rax) (0x7fb11cd47900) in non-writable VMA region: 
0x7fb11cccd000-0x7fb11cdd3000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0
  SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   CompWindow::move(int, int, bool) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
   ExpoScreen::donePaint() () from /usr/lib/compiz/libexpo.so
   CompositeScreen::donePaint() () from /usr/lib/compiz/libcomposite.so
   CompositeScreen::donePaint() () from /usr/lib/compiz/libcomposite.so
   CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so
  Title: compiz crashed with SIGSEGV in CompWindow::move()
  UpgradeStatus: Upgraded to trusty on 2014-03-04 (28 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1807
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.58
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/24/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr06902120471620100:rvnHewlett-Packard:rn1807:rvr33.58:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 06902120471620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140328-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.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: Tue Apr  1 16:25:32 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1379728] Re: gnome-keyring crashes in using GNOME-Shell 3.14

2014-10-11 Thread Fran Diéguez
** Changed in: gnome-keyring (Ubuntu)
   Status: New = Fix Released

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

Title:
  gnome-keyring crashes in using GNOME-Shell 3.14

Status in “gnome-keyring” package in Ubuntu:
  Fix Released

Bug description:
  While using gnome3-staging ppa in U-G 14.10 gnome-keyring crashes
  echoing this message:

  WARNING: gnome-keyring:: couldn't connect to: 
/run/user/1000/keyring-oCHwf5/pkcs11: Connection refused
  p11-kit: skipping module 'gnome-keyring' whose initialization failed: An 
error occurred on the device

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-keyring 3.10.1-1ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 10 11:54:33 2014
  InstallationDate: Installed on 2014-09-19 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140917)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2014-10-11 Thread Fran Diéguez
** Changed in: ubuntu-gnome
   Status: New = Fix Released

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

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

Status in Ubuntu GNOME:
  Fix Released
Status in “deja-dup” package in Ubuntu:
  New

Bug description:
  g-c-c 3.14 crashes when loading the Backup panel

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-control-center 1:3.14.0-1ubuntu1~utopic1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Oct  9 19:30:35 2014
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2014-09-19 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140917)
  ProcCmdline: /usr/bin/gnome-control-center.real --overview
  SegvAnalysis:
   Segfault happened at: 0x7faac2be3743 gtk_lock_button_set_permission+99:
cmp%rax,(%rdx)
   PC (0x7faac2be3743) ok
   source %rax ok
   destination (%rdx) (0x6a65643a706c6568) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_lock_button_set_permission () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in 
gtk_lock_button_set_permission()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with chromium

2014-10-11 Thread Mateo Salta
Here is the command line output around the time of loading and the
errors, just incase some of them are related:

[10038:10038:1011/103520:ERROR:account_tracker_service.cc(113)] 
OnGetTokenFailure: Invalid credentials.
[10038:10038:1011/103520:ERROR:account_tracker.cc(306)] OnGetTokenFailure: 
Invalid credentials.
[10038:10038:1011/103520:ERROR:account_tracker.cc(306)] OnGetTokenFailure: 
Invalid credentials.
[10038:10472:1011/103524:ERROR:get_updates_processor.cc(240)] 
PostClientToServerMessage() failed during GetUpdates
[10038:10069:1011/103540:ERROR:channel.cc(290)] RawChannel read error 
(connection broken)

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

Title:
  Unable to use the widevine plugin with chromium

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

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  it seems widevine support is only activated when branding=chrome

  as seen in

  
  
https://github.com/scheib/chromium/blob/master/third_party/widevine/cdm/widevine_cdm.gyp

  Widevine support would enable EME playing such as Netflix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1376530] Re: GTK apps crashing with Attempt to unlock mutex that was not locked

2014-10-11 Thread Bug Watch Updater
** Changed in: gtk+2.0 (Debian)
   Status: New = Fix Released

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

Title:
  GTK apps crashing with Attempt to unlock mutex that was not locked

Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “gtk+2.0” package in Debian:
  Fix Released

Bug description:
  Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in
  an immediate crash, with the message Attempt to unlock mutex that was
  not locked.

  https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the
  relevant upstream bug, and there is a patch here:
  https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec

  To some extent, this seems to be the result of individual projects
  using GTK incorrectly, and some fixes have been made to those
  individual projects.

  *However*, I am also seeing this bug occur in a closed source third
  party application, Stata 13. As Emmanuele Bassi mentions in the Gnome
  bug thread, there are probably a lot of applications out in the wild
  affected by the same issue, that in some cases cannot be fixed, so it
  would be good if a fix could be included in the versions of GTK that
  Ubuntu ships.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgtk-3-0 3.12.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct  2 10:05:20 2014
  InstallationDate: Installed on 2014-04-24 (160 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago)

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

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


[Desktop-packages] [Bug 846873] Re: Evince: Invisible text in PDF file

2014-10-11 Thread Francois Trahan
Also true in Trusty

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

Title:
  Evince: Invisible text in PDF file

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Certain format produces transparent text when viewing PDF on the
  screen. The text remains invisible even if formatted. The only way to
  get to see that text is to copy-paste it blindly into the text editor
  or the terminal. To reproduce, see for instance an O'Relly Book
  Running Linux 4th Edition which is available for download free of
  charge and is attached to this bug report for your convenience.

  Scroll down to any page containing commands to be entered into the
  terminal on the command line. Any text after the command prompt is
  invisible. For instance, at the bottom of page 58 the fdisk command
  does not appear after the # (root prompt) on the command line.
  swaponcommand cannot be seen at the bottom of page 62 and so forth.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Sep 11 12:21:58 2011
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  KernLog:
   Sep 11 10:06:44 mars kernel: [345609.072499] type=1400 
audit(1315721204.184:23): apparmor=STATUS operation=profile_replace 
name=/usr/bin/evince pid=27132 comm=apparmor_parser
   Sep 11 10:06:44 mars kernel: [345609.074807] type=1400 
audit(1315721204.184:24): apparmor=STATUS operation=profile_replace 
name=/usr/bin/evince-previewer pid=27132 comm=apparmor_parser
   Sep 11 10:06:44 mars kernel: [345609.076412] type=1400 
audit(1315721204.184:25): apparmor=STATUS operation=profile_replace 
name=/usr/bin/evince-thumbnailer pid=27132 comm=apparmor_parser
  ProcEnviron:
   LANGUAGE=ru:en
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: Upgraded to natty on 2011-04-15 (148 days ago)

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

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


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

2014-10-11 Thread Michael
Public bug reported:

I get this when I boot up.

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 11:22:26 2014
InstallationDate: Installed on 2014-10-05 (6 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
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)

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


** Tags: amd64 apport-package 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/1380123

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

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

Bug description:
  I get this when I boot up.

  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 11:22:26 2014
  InstallationDate: Installed on 2014-10-05 (6 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  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/1380123/+subscriptions

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


[Desktop-packages] [Bug 1320560] Re: Removal of gdmflexiserver breaks user switching

2014-10-11 Thread Sean Davis
Patches have been updated on the PPA.  Please test before I upload to
the archive.

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

Title:
  Removal of gdmflexiserver breaks user switching

Status in “xfce4-panel” package in Ubuntu:
  Confirmed
Status in “xfce4-whiskermenu-plugin” package in Ubuntu:
  Confirmed
Status in “xfswitch-plugin” package in Ubuntu:
  Confirmed
Status in “xscreensaver” package in Ubuntu:
  Confirmed

Bug description:
  Hello and pardon for my bad english.
  On xfce4, the button to log with a new user without logout never wants to 
works.
  It accepts to open a confirmation windows To you really want to change 
user? That's OK.
  Then I press Yes and I've got an error message who says in french : 
Impossible to create a new display
  and in english : GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.gnome.DisplayManager was not provided by any .service files

  lsb_release-rd :
  Description:Ubuntu 14.04 LTS
  Release:14.04

  apt-cache policy xfswitch-plugin
  xfswitch-plugin:
Installé : 0.0.1-4ubuntu1
Candidat : 0.0.1-4ubuntu1
   Table de version :
   *** 0.0.1-4ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  Thanks for your help.

  Claude Micouin

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfswitch-plugin 0.0.1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun May 18 00:20:57 2014
  InstallationDate: Installed on 2014-05-07 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: xfswitch-plugin
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 340294] Re: The Poker game in AisleRiot Solitaire does not record the high scores

2014-10-11 Thread van hanegen
Hello.
Just the same case in the Shuffle mode - 120 points and no reaction (see 
attachmeht)
But now it's ok with Non-Shuffle mode (when you can't move the cards)

** Attachment added: 2014-10-04 20:33:45.png
   
https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/340294/+attachment/4231703/+files/2014-10-04%2020%3A33%3A45.png

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

Title:
  The Poker game in AisleRiot Solitaire does not record the high scores

Status in Aisleriot Solitaire:
  New
Status in “aisleriot” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-games

  I am using Hardy Heron and download all updates when they become
  available.  The Poker game in AisleRiot Solitaire does not record the
  high score for games when you can move the cards.  Must have 120
  points or more; but it won't record wins under stats.  I don't know
  about games when you can't move the cards after placement on the 5x5
  grid.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Mar  9 20:52:18 2009
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: gnome-games 1:2.22.3-0ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-games
  Uname: Linux 2.6.24-23-generic i686

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

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


[Desktop-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)

2014-10-11 Thread Nerox
Running Ubuntu 14.04 on Toshiba Satellite E45-B4200. The solution #21
did not work for me. The CPU still have a constant high of consume (+-
30% strangely only for CPU1) without any programs opened. I tried with
other Ubuntu variants like Lubuntu or Xubuntu and the problem still
remains.

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

Title:
  Very high cpu usage for compiz in 14.04 (mesa incorrectly using
  llvmpipe)

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from
  compiz.

  Strangely, glxinfo reports this, which is totally incorrect - I'm
  running on Intel Sandy Bridge HD3000 graphics and VMware isn't even
  installed on this PC:

  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
  OpenGL version string: 2.1 Mesa 10.0.1

  So I guess that compiz might be using lots of cpu because it's using
  llvmpipe as the renderer. So is this a mesa bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.13.1-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
  CurrentDesktop: Unity
  Date: Sat Jan 11 22:27:28 2014
  DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): 
installArchives() failed
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-08-25 (504 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic 
root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash 
intel_pstate=enable crashkernel=384M-:128M vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago)
  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sat Jan 11 22:20:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41063 
   vendor DEL
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)

2014-10-11 Thread Nerox
Running Ubuntu 14.04 on Toshiba Satellite E45-B4200. The solution #21
did not work for me. The CPU still have a high constant  of consume
value (+- 30% strangely only for CPU-1) with no programs opened. I tried
with other Ubuntu variants like Lubuntu or Xubuntu and problem still
remains.

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

Title:
  Very high cpu usage for compiz in 14.04 (mesa incorrectly using
  llvmpipe)

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from
  compiz.

  Strangely, glxinfo reports this, which is totally incorrect - I'm
  running on Intel Sandy Bridge HD3000 graphics and VMware isn't even
  installed on this PC:

  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
  OpenGL version string: 2.1 Mesa 10.0.1

  So I guess that compiz might be using lots of cpu because it's using
  llvmpipe as the renderer. So is this a mesa bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.13.1-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
  CurrentDesktop: Unity
  Date: Sat Jan 11 22:27:28 2014
  DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): 
installArchives() failed
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-08-25 (504 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic 
root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash 
intel_pstate=enable crashkernel=384M-:128M vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago)
  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sat Jan 11 22:20:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41063 
   vendor DEL
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 1297790] Re: Unknown audio device dialog pops up every time I plug in headphones

2014-10-11 Thread Dirk Mcbratney
It's very annoying. The hardware detects whether or not there is a
microphone present in the headset. If there isn't, I only have the one
3.5mm port, so it's not like I could attach one. I don't see any
possible benefit to this feature, but creating a pile of little
obnoxious dialog boxes is a very clear detriment, and it's the sort of
thing Ubuntu normally avoids doing to avoid needlessly reducing new
users' confidence in their system.

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

Title:
  Unknown audio device dialog pops up every time I plug in headphones

Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  I've got a combined headphone/headset socket on my Laptop. Every time
  I plug in my headphones, an unknown audio device dialog pops up
  asking whether I've plugged in headphones or a headset.  This is isn't
  a great user experience as my phone can auto-detect the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1949 F pulseaudio
   /dev/snd/controlC0:  mark   1949 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 26 11:03:29 2014
  InstallationDate: Installed on 2014-03-24 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: DE004505
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: DE004505
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1246583] Re: All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10]

2014-10-11 Thread Haim
*** This bug is a duplicate of bug 1226962 ***
https://bugs.launchpad.net/bugs/1226962

I'm too, have this bug, in ubuntu 14.04.1. all the hotkeys Ctrl+?,
Ctrl+Alt+?, Ctrl+Shift+? are not working.  please fix it...

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

Title:
  All hotkeys of LibreOffice don't work in non-English keyboard layout
  [ubuntu 13.10]

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “libreoffice” package in Fedora:
  Unknown

Bug description:
  Hotkeys (Ctrl+b, Ctrl+s etc) in LibreOffice are language dependent and
  work in English language only. While writing in any other language
  i.e. any Cyrillic, it's impossible to use hotkeys, they just don't do
  anything. Switching to English input language enable hotkeys once
  again. This is very frustrating as user needs to switch language to
  save document, to make it bold, or italic, etc.

  This was not experienced in Ubuntu 13.04.

  Steps to reproduce:
  1. System Settings  Text Entry.
  2. Add another keyboard layout beside English [In my case it is Bengali 
(Probhat)] 
  3. Now launch Writer.
  4. Switch the keyboard layout from English (US) to Bengali (Probhat) by 
pressing Ctrl+Space.
  5. Press Ctrl+B to change font weight to bold.

  Error: 
  Font weight does not get changed.

  Expected: 
  Font weight should change to bold.

  Note:
  none other system hotkeys work as expected. I.e. Ctrl+s to save, or Ctrl+b to 
subscript, or Ctrl+i to italic etc.

  Workaround: 
  The only way is to -
  1. change the keyboard layout to English
  2. then press desired hotkey
  3. then switch keyboard layout back to Bengali.

  The issue is critical, as it make writer very slow for keyboard-only
  typing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-core 1:4.1.2~rc3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 10:11:53 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-05-13 (170 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (4 days ago)

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

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


[Desktop-packages] [Bug 1297790] Re: Unknown audio device dialog pops up every time I plug in headphones

2014-10-11 Thread Dirk Mcbratney
Point of fact, I think it's actually failing to recognize the microphone
in a corded headset that I normally don't use for the laptop itself. Not
that clicking microphone makes any difference to that, since I'm
understanding that it only affects whether or not the audio switches to
the new hardware by default, correct?

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

Title:
  Unknown audio device dialog pops up every time I plug in headphones

Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  I've got a combined headphone/headset socket on my Laptop. Every time
  I plug in my headphones, an unknown audio device dialog pops up
  asking whether I've plugged in headphones or a headset.  This is isn't
  a great user experience as my phone can auto-detect the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1949 F pulseaudio
   /dev/snd/controlC0:  mark   1949 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 26 11:03:29 2014
  InstallationDate: Installed on 2014-03-24 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: DE004505
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: DE004505
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1214352]

2014-10-11 Thread Sbergman
(In reply to Björn Michaelsen from comment #68)
 Scoping this bug clearly only on the missing deps for KDE thanks to the
 excellent summary in comment 59.

...which has become moot with
http://cgit.freedesktop.org/libreoffice/core/commit/?id=f9f9aa9873c5851da86d33ca75e937ac022206a3
Remove smb from X-KDE-Protocols lines, see
http://lists.freedesktop.org/archives/libreoffice/2014-October/063904.html
Re: X-KDE-Protocols=...,smb,...

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

Title:
  GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The G Library - GLib:
  Fix Released
Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

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

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


[Desktop-packages] [Bug 1214352] Re: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2014-10-11 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed = Fix Released

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

Title:
  GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The G Library - GLib:
  Fix Released
Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

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

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


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

2014-10-11 Thread BigChirv
Public bug reported:

I was dist-upgrading my beta install.

Doing apt-get --reinstall install nvidia-331 doesn't trigger the problem
again.

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 12:37:12 2014
InstallationDate: Installed on 2014-09-09 (32 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
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-27 (14 days ago)

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


** Tags: amd64 apport-package 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/1380140

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

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

Bug description:
  I was dist-upgrading my beta install.

  Doing apt-get --reinstall install nvidia-331 doesn't trigger the
  problem again.

  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 12:37:12 2014
  InstallationDate: Installed on 2014-09-09 (32 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  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-27 (14 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-prime (Ubuntu)
   Status: New = Confirmed

-- 
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 1377847] Re: unity screen saver no longer blanks nor locks automatically

2014-10-11 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-settings-daemon -
14.04.0+14.10.20141010-0ubuntu1

---
unity-settings-daemon (14.04.0+14.10.20141010-0ubuntu1) utopic; urgency=low

  [ Tim Lunn ]
  * Copy in Idle Monitor from 3.10 and hook up dbus interface (LP:
#1377847)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 10 Oct 2014 
08:06:04 +

** Changed in: unity-settings-daemon (Ubuntu Utopic)
   Status: Confirmed = Fix Released

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

Title:
  unity screen saver no longer blanks nor locks automatically

Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-desktop3” source package in Utopic:
  Confirmed
Status in “unity-settings-daemon” source package in Utopic:
  Fix Released

Bug description:
  After updating over the weekend the screen saver is no longer blanking
  or locking.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Oct  6 09:44:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (472 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago)

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

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


[Desktop-packages] [Bug 1349116] Re: Bluetooth keyboard and mouse always in low power state

2014-10-11 Thread Christopher M. Penalver
** This bug is no longer a duplicate of bug 1318026
   Apple Magic Mouse battery indicator shows 0%

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

Title:
  Bluetooth keyboard and mouse always in low power state

Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  I'm using an Apple keyword and magic trackpad, connected as bluetooth
  devices.

  The annoying thing is that the Bluetooth applet constantly reports
  these devices as have 0% energy, everytime I reconnect one of these
  devices, I get a notice in the top-right of the screen saying the
  devices have low power.

  I have attachted a couple of screenshots to show what I'm seeing.
  Please let me know if I can provide further information to help
  resolve the issue.

  I have brand-new batteries in these devices BTW, and from an Apple
  computer, the devices are seen to have close to 100% charge.

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

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


[Desktop-packages] [Bug 1332210] Re: Apple Magic Mouse battery life read as 0%

2014-10-11 Thread Christopher M. Penalver
** This bug is no longer a duplicate of bug 1318026
   05ac:8286 [MacBookPro10,1] mouse battery indicator shows 0%

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

Title:
  Apple Magic Mouse battery life read as 0%

Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  Despite being fully-functional, my Apple Magic Mouse is shown to be in
  the discharging state at 0%. It is also marked rechargable, which
  is false -- you need to replace the batteries when they run out.

  Output of `upower --dump` attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 19 10:30:37 2014
  InstallationDate: Installed on 2014-04-01 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: upower
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (55 days ago)

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

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


[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-10-11 Thread ThomasA
This appeared for me after upgrading from 13.04 to 14.04. After boot,
the keyboard layout seems English although Danish is my only installed
layout.

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=de_DE.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL=pc105
  XKBLAYOUT=de
  XKBVARIANT=
  XKBOPTIONS=

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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


[Desktop-packages] [Bug 1364305] Re: Wrong filename of firefox' apparmor profile

2014-10-11 Thread ssameer
Symlinking (or hardlinking) usr.bin.firefox to usr.lib.firefox.firefox
does not work for me.

$ sudo aa-complain /usr/lib/firefox/firefox

Setting /usr/lib/firefox/firefox to complain mode.
Traceback (most recent call last):
  File /usr/sbin/aa-complain, line 30, in module
tool.cmd_complain()
  File /usr/lib/python3/dist-packages/apparmor/tools.py, line 178, in 
cmd_complain
apparmor.set_complain(profile, program)
  File /usr/lib/python3/dist-packages/apparmor/aa.py, line 267, in 
set_complain
change_profile_flags(filename, program, 'complain', True)
  File /usr/lib/python3/dist-packages/apparmor/aa.py, line 606, in 
change_profile_flags
old_flags = get_profile_flags(filename, program)
  File /usr/lib/python3/dist-packages/apparmor/aa.py, line 603, in 
get_profile_flags
raise AppArmorException(_('%s contains no profile') % filename)
apparmor.common.AppArmorException: '/etc/apparmor.d/usr.lib.firefox.firefox 
contains no profile'


The culprit seems to be the regex trying to match /usr/lib/firefox/firefox but 
not /usr/lib/firefox/firefox.sh:

/usr/lib/firefox/firefox{,*[^s][^h]} {

Changing this to

/usr/lib/firefox/firefox {

allows apparmor to load the profile.


AppArmor Version: 2.8.95~2430-0ubuntu5

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

Title:
  Wrong filename of firefox' apparmor profile

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the apparmor profile that comes with firefox can't be turned on and
  off with the regular command line tools because of it's wrong
  filename:

  
  # aa-complain /usr/bin/firefox
  Profile for /usr/lib/firefox/firefox.sh not found, skipping

  (because /usr/bin/firefox is a link)


   
  # aa-complain /usr/lib/firefox/firefox.sh
  Profile for /usr/lib/firefox/firefox.sh not found, skipping

  (because there is no /etc/apparmor.d/usr.lib.firefox.firefox.sh )



  # aa-complain /usr/lib/firefox/firefox
  Profile for /usr/lib/firefox/firefox not found, skipping

  (because there is no /etc/apparmor.d/usr.lib.firefox.firefox )

  
  so the armor profile has the name, that does not work, i.e. the name of a 
logical link instead of an executable. 


  It should have the name of the shell script and/or the name of the
  binary.


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 31.0+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danisch3540 F panel-11-mixer
danisch3572 F pulseaudio
  BuildID: 20140715214327
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Tue Sep  2 11:38:12 2014
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IpRoute:
   default via 192.168.103.254 dev em1 
   169.254.0.0/16 dev vlan0  scope link  metric 1000 
   192.168.100.0/22 dev em1  proto kernel  scope link  src 192.168.102.179 
   192.168.200.0/24 dev vlan0  proto kernel  scope link  src 192.168.200.1
  Plugins:
   Windows Media Player Plug-in - 
/usr/lib/mozilla/plugins/gecko-mediaplayer-wmp.so (gecko-mediaplayer)
   RealPlayer 9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-rm.so 
(gecko-mediaplayer)
   QuickTime Plug-in 7.6.9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-qt.so 
(gecko-mediaplayer)
   DivX Browser Plug-In - /usr/lib/mozilla/plugins/gecko-mediaplayer-dvx.so 
(gecko-mediaplayer)
   mplayerplug-in is now gecko-mediaplayer 1.0.8 - 
/usr/lib/mozilla/plugins/gecko-mediaplayer.so (gecko-mediaplayer)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{6AC85730-7D0F-4de0-B3FA-21142DD85326}/defaults/preferences/colorzilla.js
  Profiles: Profile0 (Default) - LastVersion=31.0/20140715214327 (In use)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0104.2012.1123.1027
  dmi.board.name: DH77DF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG40293-301
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0104.2012.1123.1027:bd11/23/2012:svn:pn:pvr:rvnIntelCorporation:rnDH77DF:rvrAAG40293-301:cvn:ct3:cvr:

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1311515] Re: Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

2014-10-11 Thread L.D
Pleace, Help me! 
What am I doing wrong?

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

Title:
  Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed

Bug description:
  [Test details]
  Image: 14.04 LTS
  Platforms:
  ThinkPad-Edge-E531:~$ dmesg | grep -i syn
  [4.135984] hda_codec: Enable sync_write for stable communication
  [4.846020] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2722, fw id: 1310036
  [4.846024] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [4.906051] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6

  [Steps]
  1. install image kittyhawk-trusty-amd64-iso-20140314-1.iso via bootable USB 
or DVD
  2. launch google maps in web browser
  3. pinch touchpad with two fingers and see if map zooms in  out accordingly

  [Expected result]
  map should zoom-in when user pinches two fingers apart, zoom-out when user 
pinches two fingers together.

  [Actual result]
  sometimes zoom in  out behavior is reversed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1311515/+subscriptions

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


[Desktop-packages] [Bug 1272862] Re: Fontconfig error: /etc/fonts/conf.d/65-khmer.conf, line 14: out of memory

2014-10-11 Thread Harri Luuppala
After upgrade from 12.04 LTS to 14.04 LTS got this error message with
three fonts /etc/fonts/conf.d/65-khmer.conf

# uname -a 
Linux harri-Veriton-X2610G 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Starting firefox from shell did show the issue.
SOLVED (thanks to Marius Gedminas' propsal) by `sudo apt-get purge 
fonts-khmeros-core`

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

Title:
  Fontconfig error: /etc/fonts/conf.d/65-khmer.conf, line 14: out of
  memory

Status in Ubuntu GNOME:
  New
Status in “fonts-khmeros” package in Ubuntu:
  New
Status in “ubuntu-release-upgrader” package in Ubuntu:
  New

Bug description:
  Ever since gnome 3.10 showed up in the gnome3-team PPA for saucy I've
  been seeing these three errors repeated on the console when launching
  GUI apps:

  Fontconfig error: /etc/fonts/conf.d/65-khmer.conf, line 14: out of memory
  Fontconfig error: /etc/fonts/conf.d/65-khmer.conf, line 23: out of memory
  Fontconfig error: /etc/fonts/conf.d/65-khmer.conf, line 32: out of memory

  Even running dot from graphviz to produce an image prints these
  errors.

  This did not happen with fontconfig 2.10.93-0ubuntu1.

  /etc/fonts/conf.d/65-khmer.conf looks like a simple file with no fancy
  stuff in it (attached, just in case).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: fontconfig 2.11.0-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
  Uname: Linux 3.13.0-031300rc7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Jan 26 11:04:58 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (549 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (100 days ago)

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

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


[Desktop-packages] [Bug 1380173] [NEW] Single touchpad tap causes two click events

2014-10-11 Thread Thucydides411
Public bug reported:

A single tap on the touchpad sometimes causes two left-click events. One
way to trigger this behavior is to do a two-finger tap (to emulate a
right click), and after the context menu comes up, to do a single tap
somewhere else. The single tap will then be interpreted as two separate
left clicks.

Steps to reproduce:

1. Open up Chrome, navigate to search engine, and execute a search.

2. Tap on one of the links with two fingers. A context menu appears.

3. Tap once on Open in New Tab, making sure that the link is also
directly below the mouse when you tap.

4. Often, two left clicks occur: the first left click selects Open in
New Tab, and the second left click opens the link a second time.

Expected behavior: In the above example, only one left click should
fire. The link should only be opened once, not twice.

What happened instead: In the above example, the link is opened twice,
indicating that two left clicks fired, rather than just one.

System:

* Distribution: Ubuntu 14.04
* Kernel: 3.13.0-37-generic
* Touchpad: ETPS/2 Elantech Touchpad
* xserver-xorg-input-synaptics: 1.7.4-0ubuntu1

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


** Tags: synaptics touchpad xorg

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

Title:
  Single touchpad tap causes two click events

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  A single tap on the touchpad sometimes causes two left-click events.
  One way to trigger this behavior is to do a two-finger tap (to emulate
  a right click), and after the context menu comes up, to do a single
  tap somewhere else. The single tap will then be interpreted as two
  separate left clicks.

  Steps to reproduce:

  1. Open up Chrome, navigate to search engine, and execute a search.

  2. Tap on one of the links with two fingers. A context menu appears.

  3. Tap once on Open in New Tab, making sure that the link is also
  directly below the mouse when you tap.

  4. Often, two left clicks occur: the first left click selects Open in
  New Tab, and the second left click opens the link a second time.

  Expected behavior: In the above example, only one left click should
  fire. The link should only be opened once, not twice.

  What happened instead: In the above example, the link is opened twice,
  indicating that two left clicks fired, rather than just one.

  System:

  * Distribution: Ubuntu 14.04
  * Kernel: 3.13.0-37-generic
  * Touchpad: ETPS/2 Elantech Touchpad
  * xserver-xorg-input-synaptics: 1.7.4-0ubuntu1

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

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


[Desktop-packages] [Bug 1159724] Re: Error setting extended attribute 'xdg.origin.url' while saving a duplicate

2014-10-11 Thread yaztromo
*** This bug is a duplicate of bug 1096837 ***
https://bugs.launchpad.net/bugs/1096837

OS: Xubuntu 14.04

This error also happens when copying a file to a cifs mount or USB
stick.

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

Title:
  Error setting extended attribute 'xdg.origin.url' while saving a
  duplicate

Status in Thunar file manager:
  New
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  When I download a file from Chromium by choosing the open option (so
  the file is saved in /tmp AFAIK), when I do a file-save copy... I get
  this error in the red ribbon:

  Error setting extended attribute 'xdg.origin.url': Operation not
  supported

  The file seems to save fine, though, so there seems to be no reason
  for this error notification.

  Don't know if it makes a difference, but my /tmp is set to mount in
  memory, since I run a SSD. This is my fstab entry:

  tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

  Expected behaviour - no error notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evince 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 25 11:43:48 2013
  InstallationDate: Installed on 2012-10-19 (156 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device

2014-10-11 Thread Glenn Brumfield
This also affects Ubuntu 14.04  Ubuntu 14.10 beta as of 11 October
2014. Lubuntu 14.10 beta is also affected, so this seems common to bluez
as well as blueman.

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

Title:
  Bogus another operation in progress error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gnome-vfs-obexftp” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose bluetooth settings
  3 - select the phone among the listed devices
  4 - click on Browse files
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  = I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is another
  operation in progress. Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then ejected the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error This location could not be displayed. Another 
operation in progress, so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when ejecting 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

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

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


[Desktop-packages] [Bug 1379676] Re: TypeError: Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments passed will be ignored

2014-10-11 Thread Thibault Saunier
This is due to a change of behaviour in latest PyGobject (commit:
https://git.gnome.org/browse/pygobject/commit/?id=3a2bfc8bf01fcae3863)
and that has been fixed in gst-python here:
http://cgit.freedesktop.org/gstreamer/gst-
python/commit/?id=4c08c3396c3cdadc939a9889f1e4664f938921a0

It would be nice of you if you could put that patch in your gst-python
package. I you can not and would need me to release gst-python-1.2.2 it
can be done (also the patch from:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1363637 should be
added)

Note: That bug should not be reported as a bug in pitivi but either gst-
python (or maybe PyGobject as it is a concequence of a change in
behaviour in there).

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

Title:
  TypeError: Passing arguments to gi.types.Boxed.__init__() is
  deprecated. All arguments passed will be ignored

Status in “pitivi” package in Ubuntu:
  New

Bug description:
  Using 0.93 version with PPA in Ubuntu 14.10 Beta I get a lot errors
  like this:

  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:559: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
Gst.Caps(application/ogg),
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:563: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
video_profile = 
GstPbutils.EncodingVideoProfile.new(Gst.Caps(video/x-theora),
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:565: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
Gst.Caps(video/x-raw),
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:569: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
audio_profile = 
GstPbutils.EncodingAudioProfile.new(Gst.Caps(audio/x-vorbis),
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:571: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
Gst.Caps(audio/x-raw),
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:792: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
self.container_profile.set_format(Gst.Caps(muxertype))
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:771: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
self.video_profile.set_format(Gst.Caps(videotype))
  /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py:751: TypeError: 
Passing arguments to gi.types.Boxed.__init__() is deprecated. All arguments 
passed will be ignored.
self.audio_profile.set_format(Gst.Caps(audiotype))

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pitivi 0.93-4ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 10 09:30:08 2014
  InstallationDate: Installed on 2014-05-08 (154 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: pitivi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1380178] [NEW] Google Hangouts Camera is upside down.

2014-10-11 Thread Jeff
Public bug reported:

I have tried every forum post and trick that I can find. I hope you can
assist me.

1) Ubuntu 14.04.1 LTS Release 14.04

2) google-talkplugin 5.4.2.0-1 , google-chrome-beta 39.0.2171.19-1

3) When I start a video call or chat in Hangouts, the video image not to
be inverted.

4) When I start a video call in Google Hangouts my image is inverted,
however in Cheesebooth, I am not.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Oct 11 15:49:58 2014
DistUpgraded: 2014-04-19 18:26:21,616 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
   Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
InstallationDate: Installed on 2013-01-07 (642 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MachineType: ASUSTeK Computer Inc. P50IJ
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=dc19809e-34be-499c-a323-1dd1ce0fc337 ro splash quiet 
plymouth:debug=1=1=1=1=1=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-04-19 (174 days ago)
dmi.bios.date: 02/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P50IJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd02/14/2011:svnASUSTeKComputerInc.:pnP50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnP50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: P50IJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Oct 11 15:29:58 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   21569 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  Google Hangouts Camera is upside down.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I have tried every forum post and trick that I can find. I hope you
  can assist me.

  1) Ubuntu 14.04.1 LTS Release 14.04

  2) google-talkplugin 5.4.2.0-1 , google-chrome-beta 39.0.2171.19-1

  3) When I start a video call or chat in Hangouts, the video image not
  to be inverted.

  4) When I start a video call in Google Hangouts my image is inverted,
  however in Cheesebooth, I am not.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 11 15:49:58 2014
  DistUpgraded: 2014-04-19 18:26:21,616 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
  InstallationDate: Installed on 2013-01-07 (642 days 

[Desktop-packages] [Bug 1380177] [NEW] compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread jerrylamos
Public bug reported:

Updated 3.16.0-21 to -22, booted, got this error.

So far I've gotten compiz crashes on all four of my pc's, this 
Acer 5253 wide screen notebook, 
Lenovo M58p desktop, 
Acer Aspire 1 netbook. all with amd64 ubuntu utopic.  Even my 
Compaq Presario Pentium D 3.33 gHz 32 bit got a compiz failure a couple days 
ago.

BTW, also get failures with kernel 3.17.

Intrepid up thru July 31 no such trouble.  Grief of varying degrees
since.

This is:

Linux Acer5253 3.16.0-22-generic #29-Ubuntu SMP Thu Oct 9 16:26:18 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Wrestler [Radeon HD 6310]
model name  : AMD E-350 Processor
model name  : AMD E-350 Processor

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu5
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
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Oct 11 16:52:53 2014
Disassembly: = 0x0:Cannot access memory at address 0x0
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0520]
InstallationDate: Installed on 2014-10-06 (4 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
MachineType: Acer Aspire 5253
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=8816ff45-b40e-46b3-b865-68299aca4051 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/06/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.name: Aspire 5253
dmi.board.vendor: Acer
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd01/06/2011:svnAcer:pnAspire5253:pvrV1.05:rvnAcer:rnAspire5253:rvrV1.05:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 5253
dmi.product.version: V1.05
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sat Oct 11 16:52:35 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1
xserver.video_driver: radeon

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


** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace ubuntu 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 compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1380177

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Updated 3.16.0-21 to -22, booted, got this error.

  So far I've gotten compiz crashes on all four of my pc's, this 
  Acer 5253 wide screen notebook, 
  Lenovo M58p desktop, 
  Acer Aspire 1 netbook. all with amd64 ubuntu utopic.  Even my 
  Compaq Presario Pentium D 3.33 gHz 32 bit got a compiz failure a couple days 
ago.

  BTW, also get failures with kernel 3.17.


[Desktop-packages] [Bug 1380177] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1366351 ***
https://bugs.launchpad.net/bugs/1366351

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231878/+files/CoreDump.gz

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231890/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231892/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231893/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231894/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1380177/+attachment/4231895/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1366351
   compiz crashed with SIGSEGV in g_closure_invoke()

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Updated 3.16.0-21 to -22, booted, got this error.

  So far I've gotten compiz crashes on all four of my pc's, this 
  Acer 5253 wide screen notebook, 
  Lenovo M58p desktop, 
  Acer Aspire 1 netbook. all with amd64 ubuntu utopic.  Even my 
  Compaq Presario Pentium D 3.33 gHz 32 bit got a compiz failure a couple days 
ago.

  BTW, also get failures with kernel 3.17.

  Intrepid up thru July 31 no such trouble.  Grief of varying degrees
  since.

  This is:

  Linux Acer5253 3.16.0-22-generic #29-Ubuntu SMP Thu Oct 9 16:26:18 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Wrestler [Radeon HD 6310]
  model name: AMD E-350 Processor
  model name: AMD E-350 Processor

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu5
  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
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Oct 11 16:52:53 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0520]
  InstallationDate: Installed on 2014-10-06 (4 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
  MachineType: Acer Aspire 5253
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=8816ff45-b40e-46b3-b865-68299aca4051 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.name: Aspire 5253
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

2014-10-11 Thread tlawnsby
Public bug reported:

Saw error messages during boot but seems to work ok. Settings from
previous session set correctly for this session. I am running dual
monitors, 24 inch and 22 inch.  Background wallpaper (random, every 10
minutes) settings do not set up.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-22-generic
Date: Sat Oct 11 15:17:07 2014
InstallationDate: Installed on 2014-10-10 (1 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
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)

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


** Tags: amd64 apport-package 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/1380179

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

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

Bug description:
  Saw error messages during boot but seems to work ok. Settings from
  previous session set correctly for this session. I am running dual
  monitors, 24 inch and 22 inch.  Background wallpaper (random, every 10
  minutes) settings do not set up.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 15:17:07 2014
  InstallationDate: Installed on 2014-10-10 (1 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  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/1380179/+subscriptions

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


[Desktop-packages] [Bug 1353832] Re: arm CPUs get FATAL: cannot locate cpu MHz in /proc/cpuinfo

2014-10-11 Thread Roger Allen
I've created a gist describing how to work around this.

https://gist.github.com/rogerallen/0346a1812deda2a380da

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

Title:
  arm CPUs get FATAL: cannot locate cpu MHz in /proc/cpuinfo

Status in “jackd2” package in Ubuntu:
  Confirmed

Bug description:
  Trying to run the Supercollider http://supercollider.github.io/ sound
  synthesis program on an ARM-based NVIDIA Jetson TK1, I received this
  error.  I also received this when I tried jack_simple_client

  FATAL: cannot locate cpu MHz in /proc/cpuinfo

  This is from the Jack Library.  
  $ apt-cache policy libjack-jackd2-0:armhf
  libjack-jackd2-0:
Installed: 1.9.9.5+20130622git7de15e7a-1ubuntu1
Candidate: 1.9.9.5+20130622git7de15e7a-1ubuntu1
Version table:
   *** 1.9.9.5+20130622git7de15e7a-1ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Packages
  100 /var/lib/dpkg/status
  (updated in 2013)

  The issue is fixed in the latest source by this checkin: (from March, 2014)
  
https://github.com/jackaudio/jack2/commit/d425d8035b761b4a362c538c41eca874ff4995f0

  I have found this latest source works for me if I compile and install
  jack by hand.  So, I think updating the libjack-jackd2-0:armhf library
  would be desirable.  Until then, all ARM-based systems can't use jack.

  Also see
  https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1347914 for a
  similar report for the program Audacity.

  Additional details

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  $ uname -a
  Linux muggy 3.10.24-gf455cd4-dirty #3 SMP PREEMPT Tue Jul 22 12:20:38 PDT 
2014 armv7l armv7l armv7l GNU/Linux

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-10-11 Thread Aibara Iduas
I'm using nvidia-331 and it still does not work for me: I just get a blank 
screen instead of the usual login one. I still need to downgrade nvidia-common 
and ubuntu-driver-common to version 0.2.91.4 to be able to use any GUI. I'm on 
a Thinkpad T420s, using an nvidia GF119M [NVS 4200M] (rev a1). 
Incidentally, now that I upgraded, even though I've purged everything I can 
think of and installed the downgraded drivers, I can't switch between the 
Intel and nvidia cards at all, just like this bug, which is supposedly fixed:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310023

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed
Status in “ubuntu-drivers-common” source package in Trusty:
  Triaged
Status in “xserver-xorg-video-intel” source package in Trusty:
  Incomplete

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension GLX missing on display :0'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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

[Desktop-packages] [Bug 1322232] Re: wrong margins on HP photosmart 5520 printer

2014-10-11 Thread jc
I have a similar problem:  The printer is an HP Officejet Pro L7600,
which used to work fine on an earlier Ubuntu.  But when I upgraded to
the latest xubuntu (LTE 14.04), the pages all have a blank margin about
1.3 or 1.4 cm wide, and the text in that area (title, page number, date,
etc.) in blank.  The titles at the top typically have the bottom of
descenders  in letters like 'p', 'q', and 'y', showing that the text was
placed correctly in PDF/PS, but the top parts of the letters are
erased by something.

I've poked around in all the config stuff I can find, and done a bit of
googling, and found comments about the problem on several forums, but as
here, I've found no answers.  The fact that the printer printed in the
margin area (up to about 2 cm from each edge) proves that it's not the
printer's fault.

Anyone have a clue for how to fix it?

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

Title:
  wrong margins on HP photosmart 5520 printer

Status in “hplip” package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 14.04 LTS, hplip package 3.14.3-0ubuntu3

  With the hplip Ubuntu package, when printing with any A4 paper size
  (A4 / A4 small margins / A4 borderless), output is cut on the edges of
  the page (more than 1 cm is cut from each edge).

  Using upstream hplip 3.14.4 downloaded from http://hplipopensource.com
  , with A4 paper size, prints as expected : margins are only a few
  millimeters wide, and apps don't try to print within these margins.

  Test case : remove printer from CUPS, setup printer with hp-setup then change 
paper size with CUPS, open LibreOffice, select printer and page size in 
printer settings dialog, set margins to the lowest allowed value in format  
page  page  margins, print page.
  Tried with other apps than LibreOffice too.

  After reviewing a few bug reports about margin issues with hplip, it seems 
the timeline for this problem is the following :
  - margins were wrong in the ppd files from the original upstream packages
  - Debian and Ubuntu included a patch to alter page size in the ppd files
  - upstream fixed the margins size bug, thus causing a regression in Debian 
and Ubuntu packages
  - Debian fixed their patch to work with the fixed upstream release 
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655106#52]
  I'm not sure whether the fixed Debian patch has been ported to Ubuntu. I 
tried comparing the patches in the sources packages 
hplip_3.14.1-1.debian.tar.xz from Debian, and 
hplip_3.14.3-0ubuntu3.debian.tar.gz from Ubuntu, and it seems that the patches 
are the same now, so maybe that problem has nothing to do with my bug.

  I can add log files or ppd files if needed...

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

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


[Desktop-packages] [Bug 1310260] Re: Pulseaudio fails to detect card (probably due to hybrid graphics)

2014-10-11 Thread Vicente Luiz Scalon
Suggestion on post #27 by Letik (martin-96-59) incluning the :

options snd-hda-intel enable=0,1,0

on file  /etc/modprobe.d/alsa-base.conf works for me too.

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

Title:
  Pulseaudio fails to detect card (probably due to hybrid graphics)

Status in “alsa-driver” package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I wanted to install Trusty on my Elitebook 850 G1 with hybrid graphics (Intel 
/ AMD) but pulseaudio goes nuts on me as soon as I try to play any music / 
sound, try to change volume, etc.
  I've tried it with Ubuntu, Kubuntu and now with Xubuntu with the same result 
everytime.

  My guess is that pulseaudio has problems with the AMD GPU and it's sound 
processor being switched off automatically as enabled by Kernel 3.13 (formerly 
achieved by adding the radeon.runpm=1 kernel parameter)
  (http://lists.freedesktop.org/archives/dri-devel/2013-September/045650.html)

  root@HP-EliteBook-850-G1:~# cat /sys/kernel/debug/vgaswitcheroo/switch
  0:IGD:+:Pwr::00:02.0
  1:DIS: :DynOff::03:00.0
  2:DIS-Audio: :Off::03:00.1

  As you can see, the AMD GPU has been turned off automatically. Pulseaudio, 
the (X)Ubuntu volume applet and KMix on the other hand list it as still 
available.
  Based on that I asume pulseaudio tries to access a switched-off device and 
fails.

  I've followed the steps listed
  here: https://wiki.ubuntu.com/DebuggingSoundProblems
  and
  here: https://wiki.ubuntu.com/PulseAudio/Log

  I'll attach the logs right away. (pulseverbose1.log and my dmesg
  output)

  Pusleverbose is full of messages like this one:
  (   0.013|   0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device 
hw:0: No such file or directory

  This output of dmesg also caught my attention:
  [  354.927935] HDMI ATI/AMD: no speaker allocation for ELD
  [  357.695010] hda-intel :03:00.1: Disabling via VGA-switcheroo

  One thing I noticed using Kubuntu is that after pulseaudio becomes 
unresponsive the taskmanager lists 4 pulseaudio processes two of which are 
active on harddrive (Aktiv auf Festplatte). Those two processes cannot be 
killed even as root.
  Currently being on Xubuntu the same thing is true, although it lists only one 
process in the taskmanager that cannot be killed.

  I hope you can help me.

  Best regards,
  Paul

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Apr 20 13:47:09 2014
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP EliteBook 850 G1, IDT 92HD91BXX, Speaker, Internal] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.08
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU345BY96
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.08:bd02/19/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3008CC10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.version: A3008CC10003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310260/+subscriptions

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


[Desktop-packages] [Bug 1380194] [NEW] Terminal emulator open menu after i press F1 or F10 key

2014-10-11 Thread tuxmartin
Public bug reported:

Terminal emulator open menu after i press  F1 or F10 key. 
Midnight commander, htop and a lot of other linux TUI apps use Fx keys for own 
functions.
I don't know anyone who need F1 and F10 key bindings set to terminal emulator 
menu...

Solution:
Disable these function in terminal emulator setttings. It is simple. Why it is 
not in default config?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-terminal 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 12 01:19:24 2014
InstallationDate: Installed on 2014-10-11 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Affects: xfce4-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

** Also affects: xfce4-terminal (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Terminal emulator open menu after i press  F1 or F10 key

Status in “gnome-terminal” package in Ubuntu:
  New
Status in “lxterminal” package in Ubuntu:
  New
Status in “xfce4-terminal” package in Ubuntu:
  New

Bug description:
  Terminal emulator open menu after i press  F1 or F10 key. 
  Midnight commander, htop and a lot of other linux TUI apps use Fx keys for 
own functions.
  I don't know anyone who need F1 and F10 key bindings set to terminal emulator 
menu...

  Solution:
  Disable these function in terminal emulator setttings. It is simple. Why it 
is not in default config?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 12 01:19:24 2014
  InstallationDate: Installed on 2014-10-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1251176] Re: Can't type accented characters anymore: dead-acute is undefined

2014-10-11 Thread Pius
I put the line

(require 'iso-transl)

into my .emacs file - no difference . The dead keys remain dead.

What I do not understand: Nobody seems to have a reliable workaround.
Just some are lucky. I am not. But ` is important if you write LaTeX:
You need it when processing a LaTeX code leads an error message, to see
what is wrong. So I guess MANY people will have problems from this dead
keys behaviour. And this nasty phenomenon is not qualified as a bug? It
is a regular feature? I have been using emacs every day for many years
but never had any problem with ` , apart from the last weeks. It is
extremely annoying.

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

Title:
  Can't type accented characters anymore: dead-acute is undefined

Status in Emacs-snapshot for ubuntu:
  Triaged
Status in “emacs24” package in Ubuntu:
  Confirmed

Bug description:
  When you type an accented character through a dead-key, you might get
  one of:

     dead-acute is undefined
    dead-grave is undefined
    dead-tilde is undefined
    S-dead-tilde is undefined
    dead-diaeresis is undefined
    S-dead-diaeresis is undefined

  or something similar.

  On the web, I found several workaround:

  1/ launch emacs with XMODIFIERS='' emacs
  2/ type C-x 8 RET RET once
  3/ add (require 'iso-transl) to your .emacs.d/init.el or .emacs file

  Upstream report: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15135
  and http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15891

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs-snapshot/+bug/1251176/+subscriptions

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


  1   2   >