[Desktop-packages] [Bug 1282821] Re: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001

[Chris Wilson]

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

** This bug has been marked a duplicate of bug 1041790
   [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround 
i915.semaphores=0

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

Title:
  [sandybridge-m-gt1] False GPU lockup  IPEHR: 0x0b160001 IPEHR:
  0x0b140001

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  Error report just pops up random

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  Uname: Linux 3.13.2-031302-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Chipset: sandybridge-m-gt1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb 20 23:44:40 2014
  DistUpgraded: 2014-02-10 10:59:09,520 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
  InstallationDate: Installed on 2014-02-09 (11 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: ASUSTeK Computer Inc. K54C
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.2-031302-generic 
root=UUID=a85492a5-8cd5-456a-83a8-bf0927cc412d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt1] False GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001
  UpgradeStatus: Upgraded to trusty on 2014-02-10 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54C.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54C
  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.:bvrK54C.210:bd10/23/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54C
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140218-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~rc1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  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: Thu Feb 20 22:54:27 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12874 
   vendor SEC
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1282821/+subscriptions

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

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Alberto Milone]

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

** Also affects: nvidia-prime (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: nvidia-prime (Ubuntu)
   Importance: Undecided = High

** Changed in: nvidia-prime (Ubuntu Precise)
   Importance: Undecided = High

** Changed in: nvidia-prime (Ubuntu Precise)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Triaged
Status in “nvidia-prime” source package in Precise:
  Triaged

Bug description:
  The BusID string created by prime-xconfig could be incorrect in any of
  the following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 1239605] Re: Combo audio jack support (what did you plug in?-dialog)

[David Henningsson]

The functionality has been merged now, although I'm not sure when 14.04
will switch from gnome-settings-daemon to unity-settings-daemon.

** Changed in: unity-settings-daemon (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Combo audio jack support (what did you plug in?-dialog)

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  Won't Fix
Status in “unity-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “unity-settings-daemon” source package in Precise:
  Won't Fix

Bug description:
  This is about a specific set of new laptops, which has only one 3.5 mm
  jack for analog audio, and where that jack can be used to plug in a
  headphone, headset, and in some cases, a microphone.

  Previously, these jacks have been able to distinguish - in hardware -
  between a headphone and a headset (i e headphone with mic), but it seems
  to be increasingly common that they don't have this ability.

  Our current solution, as it works in 13.10, is that for these machines
  one has to manually select the right input and output in sound settings.

  Here's an example on how the dialog looks in Windows:
  https://launchpadlibrarian.net/70431415/2011-03-08%2017.08.26.jpg -
  probably provided by Realtek 3rd party drivers.

  We can either choose to implement a similar dialog, or just to provide
  notify-OSD on plug of audio jack for user to choose between
  microphone, headphone/speakers, or headset if it is a four ring jack.
  Choosing the notify-OSD instead of an OSD is a compromise between
  making it easy for users to reconfigure jack and avoiding annoying
  distractions.

  Timeline wise it would be nice to merge this in the early 14.04 cycle.
  We also need to ship it in OSP2 (OEM Service Pack 2, shipped on 
pre-installs). Hence it would be good if we could have input/ack from design 
team ASAP, or at least by the end of October.

  https://wiki.ubuntu.com/Sound#unknown-device: When a device is
  plugged into an audio jack that can’t distinguish between
  headphones/speakers, headsets, or microphones, Ubuntu should display
  an “Unknown Audio Device” dialog...

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

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

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Alberto Milone]

** Changed in: nvidia-prime (Ubuntu)
   Status: Triaged = In Progress

** Changed in: nvidia-prime (Ubuntu Precise)
   Status: Triaged = In Progress

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  The BusID string created by prime-xconfig could be incorrect in any of
  the following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 943993] Re: No connect to server use ~98%CPU (sftp)

[Bug Watch Updater]

** Changed in: gvfs
   Status: New = Invalid

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

Title:
  No connect to server use ~98%CPU (sftp)

Status in GVFS:
  Invalid
Status in “gvfs” package in Ubuntu:
  Triaged

Bug description:
  I'm testing nautilus and file transfer and no connect to server and
  use ~98%CPU. Attach backtrace

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gvfs 1.10.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Mar  1 10:32:58 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to oneiric on 2011-10-04 (148 days ago)

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

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

[Desktop-packages] [Bug 1082182] Re: (vino-server:8915): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed

[Andreas]

I see the exact  same problem on a 12.04 system:

$ lsb_release -rd

Description:Ubuntu 12.04.3 LTS
Release:12.04

$ apt-cache policy vino
vino:
  Installed: 3.4.2-0ubuntu1.3
  Candidate: 3.4.2-0ubuntu1.3

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

Title:
  (vino-server:8915): EggSMClient-CRITICAL **: egg_sm_client_set_mode:
  assertion `global_client == NULL || global_client_mode ==
  EGG_SM_CLIENT_MODE_DISABLED' failed

Status in “vino” package in Ubuntu:
  Confirmed

Bug description:
  In ~/.xsession-errors found error:
  (vino-server:8915): EggSMClient-CRITICAL **: egg_sm_client_set_mode: 
assertion `global_client == NULL || global_client_mode == 
EGG_SM_CLIENT_MODE_DISABLED' failed

  lsb_release -rd
  Description: Ubuntu 12.10
  Release: 12.10

  apt-cache policy vino
  vino:
Installed: 3.6.0-0ubuntu1
Candidate: 3.6.0-0ubuntu1
Version table:
   *** 3.6.0-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1282847] [NEW] desktop ui scale is huge even though the setting is set to a scale of 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I just updated and restarted the laptop. When it started, the gtk
widgets are all huge. The unity shell is not scaled. I opened up the
Display settings to find a new scale widget, which is currently set to
1. Lowering it did not change anything. This is all experienced on a
Macbook Pro Retina 11,1.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.321
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 20 20:56:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-14 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug trusty
-- 
desktop ui scale is huge even though the setting is set to a scale of 1
https://bugs.launchpad.net/bugs/1282847
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 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 1282944] [NEW] package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Tshering Namgyal Wangdi]

Public bug reported:

Insstallation of chmsee triggerred the crash of bamfdaemon. 
Ubuntu 12.04.4 x64
Gigabyte H61-S2P motherboard
Intel core i3 processor - Intel® Pentium(R) CPU G2010 @ 2.80GHz
4 gb ddr3 ram
160 GB Hard disk
Chmsee didnot install.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.126-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Fri Feb 21 14:37:18 2014
DuplicateSignature: package:bamfdaemon:0.2.126-0ubuntu1:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
MarkForUpload: True
SourcePackage: bamf
Title: package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check precise

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

Title:
  package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in “bamf” package in Ubuntu:
  New

Bug description:
  Insstallation of chmsee triggerred the crash of bamfdaemon. 
  Ubuntu 12.04.4 x64
  Gigabyte H61-S2P motherboard
  Intel core i3 processor - Intel® Pentium(R) CPU G2010 @ 2.80GHz
  4 gb ddr3 ram
  160 GB Hard disk
  Chmsee didnot install.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bamfdaemon 0.2.126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Feb 21 14:37:18 2014
  DuplicateSignature: package:bamfdaemon:0.2.126-0ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: bamf
  Title: package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1282847] Re: desktop ui scale is huge even though the setting is set to a scale of 1

[Iain Lane]

** Package changed: ubuntu-meta (Ubuntu) = gtk+3.0 (Ubuntu)

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

Title:
  desktop ui scale is huge even though the setting is set to a scale of
  1

Status in “gtk+3.0” package in Ubuntu:
  Confirmed

Bug description:
  I just updated and restarted the laptop. When it started, the gtk
  widgets are all huge. The unity shell is not scaled. I opened up the
  Display settings to find a new scale widget, which is currently set to
  1. Lowering it did not change anything. This is all experienced on a
  Macbook Pro Retina 11,1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.321
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 20 20:56:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1282944] Re: package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[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 bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1282944

Title:
  package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in “bamf” package in Ubuntu:
  New

Bug description:
  Insstallation of chmsee triggerred the crash of bamfdaemon. 
  Ubuntu 12.04.4 x64
  Gigabyte H61-S2P motherboard
  Intel core i3 processor - Intel® Pentium(R) CPU G2010 @ 2.80GHz
  4 gb ddr3 ram
  160 GB Hard disk
  Chmsee didnot install.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bamfdaemon 0.2.126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Feb 21 14:37:18 2014
  DuplicateSignature: package:bamfdaemon:0.2.126-0ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: bamf
  Title: package bamfdaemon 0.2.126-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1025839]

[Libreoffice-commits]

Michael Stahl committed a patch related to this issue.
It has been pushed to libreoffice-4-2:

http://cgit.freedesktop.org/libreoffice/core/commit/?id=138f41fd408b120d52e3d6c185940ace065512afh=libreoffice-4-2

fdo#41524: CUPS printing: use collate option when PDF is available


It will be available in LibreOffice 4.2.3.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds
Affected users are encouraged to test the fix and report feedback.

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

Title:
  Printing multiple copies submits multiple separate jobs (should submit
  one job)

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

Bug description:
  In the print dialog, if Number of Copies is set to 50 then 50
  separate, independent print jobs are spooled.  It should submit a
  single print job, specifying 50 copies.   This will allow the printer
  to do the replication if it can (all Postscript printers can).

  This is important because:
   
1) Submitting a separate jobs for each copy causes the page(s) to be 
rendered again and again,
with a drastic reduction in through-put.   

   This is CRUCIAL if the pages contain complex graphics or images which 
take a long time to render
   or transmit to the printer:   A one-minute delay for the first of 50 
copies is okay, but 1 minute for 
   *each* of 50 copies is intolerable.

2) If the print job was a mistake, it is virtually impossible to stop the 
printer.  Pressing the cancel
button on the printer cancels just one copy, but after a little while 
the next one starts printing...

3) It is very inconvenient to cancel the job in CUPS, with 50 separate 
jobs, without affecting other
unrelated jobs in the queue (you can cancel all jobs in the queue at 
once, or one at a time).

  Note that CUPS has always supported a number of copies option at the 
command-line level.
  For example
 lpr '-#50'  file.pdf
  prints 50 copies of the file, rendering it once only.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33
  Uname: Linux 3.0.0-22-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 17 11:49:58 2012
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1282952] Re: nm-applet crashed with SIGABRT in _start()

[Apport retracing service]

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

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 #1198373, 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/1282952/+attachment/3989341/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989343/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989350/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989351/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989352/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989353/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1282952/+attachment/3989354/+files/ThreadStacktrace.txt

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

** 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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1282952

Title:
  nm-applet crashed with SIGABRT in _start()

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

Bug description:
  I don't know how this came about but reporting according to apport
  system

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
  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: Thu Feb 20 15:28:55 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-12-08 (806 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.2  metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: nm-applet
  RfKill:
   
  Signal: 6
  SourcePackage: network-manager-applet
  StacktraceTop: _start ()
  Title: nm-applet crashed with SIGABRT in _start()
  UpgradeStatus: Upgraded to saucy on 2013-12-17 (65 days ago)
  UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse 
lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Adders05  3ad5b871-8dd5-4842-8135-db7b2600d9b0   
802-3-ethernet1392974869   Fri 21 Feb 2014 09:27:49 GMT   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1278653]

[Alberto Salvia Novella]

After 2 minutes the image is shown and LibreOffice Writer responds
again.

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

Title:
  LibreOffice Writer stops responding if an online image in the document
  cannot be loaded

Status in LibreOffice Productivity Suite:
  New
Status in One Hundred Papercuts:
  Triaged
Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  1. From your web browser, copy the 
http://cdn.acidcow.com/pics/20110408/smiles_21.jpg; image.
  2. Paste the image into a LibreOffice Writer document.

  **
  EXPECTED BEHAVIOUR
  **

  - The image to be pasted and shown.

  **
  REAL BEHAVIOUR
  **

  - LibreOffice Writer shows a square with the image's web link into it.
  - If you click or drag the square, LibreOffice Writer hangs.

  ***
  WORK-AROUND
  ***

  - If you see that the image is not being loaded, to undo the paste
  before doing anything else.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-writer 1:4.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Feb 11 00:50:02 2014
  InstallationDate: Installed on 2013-05-21 (265 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (115 days ago)

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

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

[Desktop-packages] [Bug 1278653]

[sophie]

Hi, under Debian 6 and LibreOffice 4.1.5.3, it takes a long time (almost
5 mn) to display the photo and if during this time you try to do
something else, Writer is unresponsive. Did you wait until the picture
is displayed? Sophie

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

Title:
  LibreOffice Writer stops responding if an online image in the document
  cannot be loaded

Status in LibreOffice Productivity Suite:
  New
Status in One Hundred Papercuts:
  Triaged
Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  1. From your web browser, copy the 
http://cdn.acidcow.com/pics/20110408/smiles_21.jpg; image.
  2. Paste the image into a LibreOffice Writer document.

  **
  EXPECTED BEHAVIOUR
  **

  - The image to be pasted and shown.

  **
  REAL BEHAVIOUR
  **

  - LibreOffice Writer shows a square with the image's web link into it.
  - If you click or drag the square, LibreOffice Writer hangs.

  ***
  WORK-AROUND
  ***

  - If you see that the image is not being loaded, to undo the paste
  before doing anything else.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-writer 1:4.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Feb 11 00:50:02 2014
  InstallationDate: Installed on 2013-05-21 (265 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (115 days ago)

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

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

[Desktop-packages] [Bug 1278653] Re: LibreOffice Writer stops responding if an online image in the document cannot be loaded

[Bug Watch Updater]

** Changed in: df-libreoffice
   Importance: High = Medium

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

Title:
  LibreOffice Writer stops responding if an online image in the document
  cannot be loaded

Status in LibreOffice Productivity Suite:
  New
Status in One Hundred Papercuts:
  Triaged
Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  1. From your web browser, copy the 
http://cdn.acidcow.com/pics/20110408/smiles_21.jpg; image.
  2. Paste the image into a LibreOffice Writer document.

  **
  EXPECTED BEHAVIOUR
  **

  - The image to be pasted and shown.

  **
  REAL BEHAVIOUR
  **

  - LibreOffice Writer shows a square with the image's web link into it.
  - If you click or drag the square, LibreOffice Writer hangs.

  ***
  WORK-AROUND
  ***

  - If you see that the image is not being loaded, to undo the paste
  before doing anything else.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-writer 1:4.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Feb 11 00:50:02 2014
  InstallationDate: Installed on 2013-05-21 (265 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (115 days ago)

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

[Corollax]

Sorry, not sure how to edit my last comment: I'm using an GeForce 630M.

Not sure if this helps, but it's strictly a visual freeze. The system
will recognize inputs after the freeze -- the screen just doesn't
update until you switch back and forth from the virtual terminals.

Hopefully that will help you debug the problem.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” package in Ubuntu:
  Opinion

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

[Corollax]

Same problem here.

Running a 64-bit 3.11.0-15-generic kernel on Mint 16 (based on Ubuntu
12.10) and both 319.60 and 331.20 drivers.

/proc/bus/input/devices reports an ETPS/2 Elantech Touchpad.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” package in Ubuntu:
  Opinion

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1239605] Re: Combo audio jack support (what did you plug in?-dialog)

[David Henningsson]

Actually, as of today ( version 14.04.0+14.04.20140219-0ubuntu1 of
unity-settings-daemon ) this functionality is released into 14.04
(ubuntu-desktop depends on unity-settings-daemon ).

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

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

Title:
  Combo audio jack support (what did you plug in?-dialog)

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  Won't Fix
Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released
Status in “unity-settings-daemon” source package in Precise:
  Won't Fix

Bug description:
  This is about a specific set of new laptops, which has only one 3.5 mm
  jack for analog audio, and where that jack can be used to plug in a
  headphone, headset, and in some cases, a microphone.

  Previously, these jacks have been able to distinguish - in hardware -
  between a headphone and a headset (i e headphone with mic), but it seems
  to be increasingly common that they don't have this ability.

  Our current solution, as it works in 13.10, is that for these machines
  one has to manually select the right input and output in sound settings.

  Here's an example on how the dialog looks in Windows:
  https://launchpadlibrarian.net/70431415/2011-03-08%2017.08.26.jpg -
  probably provided by Realtek 3rd party drivers.

  We can either choose to implement a similar dialog, or just to provide
  notify-OSD on plug of audio jack for user to choose between
  microphone, headphone/speakers, or headset if it is a four ring jack.
  Choosing the notify-OSD instead of an OSD is a compromise between
  making it easy for users to reconfigure jack and avoiding annoying
  distractions.

  Timeline wise it would be nice to merge this in the early 14.04 cycle.
  We also need to ship it in OSP2 (OEM Service Pack 2, shipped on 
pre-installs). Hence it would be good if we could have input/ack from design 
team ASAP, or at least by the end of October.

  https://wiki.ubuntu.com/Sound#unknown-device: When a device is
  plugged into an audio jack that can’t distinguish between
  headphones/speakers, headsets, or microphones, Ubuntu should display
  an “Unknown Audio Device” dialog...

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

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

[Desktop-packages] [Bug 1281938] Re: Mir shows an old frame on client startup (for Mesa GL clients)

[PS Jenkins bot]

Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown

** Changed in: mir
   Status: In Progress = Fix Committed

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

Title:
  Mir shows an old frame on client startup (for Mesa GL clients)

Status in Mir:
  Fix Committed
Status in “mesa” package in Ubuntu:
  Triaged

Bug description:
  Mir shows an old frame on client startup.

  Test case (1):
    1. Start and stop one client at a time:
   bin/mir_demo_client_egltriangle -s 500x500
   bin/mir_demo_client_eglflash -s 500x500
   ...
  Expected: Each client only shows its own frames
  Observed: The first frame of each client seems to be the last frame of the 
_previous_ client.

  Test case(2) - more definitive but requires hacking:
1. Insert a long sleep in your client code just before eglSwapBuffers
  Expected: The Mir server never shows the client till after the sleep has 
finished.
  Observed: The Mir server composites the client immediately on startup, with 
old/invalid pixel data. It only gets replaced with a valid frame after the 
sleep finishes.

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

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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Viktor Mileikovskyi]

I test the shortcat Alt+Shift.
It works only if shift pressed before alt. Pressing alt - pressing shift - 
releasing in any order does not work.
With best regards.
Viktor.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
    

[Desktop-packages] [Bug 1278735] Re: NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after hibernatioin resumed

[Yung Shen]

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

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

Title:
  NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after
  hibernatioin resumed

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

Bug description:
  It's a nvidia hybrid system, after successfully installed[0] nvidia
  driver, if you tried to hibernate then display will became garbled
  when resumed, it will freeze when it wake up, you can switch between
  VT to make it work again but the display will remain garbled, however
  all the other functions will still works.

  [0] nvidia instillation can follow this comment
  https://bugs.launchpad.net/jockey/+bug/1262539/comments/10

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.20-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Feb 11 02:18:48 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-331-updates
  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/1278735/+subscriptions

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

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

[Dmitry Shachnev]

The nm-applet issue is tracked in bug 1267100. The reporter had a fix
already, asked him to submit it to the sponsoring queue.

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

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

Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “gnome-panel” package in Ubuntu:
  Confirmed

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

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

  With previous glib (2.38+) none of this occurs

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

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

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

[Desktop-packages] [Bug 1278735] Re: NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after resumed from suspend or hibernate

[Yung Shen]

** Summary changed:

- NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after hibernatioin 
resumed
+ NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after resumed from 
suspend or hibernate

** Description changed:

  It's a nvidia hybrid system, after successfully installed[0] nvidia
- driver, if you tried to hibernate then display will became garbled when
- resumed, it will freeze when it wake up, you can switch between VT to
- make it work again but the display will remain garbled, however all the
- other functions will still works.
+ driver, if you tried to hibernate or suspend then display will became
+ garbled when resumed, it will freeze when it wake up, you can switch
+ between VT to make it work again but the display will remain garbled,
+ however all the other functions will still works.
  
- [0] nvidia instillation can follow this comment
+ [0] nvidia instillation can follow this comment, nvidia driver now can 
install correctly with jockey[1],
  https://bugs.launchpad.net/jockey/+bug/1262539/comments/10
+ 
+ [1] https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1279229
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.20-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Feb 11 02:18:48 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-331-updates
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Tags added: 201308-14114 blocks-hwcert

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

Title:
  NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after
  resumed from suspend or hibernate

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

Bug description:
  It's a nvidia hybrid system, after successfully installed[0] nvidia
  driver, if you tried to hibernate or suspend then display will became
  garbled when resumed, it will freeze when it wake up, you can switch
  between VT to make it work again but the display will remain garbled,
  however all the other functions will still works.

  [0] nvidia instillation can follow this comment, nvidia driver now can 
install correctly with jockey[1],
  https://bugs.launchpad.net/jockey/+bug/1262539/comments/10

  [1] https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1279229

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.20-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Feb 11 02:18:48 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-331-updates
  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/1278735/+subscriptions

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

[Desktop-packages] [Bug 1208333] Re: Change resolution with Mirror displays checked, extended mode will be trimmed

[Po-Hsu Lin]

Hello, it seems that this cannot be reproduced on Trusty dailylive

Verified on 201304-13249 HP Pavilion 14 Notebook PC
Steps:
1. Install 14.04 Trusty dailylive (Feb.20, 3.13.0-10), boot to desktop
2. Insert a HDMI cable, tick the Mirror displays option in display applet
3. Apply the resolution change from 1024x768 to 800x600
4. Cycle through display modes by pressing F4

Actual result:
* From step 4, it will change from:
1.  800x600 mirrored
2. 1024x768 mirrored
3. 1366x768 + 1920x1080 extended
4. 1920x1080 external monitor only
5. 1366x768 built-in display only
6. back to 1

Thanks

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

Title:
  Change resolution with Mirror displays checked, extended mode will
  be trimmed

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project precise series:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Boot up the device, then plug in HDMI/VGA port
  2. Check Mirror displays in Display of System Settings
  3. Set the screen to lower resolution (e.g. 800x600) and apply change
  4. Toggling Fn+F4 for a cycle, can't switch to extended mode

  Expected Result:
  Display modes should be Mirror mode - Extended mode - Internal only 
mode - External only mode

  Actual Result:
  Display modes are Mirror mode - Mirror mode - Internal only mode - 
External only mode

  Note:
  If unchecked Mirror displays and apply again, g-s-d can get the Xinerama 
configuration.

  Some error messages while running g-s-d in debug mode:

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **:
  gnome_rr_output_info_get_geometry: assertion `GNOME_IS_RR_OUTPUT_INFO
  (self)' failed

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **:
  gnome_rr_output_info_get_geometry: assertion `GNOME_IS_RR_OUTPUT_INFO
  (self)' failed

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **: 
gnome_rr_config_set_clone: assertion `GNOME_IS_RR_CONFIG (self)' failed
  === xinerama setup Configuration ===
none

  
  Since the gnome_rr_output_info_get_geometry() failed in 
compare_output_position(), 
trim_rightmost_outputs_that_dont_fit_in_framebuffer() will remove the Xinerama 
configuration in make_xinerama_setup().

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

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

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Alberto Milone]

Thanks for the patch and for the explanation, Daniel!

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  The BusID string created by prime-xconfig could be incorrect in any of
  the following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 1224217] Re: 50_ubuntu_sessions.patch causes gnome-flashback sessions not to load

[Dmitry Shachnev]

Tim wrote:
 gnome-panel.desktop and nautilus-classic.desktop, will need to have Unity 
 added to OnlyShowIn.

Adding a nautilus task then.

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

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

Title:
  50_ubuntu_sessions.patch causes gnome-flashback sessions not to load

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  New

Bug description:
  No errors in logs, no nothing. Just a desktop with right click
  Tried with existing  a new user account, same thing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-flashback 1:3.6.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Wed Sep 11 20:27:28 2013
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-08-07 (35 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1208333] Re: Change resolution with Mirror displays checked, extended mode will be trimmed

[Po-Hsu Lin]

Hello, it seems that this can be reproduced on Trusty dailylive

Verified on 201304-13249 HP Pavilion 14 Notebook PC
Steps:
1. Install 14.04 Trusty dailylive (Feb.20, 3.13.0-10), boot to desktop
2. Insert a HDMI cable, tick the Mirror displays option in display applet
3. Apply the resolution change from 1024x768 to 800x600
4. Cycle through display modes by pressing F4

Expected Result:
Display modes should be Mirror mode - Extended mode - Internal only 
mode - External only mode

Actual result:
* From step 4, it will change from:
1. 800x600 mirrored
2. 1024x768 mirrored
3. 1366x768 + 1920x1080 extended
4. 1920x1080 external monitor only
5. 1366x768 built-in display only
6. back to 1

Thanks

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

Title:
  Change resolution with Mirror displays checked, extended mode will
  be trimmed

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project precise series:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Boot up the device, then plug in HDMI/VGA port
  2. Check Mirror displays in Display of System Settings
  3. Set the screen to lower resolution (e.g. 800x600) and apply change
  4. Toggling Fn+F4 for a cycle, can't switch to extended mode

  Expected Result:
  Display modes should be Mirror mode - Extended mode - Internal only 
mode - External only mode

  Actual Result:
  Display modes are Mirror mode - Mirror mode - Internal only mode - 
External only mode

  Note:
  If unchecked Mirror displays and apply again, g-s-d can get the Xinerama 
configuration.

  Some error messages while running g-s-d in debug mode:

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **:
  gnome_rr_output_info_get_geometry: assertion `GNOME_IS_RR_OUTPUT_INFO
  (self)' failed

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **:
  gnome_rr_output_info_get_geometry: assertion `GNOME_IS_RR_OUTPUT_INFO
  (self)' failed

  (gnome-settings-daemon:4025): GnomeDesktop-CRITICAL **: 
gnome_rr_config_set_clone: assertion `GNOME_IS_RR_CONFIG (self)' failed
  === xinerama setup Configuration ===
none

  
  Since the gnome_rr_output_info_get_geometry() failed in 
compare_output_position(), 
trim_rightmost_outputs_that_dont_fit_in_framebuffer() will remove the Xinerama 
configuration in make_xinerama_setup().

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

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

[Desktop-packages] [Bug 1281759] Re: Unity don't start when i select Nvidia (Performance Mode)

[Alberto Milone]

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

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

Title:
  Unity don't start when i select Nvidia (Performance Mode)

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

Bug description:
  When I select, with tool nvidia-prime, in Nvidia X Server Settings,
  the Nvidia graphics card, after i did a log out and a new log in,
  Unity doesn't start, i can see only my background and I can operate on
  my OS using only the terminal. With the terminal i can open Nvidia X
  Server Setting, i can switch on my Intel graphyc card and after a
  reboot of my system Unity works.

  When i give the command lspci -n

  00:00.0 0600: 8086:0104 (rev 09)
  00:01.0 0604: 8086:0101 (rev 09)
  00:02.0 0300: 8086:0116 (rev 09)
  00:16.0 0780: 8086:1c3a (rev 04)
  00:1a.0 0c03: 8086:1c2d (rev 05)
  00:1b.0 0403: 8086:1c20 (rev 05)
  00:1c.0 0604: 8086:1c10 (rev b5)
  00:1c.1 0604: 8086:1c12 (rev b5)
  00:1c.3 0604: 8086:1c16 (rev b5)
  00:1c.5 0604: 8086:1c1a (rev b5)
  00:1d.0 0c03: 8086:1c26 (rev 05)
  00:1f.0 0601: 8086:1c49 (rev 05)
  00:1f.2 0106: 8086:1c03 (rev 05)
  00:1f.3 0c05: 8086:1c22 (rev 05)
  01:00.0 0300: 10de:1058 (rev a1)
  03:00.0 0280: 8086:08ae
  04:00.0 0c03: 1b21:1042
  05:00.0 0200: 1969:1083 (rev c0)

  This is nvidia-prime-upstart.log

  No bbswitch can be found 1st attempt
  Moving xorg.conf away
  Configuring alternatives
  Info: the intel profile is already in use
  Disabling the NVIDIA card

  This is prime-supported.log

  Laptop detected

  This is prime-switch.log

  Moving xorg.conf away
  Configuring alternatives
  Disabling the NVIDIA card

  This is prime-offload.log

  Sorry the nvidia kernel module is not is loaded

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

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

[Desktop-packages] [Bug 1270568] Re: Mesa 10.0 red screen in all games of Steam for Ubuntu with enable Anti-aliasing Msaa

[madbiologist]

What graphics hardware are you using?

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

Title:
  Mesa 10.0 red screen in all games of Steam for Ubuntu with enable
  Anti-aliasing Msaa

Status in “mesa” package in Ubuntu:
  New

Bug description:
  Sorry my English...

  Ubuntu version: 13.10 Saucy Salamander 64 bit.
  Kernels tested: 3.12.8 - 3.13rc - 3.2 - 3.11-15.
  OpenGl version:  3.0 Mesa 10.1.0-devel (git-1c5e296 saucy-oibaf-ppa+curaga)
  Games tested: Left 4 Dead 2, Portal 2, Team Fortress 2, No More Room in Hell.
  Msaa tested: 2x Msaa to 8x Msaa. All with red screen. 
  Image of the Bug (red screen - L4D2): http://k38.kn3.net/D/A/4/A/B/9/BDF.png

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

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

[Desktop-packages] [Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

[Apport retracing service]

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

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 #1234934, 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/1282997/+attachment/3989492/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989494/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989498/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989499/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989500/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989501/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1282997/+attachment/3989502/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  Unfortunately, I don't understand what I did to make this happen. I
  simply put an MP3 to play, then closed the rhythmbox window, and saw
  the error dialog. I can't reproduce the problem consistently, but it
  happens from time to time.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic i686
  NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c nvram ctr 
ccm dm_crypt joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_via crc32_pclmul aesni_intel 
snd_hda_intel aes_i586 xts snd_hda_codec parport_pc lrw gf128mul ppdev arc4 
ablk_helper cryptd snd_hwdep snd_pcm iwldvm snd_page_alloc snd_seq_midi rfcomm 
bnep snd_seq_midi_event snd_rawmidi bluetooth mac80211 snd_seq iwlwifi psmouse 
cfg80211 serio_raw snd_seq_device rtsx_pci_ms microcode snd_timer memstick snd 
soundcore mei_me lpc_ich mei mac_hid lp parport hid_generic usbhid hid i915 
i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper drm r8169 ahci rtsx_pci mii libahci 
video wmi
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 21 10:57:05 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2013-08-19 (186 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  SegvAnalysis:
   Segfault happened at: 0xb70180a8:mov%edi,0x28(%eax)
   PC (0xb70180a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1283003] [NEW] [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Fabien Lusseau]

Public bug reported:

Hi,

I found a bug in Ubuntu 14.04 !

I tried to pair a bluetooth stereo headset (A2DP compatible). The
pairing process goes well, but after that I can't select it on the audio
preferences.

When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
I must mention that it worked very well on Ubuntu 12.04.

This bug can be in the bluetooth stack or in unity-control-center or
maybe pulseaudio. I actually have no idea.

** Affects: unity-control-center
 Importance: Undecided
 Status: New

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


** Tags: regression regression-release

** Also affects: unity-control-center
   Importance: Undecided
   Status: New

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Unity Control Center:
  New
Status in “unity-control-center” package in Ubuntu:
  New

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1224217] Re: 50_ubuntu_sessions.patch causes gnome-flashback sessions not to load

[Launchpad Bug Tracker]

** Branch linked: lp:~mitya57/nautilus/lp1224217

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

Title:
  50_ubuntu_sessions.patch causes gnome-flashback sessions not to load

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  New

Bug description:
  No errors in logs, no nothing. Just a desktop with right click
  Tried with existing  a new user account, same thing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-flashback 1:3.6.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Wed Sep 11 20:27:28 2013
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-08-07 (35 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Alberto Milone]

Also, the git branches are now up-to-date

** Description changed:

- The BusID string created by prime-xconfig could be incorrect in any of
- the following cases:
+ SRU request:
+ 
+ Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.
+ 
+ [Rationale]
+ The fix .
+ 
+ [Impact]
+ Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).
+ 
+ [Test Case]
+ 1) Install the update on a hybrid system with Intel/NVIDIA GPUs
+ 2) Make sure that the system can boot and that X doesn't fail.
+ 
+ [Regression Potential]
+ Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.
+ 
+ 
+ [Full Explanation]
+ The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:
  
  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.
  
  Besides the potential correctness issues, the generated BusID string is
  missing the following recommended (but optional) information:
  
  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains
  
  A patch against nvidia-prime 0.5.5 from Trusty is attached. The version
  on github seems to be behind that version by quite a bit.

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-prime - 0.5.6

---
nvidia-prime (0.5.6) trusty; urgency=low

  [ Daniel Dadap ]
  * prime-xconfig:
- Format the BusID string correctly (LP: #1282796).
  The BusID string created by prime-xconfig had several problems:
  1) It was missing the bus type PCI, as recommended by
 xorg.conf(5).
  2) Values were written in hexadecimal, as reported by lspci,
 instead of decimal, as expected by the server. (See the
 comment at the top of xf86ParsePciBusString().)
  3) The PCI domain was not specified.
  Giving the BusID string in the wrong format could cause the X
  server to fail to parse the BusID, or to parse numbers in the
  wrong base. On systems with more than one PCI domain, `lspci -n`
  output would include the domain number, which is omitted by
  default on systems with only one PCI domain. nv_get_id()
  expects the bus number to be the first field, which would not be
  correct when `lspci -n` reports the domain, as it does on
  systems with multiple domains.
  Fix these issues by always reporting the domain with `lspci -Dn`
  and using it in the BusID string, prepending PCI: to the
  BusID string, and printing all numeric values in decimal.
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 21 Feb 2014 09:50:34 
+0100

** Changed in: nvidia-prime (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

[mmalmeida]

From the discussion in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/130
a few worhtwile considerations:

- It is said that this is caused by UEFI bug though, since Samsung's special 
hardware features are disabled in UEFI mode. 
- It therefore only affects Samsung models running in UEFI mode (which is 
required for dual booting)


I'm trying to track down the UEFI problem. Any relevant information on the 
status of that is appreciated!

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

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

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as full max
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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

[Desktop-packages] [Bug 1278329] Re: [FFe] Qt 5.2

[Dmitry Shachnev]

Hi Timo, which of the blockers are still relevant? When do you expect it
to be ready?

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

Title:
  [FFe] Qt 5.2

Status in “qt3d-opensource-src” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  New
Status in “qtcreator” package in Ubuntu:
  New
Status in “qtcreator-plugin-ubuntu” package in Ubuntu:
  New
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  New
Status in “qtdoc-opensource-src” package in Ubuntu:
  New
Status in “qtfeedback-opensource-src” package in Ubuntu:
  New
Status in “qtgraphicaleffects-opensource-src” package in Ubuntu:
  New
Status in “qtimageformats-opensource-src” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  New
Status in “qtpim-opensource-src” package in Ubuntu:
  New
Status in “qtquick1-opensource-src” package in Ubuntu:
  New
Status in “qtquickcontrols-opensource-src” package in Ubuntu:
  New
Status in “qtscript-opensource-src” package in Ubuntu:
  New
Status in “qtsensors-opensource-src” package in Ubuntu:
  New
Status in “qtserialport-opensource-src” package in Ubuntu:
  New
Status in “qtsystems-opensource-src” package in Ubuntu:
  New
Status in “qttools-opensource-src” package in Ubuntu:
  New
Status in “qttranslations-opensource-src” package in Ubuntu:
  New
Status in “qtwebkit-examples-opensource-src” package in Ubuntu:
  New
Status in “qtwebkit-opensource-src” package in Ubuntu:
  New
Status in “qtx11extras-opensource-src” package in Ubuntu:
  New
Status in “qtxmlpatterns-opensource-src” package in Ubuntu:
  New

Bug description:
  Dear Release Team,

  Regarding Qt 5.2, what has been already achieved:
  - Qt modules built in a PPA 
https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2, including the 
git snapshot ones
  - Qt packaging synced up with Debian at least once during 5.2 cycle. Private 
headers usage dropped from many Ubuntu Touch packages so that Qt modules could 
drop them too. Most of the modules are syncable from Debian as is, although for 
PPA building reasons there are bzr packaging branches also for them.
  - ~80 dependent source packages have daily recipe builds from trunks to the 
same PPA, because of the Qt 5.2 ABI break and libqt5core5 - libqt5core5a 
library rename (http://bugs.debian.org/731261)
  - The ~80 packages build successfully both against Qt 5.0 and Qt 5.2, and all 
unit tests pass. This was tracked at http://pad.ubuntu.com/qt52-dependencies 
until now the work is essentially complete.
  - Ubuntu Touch mostly works, also the desktop Qt 5 applications work
  - Most of the system integration autopilot tests pass, but there has been 
found some work remaining.
  - The needed qtbase changes for Unity appmenu support for Qt 5 contributed to 
upstream - see bug #1157213.

  Key remaining tasks that are being worked upon daily by the respective teams:
  - A handful of unfixed critical bugs 
https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.2
  - Functional multimedia support on Ubuntu Touch - unfortunately the separate 
qtmultimedia-opensource-src-touch package still needs to be maintained by the 
Multimedia team to not modify upstream Qt Multimedia too much. This was earlier 
believed to be dropped with Qt 5.2, but the dropping is now targeted to happen 
with Qt 5.3.
  - More packaging syncing with 5.2.1, contribute remaining test enablement to 
Debian, provided by the QA team (most contributed already).
  - Get 'OK' from QA team image validation of Ubuntu Touch using Qt 5.2 - this 
means all Autopilot tests pass + dogfooding
  - Upload Qt + rebuild ~80 packages in the archive

  Considering all of the above, we'd like you to consider allowing a
  Feature Freeze Exception. Ubuntu is preaching daily quality even
  during the development cycle and so we want to avoid creating any
  regression in any flavor of Ubuntu before pushing it to the archive.
  For that, we'd like to continue working a little bit longer on this
  stabilization before pushing it to the archive, to ensure the upgrade
  will be as smooth as possible.

  The FFe would include the Qt modules listed at the following document:
  
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=19
  , including the Qt Creator 3.0 + Ubuntu plugin update from the SDK
  team. The other packages need only rebuild since all sources have been
  updated to detect Qt version where necessary and use a different
  codepath accordingly.

  Summaries of main Ubuntu-specific branch changes for packages not to be 
synced directly from Debian unstable (current status, see the doc linked above 
for details):
  - qtbase: Additional patches (5 upstream, 1 

[Desktop-packages] [Bug 1282796] Re: prime-xconfig can write an invalid BusID string

[Alberto Milone]

** Changed in: nvidia-prime (Ubuntu Precise)
Milestone: None = precise-updates

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

Title:
  prime-xconfig can write an invalid BusID string

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.

  [Rationale]
  The fix .

  [Impact]
  Without this work, X will fail to start in some cases (see the Full 
Explanation section) on systems with hybrid graphics (Intel/NVIDIA).

  [Test Case]
  1) Install the update on a hybrid system with Intel/NVIDIA GPUs
  2) Make sure that the system can boot and that X doesn't fail.

  [Regression Potential]
  Low. Thanks to this fix, the xorg.conf, if anything, will have greater 
chances to work.

  
  [Full Explanation]
  The BusID string created by prime-xconfig could be incorrect in any of the 
following cases:

  a) Any numeric component of the bus ID is greater than 9: prime-xconfig will 
write a hexadecimal value, but X will parse it as decimal.
  b) The system has more than one PCI domain: `lspci -n` will show the PCI 
domain, which is normally hidden on systems with a single PCI domain. This 
breaks the formatting assumptions made by nv_get_id() about which fields are in 
which position.

  Besides the potential correctness issues, the generated BusID string
  is missing the following recommended (but optional) information:

  a) Bus type. According to xorg.conf(5) this should be PCI:
  b) PCI domain: omission of this field could lead to problems on systems with 
multiple PCI domains

  A patch against nvidia-prime 0.5.5 from Trusty is attached. The
  version on github seems to be behind that version by quite a bit.

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

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

[Desktop-packages] [Bug 1278735] Re: NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after resumed from suspend or hibernate

[Daniel Manrique]

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  NVIDIA GK106GLM [Quadro K2100M] [10de:11fc] screen garbled after
  resumed from suspend or hibernate

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

Bug description:
  It's a nvidia hybrid system, after successfully installed[0] nvidia
  driver, if you tried to hibernate or suspend then display will became
  garbled when resumed, it will freeze when it wake up, you can switch
  between VT to make it work again but the display will remain garbled,
  however all the other functions will still works.

  [0] nvidia instillation can follow this comment, nvidia driver now can 
install correctly with jockey[1],
  https://bugs.launchpad.net/jockey/+bug/1262539/comments/10

  [1] https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1279229

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.20-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Feb 11 02:18:48 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-331-updates
  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/1278735/+subscriptions

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

[Desktop-packages] [Bug 997370] Re: Totem does not use the va-api gstreamer backend

[madbiologist]

julius - Isn't that a Haswell processor?  Ubuntu 13.04 was released with
version 1.0.17-1 of the va-api driver.  According to
http://lists.freedesktop.org/archives/libva/2012-November/001420.html
Haswell support was not added until version 1.0.19 of the va-api driver.

According to http://lists.freedesktop.org/archives/gstreamer-
devel/2013-April/040527.html MPEG-4:2 support was present in gstreamer-
va-api 0.5.3 (earlier than I mentioned in comment #11).  MPEG4 support
seems to have been present since the original gstreamer-va-api release,
but I'm unsure of which part of MPEG4.

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

Title:
  Totem does not use the va-api gstreamer backend

Status in Totem Movie Player:
  Confirmed
Status in “gstreamer-vaapi” package in Ubuntu:
  Confirmed
Status in “totem” package in Ubuntu:
  Confirmed

Bug description:
  installing gstreamer -vaapi from ubuntu repos breaks thumbnail generation in 
nautilus
  furthermore acceleration does not work in totem - cpu usage is as high as 
with software rendering.

  mplayer-vaapi works perfectly on the same system.

  gst-launch-0.10 -v filesrc location=~/test.mkv ! matroskademux ! vaapidecode 
! vaapisink
  makes it possible to use vaapi via commandline

  i did not find a way to use vaapi for mpeg4 part 2 video streams.

  and i wasnt able to find proper values for gstreamer-properties that
  fix thumbnails and acceleration in totem.

  id like to share debug information. just tell me what you need.

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

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

[Desktop-packages] [Bug 238629] Re: [i965] Java plugin causes massive Xorg CPU usage, fixed with XAA (UXA/EXA)

[David Matějček]

I don't think that the problem is driver or hardware. It seems the problem is X 
server/GTK implementation.
After the simple change in /etc/X11/xorg.conf I have found here in comments the 
Eclipse had 17 hours uptime with heavy refactoring and then I only turned off 
the computer. Eclipse never before lasted so long and GUI was not so fast.

Option  AccelMethod   xaa

I can't say that the cause is exactly same, but surely helped the same thing.
I don't know who and why thinks that the problem is only with Intel ...?

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

Title:
  [i965] Java plugin causes massive Xorg CPU usage, fixed with XAA
  (UXA/EXA)

Status in “firefox” package in Ubuntu:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  See #38131 - Java plugins (stable and the .10 beta) cause massive CPU spike 
and hang of FireFox UI.
  This goes away when changing from the default 'EXA' to 'XAA' 'AccelMethod' in 
Xorg.conf

  ProblemType: Bug
  Architecture: i386
  Date: Mon Jun  9 18:56:50 2008
  DistroRelease: Ubuntu 8.04
  Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu1~fta2~hardy
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.24-17-generic i686
  UnreportableReason: This is not a genuine Ubuntu package

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

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

[Desktop-packages] [Bug 1283021] [NEW] Backport upstream patch to keep non-seat0 X servers from touching VTs

[Laércio de Sousa]

Public bug reported:

Please apply the following xserver upstream patch to current trusty
package:

http://cgit.freedesktop.org/xorg/xserver/commit/?id=46cf2a60934076bf568062eb83121ce90b6ff596

This is the last one needed to get multiseat working properly without
need of systemd-multi-seat-x wrapper.

Thanks!

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


** Tags: multiseat

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

Title:
  Backport upstream patch to keep non-seat0 X servers from touching VTs

Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Please apply the following xserver upstream patch to current trusty
  package:

  
http://cgit.freedesktop.org/xorg/xserver/commit/?id=46cf2a60934076bf568062eb83121ce90b6ff596

  This is the last one needed to get multiseat working properly without
  need of systemd-multi-seat-x wrapper.

  Thanks!

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

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

[Desktop-packages] [Bug 989784] Re: writer hangs loading rtf

[madbiologist]

The file attached to comment #1 opens without a problem in LibreOffice
4.0.2.2 on Ubuntu 13.04 Raring Ringtail.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged = 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/989784

Title:
  writer hangs loading rtf

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.0-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
   *** 1:3.5.0-2ubuntu1 0
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop  wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/989784/+attachment/3109004/+files/solenvase12-4.rtf
  -O example.rtf  lowriter --nologo example.rtf

  is the file opens quickly and successfully.

  4) What happens instead is it hangs LO. It opens via MS Word 2010
  14.0.6112.5000 (32-bit).

  WORKAROUND: Use AbiWord.

  apt-cache policy abiword
  abiword:
Installed: 2.9.2+svn20120213-1
Candidate: 2.9.2+svn20120213-1
Version table:
   *** 2.9.2+svn20120213-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 
Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1282905] Re: unity-settings-daemon crashed with SIGSEGV in g_settings_backend_changed()

[Launchpad Bug Tracker]

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

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New = Confirmed

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  g_settings_backend_changed()

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

Bug description:
  maybe something wrong with skype

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140219-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Fri Feb 21 11:05:37 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-02-09 (12 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f46bbf452ac:mov(%rax,%r13,1),%rax
   PC (0x7f46bbf452ac) ok
   source (%rax,%r13,1) (0x) not located in a known VMA region 
(needed readable region)!
   destination %rax ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_backend_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  Title: unity-settings-daemon crashed with SIGSEGV in 
g_settings_backend_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1283021] Re: Backport upstream patch to keep non-seat0 X servers from touching VTs

[Laércio de Sousa]

Related bug: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1228095

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

Title:
  Backport upstream patch to keep non-seat0 X servers from touching VTs

Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Please apply the following xserver upstream patch to current trusty
  package:

  
http://cgit.freedesktop.org/xorg/xserver/commit/?id=46cf2a60934076bf568062eb83121ce90b6ff596

  This is the last one needed to get multiseat working properly without
  need of systemd-multi-seat-x wrapper.

  Thanks!

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

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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Kom-Si]

** Attachment added: Text entry setting
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1218322/+attachment/3989552/+files/text_entry.png

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock 

[Desktop-packages] [Bug 1270568] Re: Mesa 10.0 red screen in all games of Steam for Ubuntu with enable Anti-aliasing Msaa

[Juan Pablo Lauriente]

** Description changed:

  Sorry my English...
  
  Ubuntu version: 13.10 Saucy Salamander 64 bit.
  Kernels tested: 3.12.8 - 3.13rc - 3.2 - 3.11-15.
  OpenGl version:  3.0 Mesa 10.1.0-devel (git-1c5e296 saucy-oibaf-ppa+curaga)
  Games tested: Left 4 Dead 2, Portal 2, Team Fortress 2, No More Room in Hell.
- Msaa tested: 2x Msaa to 8x Msaa. All with red screen. 
+ Msaa tested: 2x Msaa to 8x Msaa. All with red screen.
  Image of the Bug (red screen - L4D2): http://k38.kn3.net/D/A/4/A/B/9/BDF.png
+ 
+ Hardware: ATI Radeon™ HD 5450.
+ ~$ lspci |grep VGA  01:00.0 VGA compatible controller: Advanced Micro 
Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
+ 
+ About 1 month ago the problem was corrected, but I am using another PPA
+ (xorg-edgers), so I do not know if it was already resolved in the PPA
+ oibaf.

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

Title:
  Mesa 10.0 red screen in all games of Steam for Ubuntu with enable
  Anti-aliasing Msaa

Status in “mesa” package in Ubuntu:
  New

Bug description:
  Sorry my English...

  Ubuntu version: 13.10 Saucy Salamander 64 bit.
  Kernels tested: 3.12.8 - 3.13rc - 3.2 - 3.11-15.
  OpenGl version:  3.0 Mesa 10.1.0-devel (git-1c5e296 saucy-oibaf-ppa+curaga)
  Games tested: Left 4 Dead 2, Portal 2, Team Fortress 2, No More Room in Hell.
  Msaa tested: 2x Msaa to 8x Msaa. All with red screen.
  Image of the Bug (red screen - L4D2): http://k38.kn3.net/D/A/4/A/B/9/BDF.png

  Hardware: ATI Radeon™ HD 5450.
  ~$ lspci |grep VGA  01:00.0 VGA compatible controller: Advanced Micro 
Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

  About 1 month ago the problem was corrected, but I am using another
  PPA (xorg-edgers), so I do not know if it was already resolved in the
  PPA oibaf.

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

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

[Desktop-packages] [Bug 1282677] Re: New upstream microreleases 9.3.3, 9.1.12, 8.4.20

[Marc Deslauriers]

Thanks pitti for preparing these! I'll test and publish them.

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

Title:
  New upstream microreleases 9.3.3, 9.1.12, 8.4.20

Status in “postgresql-8.4” package in Ubuntu:
  Invalid
Status in “postgresql-9.1” package in Ubuntu:
  Fix Released
Status in “postgresql-9.3” package in Ubuntu:
  Fix Released
Status in “postgresql-8.4” source package in Lucid:
  In Progress
Status in “postgresql-8.4” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Quantal:
  In Progress
Status in “postgresql-9.1” source package in Saucy:
  In Progress
Status in “postgresql-9.1” source package in Trusty:
  Fix Released
Status in “postgresql-9.3” source package in Trusty:
  Fix Released

Bug description:
  New PostgreSQL security/bug fix release today:
  http://www.postgresql.org/about/news/1506/

  Packages for all stable releases are on
  http://people.canonical.com/~pitti/packages/psql/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1282677/+subscriptions

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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Kom-Si]

Not quite so, @Viktor Mileikovskyi (v-mil). It depends on which button
you press first when setting the shortcut. I.e. it could be both
Shift+Alt L or Alt+Shift L (see screenshot). I have only two input
sources: English and Russian. So I set Shift+Alt L for next input and
Alt+Shift L for previous. Works like a charm, no matter which I press
first. Cheers...

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  

[Desktop-packages] [Bug 238629] Re: [i965] Java plugin causes massive Xorg CPU usage, fixed with XAA (UXA/EXA)

[Chris Wilson]

This bug is filed against -intel, where it has been fixed.

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

Title:
  [i965] Java plugin causes massive Xorg CPU usage, fixed with XAA
  (UXA/EXA)

Status in “firefox” package in Ubuntu:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  See #38131 - Java plugins (stable and the .10 beta) cause massive CPU spike 
and hang of FireFox UI.
  This goes away when changing from the default 'EXA' to 'XAA' 'AccelMethod' in 
Xorg.conf

  ProblemType: Bug
  Architecture: i386
  Date: Mon Jun  9 18:56:50 2008
  DistroRelease: Ubuntu 8.04
  Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu1~fta2~hardy
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.24-17-generic i686
  UnreportableReason: This is not a genuine Ubuntu package

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

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

[Desktop-packages] [Bug 286053] Re: gvfsd-sftp crashed with SIGSEGV in strlen()

[Bug Watch Updater]

** Changed in: gvfs
   Status: New = Expired

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

Title:
  gvfsd-sftp crashed with SIGSEGV in strlen()

Status in GVFS:
  Expired
Status in “gvfs” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gvfs

  Not sure where or what crashes every now and then.

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/lib/gvfs/gvfsd-sftp
  NonfreeKernelModules: ath_hal
  Package: gvfs-backends 1.0.1-0ubuntu5
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.2 /org/gtk/gvfs/exec_spaw/2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_ZA.UTF-8
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   strlen () from /lib/tls/i686/cmov/libc.so.6
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-sftp crashed with SIGSEGV in strlen()
  Uname: Linux 2.6.27-7-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

[Jon Schewe]

Brandon, what do you do in pavucontrol to get audio? I've installed the
app and started it up, but besides the checkboxes for different types of
audio (PCM, DTS, AC3, MPEG, EAC3) I don't see anything different from
the regular sound settings. I don't get anymore output devices listed as
options even when I'm showing all output devices.

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  In Progress
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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

[Desktop-packages] [Bug 1282851] Re: 24.3+1-2~ppa1~precise1 package

[Damien Cassou]

Dear Martin,

could you please report your bug to https://bugs.launchpad.net/emacs-
snapshot/ (which is my official issue tracker) instead of here (which is
Ubuntu's)?

Then, could you please execute these lines and write the result in your
bug report?

$ apt-cache policy emacs24
$ apt-cache policy libmagickwand5
$ lsb_release -c

Finally, could you please tell me all the steps to reproduce your
problem starting with emacs -Q

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

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

Title:
   24.3+1-2~ppa1~precise1 package

Status in “emacs24” package in Ubuntu:
  Invalid

Bug description:
  Hello Damien:

  can you please rebuild Emacs against the latest ImageMagick version? As I 
upgrade ImageMagick (I use it on a daily basis, just like Emacs) I've found 
that Emacs stopped working throwing with the following error message:
  emacs: error while loading shared libraries: libMagickWand.so.4: cannot open 
shared object file: No such file or directory

  Thank you very much for contributing this must-have PPA!
  Best regards.

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

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

[Desktop-packages] [Bug 1283034] [NEW] ibus-daemon crashed with SIGABRT in g_assertion_message()

[wolfy1339]

Public bug reported:

I just booted up and this hapened

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: ibus 1.5.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 21 07:29:09 2014
ExecutablePath: /usr/bin/ibus-daemon
InstallationDate: Installed on 2014-01-15 (37 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash apport-failed-retrace trusty

** Information type changed from Private to Public

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 902033] Re: Size 0 dots are large and visible

[madbiologist]

This should have been fixed in Ubuntu 13.04 Raring Ringtail.  Can you
test in Ubuntu 13.10 Saucy Salamander and confirm?

** Changed in: poppler (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Size 0 dots are large and visible

Status in Poppler:
  Confirmed
Status in “poppler” package in Ubuntu:
  Incomplete

Bug description:
  I'm creating some PDF files with dots of 0 size. In evince, they're
  visible: they're pretty large and off-center. In other viewers, such
  as Mac Preview and Adobe Reader on Mac, the dots are not visible.

  This code will generate a test file in R. There is a line of 10 dots
  going from lower left to upper right that should be visible. There's
  another line of 0mm dots going from upper left to lower right, and
  they should not be visible.

  library(grid)
  pdf(dotsizetest.pdf, width=4, height=4)
  x - y - 1:10
  pushViewport(plotViewport(c(5.1, 4.1, 4.1, 2.1)))
  pushViewport(dataViewport(x, y))
  grid.rect()
  grid.points(x, y)
  grid.points(x, 10-y, gp=gpar(fill=black), size=unit(0,mm))
  popViewport(2)
  dev.off()


  EXPECTED RESULT: 
  One diagonal line of dots

  ACTUAL RESULT:
  Two crossing diagonal lines of dots.

  
  $ lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  $ apt-cache policy evince
  evince:
Installed: 3.2.1-0ubuntu2
Candidate: 3.2.1-0ubuntu2
Version table:
   *** 3.2.1-0ubuntu2 0
  500 http://mirror.anl.gov/pub/ubuntu/ oneiric-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.2.0-0ubuntu1 0
  500 http://mirror.anl.gov/pub/ubuntu/ oneiric/main amd64 Packages

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

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

[Desktop-packages] [Bug 1283034]

[Apport retracing service]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Apport retracing service]

** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1283034/+attachment/3989619/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

** Tags removed: need-amd64-retrace

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Apport retracing service]

** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1283034/+attachment/3989617/+files/Stacktrace.txt

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Apport retracing service]

** Attachment added: StacktraceSource.txt
   
https://bugs.launchpad.net/bugs/1283034/+attachment/3989618/+files/StacktraceSource.txt

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 878906] Re: Not obvious that giving your account a password is not physical security

[Matthew Paul Thomas]

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  Not obvious that giving your account a password is not physical
  security

Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “ubiquity” package in Ubuntu:
  In Progress

Bug description:
  If you have a user account with a password, someone with physical
  access to your computer can still access your account by holding down
  Shift during startup, choosing recovery mode, and changing your
  password.

  This is an intractable problem. For example, from Microsoft's 10
  immutable laws of security: If a bad guy has unrestricted physical
  access to your computer, it's not your computer anymore.
  http://technet.microsoft.com/en-gb/library/cc722487.aspx#EIAA

  However, probably it isn't obvious to a non-professional that a
  password alone isn't enough to secure their stuff.

  So perhaps, wherever Ubuntu lets you set a password (Ubiquity, System
  Settings User Accounts), it should contain a brief (very brief)
  explanation of this. Something like: A password doesn’t protect
  against someone with physical access to the computer.

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

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

[Desktop-packages] [Bug 1283034] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()

[Jörg Frings-Fürst]

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

** This bug has been marked a duplicate of bug 1266970
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I just booted up and this hapened

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 07:29:09 2014
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2014-01-15 (37 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140112)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty

[Iain Lane]

Thanks, this is a bug in unity-settings-daemon that is fixed in
lp:~laney/unity-settings-daemon/always-gnome-screenshot which should be
uploaded to trusty soon

** Package changed: unity (Ubuntu) = unity-settings-daemon (Ubuntu)

** Branch linked: lp:~laney/unity-settings-daemon/always-gnome-
screenshot

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided = High

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

Title:
  Unable to make screenshot with PrintScreen key in Unity session in
  Trusty

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

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot with Print Screen keyboard button.

  The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and 
desired screenshot is not saved in ~/Pictures.
  Tested in guest and normal sessions.

  Please fix this bug. Do not forget about Alt+PrintScreen,
  Ctrl+PrintScreen and Ctrl+Shift+PrintScreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 20 19:40:24 2014
  DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Sony Corporation Device [104d:907a]
  InstallationDate: Installed on 2013-10-20 (123 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  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: Thu Feb 20 19:32:11 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1280699] [NEW] Main Menu Application Scrolls Up Unexpectly

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Main Menu application sometimes scrolls up when a check box is
toggled.

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

-- 
Main Menu Application Scrolls Up Unexpectly
https://bugs.launchpad.net/bugs/1280699
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alacarte 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 1280699] Re: Main Menu Application Scrolls Up Unexpectly

[Thaddäus Tintenfisch]

** Package changed: xfdesktop4 (Ubuntu) = alacarte (Ubuntu)

** Changed in: alacarte (Ubuntu)
   Status: Incomplete = New

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

Title:
  Main Menu Application Scrolls Up Unexpectly

Status in “alacarte” package in Ubuntu:
  New

Bug description:
  The Main Menu application sometimes scrolls up when a check box is
  toggled.

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

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

[Desktop-packages] [Bug 1207812] Re: iOS 7, Trust Prompt Looping

[Ingo Haschler]

Errors like libimobiledevice.so.2 not found fixed in ppa. There was a faulty 
symlink.
@jpv4433: I did never claim it was more than a qd fix, see post #113.

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

Title:
  iOS 7, Trust Prompt Looping

Status in “libimobiledevice” package in Ubuntu:
  Triaged

Bug description:
  The iPhone reporting Trust the currently connected computer? Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1275441] [NEW] unrequested screen brightness changes-ubuntu 13.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Prefer the screen brightness set to ~66%, occasionally I set to 95%.

Wherever the the setting is left, the next time I boot the brightness
has changed; usually to ~47%, sometimes 100%

Using a Dell Vostro 1720, dual booting Win7 Pro and Ubuntu 13.10
Plenty of hard drive available, plenty of ram available!

Just boot into 13.10, click onto 'Brightness|Lock', pull brightness bar
to ~66% and then return to use the m/c.

shut down sometime later, Just boot into 13.10, click onto
'Brightness|Lock', and lo  behold bar now at typically ~47%

Sometimes do not have to shut down,  brightness just changes.

gtw

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


** Tags: bot-comment saucy
-- 
unrequested screen brightness changes-ubuntu 13.10
https://bugs.launchpad.net/bugs/1275441
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-screensaver 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 1275441] Re: unrequested screen brightness changes-ubuntu 13.10

[John Kim]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command, as it will automatically gather 
debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and 
the name of the package affected. You can learn more about this functionality 
at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: saucy

** Package changed: ubuntu = gnome-screensaver (Ubuntu)

** Changed in: gnome-screensaver (Ubuntu)
   Status: New = Incomplete

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

Title:
  unrequested screen brightness changes-ubuntu 13.10

Status in “gnome-screensaver” package in Ubuntu:
  Incomplete

Bug description:
  Prefer the screen brightness set to ~66%, occasionally I set to 95%.

  Wherever the the setting is left, the next time I boot the brightness
  has changed; usually to ~47%, sometimes 100%

  Using a Dell Vostro 1720, dual booting Win7 Pro and Ubuntu 13.10
  Plenty of hard drive available, plenty of ram available!

  Just boot into 13.10, click onto 'Brightness|Lock', pull brightness
  bar to ~66% and then return to use the m/c.

  shut down sometime later, Just boot into 13.10, click onto
  'Brightness|Lock', and lo  behold bar now at typically ~47%

  Sometimes do not have to shut down,  brightness just changes.

  gtw

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

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

[Desktop-packages] [Bug 1044955] Re: Xorg.log contains BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)'

[Thomas Hood]

Sorry, I no longer own the laptop where I had the problem.

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

Title:
  Xorg.log contains BUG: triggered 'if (!dev-valuator ||
  dev-valuator-numAxes  2)'

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Incomplete

Bug description:
  If I use Displays... to resize the display of the external monitor I
  get the following messages, repeated about forty times (with different
  time stamp, obviously).

  [ 12472.040] (II) intel(0): Allocated new frame buffer 2752x1050 stride 
11264, tiled
  [ 12472.075] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [ 12472.075]
  Backtrace:
  [ 12472.075] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f922a950846]
  [ 12472.075] 1: /usr/bin/X (0x7f922a7c8000+0x622fe) [0x7f922a82a2fe]
  [ 12472.075] 2: /usr/bin/X (0x7f922a7c8000+0x62f6d) [0x7f922a82af6d]
  [ 12472.075] 3: /usr/bin/X (GetPointerEvents+0xe4) [0x7f922a82c304]
  [ 12472.075] 4: /usr/bin/X (0x7f922a7c8000+0x1730a6) [0x7f922a93b0a6]
  [ 12472.075] 5: /usr/bin/X (miPointerWarpCursor+0xe7) [0x7f922a93b527]
  [ 12472.075] 6: /usr/bin/X (0x7f922a7c8000+0x871b1) [0x7f922a84f1b1]
  [ 12472.075] 7: /usr/bin/X (0x7f922a7c8000+0x173a7c) [0x7f922a93ba7c]
  [ 12472.075] 8: /usr/bin/X (0x7f922a7c8000+0x112183) [0x7f922a8da183]
  [ 12472.075] 9: /usr/bin/X (0x7f922a7c8000+0xfd06e) [0x7f922a8c506e]
  [ 12472.075] 10: /usr/bin/X (RRPointerScreenConfigured+0x75) [0x7f922a8c5295]
  [ 12472.075] 11: /usr/bin/X (RRScreenSizeNotify+0x124) [0x7f922a8c7774]
  [ 12472.075] 12: /usr/bin/X (0x7f922a7c8000+0xc9876) [0x7f922a891876]
  [ 12472.075] 13: /usr/bin/X (ProcRRSetScreenSize+0x1e1) [0x7f922a8c7c81]
  [ 12472.076] 14: /usr/bin/X (0x7f922a7c8000+0x4e8a1) [0x7f922a8168a1]
  [ 12472.076] 15: /usr/bin/X (0x7f922a7c8000+0x3d7ba) [0x7f922a8057ba]
  [ 12472.076] 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7f922898376d]
  [ 12472.076] 17: /usr/bin/X (0x7f922a7c8000+0x3daad) [0x7f922a805aad]

  System information

  ThinkPad X220

  Ubuntu 12.04 with some packages upgraded to Quantal

  linux-image-3.5.0-10-generic  3.5.0-10.10 
  linux-image-extra-3.5.0-10-generic3.5.0-10.10 
  udev175-0ubuntu10  
  xserver-xorg  1:7.6+12ubuntu1 
  xserver-xorg-core 2:1.11.4-0ubuntu10.7 
  xserver-xorg-video-intel  2:2.17.0-1ubuntu4.1

  $ uname -a
  Linux tenerife 3.5.0-10-generic #10-Ubuntu SMP Mon Aug 13 15:23:58 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  $ lspci -s 00:02.0 -v
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Device 21da
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915
Kernel modules: i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1044955/+subscriptions

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

[Desktop-packages] [Bug 1193714] Re: bamfdaemon crashed with signal 5 in _XReply()

[databill]

This bug also affects to me. Everty time I poweron the mechine, this bug happen 
to occur.
Now I can not use Ubuntu any more, because I can not open any Apps on Graphic 
mode. I only can use it in traditional terminal mode(Ctrl_alt_f1).

wait for the release version.

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

Title:
  bamfdaemon crashed with signal 5 in _XReply()

Status in BAMF Application Matching Framework:
  Fix Committed
Status in BAMF 0.5 series:
  Fix Committed
Status in “bamf” package in Ubuntu:
  Fix Released

Bug description:
  This happened while search for an application in the dash.  Took out
  compiz in the process, somehow.  Fun.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: bamfdaemon 0.5.0daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 22 16:10:03 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  InstallationDate: Installed on 2012-12-09 (194 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121209)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, user)
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
  Signal: 5
  SourcePackage: bamf
  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
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: bamfdaemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sbuild sudo

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

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

[Desktop-packages] [Bug 1283088] [NEW] [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all

[Michael Che]

Public bug reported:

There is no sound playing. I have tried troubleshooting, but nothing
seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  michael1613 F pulseaudio
 /dev/snd/controlC0:  michael1613 F pulseaudio
 /dev/snd/pcmC0D0c:   michael1613 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe7f irq 16'
   Mixer name   : 'Realtek ID 888'
   Components   : 'HDA:10ec0888,103c2ab1,00100302'
   Controls  : 4
   Simple ctrls  : 3
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
   Mixer name   : 'ATI RS690/780 HDMI'
   Components   : 'HDA:1002791a,00791a00,0010'
   Controls  : 4
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Feb 21 10:08:45 2014
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_DevicesInUse:
 1613  1613  1613  michael   F pulseaudio
 /dev/snd/controlC0:  michael   F pulseaudio
 /dev/snd/pcmC0D0c:   michael   F...m pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.04
dmi.board.name: 2AB1
dmi.board.vendor: FOXCONN
dmi.board.version: 1.00
dmi.chassis.asset.tag: MXX0480WWR
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.04:bd09/07/2010:svnHewlett-Packard:pnp6654y:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6654y
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-03-10T08:57:06.571656

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


** Tags: amd64 apport-bug precise

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

Title:
  [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all

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

Bug description:
  There is no sound playing. I have tried troubleshooting, but nothing
  seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1613 F pulseaudio
   /dev/snd/controlC0:  michael1613 F pulseaudio
   /dev/snd/pcmC0D0c:   michael1613 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe7f irq 16'
 Mixer name : 'Realtek ID 888'
 Components : 'HDA:10ec0888,103c2ab1,00100302'
 Controls  : 4
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
 Mixer name : 'ATI RS690/780 HDMI'
 Components : 'HDA:1002791a,00791a00,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Feb 21 10:08:45 2014
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   1613  1613  1613  michael   F pulseaudio
   /dev/snd/controlC0:  michael   F pulseaudio
   /dev/snd/pcmC0D0c:   michael   F...m 

[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/unity-settings-daemon

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

Title:
  Unable to make screenshot with PrintScreen key in Unity session in
  Trusty

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

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot with Print Screen keyboard button.

  The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and 
desired screenshot is not saved in ~/Pictures.
  Tested in guest and normal sessions.

  Please fix this bug. Do not forget about Alt+PrintScreen,
  Ctrl+PrintScreen and Ctrl+Shift+PrintScreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 20 19:40:24 2014
  DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Sony Corporation Device [104d:907a]
  InstallationDate: Installed on 2013-10-20 (123 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  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: Thu Feb 20 19:32:11 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1266140] Re: fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to build

[Launchpad Bug Tracker]

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

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

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: New = Confirmed

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

Title:
  fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to
  build

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

Bug description:
  Well found a copy but hope it gives more infomation for ya's to help ya out 
but i was testing the new Kernel 3.13 rc-7 and on Ubuntu 14.04 LTS
   got a error while running at start up black screen though and mouse as X
  But got good news 2 on Kernel 3.12.0-8 the fglrx-updates works 100% at the 
moment
  did see some errors at (Ubuntu) start up screen press f12 while going and 
starting programs up i found 3 lines of errors but went to fast to copy on 
paper or something would that help?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 2:13.125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.13.0-031300rc7-generic
  Date: Sat Jan  4 20:17:46 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:fglrx-updates:2:13.125-0ubuntu1:/var/lib/dkms/fglrx-updates/13.125/build/2.6.x/kcl_acpi.c:796:59:
 error: ‘struct acpi_dev_node’ has no member named ‘handle’
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:0592]
  InstallationDate: Installed on 2013-12-10 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131209)
  MachineType: eMachines EL1360G
  PackageVersion: 2:13.125-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=930e52b6-4cde-4825-a126-04981105ac3d ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-C1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EL1360G
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr:
  dmi.product.name: EL1360G
  dmi.sys.vendor: eMachines
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  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.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sat Jan  4 20:27:27 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2
  xserver.video_driver: fglrx

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1283095] [NEW] fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build steam crashesd glXChoose visual failed

[vinibali]

Public bug reported:

after starting steam:
glxchoose visual failed
catalyst 14.1
Running Steam on ubuntu 14.04 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
Fontconfig error: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 70: 
non-double matrix element
Fontconfig error: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 70: 
non-double matrix element
Fontconfig warning: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 78: 
saw unknown, expected number
[0221/161802:WARNING:proxy_service.cc(958)] PAC support disabled because there 
is no system implementation
Steam: An X Error occurred
X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  157
Serial number of failed request:  39
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  156
Serial number of failed request:  40
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  156
Serial number of failed request:  41
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  156
Serial number of failed request:  42
xerror_handler: X failed, continuing
glXChooseVisual failedAssert( Assertion Failed: Fatal Error: glXChooseVisual 
failed 
):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamUI/Main.cpp:286

Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
Uploading dump (out-of-process) [proxy '']
/tmp/dumps/crash_20140221161804_5.dmp

theres also no GPU-acc at chrome

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:13.350-0ubuntu1
Uname: Linux 3.13.0-11.31-031400rc3-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
DKMSKernelVersion: 3.13.0-11.31-031400rc3-generic
Date: Thu Feb 20 14:22:34 2014
PackageVersion: 2:13.350-0ubuntu1
SourcePackage: fglrx-installer
Title: fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build steam
  crashesd glXChoose visual failed

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  after starting steam:
  glxchoose visual failed
  catalyst 14.1
  Running Steam on ubuntu 14.04 64-bit
  STEAM_RUNTIME is enabled automatically
  Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
  Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
  Installing breakpad exception handler for 
appid(steam)/version(1392853084_client)
  Fontconfig error: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 70: 
non-double matrix element
  Fontconfig error: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 70: 
non-double matrix element
  Fontconfig warning: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf, line 78: 
saw unknown, expected number
  [0221/161802:WARNING:proxy_service.cc(958)] PAC support disabled because 
there is no system implementation
  Steam: An X Error occurred
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
  Major opcode of failed request:  157
  Serial number of failed request:  39
  xerror_handler: X failed, continuing
  Steam: An X Error occurred
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
  Major opcode of failed request:  156
  Serial number of failed request:  40
  xerror_handler: X failed, continuing
  Steam: An X Error occurred
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
  Major opcode of failed request:  156
  Serial number of failed request:  41
  xerror_handler: X failed, continuing
  Steam: An X Error occurred
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
  Major opcode of failed request:  156
  Serial number of failed request:  42
  xerror_handler: X failed, continuing
  glXChooseVisual failedAssert( Assertion Failed: Fatal Error: glXChooseVisual 
failed 
):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamUI/Main.cpp:286

  Installing breakpad 

[Desktop-packages] [Bug 1245211] Re: gimp-2.8 SIGSEGV in g_slice_alloc() while idling

[Moses Moore]

forgot I already filed this bug; happens more than once a week now.

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

Title:
  gimp-2.8 SIGSEGV in g_slice_alloc() while idling

Status in “gimp” package in Ubuntu:
  New

Bug description:
  I often leave gimp minimized in the background, with no image loaded.
  After upgrading to Ubuntu 13.10, three times now I've had it crash while 
minimzed.

  The apport report says gimp-2.8 crashed with SIGSEGV in
  g_slice_alloc() and reading unknown VMA.

  I have trouble reproducing the error because it only happens when I'm
  *not* using gimp.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gimp 2.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sun Oct 27 11:55:29 2013
  InstallationDate: Installed on 2013-06-08 (141 days ago)
  InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1)
  MarkForUpload: True
  SourcePackage: gimp
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (8 days ago)

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

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

[Desktop-packages] [Bug 1245211] Re: gimp-2.8 SIGSEGV in g_slice_alloc() while idling

[Moses Moore]

I don't know how to get apport to give me a copy of the crash info,
instead of sending off into the aether and vanishing.  I can look at the
text on-screen and transcribe it here.

SegvAnalysis:
  Segfault happened at: 0xb6a4db2e g_slice_alloc+158: mov (%edit),%edx
  PC(0xb6a4db2e) ok
  source (%edi) (0x503b276e) not located in a known VMA region (needed 
readable region!)
  destination %edx ok
  Stack memory exhasted (SP below stack segment)
SegvReason: 
  reading unknown VMA
StackTraceTop:
  g_slice_alloc() from /lib/i386-linux-gnu/libglib-2.0.so.0
  g_slice_allo0() from /lib/i386-linux-gnu/libglib-2.0.so.0
  g_type_create_instance() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  ??() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  g_object_newv() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0

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

Title:
  gimp-2.8 SIGSEGV in g_slice_alloc() while idling

Status in “gimp” package in Ubuntu:
  New

Bug description:
  I often leave gimp minimized in the background, with no image loaded.
  After upgrading to Ubuntu 13.10, three times now I've had it crash while 
minimzed.

  The apport report says gimp-2.8 crashed with SIGSEGV in
  g_slice_alloc() and reading unknown VMA.

  I have trouble reproducing the error because it only happens when I'm
  *not* using gimp.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gimp 2.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sun Oct 27 11:55:29 2013
  InstallationDate: Installed on 2013-06-08 (141 days ago)
  InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1)
  MarkForUpload: True
  SourcePackage: gimp
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (8 days ago)

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

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

[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty

[Launchpad Bug Tracker]

This bug was fixed in the package unity-settings-daemon -
14.04.0+14.04.20140221-0ubuntu1

---
unity-settings-daemon (14.04.0+14.04.20140221-0ubuntu1) trusty; urgency=low

  [ Iain Lane ]
  * Always use gnome-screenshot directly, not the gnome-shell screenshot
interface. We aren't using the legacy keygrabber under Unity, but
neither can we use gnome-shell's interface since Unity doesn't
implement it. (LP: #1282649)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 21 Feb 2014 
13:48:58 +

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

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

Title:
  Unable to make screenshot with PrintScreen key in Unity session in
  Trusty

Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot with Print Screen keyboard button.

  The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and 
desired screenshot is not saved in ~/Pictures.
  Tested in guest and normal sessions.

  Please fix this bug. Do not forget about Alt+PrintScreen,
  Ctrl+PrintScreen and Ctrl+Shift+PrintScreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 20 19:40:24 2014
  DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Sony Corporation Device [104d:907a]
  InstallationDate: Installed on 2013-10-20 (123 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  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: Thu Feb 20 19:32:11 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1264600] Re: after upgrade 0.51 to 0.52 on ubuntu 14.04 no brightness control

[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/1264600

Title:
  after upgrade 0.51 to 0.52 on ubuntu 14.04 no brightness control

Status in “nvidia-prime” package in Ubuntu:
  Confirmed

Bug description:
  brightness control stop working after upgrade to 0.52. need grub
  acpi_osi='!Windows 2012 (is a problem because i don t have 10 levels
  of control, only 5

  asus k56cb default ubuntu kernel (i used upstream without no result)

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

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

[Desktop-packages] [Bug 1283088] Re: [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all

[Raymond]

http://voices.canonical.com/david.henningsson/2012/07/13/top-five-wrong-
ways-to-fix-your-audio/

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

Title:
  [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all

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

Bug description:
  There is no sound playing. I have tried troubleshooting, but nothing
  seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1613 F pulseaudio
   /dev/snd/controlC0:  michael1613 F pulseaudio
   /dev/snd/pcmC0D0c:   michael1613 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe7f irq 16'
 Mixer name : 'Realtek ID 888'
 Components : 'HDA:10ec0888,103c2ab1,00100302'
 Controls  : 4
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
 Mixer name : 'ATI RS690/780 HDMI'
 Components : 'HDA:1002791a,00791a00,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Feb 21 10:08:45 2014
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   1613  1613  1613  michael   F pulseaudio
   /dev/snd/controlC0:  michael   F pulseaudio
   /dev/snd/pcmC0D0c:   michael   F...m pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [p6654y, Realtek ID 888, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.04
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX0480WWR
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.04:bd09/07/2010:svnHewlett-Packard:pnp6654y:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6654y
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-03-10T08:57:06.571656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1283088/+subscriptions

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

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Tom Chiverton]

Also occurs on my Dell Latitude E5430

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1283115] [NEW] [ffe] backport of some 3.8 improvements and bugfixes

[Sebastien Bacher]

Public bug reported:

The transition to unity-control-center is quite new, we didn't manage to
land all the code updates and fixes we wanted for ff but it would be
nice to get those for the LTS, that includes those updates:

* 
https://code.launchpad.net/~seb128/unity-control-center/users-backport-commits/+merge/207686
* 
https://code.launchpad.net/~seb128/unity-control-center/bluetooth-hide-indicator/+merge/207567
* 
https://code.launchpad.net/~xnox/unity-control-center/versioned-logo/+merge/207574

** Affects: unity-control-center (Ubuntu)
 Importance: High
 Status: Confirmed

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = High

** Changed in: unity-control-center (Ubuntu)
   Status: New = Confirmed

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

Title:
  [ffe] backport of some 3.8 improvements and bugfixes

Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  The transition to unity-control-center is quite new, we didn't manage
  to land all the code updates and fixes we wanted for ff but it would
  be nice to get those for the LTS, that includes those updates:

  * 
https://code.launchpad.net/~seb128/unity-control-center/users-backport-commits/+merge/207686
  * 
https://code.launchpad.net/~seb128/unity-control-center/bluetooth-hide-indicator/+merge/207567
  * 
https://code.launchpad.net/~xnox/unity-control-center/versioned-logo/+merge/207574

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

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

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Tom Chiverton]

Can any one else confirm that directly changing via the command line is
instant ? It certainly is for me eg.

$ cat /sys/class/backlight/intel_backlight/max_brightness 
976
$ cat /sys/class/backlight/intel_backlight/brightness 
123
$ echo 600 | sudo tee /sys/class/backlight/intel_backlight/brightness
600
$ echo 200 | sudo tee /sys/class/backlight/intel_backlight/brightness
200

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1283112] [NEW] Locally-integrated menus (LIM) stick to recently restored window even when disabled

[Edwin Pujols]

Public bug reported:

If I maximize a window and then restore it, the LIM will appear on the
title bar even when the option is disabled under Appearance. The menus
will disappear if I open a new window (of any application).

**Steps to reproduce**

 - Open Firefox
 - Maximize it
 - Restore it (via dragging, key binding, or button).

If you hover over the title bar the LIM is drawn. If you open a new
window and focus it, the LIM will be gone.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140220-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Feb 21 11:39:29 2014
InstallationDate: Installed on 2014-01-14 (38 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

** Summary changed:

- Locally-integrated menus (LIM) stick to recently restored windows even when 
disabled
+ Locally-integrated menus (LIM) stick to recently restored window even when 
disabled

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

Title:
  Locally-integrated menus (LIM) stick to recently restored window even
  when disabled

Status in “unity” package in Ubuntu:
  New

Bug description:
  If I maximize a window and then restore it, the LIM will appear on the
  title bar even when the option is disabled under Appearance. The menus
  will disappear if I open a new window (of any application).

  **Steps to reproduce**

   - Open Firefox
   - Maximize it
   - Restore it (via dragging, key binding, or button).

  If you hover over the title bar the LIM is drawn. If you open a new
  window and focus it, the LIM will be gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Feb 21 11:39:29 2014
  InstallationDate: Installed on 2014-01-14 (38 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1283109] Re: unity-control-center crashed with SIGSEGV in __GI___pthread_mutex_lock()

[Apport retracing service]

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

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 #1281590, 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/1283109/+attachment/3989717/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989719/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989720/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989721/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989722/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989723/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1283109/+attachment/3989724/+files/ThreadStacktrace.txt

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

** 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 unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1283109

Title:
  unity-control-center crashed with SIGSEGV in
  __GI___pthread_mutex_lock()

Status in “unity-control-center” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  unity-control-center:
Installiert:   14.04.3+14.04.20140220.1-0ubuntu1
Installationskandidat: 14.04.3+14.04.20140220.1-0ubuntu1
Versionstabelle:
   *** 14.04.3+14.04.20140220.1-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Tried to start the system settings app which produced this error while
  starting. Functionality didn't seem to be affected.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140220.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 16:32:36 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-02-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221)
  ProcCmdline: unity-control-center appearance
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb02493414 __GI___pthread_mutex_lock+4:  mov
0x10(%rdi),%esi
   PC (0x7feb02493414) ok
   source 0x10(%rdi) (0x20d8) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   start_thread (arg=0x7feacf3cc700) at pthread_create.c:312
  Title: unity-control-center crashed with SIGSEGV in 
__GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1283118] [NEW] eclipse (kepler) and 3.8 close but the window progresse information stay

[lemoineo]

Public bug reported:

Hello,
under Mint (petra/cinnamon), the eclipse program close normally (no process) 
but in the middle of the screen, a pretty window stay Progress Information. 
The -, + and x are on the right corner, but no action when i click under.
The window stay before all others windows , 
it is very unpleasant. 
Thanks for your ideas

** Affects: at-spi (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  eclipse (kepler) and 3.8 close but the window progresse information
  stay

Status in “at-spi” package in Ubuntu:
  New

Bug description:
  Hello,
  under Mint (petra/cinnamon), the eclipse program close normally (no process) 
  but in the middle of the screen, a pretty window stay Progress Information. 
  The -, + and x are on the right corner, but no action when i click under.
  The window stay before all others windows , 
  it is very unpleasant. 
  Thanks for your ideas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/1283118/+subscriptions

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

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Tom Chiverton]

Might this be upstream kernel issue :
https://bugzilla.kernel.org/show_bug.cgi?id=63931 ?

** Bug watch added: Linux Kernel Bug Tracker #63931
   http://bugzilla.kernel.org/show_bug.cgi?id=63931

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1266140] Re: fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to build

[J Cord]

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

I was able to get fglrx-updates running with the following work around:

From init Terminal Mode ( cntl + alt  F1) ran sudo apt-get install 
fglrx-updates, then
note the suggested deb pkg's listed as suggested and installed them FIRST, 
before proceeding with the amd driver installation.

I installed them fisrt, along with all their dependencies which were
listed,  one of which was FAKE ROOT, which may not be installed through
the gui installer possibly part of the problem ???.

After those were all installed (debhelper etc and depends)  then I
installed  fglrx-updates and it's depends and the installation completed
without error and have the correct divers installed and working
correctly now.

I am on kernel 3.13.0-11 on an intel sandy bridge i7 2600-k with amd ati
asus 6570 gpu.

Sorry apport was crashing on me also this morning cannot provide log ,
however, what what I could see it was basically the same description and
problem as already posted.  Hopefully this will help someone else until
a fix is released.  This worked for me. Good Luck !

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

Title:
  fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to
  build

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

Bug description:
  Well found a copy but hope it gives more infomation for ya's to help ya out 
but i was testing the new Kernel 3.13 rc-7 and on Ubuntu 14.04 LTS
   got a error while running at start up black screen though and mouse as X
  But got good news 2 on Kernel 3.12.0-8 the fglrx-updates works 100% at the 
moment
  did see some errors at (Ubuntu) start up screen press f12 while going and 
starting programs up i found 3 lines of errors but went to fast to copy on 
paper or something would that help?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 2:13.125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.13.0-031300rc7-generic
  Date: Sat Jan  4 20:17:46 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:fglrx-updates:2:13.125-0ubuntu1:/var/lib/dkms/fglrx-updates/13.125/build/2.6.x/kcl_acpi.c:796:59:
 error: ‘struct acpi_dev_node’ has no member named ‘handle’
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:0592]
  InstallationDate: Installed on 2013-12-10 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131209)
  MachineType: eMachines EL1360G
  PackageVersion: 2:13.125-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=930e52b6-4cde-4825-a126-04981105ac3d ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:13.125-0ubuntu1: fglrx-updates kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-C1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EL1360G
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr:
  dmi.product.name: EL1360G
  dmi.sys.vendor: eMachines
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  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.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sat Jan  4 20:27:27 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 

[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty

[Adolfo Jayme]

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988374/+files/BootDmesg.txt

** Attachment removed: BootLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988375/+files/BootLog.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988376/+files/CurrentDmesg.txt

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988377/+files/Dependencies.txt

** Attachment removed: DpkgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988378/+files/DpkgLog.txt

** Attachment removed: GconfCompiz.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988379/+files/GconfCompiz.txt

** Attachment removed: LightdmDisplayLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988380/+files/LightdmDisplayLog.txt

** Attachment removed: LightdmGreeterLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988381/+files/LightdmGreeterLog.txt

** Attachment removed: LightdmGreeterLogOld.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988382/+files/LightdmGreeterLogOld.txt

** Attachment removed: LightdmLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988383/+files/LightdmLog.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988384/+files/Lspci.txt

** Attachment removed: Lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988385/+files/Lsusb.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988386/+files/ProcCpuinfo.txt

** Attachment removed: ProcEnviron.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988387/+files/ProcEnviron.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988388/+files/ProcInterrupts.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988389/+files/ProcModules.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988390/+files/UdevDb.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988391/+files/UdevLog.txt

** Attachment removed: UnitySupportTest.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988392/+files/UnitySupportTest.txt

** Attachment removed: XorgLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988393/+files/XorgLog.txt

** Attachment removed: XorgLogOld.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988394/+files/XorgLogOld.txt

** Attachment removed: Xrandr.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988395/+files/Xrandr.txt

** Attachment removed: xdpyinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988396/+files/xdpyinfo.txt

** Attachment removed: xserver.devices.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988397/+files/xserver.devices.txt

** Attachment removed: xserver.outputs.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+attachment/3988398/+files/xserver.outputs.txt

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

Title:
  Unable to make screenshot with PrintScreen key in Unity session in
  Trusty

Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot with Print Screen keyboard button.

  The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and 
desired screenshot is not saved in ~/Pictures.
  Tested in guest and normal sessions.

  Please fix this bug. Do not forget about Alt+PrintScreen,
  Ctrl+PrintScreen and Ctrl+Shift+PrintScreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: 

[Desktop-packages] [Bug 1008265] Re: nautilus Connect to Server infobars label not readable

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1008265

Title:
  nautilus Connect to Server infobars label not readable

Status in One Hundred Papercuts:
  Confirmed
Status in One Hundred Papercuts precise series:
  Confirmed
Status in One Hundred Papercuts raring series:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” source package in Precise:
  Confirmed

Bug description:
  The color of the error text in Nautilus ConnectToServer is light-grey
  w/ a pale yellow backround. Yuck. It's extremely difficult to read. My
  theme is Ambience (default theme)

  Replicate:
  In Nautilus:
  File
  Connect to Server
  127.0.1.1
  Press Connect
  Scratch Your head wondering what the error says.
  Quietly Weep.

  I will attatch a Screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-powerpc-smp 3.2.14
  Uname: Linux 3.2.0-24-powerpc-smp ppc
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: powerpc
  Date: Sun Jun  3 15:53:17 2012
  GsettingsChanges: org.gnome.nautilus.window-state geometry '794x598+65+24'
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release powerpc 
(20120423)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 996851] Re: highlighting current line does not work

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/996851

Title:
  highlighting current line does not work

Status in Light-Weight Text Editor for Gnome:
  Fix Released
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  The preference allows for the current line to be highlighted.  It used
  to work under 11.xx, it does not work under 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 10:02:06 2012
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
  SourcePackage: gedit
  UpgradeStatus: Upgraded to precise on 2012-05-01 (7 days ago)

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

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

[Desktop-packages] [Bug 1010189] Re: Characters are no longer hilited when searching

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1010189

Title:
  Characters are no longer hilited when searching

Status in “ubuntu-themes” package in Ubuntu:
  Triaged

Bug description:
  In previous version of gucharmap, when you used Ctrl+F to search for a
  character, the current match would have a hilighted background so you
  can see which one it is.

  In the current version on Ubuntu 12.04, this is no longer the case.
  The display still scrolls to show the currently matched character, and
  the text at the bottom-left shows the correct character, but the
  actual entry is no longer highlighted.

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

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

[Desktop-packages] [Bug 535490] Re: some dialogs in rhythmbox use tooltip's background color and are unreadable

[Matthew Paul Thomas]

** 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 rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/535490

Title:
  some dialogs in rhythmbox use tooltip's background color and are
  unreadable

Status in “rhythmbox” package in Ubuntu:
  Fix Released
Status in “ubuntu-themes” package in Ubuntu:
  Triaged
Status in “rhythmbox” source package in Lucid:
  Won't Fix
Status in “ubuntu-themes” source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: light-themes

  Rhythmbox uses GeditMessageArea which is old, custom widget (I guess from 
gedit ;) ) replaced in the recent GTK+ by GtkInfoBar. It doesn't support 
changing urgency of the message and uses background color which is the same as 
the one used in tooltips. On the new Ubuntu themes the background color for 
tooltips is aubergine so it is used by the rhythmbox - the effect is pretty bad 
as can be seen on the attached screenshot.
  Now it may be that the GeditMessageArea should be fixed to either don't get 
color from tooltip or to change font color based on the theme - I'm not sure 
though so the bug is reported against both packages for now.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: c796df2c03d28b45a22c8d1850f0e643
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  Date: Wed Mar 10 04:17:49 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100201)
  Package: light-themes 0.1.5.6
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.24-generic-pae
  SourcePackage: light-themes
  Uname: Linux 2.6.32-16-generic-pae i686

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

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

[Desktop-packages] [Bug 671550] Re: Eclipse content assist popup

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/671550

Title:
  Eclipse content assist popup

Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: light-themes

  The selected item in the Eclipse content assist popup window is
  unreadable with Ambiance/Radiance

  Versions:
  Ubuntu 10.10
  light-themes 0.1.8.2
  Eclipse 3.5 and 3.6

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

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

[Desktop-packages] [Bug 835096] Re: Tables of contents in help are orange on blue

[Matthew Paul Thomas]

** 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 yelp in Ubuntu.
https://bugs.launchpad.net/bugs/835096

Title:
  Tables of contents in help are orange on blue

Status in “ubuntu-themes” package in Ubuntu:
  Confirmed
Status in “yelp” package in Ubuntu:
  New

Bug description:
  light-themes  0.1.8.22, Ubuntu Ocelot

  1. Launch Terminal, or Ubuntu Software Center, or Aisleriot Solitaire.
  2. Open the help from the Help menu.

  What you see: Orange links on a blue background.

  I mean, using bright orange in an OS theme is bad enough, but ...
  orange on blue? Really?

  What you should see: Neutral colors.

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

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

[Desktop-packages] [Bug 893174] Re: Increased terminal padding under precise: 160 columns of 8-pixel wide no longer fit at 72 point on 1280 pixel display

[Matthew Paul Thomas]

** 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 vte in Ubuntu.
https://bugs.launchpad.net/bugs/893174

Title:
  Increased terminal padding under precise: 160 columns of 8-pixel wide
  no longer fit at 72 point on 1280 pixel display

Status in Gnome Virtual Terminal Emulator:
  Invalid
Status in “ubuntu-themes” package in Ubuntu:
  Incomplete
Status in “vte” package in Ubuntu:
  Confirmed

Bug description:
  Laptop screen resolution is 1280x800.

  Set gnome-terminal font to Ubuntu Mono 11.

  In Oneiric, I was able to fit two terminals side by side without any
  overlap. In fact, they fit without overlap and without causing the
  launcher to autohide.

  After upgrading to Precise, the terminals now push over into the
  launcher area, causing it to autohide, and even then, they still
  overlap. Notice the terminal on the right, the 'a' in 'achiang' is
  covered up by the terminal on the left.

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

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

[Desktop-packages] [Bug 556746] Re: When radio items are disabled dots should be dimmed

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/556746

Title:
  When radio items are disabled dots should be dimmed

Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: light-themes

  See screenshot.  I think the radio dot should be grey as well.
  When menu item is disabled , corresponding radio button it should be drawn 
with the same color as the text.

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

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

[Desktop-packages] [Bug 617435] Re: Disclosure triangles are tiny and have no padding to their left

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/617435

Title:
  Disclosure triangles are tiny and have no padding to their left

Status in Ayatana Design:
  Fix Committed
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  light-themes 0.1.6.8, Ubuntu Maverick
  light-themes 0.1.8.21, Ubuntu Ocelot

  In both Ambiance and Radiance themes, disclosure triangles are tiny
  and have no padding to their left. This looks like a mistake, and
  makes it difficult for people to see they can expand a branch.

  In 0.1.6.8 this was a problem in Ambiance only, but now it is a
  problem in both of the Light themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/617435/+subscriptions

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

[Desktop-packages] [Bug 393585] Re: Focused/unfocused selection colors are confusingly similar

[Matthew Paul Thomas]

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/393585

Title:
  Focused/unfocused selection colors are confusingly similar

Status in One Hundred Papercuts:
  Invalid
Status in “community-themes” package in Ubuntu:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Invalid
Status in “ubuntu-themes” package in Ubuntu:
  Incomplete

Bug description:
  Problem occurs with: Ambiance, Radiance, Clearlooks, DarkRoom,  Dust, 
Elementary, Glossy, Human, Human-Clearlooks
  Does not occur with: New Wave

  For example, open a Nautilus window and select an icon.  Switch focus
  to the desktop by clicking on it.  The window is not active but the
  icon in it retains the selected items color.  It appears as though
  it is still selected and that it can be modified by keyboard
  shortcuts.  By clicking on an icon on the desktop it changes color to
  be selected an now it appears that two items are selected.

  Several times I've deleted things by accident due to this, especially
  when I was new to GNOME.  I would have several windows open with items
  selected.  I would see the item I want selected and hit the delete key
  to remove it, only to realize that I had some other window focused
  where I had deleted something else.

  In Windows selected items in unfocused windows turn gray.  I think it
  also adds another visual clue as to what window is focused besides
  just the title bar.

  Firefox and Thunderbird deliver the behavior I expect (probably
  because they are only faux GTK apps).  Select some text in Firefox and
  then focus to another window and you will see that the selected text
  turns gray, indicating it is not active.  Try that in gedit or evince
  and the text will remain blue.

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

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

[Desktop-packages] [Bug 1093440] Re: ugly scaled volume control icon in OSD display when using Ambiance theme

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1093440

Title:
  ugly scaled volume control icon in OSD display when using Ambiance
  theme

Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  When using the Ambiance theme and using the keyboard key to change the
  volume, the volume is displayed in OSD along an icon. This icon
  appears to be a low resolution icon scaled up, and is really ugly.

  If I switch to another theme like Adwaita, the icon used is an icon at
  the correct resolution and appears sharp and nice.

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

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

[Desktop-packages] [Bug 1040912] Re: Logout/Suspend/Shutdown button missing after upgrade to Ubuntu 12.04 LTS

[Matthew Paul Thomas]

** 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 light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1040912

Title:
  Logout/Suspend/Shutdown button missing after upgrade to Ubuntu 12.04
  LTS

Status in “ubuntu-themes” package in Ubuntu:
  New

Bug description:
  Logout/Power off icon and other icons missing from desktop after upgrade to 
12.04.
  The error was due to the Theme setting in Appearance configuration being 
left unitialized. The Theme selctor drop down menu was blank. Switching it to a 
different them and then setting it back to the default reinitializes the 
Appearance theme and all icons and buttons reappear. Please initialize the 
Appearance theme to the actual default.

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

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

[Desktop-packages] [Bug 1272001] Re: Evolution black background in mail display

[Matthew Paul Thomas]

** 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 evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1272001

Title:
  Evolution black background in mail display

Status in “evolution” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  New

Bug description:
  With different GT3 theme (tested : Adwaita, Zukitwo and Zukiwi),
  Evolution 3.10 display e-mail with a black background. I put a
  screenshot in attachment.

  It's work but it's very ugly ! Please, give us a workaround.

  --

  I wanna attach this bug to the package evolution but the package
  search (Choose...) refuse to give me a link and display to my screen
  Too many matches. Please try to narrow your search.. So I choose to
  target evolution-common.

  Have a nice day.
  Jo.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2012-05-11 (634 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  Package: evolution 3.10.3-0ubuntu3~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags: third-party-packages saucy gnome3-ppa
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-11-08 (88 days ago)
  UserGroups: adm audio cdrom dip fuse kvm libvirtd lpadmin plugdev sambashare 
sudo vboxusers vdr video weston-launch

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

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

[Desktop-packages] [Bug 1025935] Re: Thunderbird 14.0 scrollbars have a wrong background [regression]

[Matthew Paul Thomas]

** Project changed: light-themes = ubuntu-themes (Ubuntu)

** No longer affects: light-themes (Ubuntu)

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

Title:
  Thunderbird 14.0 scrollbars have a wrong background [regression]

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  Confirmed
Status in “ubuntu-themes” package in Ubuntu:
  New

Bug description:
  I have updated to Thunderbird 14.0 via the update manager recently.
  However, there is some issue with the scroll bars. They have a
  background that does not fit at all.

  Have a look at the attached screenshot.

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

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