[Desktop-packages] [Bug 1350182] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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 #1295480, 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/1350182/+attachment/4165599/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165601/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165603/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165604/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165605/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165606/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1350182/+attachment/4165607/+files/ThreadStacktrace.txt

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

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1350182

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Open Tab, copy in tab, delete folder, Open Tab, Close Tab... Close
  windows of nautilus... Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu12
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Jul 30 00:28:24 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-04-27 (93 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x479e69:  cmp%rax,(%rdx)
   PC (0x00479e69) ok
   source "%rax" ok
   destination "(%rdx)" (0x0004c300) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Bill Filler]

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** No longer affects: android (Ubuntu)

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

Title:
  Poor microphone quality (mako)

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

[Desktop-packages] [Bug 1309727] Re: headphone button does not answer or hangup phone call.

[Bill Filler]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

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

Title:
  headphone button does not answer or hangup phone call.

Status in Dialer app for Ubuntu Touch:
  Triaged
Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Summary:
  headphone button does not answer or hangup phone call.

  Steps:
  1. plug in headphones with a call/hangup button in headphone jack
  2.  call the phone with the headphones plugged in with step 1
  3.  press headphone answer/hangup button

  expected results:
  call is answered

  actual results
  nothing happens. 

  
  Additional info, this should also play/pause music when no call is in session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1309727/+subscriptions

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

[Desktop-packages] [Bug 1278569] Re: ibus breaks emacs and eclipse control-space keybinding

[Aron Xu]

For MineCraft, there is problem in its keyboard handling code and no
input method is working with it, including other input fields within the
program cannot be working. It's a different issue that should be handled
by MineCraft.

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

Title:
  ibus breaks emacs and eclipse control-space keybinding

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Installing ibus 1.5.5-1ubuntu1 breaks Emacs 24's control-space
  keybinding.  I generally have that bound to a custom lisp function,
  but by default (e.g. starting with `emacs -Q`) it is bound to set-
  mark-command.  After doing a dist-upgrade in Trusty which installs
  ibus 1.5.5-1ubuntu1, emacs no longer even sees the control-space key
  chord.  My guess is that ibus is consuming this event, preventing
  emacs from seeing it.  This is a critical regression that makes emacs
  almost unusable.

  By process of elimination, I've narrowed it down to one of these 4
  binary packages.

  gir1.2-ibus-1.0
  ibus
  ibus-gtk
  ibus-gtk3

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 10 15:15:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-06 (66 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1309894] Re: [Satellite C665, Conexant CX20585, Speaker, Internal] fails after a while

[Николай]

This helps in my case, looks like the related bug is very similar 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1283168/comments/3

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

Title:
  [Satellite C665, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I Upgrade the OS from 12.04 to 14.04 and getting issue with sound as
  sometime it  works and after a while sound is not coming to speaker as
  it is working fine with headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ritesh 1762 F pulseaudio
    ritesh 6359 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 19 14:52:53 2014
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite C665, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd11/09/2011:svnTOSHIBA:pnSatelliteC665:pvrPSC14G-01900V:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C665
  dmi.product.version: PSC14G-01900V
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca.

[Hristo Erinin]

Hello,

This problem still exists in 14.04.

Alt+Super+S  shortcut as suggested by Vladimir Rutsky works.

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

Title:
  There is no apparent way to stop Orca.

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

Bug description:
  The "Orca Screen Reader" icon in the Dash is a trap. If a user
  accidentally opens it, the only apparent recourse for the incessant
  jabber is to either mute the volume system-wide or log out. This makes
  for a very poor user experience.

  Orca could avoid this situation by providing at least one of the
  following:

1) A notification of how to stop it, if there is a way to stop it.
2) A confirmation prompt prior to starting.
3) A quit option in a standard location such as the indicator menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-orca 3.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 18:35:02 2013
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-orca
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1350104] Re: package fglrx (not installed) failed to install/upgrade: subprocesso novo script pre-installation retornou erro do status de saída 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: fglrx-installer (Ubuntu)
   Importance: Undecided => Low

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Invalid

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

Title:
  package fglrx (not installed) failed to install/upgrade: subprocesso
  novo script pre-installation retornou erro do status de saída 1

Status in “fglrx-installer” package in Ubuntu:
  Invalid

Bug description:
  ATI HD7700

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 29 23:33:49 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:fglrx:(not installed):subprocesso novo script 
pre-installation retornou erro do status de saída 1
  ErrorMessage: subprocesso novo script pre-installation retornou erro do 
status de saída 1
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde LE [Radeon HD 7730/8730] 
[1002:6837] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e228]
  InstallationDate: Installed on 2014-05-04 (86 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=84cace65-29f4-460e-9779-81024b402167 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: fglrx-installer
  Title: package fglrx (not installed) failed to install/upgrade: subprocesso 
novo script pre-installation retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/05/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jul 29 23:48:30 2014
  xserver.configfile: default
  xserver.devices:
   
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or 
incompatible.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1256569] Re: EMU 0202 volume control not working

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  EMU 0202 volume control not working

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

Bug description:
  Hello,

  I'm using Ubuntu 13.10 and I have EMU 0202 USB audio interface.
  Everything is working correctly except that I can't change the master
  volume. I've tried to lower the output volume from gnome control
  center and alsamixer, but both have absolutely no effect on the output
  volume. However, muting is working ok.

  The built-in Intel audio interface is working without such problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1256569/+subscriptions

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

[Desktop-packages] [Bug 755406] Re: Mouse offset problem when using a WINE application maximized

[Launchpad Bug Tracker]

[Expired for Unity because there has been no activity for 60 days.]

** Changed in: unity
   Status: Incomplete => Expired

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

Title:
  Mouse offset problem when using a WINE application maximized

Status in Compiz:
  Expired
Status in Compiz Core:
  Won't Fix
Status in Unity:
  Expired
Status in “compiz” package in Ubuntu:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  When putting Picasa in fullscreen, all controls on the screen are
  drawn as expected (window without title bar) but the mouse has to be
  the size of the title bar BELOW these controls. There seems to be a
  y-offset of the height of the title bar.

  I only noticed this for Picasa for now, but I found a report from
  another user of this behavior there:
  http://answers.unity3d.com/questions/44091/mouse-input-offset-problem-
  in-web-fullscreen .

  I attached a screenshot. Please notice the mouse pointer being below
  the button, but the button is highlighted. Also the original title bar
  is shining through the slightly transparent globalmenu-bar. Picasa is
  3.8 installed into the original Picasa 3.x-wine-environment from
  Google (picasa-package). This is on Natty with today's updates.

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

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

[Desktop-packages] [Bug 577309] Re: gdm 2.30.0-0ubuntu5 failed to install /var/lib/gdm/.cache/login_frequency.cache

[Launchpad Bug Tracker]

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

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

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

Title:
   gdm 2.30.0-0ubuntu5 failed to install
  /var/lib/gdm/.cache/login_frequency.cache

Status in “gdm” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gdm

  lucid updated

  into /var/log/daemon.log: Unable to write to login cache file:
  /var/lib/gdm/.cache/login_frequency.cache

  looking there, /var/lib/gdm/ is empty, no .cache

  i've removing/purging gdm with synaptic and console too but got error
  :exist with status 1, then i've found a silent crash

  gdm folder into /var/lib/ have an icon with 2 white cross lines over
  it

  running: sudo dpkg-reconfigure gdm does not help

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: gdm 2.30.0-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic-pae i686
  NonfreeKernelModules: nvidia
  AptOrdering: gdm: Purge
  Architecture: i386
  Date: Sat May  8 08:04:19 2010
  ErrorMessage: le sous-processus script post-removal installé a retourné une 
erreur de sortie d'état 1
  SourcePackage: gdm
  Title: package gdm 2.30.0-0ubuntu5 failed to install/upgrade: le 
sous-processus script post-removal installé a retourné une erreur de sortie 
d'état 1

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

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

[Desktop-packages] [Bug 755406] Re: Mouse offset problem when using a WINE application maximized

[Launchpad Bug Tracker]

[Expired for Compiz because there has been no activity for 60 days.]

** Changed in: compiz
   Status: Incomplete => Expired

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

Title:
  Mouse offset problem when using a WINE application maximized

Status in Compiz:
  Expired
Status in Compiz Core:
  Won't Fix
Status in Unity:
  Expired
Status in “compiz” package in Ubuntu:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  When putting Picasa in fullscreen, all controls on the screen are
  drawn as expected (window without title bar) but the mouse has to be
  the size of the title bar BELOW these controls. There seems to be a
  y-offset of the height of the title bar.

  I only noticed this for Picasa for now, but I found a report from
  another user of this behavior there:
  http://answers.unity3d.com/questions/44091/mouse-input-offset-problem-
  in-web-fullscreen .

  I attached a screenshot. Please notice the mouse pointer being below
  the button, but the button is highlighted. Also the original title bar
  is shining through the slightly transparent globalmenu-bar. Picasa is
  3.8 installed into the original Picasa 3.x-wine-environment from
  Google (picasa-package). This is on Natty with today's updates.

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

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

[Desktop-packages] [Bug 755406] Re: Mouse offset problem when using a WINE application maximized

[Launchpad Bug Tracker]

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

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

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

Title:
  Mouse offset problem when using a WINE application maximized

Status in Compiz:
  Expired
Status in Compiz Core:
  Won't Fix
Status in Unity:
  Expired
Status in “compiz” package in Ubuntu:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  When putting Picasa in fullscreen, all controls on the screen are
  drawn as expected (window without title bar) but the mouse has to be
  the size of the title bar BELOW these controls. There seems to be a
  y-offset of the height of the title bar.

  I only noticed this for Picasa for now, but I found a report from
  another user of this behavior there:
  http://answers.unity3d.com/questions/44091/mouse-input-offset-problem-
  in-web-fullscreen .

  I attached a screenshot. Please notice the mouse pointer being below
  the button, but the button is highlighted. Also the original title bar
  is shining through the slightly transparent globalmenu-bar. Picasa is
  3.8 installed into the original Picasa 3.x-wine-environment from
  Google (picasa-package). This is on Natty with today's updates.

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

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

[Desktop-packages] [Bug 755406] Re: Mouse offset problem when using a WINE application maximized

[Launchpad Bug Tracker]

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

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

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

Title:
  Mouse offset problem when using a WINE application maximized

Status in Compiz:
  Expired
Status in Compiz Core:
  Won't Fix
Status in Unity:
  Expired
Status in “compiz” package in Ubuntu:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  When putting Picasa in fullscreen, all controls on the screen are
  drawn as expected (window without title bar) but the mouse has to be
  the size of the title bar BELOW these controls. There seems to be a
  y-offset of the height of the title bar.

  I only noticed this for Picasa for now, but I found a report from
  another user of this behavior there:
  http://answers.unity3d.com/questions/44091/mouse-input-offset-problem-
  in-web-fullscreen .

  I attached a screenshot. Please notice the mouse pointer being below
  the button, but the button is highlighted. Also the original title bar
  is shining through the slightly transparent globalmenu-bar. Picasa is
  3.8 installed into the original Picasa 3.x-wine-environment from
  Google (picasa-package). This is on Natty with today's updates.

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

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

[Desktop-packages] [Bug 315766] Re: [ooo-build] open .doc having images with negative crop looks wrong

[Bug Watch Updater]

** Changed in: openoffice
   Status: Confirmed => Won't Fix

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

Title:
  [ooo-build] open .doc having images with negative crop looks wrong

Status in The OpenOffice.org Suite:
  Won't Fix
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  If I open msword ".doc" files in openoffice writer that have images
  with negative crop, the image doesn't look good. Sometimes it
  disappears and sometimes it gets wrong size.

  The value entered under the crop-tab in word isn't the same that is
  shown in openoffice. Things work better with positive crop, or no crop
  at all.

  The attached file has -0,5 cm an all edges if opened in msword, but in
  openoffice its NOT -0,5cm.

  $ lsb_release -rd
  Description:Ubuntu 8.10
  Release:8.10

  $ apt-cache policy openoffice.org-writer
  openoffice.org-writer:
Installed: 1:2.4.1-11ubuntu2.1
Candidate: 1:2.4.1-11ubuntu2.1
Version table:
   *** 1:2.4.1-11ubuntu2.1 0
  500 http://se.archive.ubuntu.com intrepid-updates/main Packages
  500 http://security.ubuntu.com intrepid-security/main Packages
  100 /var/lib/dpkg/status
   1:2.4.1-11ubuntu2 0
  500 http://se.archive.ubuntu.com intrepid/main Packages

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

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

[Desktop-packages] [Bug 267676] Re: [ooo-build] SVG invisible when inserted to document, in exported PDF too

[Bug Watch Updater]

** Changed in: openoffice
   Status: Confirmed => Fix Released

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

Title:
  [ooo-build] SVG invisible when inserted to document, in exported PDF
  too

Status in The OpenOffice.org Suite:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Put the test SVG into clean document. Image is invisible immediately, and 
also in exported PDF
  file. If PNG is created from the SVG, it is both displayed and exported 
correctly.

  The bug is reported upstream too, however OOo claims, that the bug is
  not related to vanilla OOo package, and Ubuntu uses some other build
  that is out of their scope.

  For details, please look at
  http://www.openoffice.org/issues/show_bug.cgi?id=93411

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

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

[Desktop-packages] [Bug 207220] Re: [Upstream] [ooo-build] cursor does not change to arrow hovering over "X" box

[Bug Watch Updater]

** Changed in: openoffice
   Status: Confirmed => Invalid

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

Title:
  [Upstream] [ooo-build] cursor does not change to arrow hovering over
  "X" box

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/207220/+attachment/2134007/+files/Unbenannt%201.doc
  && lowriter -nologo Unbenannt\ 1.doc

  hover ones mouse cursor over the checkbox and it changes from the I to
  an arrow.

  4) What happens instead is it remains an I.

  Original Reporter Comments: Ubuntu hardy beta, OOo 2.4.0-rc2-1ubuntu3

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

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

[Desktop-packages] [Bug 315766]

[Msvec-u]

SUSE no longer offers a LibreOffice product (and this was not filed
as a service request against a subscription back then), so this is
not going to be addressed by SUSE any more.

Please check with a recent openSUSE release (13.1) and a recent LO
(4.2) and if the bug still persists please open a new bug report at
the LO bug tracker: https://www.libreoffice.org/get-help/bug/
Thanks.

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

Title:
  [ooo-build] open .doc having images with negative crop looks wrong

Status in The OpenOffice.org Suite:
  Won't Fix
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  If I open msword ".doc" files in openoffice writer that have images
  with negative crop, the image doesn't look good. Sometimes it
  disappears and sometimes it gets wrong size.

  The value entered under the crop-tab in word isn't the same that is
  shown in openoffice. Things work better with positive crop, or no crop
  at all.

  The attached file has -0,5 cm an all edges if opened in msword, but in
  openoffice its NOT -0,5cm.

  $ lsb_release -rd
  Description:Ubuntu 8.10
  Release:8.10

  $ apt-cache policy openoffice.org-writer
  openoffice.org-writer:
Installed: 1:2.4.1-11ubuntu2.1
Candidate: 1:2.4.1-11ubuntu2.1
Version table:
   *** 1:2.4.1-11ubuntu2.1 0
  500 http://se.archive.ubuntu.com intrepid-updates/main Packages
  500 http://security.ubuntu.com intrepid-security/main Packages
  100 /var/lib/dpkg/status
   1:2.4.1-11ubuntu2 0
  500 http://se.archive.ubuntu.com intrepid/main Packages

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

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

[Desktop-packages] [Bug 1350163] Re: [regression] Mir GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

[Daniel van Vugt]

Added a "Mir" task back in, temporarily just so the team can find this
bug.

** Summary changed:

- [regression] Mir GL clients crash immediately on startup (Mesa is trying to 
use X11 instead of Mir)
+ [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is trying 
to use X11 instead of Mir)

** Changed in: mir
   Status: Invalid => New

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

Title:
  [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is
  trying to use X11 instead of Mir)

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  In Progress

Bug description:
  [regression] Mir GL clients crash immediately on startup.

  This is on a freshly updated utopic system.

  (gdb) bt
  #0  0x7ff4f1b706d7 in XGetXCBConnection ()
 from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x7ff4f352abb1 in dri2_initialize_x11_dri2 (drv=, 
  disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
  #2  dri2_initialize_x11 (drv=, disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
  #3  0x7ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
  at ../../../../../src/egl/main/egldriver.c:613
  #4  0x7ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910, 
  test_only=test_only@entry=0) at 
../../../../../src/egl/main/egldriver.c:643
  #5  0x7ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
  at ../../../../../src/egl/main/eglapi.c:355
  #6  0x00402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8, 
  width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
  at /home/dan/bzr/mir/dev/examples/eglapp.c:386
  #7  0x00401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
  at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

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

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

[Desktop-packages] [Bug 1350163] Re: [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

[Daniel van Vugt]

Actually, make it "New" for Mir. If there's some symbol we've
accidentally hidden then that's a Mir bug.

** Changed in: mesa (Ubuntu)
   Status: New => In Progress

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

Title:
  [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is
  trying to use X11 instead of Mir)

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  In Progress

Bug description:
  [regression] Mir GL clients crash immediately on startup.

  This is on a freshly updated utopic system.

  (gdb) bt
  #0  0x7ff4f1b706d7 in XGetXCBConnection ()
 from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x7ff4f352abb1 in dri2_initialize_x11_dri2 (drv=, 
  disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
  #2  dri2_initialize_x11 (drv=, disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
  #3  0x7ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
  at ../../../../../src/egl/main/egldriver.c:613
  #4  0x7ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910, 
  test_only=test_only@entry=0) at 
../../../../../src/egl/main/egldriver.c:643
  #5  0x7ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
  at ../../../../../src/egl/main/eglapi.c:355
  #6  0x00402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8, 
  width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
  at /home/dan/bzr/mir/dev/examples/eglapp.c:386
  #7  0x00401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
  at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

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

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

[Desktop-packages] [Bug 207220]

[Gp-v]

The document is, unfortunately, not available any more under that URL.

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

Title:
  [Upstream] [ooo-build] cursor does not change to arrow hovering over
  "X" box

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/207220/+attachment/2134007/+files/Unbenannt%201.doc
  && lowriter -nologo Unbenannt\ 1.doc

  hover ones mouse cursor over the checkbox and it changes from the I to
  an arrow.

  4) What happens instead is it remains an I.

  Original Reporter Comments: Ubuntu hardy beta, OOo 2.4.0-rc2-1ubuntu3

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

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

[Desktop-packages] [Bug 267676]

[Gp-v]

This works for me with LibreOffice 4.2.  I can see text "DT" running
from top to bottom (at a 90 degree angle).

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

Title:
  [ooo-build] SVG invisible when inserted to document, in exported PDF
  too

Status in The OpenOffice.org Suite:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Put the test SVG into clean document. Image is invisible immediately, and 
also in exported PDF
  file. If PNG is created from the SVG, it is both displayed and exported 
correctly.

  The bug is reported upstream too, however OOo claims, that the bug is
  not related to vanilla OOo package, and Ubuntu uses some other build
  that is out of their scope.

  For details, please look at
  http://www.openoffice.org/issues/show_bug.cgi?id=93411

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

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

[Desktop-packages] [Bug 543183]

[V-cameron]

Any progress on this yet? As was mentioned earlier, this can be a major
inconvenience in an enterprise environment.

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

Title:
  Updating system certificates requires rebuild

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Triaged
Status in “firefox” package in Fedora:
  Unknown

Bug description:
  Binary package hint: firefox

  Hi,
  Updating the list of trusted root certificate authorities across all users of 
a system seems requires rebuilding a library. Non-root certificates may 
similarly be impacted.

  update-ca-certificates could be a mechanism  to update the root
  certificates used by firefox.

  On a corporate install of firefox, currently the only options to adding an 
internal root certificate authority are to:
 * Hack it into the user creation script to extract a pre-created profile, 
and update all the existing users profile directory. This bypasses the random 
profile directory creation.
 * Re-compile the shared library (.so) containing the root certificate 
authorities (extra maintenance for dealing with ubuntu package updates).
 * Have every user of the system go through a manual process of adding the 
root certificate (most users don't know how).
 * Use a plugin extension for firefox (do any exist?) that is automatically 
used by all users (can this be done?)
 * Have the root certificate signed at great expense by an external root 
certificate authority already included. CaCert integration would lower the cost 
but that seems far away, and is still an external authority. These root 
certificates also might be limited to a single domain (wildcard certificate?) 
or have other limitations ("low" expiry?, contractual restrictions...).

  It seems unlikely that Mozilla will move away from having the root
  certificates stored in the shared library as it would take some
  control away from them. The shared libary method makes it harder for
  malicious changes to be made, but only by adding the barier of
  recompilation and installation of a shared library.

  Thanks,

   Drew Daniels
  Resume: http://www.boxheap.net/ddaniels/resume.html

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

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

[Desktop-packages] [Bug 1350163] Re: [regression] Mir GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

[Daniel van Vugt]

At a guess we removed/changed some symbol in libmirclient (yesterday)
and that prevents libEGL from finding/using libmirclient properly.

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
   Importance: Undecided => Critical

** Changed in: mir
   Status: New => Invalid

** Changed in: mir
Milestone: None => 0.6.0

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

Title:
  [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is
  trying to use X11 instead of Mir)

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  In Progress

Bug description:
  [regression] Mir GL clients crash immediately on startup.

  This is on a freshly updated utopic system.

  (gdb) bt
  #0  0x7ff4f1b706d7 in XGetXCBConnection ()
 from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x7ff4f352abb1 in dri2_initialize_x11_dri2 (drv=, 
  disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
  #2  dri2_initialize_x11 (drv=, disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
  #3  0x7ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
  at ../../../../../src/egl/main/egldriver.c:613
  #4  0x7ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910, 
  test_only=test_only@entry=0) at 
../../../../../src/egl/main/egldriver.c:643
  #5  0x7ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
  at ../../../../../src/egl/main/eglapi.c:355
  #6  0x00402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8, 
  width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
  at /home/dan/bzr/mir/dev/examples/eglapp.c:386
  #7  0x00401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
  at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

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

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

[Desktop-packages] [Bug 1350163] Re: [regression] Mir GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

[Chris Halse Rogers]

** Project changed: mir => mesa (Ubuntu)

** Changed in: mesa (Ubuntu)
Milestone: 0.6.0 => None

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

Title:
  [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is
  trying to use X11 instead of Mir)

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  In Progress

Bug description:
  [regression] Mir GL clients crash immediately on startup.

  This is on a freshly updated utopic system.

  (gdb) bt
  #0  0x7ff4f1b706d7 in XGetXCBConnection ()
 from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x7ff4f352abb1 in dri2_initialize_x11_dri2 (drv=, 
  disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
  #2  dri2_initialize_x11 (drv=, disp=0x122e910)
  at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
  #3  0x7ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
  at ../../../../../src/egl/main/egldriver.c:613
  #4  0x7ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910, 
  test_only=test_only@entry=0) at 
../../../../../src/egl/main/egldriver.c:643
  #5  0x7ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
  at ../../../../../src/egl/main/eglapi.c:355
  #6  0x00402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8, 
  width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
  at /home/dan/bzr/mir/dev/examples/eglapp.c:386
  #7  0x00401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
  at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

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

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

[Desktop-packages] [Bug 1320280] Re: Caller has real bad audio quality

[Bill Filler]

confirmed, if you are the person on the receiving end talking to some
one on an Ubuntu Phone that audio quality sounds very muffled.

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

** Summary changed:

- Caller has real bad audio quality
+ audio quality bad when on call

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Tags added: rtm14

** No longer affects: dialer-app (Ubuntu)

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

Title:
  audio quality bad when on call

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Dear All!
  I have installed the ubuntu version 14.10 (r44) on my Nexus 4 and I have 
exactly the same problem as Henrik!
  I can hear the caller in good audio quality but the receiver hear my voice in 
very bad quality as I would use a yogurt cup ;-)

  I hope somebody has a solution for this problem and tell it me!

  Till then a lot of greetings here from a small village in Austria!
  Ulrix

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

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

[Desktop-packages] [Bug 1350163] [NEW] [regression] Mir GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[regression] Mir GL clients crash immediately on startup.

This is on a freshly updated utopic system.

(gdb) bt
#0  0x7ff4f1b706d7 in XGetXCBConnection ()
   from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
#1  0x7ff4f352abb1 in dri2_initialize_x11_dri2 (drv=, 
disp=0x122e910)
at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
#2  dri2_initialize_x11 (drv=, disp=0x122e910)
at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
#3  0x7ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
at ../../../../../src/egl/main/egldriver.c:613
#4  0x7ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910, 
test_only=test_only@entry=0) at ../../../../../src/egl/main/egldriver.c:643
#5  0x7ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
at ../../../../../src/egl/main/eglapi.c:355
#6  0x00402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8, 
width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
at /home/dan/bzr/mir/dev/examples/eglapp.c:386
#7  0x00401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

** Affects: mesa (Ubuntu)
 Importance: Critical
 Assignee: Chris Halse Rogers (raof)
 Status: New

-- 
[regression] Mir GL clients crash immediately on startup (Mesa is trying to use 
X11 instead of Mir)
https://bugs.launchpad.net/bugs/1350163
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mesa 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 1278569] Re: ibus breaks emacs and eclipse control-space keybinding

[Jonathan Paul]

This not only is affecting eclipse users, it's affecting people of all
different types of programs, including Minecraft players. It causes the
player to not be able to sprint (ctrl) and jump (space) at the same
time.

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

Title:
  ibus breaks emacs and eclipse control-space keybinding

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Installing ibus 1.5.5-1ubuntu1 breaks Emacs 24's control-space
  keybinding.  I generally have that bound to a custom lisp function,
  but by default (e.g. starting with `emacs -Q`) it is bound to set-
  mark-command.  After doing a dist-upgrade in Trusty which installs
  ibus 1.5.5-1ubuntu1, emacs no longer even sees the control-space key
  chord.  My guess is that ibus is consuming this event, preventing
  emacs from seeing it.  This is a critical regression that makes emacs
  almost unusable.

  By process of elimination, I've narrowed it down to one of these 4
  binary packages.

  gir1.2-ibus-1.0
  ibus
  ibus-gtk
  ibus-gtk3

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 10 15:15:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-06 (66 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Raymond]

http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-
emu.git/tree/codecs/vt1802-asus-u30s?id=HEAD


compare with this notebook,  device 0 nid is using speaker 's audio output and 
device 2 is using headphone 's audio output

seem spec->gen.indep_hp = 1 is not enough to force the driver to use
speaker audio output by device 0


=> lo_type=2, wired=1, mio=1, badness=0x0
multi_outs = 25/0/0/0 : 8/0/0/0 (type HP)
  out path: depth=4 :08:35:15:25
spk_outs = 24/0/0/0 : 9/0/0/0
  spk path: depth=4 :09:34:14:24
  mix path: depth=4 :08:21:15:25
  mix path: depth=4 :08:21:14:24
==> Best config: lo_type=2, wired=1, mio=1
multi_outs = 25/0/0/0 : 8/0/0/0 (type HP)
  out path: depth=4 :08:35:15:25
spk_outs = 24/0/0/0 : 9/0/0/0
  spk path: depth=4 :09:34:14:24
  mix path: depth=4 :08:21:15:25
  mix path: depth=4 :08:21:14:24

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/hda/hda_generic.c

you need to change

static bool indep_hp_possible(struct hda_codec *codec)
{
struct hda_gen_spec *spec = codec->spec;
struct auto_pin_cfg *cfg = &spec->autocfg;
struct nid_path *path;
int i, idx;

+   if (cfg->line_out_type == AUTO_PIN_HP_OUT)
+   return false;

if (cfg->line_out_type == AUTO_PIN_HP_OUT)
idx = spec->out_paths[0];


http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-
emu.git/tree/codecs/vt1802-asus-g75?id=HEAD

but it is strange that there are two volume controls in same node when
it has headphone, speaker and subwoofer


Node 0x08 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Device: name="VT1802 Analog", type="Audio", device=0
  Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
  Amp-Out vals:  [0x22 0x22]
  Converter: stream=8, channel=0
  PCM:
rates [0x5e0]: 44100 48000 88200 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x09 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Surround Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
  Amp-Out vals:  [0x1d 0x1d]
  Converter: stream=8, channel=2
  PCM:
rates [0x5e0]: 44100 48000 88200 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0


in your case , it is strange that balanced is set in eapd

EAPD 0x3: BALANCED EAPD


BTL controls the output configuration of a Pin Widget which has indicated 
support for balanced I/O (bit 6, Pin Capabilities Parameter).  When this bit is 
0, the output drivers are configured in normal, single-ended mode; when this 
bit is 1, they are configured in balanced mode.  Note that in balanced mode, 
the Pin Widget has twice as many pins as it does in normal mode; i.e., a stereo 
Pin Widget in balanced mode has four signal pins (in addition to Vref pins).  
However, in both modes it must appear to software as a single Pin Widget.  The 
additional pins must be reserved to this purpose; thus, in a configuration 
supporting BTL outputs the additional pins may not be enumerated as a separate 
Pin Widget. 


Node 0x24 [Pin Complex] wcaps 0x40050d: Stereo Amp-Out
  Control: name="Speaker Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Speaker Phantom Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x00010050: OUT EAPD Balanced
  EAPD 0x3: BALANCED EAPD
  Pin Default 0x901701f0: [Fixed] Speaker at Int N/A
Conn = Analog, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 2
 0x14* 0x3e

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 

[Desktop-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming

[Bill Filler]

** Changed in: telephony-service (Ubuntu)
   Status: New => Triaged

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

Title:
  Rename QML modules to follow qml-module-foo naming

Status in “accounts-qml-module” package in Ubuntu:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “clickmanager-plugin” package in Ubuntu:
  New
Status in “content-hub” package in Ubuntu:
  New
Status in “cordova-ubuntu” package in Ubuntu:
  New
Status in “dee-qt” package in Ubuntu:
  New
Status in “gsettings-qt” package in Ubuntu:
  New
Status in “history-service” package in Ubuntu:
  New
Status in “libhud-qt” package in Ubuntu:
  New
Status in “libqofono” package in Ubuntu:
  New
Status in “libusermetrics” package in Ubuntu:
  New
Status in “mediascanner2” package in Ubuntu:
  New
Status in “poppler-qml-plugin” package in Ubuntu:
  New
Status in “qml-box2d” package in Ubuntu:
  New
Status in “qml-friends” package in Ubuntu:
  New
Status in “qt3d-opensource-src” package in Ubuntu:
  New
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtgrilo” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtquickcontrols-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsensors-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
  Fix Released
Status in “reminders-app” package in Ubuntu:
  New
Status in “solid” package in Ubuntu:
  New
Status in “sync-monitor” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu:
  Triaged
Status in “thumbnailer” package in Ubuntu:
  New
Status in “u1db-qt” package in Ubuntu:
  New
Status in “ubuntu-download-manager” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New
Status in “ubuntu-ui-extras” package in Ubuntu:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “ubuntuone-credentials” package in Ubuntu:
  New
Status in “unity-action-api” package in Ubuntu:
  New
Status in “unity-notifications” package in Ubuntu:
  New
Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  The package names of QML modules should be of the format qml-module
  -{$module-name}[version], a transition that was started during Qt 5.3
  preparation in Ubuntu. For example this could be qml-module-qtquick-
  localstorage or qml-module-qtsysteminfo for non versioned modules, and
  qml-module-ubuntu-webthing0.3 for versioned/co-installable modules.

  Further details in Debian e-mail:
  http://lists.alioth.debian.org/pipermail/pkg-kde-
  talk/2014-March/001889.html

  For Ubuntu, transitional packages should be put in place for smooth 
distribution upgrades, since we're shipping with the old names in previous 
Ubuntus. An example of that is at 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
 - in other words:
  - Make the old package a transitional oldlibs package that depends on the new 
package
  - Add Breaks/Replaces to the new package for the old non-transitional 
packages (be careful about the version number specification)
  - Keep Multi-Arch: same and Architecture: any for the transitional package
  - Write "QML module" instead of "QML plugin"
  - Rename also the *.install files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions

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

[Desktop-packages] [Bug 1350153] [NEW] trvando

[najaubuntu]

Public bug reported:

ele trava a tela e para tudo ctrl +alt+f1 adianta...tem que reiniciar

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-prime (not installed)
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Tue Jul 29 23:42:34 2014
InstallationDate: Installed on 2014-05-27 (63 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  trvando

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  ele trava a tela e para tudo ctrl +alt+f1 adianta...tem que reiniciar

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Tue Jul 29 23:42:34 2014
  InstallationDate: Installed on 2014-05-27 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1349436] Re: "Move window to workspace #" shortcut is not working

[João Melo]

** Description changed:

  Steps to reproduce:
  1. Login (using unity)
  2. Open System Settings -> Keyboard -> Shortcuts -> Navigation
- 3. Set "Move window to workspace 2" shortcut to Alt + 2
+ 3. Set "Move window to workspace 2" shortcut to Alt + 2 (or any shortcut)
  4. Press Alt + 2
  
  What should happen:
  Settings window should be moved to workspace 2.
  
  What happens:
  Nothing.
  
  ---
  
  there is already a bug fixed about this(if it helps):
  https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/898087
  
  i've contacted Didier Roche ( https://launchpad.net/~didrocks ), to ask
  to re-open the bug #898087 in which he responded:
  
  "The bug reappeared with a different behavior I guess, and due to another 
cause.
  It's a different team taking care of that. The easiest would be for you to 
report a new bug I guess."
  
  i asked on IRC and multiple users were having the same problem.
  
  Thanks,
  João Melo
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04  (fresh install and updated)
- Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 
+ Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  Package: Unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 28 15:01:39 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-07-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

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

Title:
  "Move window to workspace #" shortcut is not working

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

Bug description:
  Steps to reproduce:
  1. Login (using unity)
  2. Open System Settings -> Keyboard -> Shortcuts -> Navigation
  3. Set "Move window to workspace 2" shortcut to Alt + 2 (or any shortcut)
  4. Press Alt + 2

  What should happen:
  Settings window should be moved to workspace 2.

  What happens:
  Nothing.

  ---

  there is already a bug fixed about this(if it helps):
  https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/898087

  i've contacted Didier Roche ( https://launchpad.net/~didrocks ), to
  ask to re-open the bug #898087 in which he responded:

  "The bug reappeared with a different behavior I guess, and due to another 
cause.
  It's a different team taking care of that. The easiest would be for you to 
report a new bug I guess."

  i asked on IRC and multiple users were having the same problem.

  Thanks,
  João Melo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04  (fresh install and updated)
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  Package: Unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 28 15:01:39 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-07-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1350145] [NEW] network-manager does not reconnect after resuming from suspend

[Craig Magina]

Public bug reported:

On a 2013 Mac Book Pro 11,1, the network-manager does not reconnect
after resuming from suspend. To work around this you need to stop
network-manager, delete /var/lib/NetworkManager/NetworkManager.state and
then start network-manager again. A more permanent workaround is to put
that in a script under /etc/pm/sleep.d/

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

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1268257, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

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

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

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

Bug description:
  during apt-get dist-upgrade, no further information, system still
  works after reboot

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-6-generic
  Date: Tue Jul 29 12:19:44 2014
  InstallationDate: Installed on 2011-10-03 (1030 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  PackageVersion: 331.89-0ubuntu2
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu2: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-07-09 (19 days ago)

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

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

[Desktop-packages] [Bug 1349123] Re: create ubuntu software center account captcha is impossible to solve

[Launchpad Bug Tracker]

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

** Changed in: software-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  create ubuntu software center account captcha is impossible  to solve

Status in “software-center” package in Ubuntu:
  Confirmed

Bug description:
  I spent half an hour laboriously squinting at the deplorably poorly
  resolved xored captcha word pairs and didn't get a single one right! I
  finally gave up and no longer use the program. This should be changed
  to something much more reasonab le - all I had to do to get this
  account was to type in the three numbers above a picture of a door!

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

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

[Desktop-packages] [Bug 1229172]

[Bugzilla-spray]

*** Bug 910848 has been marked as a duplicate of this bug. ***

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

Title:
  Thunderbird "Spell check as you type" stopped working after update to
  1:24.0+build1-0ubuntu0.12.04.1 (precise-updates)

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  After installing the 1:24.0+build1-0ubuntu0.12.04.1 (precise-updates)
  update to Mozilla Thunderbird on 12.04, the "Spell check as you type"
  feature no longer works.  Downgrading to 11.0.1+build1-0ubuntu2
  (precise) restores the functionality.

  Steps to reproduce:
  * Open a new message.
  * Verify "Options->Spell Check As You Type" is selected
  * Type something like "check my spleling please" in the body of the message

  Expected Result:
  * spleling should be underlined in red and when right-clicked offer 
correction options

  Actual Result:
  * No words are underlined to indicate mispellings were found. Right-clicking 
on "spleling" shows the standard context menu. Toggling the spell check as you 
type option has no effect. Click the "Spelling" button, however, does lauch the 
spell checker and identify the mispelled word.

  Downgrading to 11.0.1+build1-0ubuntu2 (precise) restores the check as
  you type functionality.

  
  ~$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

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

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

[Desktop-packages] [Bug 1350104] Re: package fglrx (not installed) failed to install/upgrade: subprocesso novo script pre-installation retornou erro do status de saída 1

[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 fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1350104

Title:
  package fglrx (not installed) failed to install/upgrade: subprocesso
  novo script pre-installation retornou erro do status de saída 1

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  ATI HD7700

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 29 23:33:49 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:fglrx:(not installed):subprocesso novo script 
pre-installation retornou erro do status de saída 1
  ErrorMessage: subprocesso novo script pre-installation retornou erro do 
status de saída 1
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde LE [Radeon HD 7730/8730] 
[1002:6837] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e228]
  InstallationDate: Installed on 2014-05-04 (86 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=84cace65-29f4-460e-9779-81024b402167 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: fglrx-installer
  Title: package fglrx (not installed) failed to install/upgrade: subprocesso 
novo script pre-installation retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/05/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jul 29 23:48:30 2014
  xserver.configfile: default
  xserver.devices:
   
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or 
incompatible.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1350104] Re: package fglrx (not installed) failed to install/upgrade: subprocesso novo script pre-installation retornou erro do status de saída 1

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package fglrx (not installed) failed to install/upgrade: subprocesso
  novo script pre-installation retornou erro do status de saída 1

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  ATI HD7700

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 29 23:33:49 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:fglrx:(not installed):subprocesso novo script 
pre-installation retornou erro do status de saída 1
  ErrorMessage: subprocesso novo script pre-installation retornou erro do 
status de saída 1
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde LE [Radeon HD 7730/8730] 
[1002:6837] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e228]
  InstallationDate: Installed on 2014-05-04 (86 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=84cace65-29f4-460e-9779-81024b402167 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: fglrx-installer
  Title: package fglrx (not installed) failed to install/upgrade: subprocesso 
novo script pre-installation retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/05/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jul 29 23:48:30 2014
  xserver.configfile: default
  xserver.devices:
   
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or 
incompatible.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1350086] Re: Focus is on the app behind the lock screen after resume from suspend

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1349961
   lock screen don't get focus by closing the lid

** Information type changed from Private Security to Public

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

Title:
  Focus is on the app behind the lock screen after resume from suspend

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Recently, when I resume from suspend I often can't input anything into
  the password field. After selecting an icon in the top left corner of
  the screen lock and then selecting the password field again I can type
  my password and unlock the computer. Once I do that whatever I typed
  in the password field actually shows up in whatever app had focus
  before I suspended, potentially leaking my password to a remote
  attacker if the focused app is a browser, as it often is.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 29 23:51:33 2014
  InstallationDate: Installed on 2014-05-03 (87 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=pedrocr
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1350123] [NEW] Startup with iPhone plugged in causes inability to logout

[Aurosutru]

Public bug reported:

In 14.04 startup with an iPhone 3G plugged in causes several problems.
Changes to Unity made with Unity Tweak Tool are not recognized after
such a startup, and attempting to logout hangs after the desktop icons
are erased and only the desktop background remains.  Startup without the
iPhone plugged into a usb port works fine, as does operation when
plugging in the iPhone after startup.

The iPhone is jail-broken and is set to tether.  Synaptic shows only
libplist1, libimobiledevice, usbmuxd and libusbmuxd2 installed related
to iPhones.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 30 06:10:49 2014
InstallationDate: Installed on 2014-01-11 (199 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: libimobiledevice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Startup with iPhone plugged in causes inability to logout

Status in “libimobiledevice” package in Ubuntu:
  New

Bug description:
  In 14.04 startup with an iPhone 3G plugged in causes several problems.
  Changes to Unity made with Unity Tweak Tool are not recognized after
  such a startup, and attempting to logout hangs after the desktop icons
  are erased and only the desktop background remains.  Startup without
  the iPhone plugged into a usb port works fine, as does operation when
  plugging in the iPhone after startup.

  The iPhone is jail-broken and is set to tether.  Synaptic shows only
  libplist1, libimobiledevice, usbmuxd and libusbmuxd2 installed related
  to iPhones.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 30 06:10:49 2014
  InstallationDate: Installed on 2014-01-11 (199 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libimobiledevice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1350052] Re: Unity FTBFS - gcc 4.9

[Brandon Schaefer]

urrg... hit Wont Fix on accident .. now I get a timeout error anytime I
try to change it. Yay launchpad! (Same when attempting to link the
branch to fix this...)

** Changed in: unity
   Status: Won't Fix => In Progress

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

Title:
  Unity FTBFS - gcc 4.9

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Confirmed gcc/g++ 4.9 causes this FTBFS

  [ 17%] Building CXX object 
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
  In file included from 
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
  /home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
   DECLARE_LOGGER(logger, "unity.dash.filter.checkoption");
  ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
     ::nux::logging::Logger& logger()   \
     ^
  In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
   from /home/bschaefer/src/unity/UnityCore/Model.h:107,
   from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
   from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
  /home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
   DECLARE_LOGGER(logger, "unity.dash.filter");
  ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
     ::nux::logging::Logger& logger()   \
     ^
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
  make[2]: *** 
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
  make[2]: *** Waiting for unfinished jobs
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
  make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
  CMakeFiles/Makefile2:6381: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
  make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
  Makefile:113: recipe for target 'all' failed
  make: *** [all] Error 2

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

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

[Desktop-packages] [Bug 1350052] Re: Unity FTBFS - gcc 4.9

[Brandon Schaefer]

** Changed in: unity
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

** Changed in: unity
   Status: Triaged => In Progress

** Changed in: unity
   Status: In Progress => Won't Fix

** Changed in: unity (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Unity FTBFS - gcc 4.9

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Confirmed gcc/g++ 4.9 causes this FTBFS

  [ 17%] Building CXX object 
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
  In file included from 
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
  /home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
   DECLARE_LOGGER(logger, "unity.dash.filter.checkoption");
  ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
     ::nux::logging::Logger& logger()   \
     ^
  In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
   from /home/bschaefer/src/unity/UnityCore/Model.h:107,
   from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
   from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
  /home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
   DECLARE_LOGGER(logger, "unity.dash.filter");
  ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
     ::nux::logging::Logger& logger()   \
     ^
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
  make[2]: *** 
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
  make[2]: *** Waiting for unfinished jobs
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
  make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
  CMakeFiles/Makefile2:6381: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
  make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
  Makefile:113: recipe for target 'all' failed
  make: *** [all] Error 2

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[Gao Shichao]

I also have this bug with google-chrome 36.0.1985.125-1, so this bug is
not fixed, please someone take a look. Also workaround by clicking some
of the icons on the panel.

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, 
this window will still have the grab and thusly, you can't enter your password 
in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity 
control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or 
a virtual
 machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to 
another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something 
takes the grab in X, or we won't able to get input back. This is not a 
regression because it has never been possible in Ubuntu before, while when we 
tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at 
https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
gsettings set org.gnome.desktop.session idle-delay 5
  and resetting it with:
gsettings reset org.gnome.desktop.session idle-delay

  ---

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1317175] Re: freerdp-x11 error in spanish keyboard numeric keypad

[Ubuntu Foundations Team Bug Bot]

The attachment "fix-german-keypad-divide.patch" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  freerdp-x11 error in spanish keyboard numeric keypad

Status in “freerdp” package in Ubuntu:
  Confirmed

Bug description:
  
 * What led up to the situation?
  xfreerdp --sec rdp --no-nla  --plugin rdpsnd --data alsa latency:40 -- 
--plugin rdpdr --data disk:terminal:/media -- -u user -a 16 -k 0x040A 
--plugin cliprdr -z 192.168.0.205

 * What was the outcome of this action?
  With spanish keyboard In numeric keypad, pressing key / button appears -  and 
pressing key . button appears ,

 * What outcome did you expect instead?
  In numeric keypad, pressing key / button appears / , and pressing key . 
button appears .

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

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

[Desktop-packages] [Bug 1208473] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()

[Chris Halse Rogers]

Hello Dylan, or anyone else affected,

Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Xorg crashed with SIGABRT in mieqMoveToNewScreen()

Status in X.Org X server:
  In Progress
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  apport showed up

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu7
  Uname: Linux 3.11.0-rc1-custom i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug  5 15:32:06 2013
  DistUpgraded: 2013-08-04 14:50:50,172 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.10.0-6-generic, i686: installed
   virtualbox, 4.2.16, 3.11.0-rc1-custom, i686: installed
   virtualbox-guest, 4.2.16: added
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
  InstallationDate: Installed on 2011-11-11 (633 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-rc1-custom 
root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   mieqProcessDeviceEvent ()
   mieqProcessInputEvents ()
   ?? ()
   DisableDevice ()
   ?? ()
  Title: Xorg crashed with SIGABRT in mieqProcessDeviceEvent()
  UpgradeStatus: Upgraded to saucy on 2013-08-04 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 07/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu1.1
  xserver.bootTime: Mon Aug  5 15:32:10 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8954 
   vendor ACI
  xserver.version: 2:1.14.2-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launc

[Desktop-packages] [Bug 1322212] Re: Switching to the Guest session results in a black screen

[Chris Halse Rogers]

Hello Alberto, or anyone else affected,

Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: xorg-server (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Switching to the Guest session results in a black screen

Status in HWE Next Project:
  Fix Committed
Status in HWE Next precise series:
  Fix Released
Status in HWE Next trusty series:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server-lts-saucy” package in Ubuntu:
  Fix Released
Status in “xorg-server-lts-trusty” package in Ubuntu:
  Triaged
Status in “xorg-server” source package in Trusty:
  Fix Committed
Status in “xorg-server-lts-saucy” source package in Trusty:
  Invalid
Status in “xorg-server-lts-trusty” source package in Trusty:
  Invalid

Bug description:
  SRU Request:

  Running the proprietary nvidia drivers in an Optimus config works
  (Intel+NVIDIA), but switching to the guest session results in a black
  screen.

  [Impact]
   * Causes a black screen when switching to the guest session.

  [Test Case]
   * Run xrandr --output SOMEOUTPUT --rotation left
  - Expected: Screen should rotate, or the call should fail.
  - Bad behavior: Succeeds, but causes a black screen.

  [Test Case]
   * Boot the system
   * Switch to guest session from top menu
   - Expected: Switches to the guest session without problems.
   - Actual results: The screen is black, only the cursor is visible in the 
upper left corner of the screen.

  [Regression Potential]
   * Low, as we already use the patch in Trusty and Utopic.

  [Other Info]
   * N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1322212/+subscriptions

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

[Desktop-packages] [Bug 1333422] Re: Incorrect byte order on ppc64el

[Chris Halse Rogers]

Hello Benjamin, or anyone else affected,

Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Incorrect byte order on ppc64el

Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  The X server has an old assumption that __powerpc__ is big endian. This was 
just fixed
  upstream with this very simple patch which should be applied to ubuntu's 
version as well:

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

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[Erik Axelsson]

I also have this bug with chromium:

chromium-browser:
  Installed: 34.0.1847.116-0ubuntu2

compiz:
  Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1

unity:
  Installed: 7.2.2+14.04.20140714-0ubuntu1

A work around is to suspend and wake up the computer one more.

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, 
this window will still have the grab and thusly, you can't enter your password 
in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity 
control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or 
a virtual
 machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to 
another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something 
takes the grab in X, or we won't able to get input back. This is not a 
regression because it has never been possible in Ubuntu before, while when we 
tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at 
https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
gsettings set org.gnome.desktop.session idle-delay 5
  and resetting it with:
gsettings reset org.gnome.desktop.session idle-delay

  ---

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1290785] Re: Users with UID > 60000 are invisible in login and Settings->User unless /etc/login.defs updated

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.1

---
accountsservice (0.6.35-0ubuntu7.1) trusty-proposed; urgency=medium

  * debian/patches/0018-no-max-uid.patch:
- Don't have a maximum UID (LP: #1290785)
 -- Robert AncellFri, 18 Jul 2014 12:26:01 
+1200

** Changed in: accountsservice (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Users with UID > 6 are invisible in login and Settings->User
  unless /etc/login.defs updated

Status in “accountsservice” package in Ubuntu:
  Fix Released
Status in “accountsservice” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Users of Ubuntu 14.04 LTS with UID > 6 will not show in the greeter or 
system settings without editing UID_MAX in /etc/login.defs. This was not 
required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID < 
UID_MIN. In 13.10 this was changed to UID < UID_MIN or UID > UID_MAX.

  [Test Case]
  1. Create a user with a UID > UID_MAX:
  $ adduser --uid 60001 big-uid
  2. Restart system
  Expected result:
  "big-uid" is shown in the greeter. Once logged in "big-uid" is shown in 
system settings.
  Observed result:
  "big-uid" is not shown in the greeter (14.04 LTS, 14.10)
  "big-uid" is not shown in system settings (13.10, 14.04LTS, 14.10)

  [Regression Potential]
  This could cause users that were previously hidden to be shown. This seems 
unlikely to be a problem as all system created user accounts are less than 
UID_MIN and there doesn't seem be a convention to use accounts > UID_MAX for 
this case.

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

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

[Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager-applet -
0.9.8.8-0ubuntu4.3

---
network-manager-applet (0.9.8.8-0ubuntu4.3) trusty-proposed; urgency=medium

  * debian/patches/git_revert_system_ca_cert.patch: don't require system CA
certs to validate the wireless AP certs if the user chooses not to supply
a certificate. (LP: #1104476)
 -- Mathieu Trudel-LapierreMon, 07 Jul 2014 11:11:52 
-0400

** Changed in: network-manager-applet (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without
  CA_Certificate

Status in NetworkManager:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in “network-manager-applet” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” source package in Saucy:
  Won't Fix
Status in “network-manager-applet” source package in Trusty:
  Fix Released
Status in “network-manager-applet” source package in Utopic:
  Fix Released
Status in Gentoo Linux:
  Fix Released
Status in “network-manager” package in openSUSE:
  Confirmed

Bug description:
  SRU Justification:
  [Impact]
  When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA 
Certificate network manager may incorrectly mark the CA certificate as needing 
verification and fail that verification.

  [Test Case]
  Attempt to connect to a WPA2/PEAP/MSCHAPv2 network without CA_Certificate 
using Network Manager

  [Regression Potential]
  This has been fixed in Utopic already and it a backport of an upstream patch.

  --

  === Release Notes Text ===

  When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have
  a CA Certificate network manager may incorrectly mark the CA
  certificate as needing verification and fail that verification.  See
  the bug for workarounds.

  ===

  I can connect to Eduroam in 12.10 and any other previous release, but
  not in 13.04. I checked, my name and password are correct, all
  settings are the same as in 12.10.

  Network properties:

  security: WPA - WPA2 enterprise
  authentication: protected EAP (PEAP)
  CA certificate: none
  PEAP version: automatic
  inner autentication: MSCHAPv2
  username: (required)
  password: (required)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  CasperVersion: 1.330
  Date: Thu Jan 24 21:32:25 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.43.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.149  
metric 9
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123)
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7   
802-11-wireless   1359063171   Thu 24 Jan 2013 09:32:51 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/2
   Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e   
802-3-ethernet1359062570   Thu 24 Jan 2013 09:22:50 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/1
   eduroam   00f69a95-4a1b-436c-b462-a284f45fbaa1   
802-11-wireless   1359063171   Thu 24 Jan 2013 09:32:51 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.7.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1104476] Update Released

[Chris Halse Rogers]

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

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

Title:
  Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without
  CA_Certificate

Status in NetworkManager:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in “network-manager-applet” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” source package in Saucy:
  Won't Fix
Status in “network-manager-applet” source package in Trusty:
  Fix Released
Status in “network-manager-applet” source package in Utopic:
  Fix Released
Status in Gentoo Linux:
  Fix Released
Status in “network-manager” package in openSUSE:
  Confirmed

Bug description:
  SRU Justification:
  [Impact]
  When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA 
Certificate network manager may incorrectly mark the CA certificate as needing 
verification and fail that verification.

  [Test Case]
  Attempt to connect to a WPA2/PEAP/MSCHAPv2 network without CA_Certificate 
using Network Manager

  [Regression Potential]
  This has been fixed in Utopic already and it a backport of an upstream patch.

  --

  === Release Notes Text ===

  When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have
  a CA Certificate network manager may incorrectly mark the CA
  certificate as needing verification and fail that verification.  See
  the bug for workarounds.

  ===

  I can connect to Eduroam in 12.10 and any other previous release, but
  not in 13.04. I checked, my name and password are correct, all
  settings are the same as in 12.10.

  Network properties:

  security: WPA - WPA2 enterprise
  authentication: protected EAP (PEAP)
  CA certificate: none
  PEAP version: automatic
  inner autentication: MSCHAPv2
  username: (required)
  password: (required)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  CasperVersion: 1.330
  Date: Thu Jan 24 21:32:25 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.43.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.149  
metric 9
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123)
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7   
802-11-wireless   1359063171   Thu 24 Jan 2013 09:32:51 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/2
   Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e   
802-3-ethernet1359062570   Thu 24 Jan 2013 09:22:50 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/1
   eduroam   00f69a95-4a1b-436c-b462-a284f45fbaa1   
802-11-wireless   1359063171   Thu 24 Jan 2013 09:32:51 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.7.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites

[SammyA]

Spoke too soon... Just crashed again :-( 
It is certainly more stable though under 14.04 but not 100%

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

Title:
  Ubuntu 13.10 random screen freeze while Normal OS activites

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

Bug description:
  *PLEASE DO NOT MAKE A COMMENT IN THIS REPORT*
  As this issue is hardware dependent, not symptom(s), and the original 
reporter (Naveen) has not provided the hardware in use, this bug report is not 
about you or your hardware, so please do not make a comment. Instead, file a 
new bug report. Thanks.
  *

  I have recently, re-installed fresh ubuntu 13.10 distribution release. But 
everything worked fine. until recently i had strange problem of my display 
screen getting freezed randomly; but no response to either mouse/keyboard.
  But i want to point it out; it happens randomly and is not specific ?
  Other day, i had music player playing in background, but screen freezed. but 
my music was still running.
  Kindly note, i used multiple monitor setup and same issue of screen freeze 
also cropped up.

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

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

[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon

[Alberto Salvia Novella]

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Triaged => Invalid

** No longer affects: gdk-pixbuf (Ubuntu)

** No longer affects: gdk-pixbuf

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

Title:
  Several XFCE applications appear unresponsive after communicating with
  a daemon

Status in One Hundred Papercuts:
  Triaged
Status in System policy:
  Confirmed
Status in Thunar file manager:
  Confirmed
Status in xfce4-appfinder:
  Confirmed
Status in Xfce4 Power Manager:
  Confirmed
Status in xfce4-settings:
  Fix Released
Status in Volume management daemon for Xfce:
  Confirmed
Status in “policykit-1” package in Ubuntu:
  Triaged
Status in “thunar” package in Ubuntu:
  Triaged
Status in “xfce4-appfinder” package in Ubuntu:
  Triaged
Status in “xfce4-power-manager” package in Ubuntu:
  Triaged
Status in “xfce4-settings” package in Ubuntu:
  Triaged
Status in “xfce4-volumed” package in Ubuntu:
  Triaged

Bug description:
  Several programs in Xfce have a daemon mode call gtk_init() before
  fork()ing.

  This is unsafe, and when it goes wrong this will typically manifest as
  the daemon hanging shortly after forking, and appearing to simply do
  nothing at all.

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

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

[Desktop-packages] [Bug 1333512] Update Released

[Chris Halse Rogers]

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

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

Title:
  Failing to import module breaks logging configurability and adds noise

Status in Python bindings for GObject:
  Fix Released
Status in “pygobject” package in Ubuntu:
  Fix Released
Status in “pygobject” source package in Trusty:
  Fix Released
Status in “pygobject” source package in Utopic:
  Fix Released

Bug description:
  When failing to import a module the gi.repository import.py module logs an 
error with `logging.error(..)` causing a logging handler to be added.
  This basically breaks the ability to configure the logging as it happens so 
early (i.e. at the import stage before an authors code is executed).

  To reproduce/Example:

  Run this script: http://pastebin.ubuntu.com/7698632/

  Expected outcome:
  No output to stdout or stderr and the text "log message" in the file 
"/tmp/example.log

  Actual outcome:
  No log file, and this text output to stderr:
    ERROR:root:Could not find any typelib for rubbish
    ERROR:root:log message

  Upstream fix:
  https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e

  Regression potential:
  - The behaviour of raising ImportError on a nonexisting name does not change, 
but its text changes.
Old: ImportError: cannot import name 'foo'
New: ImportError: cannot import name foo, introspection typelib not found

It's unlikely, however theoretically possible that a program matches
  on the precise error message.

  - It's theoretically possible that a program watches for the logged
  error message and ignores the ImportError. However, that would be
  extremely bad design, un-Pythonic and brittle as the logging
  format/destination can be changed arbitrarily.

  In summary the regression potential is very low.

  
  Ubuntu Version:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Package Version:
  python3-gi 3.12.0-1

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

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

[Desktop-packages] [Bug 1333512] Re: Failing to import module breaks logging configurability and adds noise

[Launchpad Bug Tracker]

This bug was fixed in the package pygobject - 3.12.0-1ubuntu1

---
pygobject (3.12.0-1ubuntu1) trusty-proposed; urgency=medium

  * Add 00upstream-importerror-logging.patch: Raise ImportError when importing
modules not found in repository, instead of logging to stderr. The former
matches the behaviour of "import" in general, and the latter breaks the
possibility of configuring "logging" in your program, as any call to
basicConfig() would happen after the import statements. (LP: #1333512)
 -- Martin PittWed, 25 Jun 2014 08:14:43 +0200

** Changed in: pygobject (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Failing to import module breaks logging configurability and adds noise

Status in Python bindings for GObject:
  Fix Released
Status in “pygobject” package in Ubuntu:
  Fix Released
Status in “pygobject” source package in Trusty:
  Fix Released
Status in “pygobject” source package in Utopic:
  Fix Released

Bug description:
  When failing to import a module the gi.repository import.py module logs an 
error with `logging.error(..)` causing a logging handler to be added.
  This basically breaks the ability to configure the logging as it happens so 
early (i.e. at the import stage before an authors code is executed).

  To reproduce/Example:

  Run this script: http://pastebin.ubuntu.com/7698632/

  Expected outcome:
  No output to stdout or stderr and the text "log message" in the file 
"/tmp/example.log

  Actual outcome:
  No log file, and this text output to stderr:
    ERROR:root:Could not find any typelib for rubbish
    ERROR:root:log message

  Upstream fix:
  https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e

  Regression potential:
  - The behaviour of raising ImportError on a nonexisting name does not change, 
but its text changes.
Old: ImportError: cannot import name 'foo'
New: ImportError: cannot import name foo, introspection typelib not found

It's unlikely, however theoretically possible that a program matches
  on the precise error message.

  - It's theoretically possible that a program watches for the logged
  error message and ignores the ImportError. However, that would be
  extremely bad design, un-Pythonic and brittle as the logging
  format/destination can be changed arbitrarily.

  In summary the regression potential is very low.

  
  Ubuntu Version:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Package Version:
  python3-gi 3.12.0-1

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

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

[Desktop-packages] [Bug 1315348] Re: Firefox 29 can't handle keyboard input correctly after waking up from suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox 29 can't handle keyboard input correctly after waking up from
  suspend

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  After waking up the laptop from suspend, firefox doesn't handle the
  keyboard input correctly. For example by pressing tab button after
  typing a few words of address in urlbar, it doesn't go down to auto
  complete the address, or I should click on the input areas twice in
  web pages like twitter to be able to type in there, or the the input
  area will lose the focus and nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 29.0+build1-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danialbehzadi   2224 F pulseaudio
  BuildID: 20140428193813
  CRDA:
   country IR:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 40), (N/A, 30)
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri May  2 15:39:01 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-27 (187 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.5  metric 9
  MostRecentCrashID: bp-db75c3db-a5f2-47a6-8d27-77a7b2140501
  PrefSources:
   prefs.js
   [Profile]/extensions/foxypr...@eric.h.jung/defaults/preferences/prefs.js
   
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
  Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu2
   icedtea-7-plugin  1.5-1ubuntu1
   totem-mozilla 3.10.1-1ubuntu4
   gnome-shell   3.10.4-0ubuntu5
   google-talkplugin 5.2.4.0-1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to trusty on 2014-02-20 (70 days ago)
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349KEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET97WW(2.57):bd09/04/2013:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2349KEG
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1182205] Re: totem freezes after changing/disabling subtitle on mp4 files.

[LeLapin]

It's worse on my Ubuntu-Studio (Xubuntu with rt kernel) Trusty (14.04) :
not only it freezes whenever you try to change subs, but it makes Xfce
hangs and restart (when lucky and stable) if you try to kill
totem/answer yes to the dialog box to force-close it...!

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

Title:
  totem freezes after changing/disabling subtitle on mp4 files.

Status in “totem” package in Ubuntu:
  Confirmed

Bug description:
  this bug is reproducible every time. I just need to open an mp4 video
  file with a subtitle file in the same folder. then the subtitle shows
  and the video plays ok. then if I try to disable the subtitle, totem
  freezes, and I have to close it by force.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Mon May 20 21:50:27 2013
  InstallationDate: Installed on 2010-07-31 (1024 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to raring on 2013-04-26 (24 days ago)

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

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

[Desktop-packages] [Bug 1311951] Re: Save dialog New Folder Closes with Shift

[Launchpad Bug Tracker]

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

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

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

Title:
  Save dialog New Folder Closes with Shift

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  1. Open an application you can save from (ex gedit, libreoffice writer)
  2. Press Ctrl+S to save a document
  3. Navigate to a directory (ex desktop)
  4. Click "Create Folder"
  5. Press shift and push any letter
  6. Instead of typing a capital letter, it just cancels the New Folder 
operation

  Release: Ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 21:47:42 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-04-21 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1350052] [NEW] Unity FTBFS - gcc 4.9

[Brandon Schaefer]

Public bug reported:

Confirmed gcc/g++ 4.9 causes this FTBFS

[ 17%] Building CXX object 
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from 
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
 DECLARE_LOGGER(logger, "unity.dash.filter.checkoption");
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
   ::nux::logging::Logger& logger()   \
   ^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
 from /home/bschaefer/src/unity/UnityCore/Model.h:107,
 from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
 from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
 DECLARE_LOGGER(logger, "unity.dash.filter");
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
   ::nux::logging::Logger& logger()   \
   ^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] 
Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2

** Affects: unity
 Importance: Critical
 Status: Triaged

** Affects: unity (Ubuntu)
 Importance: Critical
 Status: Triaged

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

** Changed in: unity (Ubuntu)
   Status: New => Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided => Critical

** Description changed:

+ 4.8 worked fine, upgrade to 4.9 now unity FTBFS. Ill double check gcc
+ though.
+ 
  [ 17%] Building CXX object 
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
  In file included from 
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
  /home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
-  DECLARE_LOGGER(logger, "unity.dash.filter.checkoption");
- ^
+  DECLARE_LOGGER(logger, "unity.dash.filter.checkoption");
+ ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
-::nux::logging::Logger& logger()   \
-^
+    ::nux::logging::Logger& logger()   \
+    ^
  In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
-  from /home/bschaefer/src/unity/UnityCore/Model.h:107,
-  from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
-  from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
+  from /home/bschaefer/src/unity/UnityCore/Model.h:107,
+  from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
+  from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
  /home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error: 
‘nux::logging::Logger& unity::dash::{anonymous}::logger()’ defined but not used 
[-Werror=unused-function]
-  DECLARE_LOGGER(logger, "unity.dash.filter");
- ^
+  DECLARE_LOGGER(logger, "unity.dash.filter");
+ ^
  /usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro 
‘DECLARE_LOGGER’
-::nux::logging::Logger& logger()   \
-^
+    ::nux::logging::Logger& logger()   \
+    ^
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target 
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
  make[2]: *** 
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
  make[2]: *** Waiting for unfinished jobs
  cc1plus: all warnings being treated as errors
  UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: reci

[Desktop-packages] [Bug 637066] Re: Volume adjustment is extreme

[tuxiano]

Hi, I have the exact same problem with the following sound card:

lsusb | grep -i audio
Bus 003 Device 002: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter

Has the patch of #9 already be applied?

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

Title:
  Volume adjustment is extreme

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I am using an Altec Lansing USB sound adapter (ID 0d8c:000c C-Media
  Electronics, Inc. Audio Adapter).  It plays sound just fine but volume
  adjustment is calibrated incorrectly.  2/3 of scale is loud.  One
  click below (in the horizontal volume slider) is too low to hear, and
  one click above would make Spinal Tap envious.  Mine goes to 12

  I have to manually adjust the volume using my speaker adjustment.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libpulse0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kpratt 1938 F pulseaudio
   /dev/snd/pcmC2D0p:   kpratt 1938 F...m pulseaudio
   /dev/snd/controlC1:  kpratt 1938 F pulseaudio
   /dev/snd/controlC0:  kpratt 1938 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21'
 Mixer name : 'SigmaTel STAC9205'
 Components : 'HDA:838476a0,102801f8,00100204'
 Controls  : 19
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x8c9'/'USB Device 0x46d:0x8c9 at usb-:00:1d.7-1.2, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:08c9'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'default'/'C-Media USB Headphone Set   at usb-:00:1d.7-1.1.5, 
full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:000c'
 Controls  : 5
 Simple ctrls  : 3
  CheckboxSubmission: 48d893255053224631a12a7b4064254b
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Mon Sep 13 08:31:30 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0WY897
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0WY897:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6300
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1257939] Re: Does not show fingerprint in key import dialog

[Bug Watch Updater]

** Changed in: seahorse
   Status: Confirmed => Fix Released

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

Title:
  Does not show fingerprint in key import dialog

Status in Seahorse:
  Fix Released
Status in “seahorse” package in Ubuntu:
  Triaged

Bug description:
  Using the seahorse option to find and import remote public keys, the
  properties dialog does not show the correct fingerprint but the key ID
  instead.

  
  to reproduce:

  go to remote, find remote keys, enter a valid search term, select a
  key from the results and select properties in the context menu of the
  selected key.

  
  bug was confirmed using the following versions:

  3.10.1 (using ArchLinux)
  3.2.2 (Using Ubuntu 12.04.3)

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

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

[Desktop-packages] [Bug 1228464] Re: Ubuntu Touch Missing service provider name

[Bill Filler]

** Changed in: telephony-service
   Status: New => Incomplete

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

** No longer affects: telephony-service

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

Title:
  Ubuntu Touch Missing service provider name

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

Bug description:
  I have "Life :)" ("Life BY") service provider, but serverproviders.xml
  file have "Life :)"... 3G isn't work, but if change "Life :)" to "Life
  BY" 3G is work.

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

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

[Desktop-packages] [Bug 1317528] Re: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1, making some packages uninstallable

[Graham Inggs]

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

** This bug has been marked a duplicate of bug 1307792
   nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict

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

Title:
  Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and
  libopencl-1.2-1, making some packages uninstallable

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ocl-icd” package in Ubuntu:
  Invalid

Bug description:
  The packages nvidia-libopencl1-... don't provide the virtual packages
  libopencl-1.1-1 and libopencl-1.2-1.

  This causes problems with the installation of the following packages:
  python-pyopencl
  python3-pyopencl
  wine1.6-i386 (see 
https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1313123)
  wine1.6-amd64
  starpu-contrib-examples
  libstarpu-contrib

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

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

[Desktop-packages] [Bug 1317175] Re: freerdp-x11 error in spanish keyboard numeric keypad

[Marcus Trautwig]

Upstream knows about the divide key problem and already has a solution:
https://github.com/FreeRDP/FreeRDP/issues/446

I have built a package with the fix in my PPA: https://launchpad.net
/~marcus-trautwig/+archive/ubuntu/fixes/

The change is also in their stable-1.0 branch, so it should appear in
1.0.3.

** Patch added: "fix-german-keypad-divide.patch"
   
https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1317175/+attachment/4165375/+files/fix-german-keypad-divide.patch

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

Title:
  freerdp-x11 error in spanish keyboard numeric keypad

Status in “freerdp” package in Ubuntu:
  Confirmed

Bug description:
  
 * What led up to the situation?
  xfreerdp --sec rdp --no-nla  --plugin rdpsnd --data alsa latency:40 -- 
--plugin rdpdr --data disk:terminal:/media -- -u user -a 16 -k 0x040A 
--plugin cliprdr -z 192.168.0.205

 * What was the outcome of this action?
  With spanish keyboard In numeric keypad, pressing key / button appears -  and 
pressing key . button appears ,

 * What outcome did you expect instead?
  In numeric keypad, pressing key / button appears / , and pressing key . 
button appears .

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

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

[Desktop-packages] [Bug 1307792] Re: Packages nvidia-libopencl1-* should provide libopencl-1.1-1

[Graham Inggs]

** Summary changed:

- nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict
+ Packages nvidia-libopencl1-* should provide libopencl-1.1-1

** Changed in: nvidia-cuda-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Packages nvidia-libopencl1-* should provide libopencl-1.1-1

Status in “nvidia-cuda-toolkit” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-cuda-toolkit” package in Debian:
  Fix Released

Bug description:
  The nvidia-opencl-dev package depends on nvidia-libopencl1-331 |
  nvidia-libopencl1-331-updates. This dependency is too strict as
  nvidia-libopencl1-334 and nvidia-libopencl1-337 will also satisfy it.
  There should be a virtual dependency (libopencl1)

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

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

[Desktop-packages] [Bug 1296006] Re: Package libgl1-nvidia-glx:i386 is missing from repositories

[Graham Inggs]

Why do you need libgl1-nvidia-glx:i386?

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

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

Title:
  Package libgl1-nvidia-glx:i386 is missing from repositories

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

Bug description:
  1) Ubuntu 14.04
  2) None...since it's not provided
  3) The package being availabe via Synaptics/apt-get but not even the 64bit 
variant is available.
  4) The package was not available/installable

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

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

[Desktop-packages] [Bug 1307792] Re: nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict

[Launchpad Bug Tracker]

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

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

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

Title:
  Packages nvidia-libopencl1-* should provide libopencl-1.1-1

Status in “nvidia-cuda-toolkit” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-cuda-toolkit” package in Debian:
  Fix Released

Bug description:
  The nvidia-opencl-dev package depends on nvidia-libopencl1-331 |
  nvidia-libopencl1-331-updates. This dependency is too strict as
  nvidia-libopencl1-334 and nvidia-libopencl1-337 will also satisfy it.
  There should be a virtual dependency (libopencl1)

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

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

[Desktop-packages] [Bug 1337292] Re: nvidia-331 331.20-0ubuntu0.0.2: nvidia-331 kernel module failed to build [Error! Bad return status for module build on kernel: 3.2.0-65-generic (x86_64)]

[Launchpad Bug Tracker]

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

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

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

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

Title:
  nvidia-331 331.20-0ubuntu0.0.2: nvidia-331 kernel module failed to
  build [Error! Bad return status for module build on kernel:
  3.2.0-65-generic (x86_64)]

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

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

  
  There is no such file as  "/var/lib/dkms/nvidia-331/331.20/build/make.log"

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331 331.20-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic 3.2.59
  Uname: Linux 3.2.0-64-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DKMSKernelVersion: 3.2.0-65-generic
  Date: Thu Jul  3 21:31:37 2014
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageVersion: 331.20-0ubuntu0.0.2
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.20-0ubuntu0.0.2: nvidia-331 kernel module failed to 
build
  UpgradeStatus: Upgraded to precise on 2013-01-31 (517 days ago)

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

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

[Desktop-packages] [Bug 1328542] Re: Build dependency on virtual libopencl1 with no default

[Graham Inggs]

** Summary changed:

- [xorg-edgers] OCL-ICD provides a free generic OpenCL implementation, should 
ubuntu policy be to build applications against this loader vs closed vendor 
implementations
+ Build dependency on virtual libopencl1 with no default

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

Title:
  Build dependency on virtual libopencl1 with no default

Status in “fglrx-driver” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “ocl-icd” package in Ubuntu:
  Invalid
Status in “viennacl” package in Ubuntu:
  New

Bug description:
  Relevant Packages: ocl-icd-libopencl1

  Applications that wish to use OpenCL encounter a few problems when you
  attempt to distribute them.

  PROBLEM:

  Applications compiled against one implementation of OpenCL
  (libOpenCL.so) will not run on a system with another implementation
  installed. OpenCL loader library is supposed to be agnostic to the
  kernel loaded (nvidia libOpenCL.so will run amd kernels for example)
  but testing has shown significant performance differences when using
  OpenCL implementations from different vendors. System must have
  libOpenCL.so used at build time in order to run an application using
  OpenCL

  As the number of OpenCL applications grows there will be packaging
  conflicts between those built against nvidia/ocl and potentially other
  vendor OpenCL implementations as they are added to ubuntu.

  Solution:

  ocl-icd-libopencl1 (http://packages.ubuntu.com/trusty/ocl-icd-
  libopencl1) provides an open source implementation of libOpenCL.so
  that will work with vendor OpenCL kernels files provided by
  intel/nvidia/amd.

  Policy for packages to use ocl-icd as the default implementation,
  allowing the use of other kernel loaders for alternative packages in
  the same source package(if desired)

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

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

[Desktop-packages] [Bug 1350025] [NEW] mousepad bug

[tzotrag]

Public bug reported:

mousepad stoped working after last update

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Jul 29 23:04:46 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0a11]
MachineType: Acer Peppy
ProcEnviron:
 TERM=xterm
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d28a7d8-0815-4575-913f-75f87f1d0a3c ro quiet splash add_efi_memmap 
boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 
nmi_watchdog=panic,lapic vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvncoreboot:bvr:bd04/30/2014:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr:
dmi.product.name: Peppy
dmi.product.version: 1.0
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Jul 29 22:33:04 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4402 
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  mousepad bug

Status in “xorg” package in Ubuntu:
  New

Bug description:
  mousepad stoped working after last update

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jul 29 23:04:46 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0a11]
  MachineType: Acer Peppy
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9d28a7d8-0815-4575-913f-75f87f1d0a3c ro quiet splash add_efi_memmap 
boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 
nmi_watchdog=panic,lapic vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd04/30/2014:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-

[Desktop-packages] [Bug 1349963] Re: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1349963/+attachment/4165294/+files/VarLogDistupgradeTermlog.gz

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

Title:
  package texlive-latex-base 2013.20140215-1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 1

Status in “texlive-base” package in Ubuntu:
  New

Bug description:
  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-latex-base 2013.20140215-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jul 30 02:52:26 2014
  DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2011-10-22 (1011 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: texlive-base
  Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1349963/+subscriptions

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

[Desktop-packages] [Bug 1349963] Re: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[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 texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/1349963

Title:
  package texlive-latex-base 2013.20140215-1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 1

Status in “texlive-base” package in Ubuntu:
  New

Bug description:
  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-latex-base 2013.20140215-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jul 30 02:52:26 2014
  DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2011-10-22 (1011 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: texlive-base
  Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1349963/+subscriptions

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

[Desktop-packages] [Bug 379019] Re: loading subtitles resets the movie

[Edward Donovan]

Ah!  No, not on my system, at least.  Ubuntu 14.04, with all current
updates.  totem is 3.10.1-1ubuntu4 .

Totem hung on me while I was testing, but that seemed related to opening
a movie while another instance was running. I don't have time to go
after that one right now!  But nothing bad appeared at all related to
loading subtitles.

Tested it on two movies.  Loading a new sub file did not reset or change
the point in the movie at all.  Looks fixed here.  Thanks for raising
the question.

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

Title:
  loading subtitles resets the movie

Status in Totem Movie Player:
  Fix Released
Status in “totem” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: totem

  Currently in totem, whenever you load a subtitle from a file, the
  movie restarts. In every other movie player that I tried, movie
  continues to play without any interception. That should be the case
  for totem too.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/totem-gstreamer
  NonfreeKernelModules: nvidia
  Package: totem-gstreamer 2.26.1-0ubuntu5
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 1328542] Re: [xorg-edgers] OCL-ICD provides a free generic OpenCL implementation, should ubuntu policy be to build applications against this loader vs closed vendor implementat

[Graham Inggs]

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

** Changed in: fglrx-driver (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ocl-icd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [xorg-edgers] OCL-ICD provides a free generic OpenCL implementation,
  should ubuntu policy be to build applications against this loader vs
  closed vendor implementations

Status in “fglrx-driver” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “ocl-icd” package in Ubuntu:
  Invalid
Status in “viennacl” package in Ubuntu:
  New

Bug description:
  Relevant Packages: ocl-icd-libopencl1

  Applications that wish to use OpenCL encounter a few problems when you
  attempt to distribute them.

  PROBLEM:

  Applications compiled against one implementation of OpenCL
  (libOpenCL.so) will not run on a system with another implementation
  installed. OpenCL loader library is supposed to be agnostic to the
  kernel loaded (nvidia libOpenCL.so will run amd kernels for example)
  but testing has shown significant performance differences when using
  OpenCL implementations from different vendors. System must have
  libOpenCL.so used at build time in order to run an application using
  OpenCL

  As the number of OpenCL applications grows there will be packaging
  conflicts between those built against nvidia/ocl and potentially other
  vendor OpenCL implementations as they are added to ubuntu.

  Solution:

  ocl-icd-libopencl1 (http://packages.ubuntu.com/trusty/ocl-icd-
  libopencl1) provides an open source implementation of libOpenCL.so
  that will work with vendor OpenCL kernels files provided by
  intel/nvidia/amd.

  Policy for packages to use ocl-icd as the default implementation,
  allowing the use of other kernel loaders for alternative packages in
  the same source package(if desired)

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

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

[Desktop-packages] [Bug 1309727] Re: headphone button does not answer or hangup phone call.

[Bill Filler]

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

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

Title:
  headphone button does not answer or hangup phone call.

Status in Dialer app for Ubuntu Touch:
  Triaged
Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Summary:
  headphone button does not answer or hangup phone call.

  Steps:
  1. plug in headphones with a call/hangup button in headphone jack
  2.  call the phone with the headphones plugged in with step 1
  3.  press headphone answer/hangup button

  expected results:
  call is answered

  actual results
  nothing happens. 

  
  Additional info, this should also play/pause music when no call is in session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1309727/+subscriptions

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

[Desktop-packages] [Bug 349745] Re: Opened sudo gedit -> Apport said pidgin crashed... when it didn't. -> gedit crashed -> apport failed to report the pidgin crash -> apport notified me of gedit crash

[Mörgæs]

Closing due to age.
If a similar bug appears in Ubuntu 14.04 please open a new report.

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

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

Title:
  Opened sudo gedit -> Apport said pidgin crashed... when it didn't. ->
  gedit crashed -> apport failed to report the pidgin crash -> apport
  notified me of gedit crashing 3 minutes later.

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  interestingly enough, non-sudo gedit stayed online.
  I was running the suspend/resume testing just before i rebooted and tried to 
do this (unrelated) stuff
  pidgin didn't crash.. I don't know why it said it did.
  I don't know what to tell you.. half of the time when apport says something 
crashed I don't even know what i was doing at the time, nor what the package it 
claims crashed does or is.

  This is the only time a program that *I* started within a few minutes
  of boot crashed and apport reported it, normally about 5 or 4 programs
  that I don't even know about crash.

  heres a screenshot.. I don't know how to reproduce this issue, nor do
  I really know exactly what happened.

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

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

[Desktop-packages] [Bug 635127] Re: apport-collect errno 13

[Mörgæs]

Closing due to age.
If a similar bug appears in Ubuntu 14.04 please open a new report.


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

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

Title:
  apport-collect errno 13

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: apport

  $ apport-collect 635076
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 368, in 
  app.run_argv()
File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 560, in run_argv
  return self.run_update_report()
File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 422, in 
run_update_report
  if not self.crashdb.can_update(self.options.update_report):
File "/usr/lib/python2.6/dist-packages/apport/crashdb_impl/launchpad.py", 
line 451, in can_update
  if bug.duplicate_of:
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", 
line 643, in __getattr__
  return super(Entry, self).__getattr__(name)
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", 
line 305, in __getattr__
  return self.lp_get_parameter(attr)
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", 
line 196, in lp_get_parameter
  self._ensure_representation()
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", 
line 331, in _ensure_representation
  representation = self._root._browser.get(self._wadl_resource)
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py", 
line 287, in get
  response, content = self._request(url, extra_headers=headers)
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py", 
line 242, in _request
  str(url), method=method, body=data, headers=headers)
File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py", 
line 211, in _request_and_retry
  url, method=method, body=body, headers=headers)
File "/usr/lib/python2.6/dist-packages/httplib2/__init__.py", line 1112, in 
request
  _updateCache(headers, merged_response, content, self.cache, cachekey)
File "/usr/lib/python2.6/dist-packages/httplib2/__init__.py", line 396, in 
_updateCache
  cache.set(cachekey, text)
File "/usr/lib/python2.6/dist-packages/httplib2/__init__.py", line 664, in 
set
  f = file(cacheFullPath, "wb")
  IOError: [Errno 13] Permission denied: 
'/home/keimpe/.launchpadlib/api.edge.launchpad.net/cache/api.edge.launchpad.net,1.0,bugs,635076-application,json,d2cb75d1db219bb37e3c583d33a0a5f2'

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

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

[Desktop-packages] [Bug 461068] Re: [karmic] apport-kde reports bug for wrong package

[Mörgæs]

Closing due to age.
If a similar bug appears in Ubuntu 14.04 please open a new report.

** Changed in: apport (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [karmic] apport-kde reports bug for wrong package

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  This bug was reported from Karbon but Apport (from the Report Bug menu
  item) decided that it is supposed to report it against kdelibs. The
  same seem to happen when I try to report a bug from any other package.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Oct 26 14:11:47 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/kdeinit4
  Package: kdelibs-bin 4:4.3.2-0ubuntu7
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: kde4libs
  Uname: Linux 2.6.31-14-generic x86_64
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (npviewer.bin:4074): Gtk-WARNING **: 
/usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64

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

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

[Desktop-packages] [Bug 319354] Re: MSN user name change to often causes msg box overflow and kills client

[Mörgæs]

Closing due to age.
If a similar bug appears in Ubuntu 14.04 please open a new report.

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

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

Title:
  MSN user name change to often causes msg box overflow and kills client

Status in “pidgin” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pidgin

  If the MSN user changes its name too often, then 
  there is an error msg that shows up, it does not say which user, just that it 
was too often.
  If the name continues to change too often, there will be hundreds of such 
boxes open.
  this is a form of an attack,and can kill the client process and block then 
entire session.

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

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

[Desktop-packages] [Bug 1218294] Re: [dialer app] During a live call, there's no volume adjustment available

[Bill Filler]

just tested on Utopic build 157 and volume adjustment during call
doesn't seem to control the volume of the earpiece, only the speaker
phone. And turning the volume all the way down even when the
speakerphone is on doesn't turn off all the sound as I expected, it just
lowers it to a certain point.

** No longer affects: pulseaudio (Ubuntu Saucy)

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: David Henningsson (diwic) => Ricardo Salveti (rsalveti)

** No longer affects: dialer-app (Ubuntu Saucy)

** No longer affects: dialer-app (Ubuntu)

** No longer affects: dialer-app

** Tags added: rtm14

** Summary changed:

- [dialer app] During a live call, there's no volume adjustment available
+ During a live call, volume adjustment doesn't work in earpiece

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

Title:
  During a live call, volume adjustment doesn't work in earpiece

Status in Ubuntu UX bugs:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Current situation:
  Can't adjust the voice volume during a live call, making it difficult to hear 
the receiver

  Desired:
  Can adjust volume during a live call (Eg using the volume buttons on the 
device)

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

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

[Desktop-packages] [Bug 1350004] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified:
  usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in “libav” package in Ubuntu:
  New

Bug description:
  i can't upgrade my ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Tue Jul 29 10:19:12 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown]
   libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so 
lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so 
lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so 
lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so 
lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so 
lib/x86_64-linux-gnu/libutil-2.19.so]
   libgcc1 1:4.9-20140406-0ubuntu1 [modified: 
lib/x86_64-linux-gnu/libgcc_s.so.1]
   multiarch-support 2.19-0ubuntu6
  DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 
[modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 
6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 
which has multiple installed instances
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-03-26 (490 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: 
libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable 
with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago)

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

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

[Desktop-packages] [Bug 1350004] [NEW] package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git

[gian marco]

Public bug reported:

i can't upgrade my ubuntu

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Tue Jul 29 10:19:12 2014
Dependencies:
 gcc-4.9-base 4.9-20140406-0ubuntu1
 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown]
 libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so 
lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so 
lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so 
lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so 
lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so 
lib/x86_64-linux-gnu/libutil-2.19.so]
 libgcc1 1:4.9-20140406-0ubuntu1 [modified: lib/x86_64-linux-gnu/libgcc_s.so.1]
 multiarch-support 2.19-0ubuntu6
DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 
6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 
which has multiple installed instances
ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
InstallationDate: Installed on 2013-03-26 (490 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: libav
Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: 
libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable 
with libpostproc52 which has multiple installed instances
UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago)

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


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

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified:
  usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in “libav” package in Ubuntu:
  New

Bug description:
  i can't upgrade my ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Tue Jul 29 10:19:12 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown]
   libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so 
lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so 
lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so 
lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so 
lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so 
lib/x86_64-linux-gnu/libutil-2.19.so]
   libgcc1 1:4.9-20140406-0ubuntu1 [modified: 
lib/x86_64-linux-gnu/libgcc_s.so.1]
   multiarch-support 2.19-0ubuntu6
  DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 
[modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 
6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 
which has multiple installed instances
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-03-26 (490 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: 
usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: 
libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable 
with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago)

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

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

[Desktop-packages] [Bug 964673] Re: keyboard shortcut overlay needs more consistent wording

[Gunnar Hjalmarsson]

** No longer affects: ubuntu-translations

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

Title:
  keyboard shortcut overlay needs more consistent wording

Status in Ayatana Design:
  New
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  I'm submitting a merge proposal to go with this.

  The keyboard shortcut overlay (when you hold down the Windows key) has
  several wording issues:

  - Inconsistent verb tenses ("open" and "opens")
  - Minimise (Minimize is the correct spelling in US English, which is what the 
C locale should use)
  - Super (Press) is confusing; changing the text to Super (Hold) makes it more 
clear that holding down the Super key will show the overlay
  - Cursor keys; I think a typical person calls them arrow keys

  This won't affect ubuntu-docs, but it does create new strings for the
  translators.

  Translators notified:
  https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c
  CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Mar 25 13:19:15 2012SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/964673/+subscriptions

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

[Desktop-packages] [Bug 1349983] [NEW] "GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host accounts.google.com not found" while network available

[Lucio Torre]

Public bug reported:

While calling signon_auth_session_new from accounts-polld i kept getting
 2014/07/28 19:26:05 Account 2 failed to authenticate: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host 
accounts.google.com not found

But network was available. Error was not transient as this call was
repeated every 5 minutes for a long time and network on the phone was
available (tested browser and scopes).

Tested on:
$ system-image-cli -i
current build number: 154
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-07-28 15:59:27
version version: 154
version ubuntu: 20140728
version device: 20140725.1

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

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

Title:
  "GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection:
  Host accounts.google.com not found" while network available

Status in “signon” package in Ubuntu:
  New

Bug description:
  While calling signon_auth_session_new from accounts-polld i kept getting
   2014/07/28 19:26:05 Account 2 failed to authenticate: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host 
accounts.google.com not found

  But network was available. Error was not transient as this call was
  repeated every 5 minutes for a long time and network on the phone was
  available (tested browser and scopes).

  Tested on:
  $ system-image-cli -i
  current build number: 154
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-28 15:59:27
  version version: 154
  version ubuntu: 20140728
  version device: 20140725.1

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

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

[Desktop-packages] [Bug 1295207] Re: Migrate to farsight 0.2* / gstreamer 1.0

[Bryan Quigley]

The Pidgin version in upstream git (seems to be for version 3.x), can be
built  --with-gstreamer=1.0

The released (2.10.9) version always wants gstremer0.10.  (I'm not sure
if there are other changes between them that makes gstreamer1.0 work
better..)

If you grep configure.ac and yours has "gst10_pkg" that indicates you're
on the gstreamer1.0 compatible one.

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

Title:
  Migrate to farsight 0.2* / gstreamer 1.0

Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “pidgin” package in Fedora:
  Unknown

Bug description:
  1) Ubuntu 14.04
  2) 1:2.10.9-0ubuntu2
  3) I expect it to depend against the latest farsight/gstreamer 1.0
  4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty 
cd, through libpurple.

  It seems upstream already supports building against farstream-0.2 and 
gstreamer1.0, see:
  https://developer.pidgin.im/wiki/Dependencies

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

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

[Desktop-packages] [Bug 964673] Re: keyboard shortcut overlay needs more consistent wording

[Stephen M. Webb]

This was merged 2012-08-27 and shipped in Ubuntu 12.10, the Fix is as
Released as it's going to get.

** Changed in: unity
   Status: Incomplete => Fix Released

** Changed in: unity (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  keyboard shortcut overlay needs more consistent wording

Status in Ayatana Design:
  New
Status in Ubuntu Translations:
  Triaged
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  I'm submitting a merge proposal to go with this.

  The keyboard shortcut overlay (when you hold down the Windows key) has
  several wording issues:

  - Inconsistent verb tenses ("open" and "opens")
  - Minimise (Minimize is the correct spelling in US English, which is what the 
C locale should use)
  - Super (Press) is confusing; changing the text to Super (Hold) makes it more 
clear that holding down the Super key will show the overlay
  - Cursor keys; I think a typical person calls them arrow keys

  This won't affect ubuntu-docs, but it does create new strings for the
  translators.

  Translators notified:
  https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c
  CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Mar 25 13:19:15 2012SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/964673/+subscriptions

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

[Desktop-packages] [Bug 1348734] Re: SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all

[Joseph Salisbury]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all

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

Bug description:
   ALSA info page http://www.alsa-
  project.org/db/?f=35e0e257c3193758fe2129db6d39552c1af3d687

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vladimir   1512 F pulseaudio
   /dev/snd/controlC1:  vladimir   1512 F pulseaudio
   /dev/snd/pcmC1D0p:   vladimir   1512 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 25 21:22:39 2014
  HibernationDevice: RESUME=UUID=bf69b978-a32b-4de3-a839-4c1ef87ae5fd
  InstallationDate: Installed on 2014-07-24 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Acer Aspire One 522
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=e2267848-1bb4-486d-81e0-ec8507180a34 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.09
  dmi.board.name: Aspire One 522
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.09:bd03/21/2011:svnAcer:pnAspireOne522:pvrV1.09:rvnAcer:rnAspireOne522:rvrV1.09:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire One 522
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1348734/+subscriptions

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

[Desktop-packages] [Bug 1349953] Re: Screen locking issue

[Seth Arnold]

** Information type changed from Private Security to Public

** Package changed: gnome-screensaver (Ubuntu) => unity (Ubuntu)

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

Title:
  Screen locking issue

Status in “unity” package in Ubuntu:
  New

Bug description:
  After coming out of sleep mode, my keyboard cannot type to the
  password entry field. When I try to type to the password entry field,
  the computer sends my input to whatever window I had open before my
  computer went to sleep. This means that if I type my password and
  press enter, and the last window I had open was, say, a gchat, I will
  send my password to the person with whom I was talking.

  It seems like this bug only occurs when I had a text entry field
  selected before putting my computer to sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 29 09:40:10 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 1800
  InstallationDate: Installed on 2012-12-24 (582 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago)

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

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

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Forest]

** Tags added: regression-release saucy

** Tags added: trusty

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+subscriptions

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

[Desktop-packages] [Bug 1349963] [NEW] package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Farmer Schlutzenberg]

Public bug reported:

failed to install

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: texlive-latex-base 2013.20140215-1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Wed Jul 30 02:52:26 2014
DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
InstallationDate: Installed on 2011-10-22 (1011 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: texlive-base
Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package texlive-latex-base 2013.20140215-1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 1

Status in “texlive-base” package in Ubuntu:
  New

Bug description:
  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-latex-base 2013.20140215-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jul 30 02:52:26 2014
  DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2011-10-22 (1011 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: texlive-base
  Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1349963/+subscriptions

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

[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Kiril]

Disabled independent HP by commenting the line in patch_via.c:
//spec->gen.indep_hp = 1;

Headphones does not works after resume.
alsa-info before suspend: 
http://www.alsa-project.org/db/?f=c7f2d491818afda332e303228f893447e71f37e8
alsa-info after resume: 
http://www.alsa-project.org/db/?f=75c3f86d7a1a3c65b0851d402dfa4186b7f15bb0

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions

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

[Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration

[Stefan Bader]

Hi Patricia, that was only the release-notes task. So we just noted
wrote down there that this can happen and how to work around it. I have
not seen or heard anyone fixing (or even looking at) the problem.

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

Title:
  Dual screen greeter can break 3D acceleration

Status in Release Notes for Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  When booting with two screens (internal LVDS and VGA), lightdm comes
  up in a mode where it displays separate screen content on both
  displays (so no mirror mode). These screens seem to be arranged side-
  by-side regardless of the fact that (like in my case) the combined
  width can be greater than 2048 and that is not supported with 3D
  acceleration at least on that older i945GME graphics.

  This results in very poor graphics performance and compiz using a lot
  of cpu cycles (which are rather limited on this Atom N270 anyways).
  Even worse, this does not get resolved when changing the setup in
  system settings to either only having one screen active or arranging
  them on top of each other).

  WORKAROUND:
   * Plug in external monitor after login (1)
   * Boot with "video=LVDS-1:d" (2)

  (1) Booting with only the internal screen and then plugging in the
  external one after login seems to handle this better (although I
  probably need to remove any previous config to get into a kind of
  vanilla state again). Also it seems to be ok when I had the dual
  monitor boot and lightdm coming up side-by-side, when unplugging the
  external monitor before logging in.

  (2) This will completely disable the internal screen for that boot. It
  cannot be enabled through the settings dialogue.

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

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

[Desktop-packages] [Bug 763148] Re: Adding/Removing an external monitor causes open windows to move to another workspace

[Launchpad Bug Tracker]

This bug was fixed in the package compiz - 1:0.9.7.12-0ubuntu4

---
compiz (1:0.9.7.12-0ubuntu4) precise; urgency=low

  * debian/patches/fix_external_monitor_hotplug.patch
- Cherry-pick fixes upstream for window mismanagement when adding
  and/or removing an external monitor. (LP: #763148) (LP: #1171878)
 -- Chris TownsendMon, 07 Jul 2014 
15:15:43 -0400

** Changed in: compiz (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

Title:
  Adding/Removing an external monitor causes open windows to move to
  another workspace

Status in Compiz:
  Fix Released
Status in Compiz 0.9.9 series:
  Fix Committed
Status in Compiz Core:
  Fix Committed
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  Many users will put different windows in different workspaces for better work 
flow.  If a user connects and/or disconnects an external monitor or projector, 
all of these windows will be put in the first workspace.  Having to go back and 
move all of the windows back to their workspaces is very frustrating and time 
consuming.

  [Test Case]
  #. Open some applications in different workspaces.
  #. Plug in an external monitor.

  [Regression Potential]
  Very low possibility that a window still ends up in the wrong workspace.

  

  Original description:
  well, i plug in my external screen.

  expected behaviour would be, if all of my windows would stay in the
  workspaces i aligned them to, and if they'd be on the same screen i
  had them in the first place.

  unfortunatly in unity, if i plug-in (or plug-off) my external screen
  the windows are all around, but not where i'd expect them to be
  (namely in the same place they were before). so i always have to
  toggle expo-mode and re-align all of my windows.

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

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

[Desktop-packages] [Bug 1171878] Re: Adding/Removing an external monitor causes maximized windows to move to another workspace

[Launchpad Bug Tracker]

This bug was fixed in the package compiz - 1:0.9.7.12-0ubuntu4

---
compiz (1:0.9.7.12-0ubuntu4) precise; urgency=low

  * debian/patches/fix_external_monitor_hotplug.patch
- Cherry-pick fixes upstream for window mismanagement when adding
  and/or removing an external monitor. (LP: #763148) (LP: #1171878)
 -- Chris TownsendMon, 07 Jul 2014 
15:15:43 -0400

** Changed in: compiz (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

Title:
  Adding/Removing an external monitor causes maximized windows to move
  to another workspace

Status in Compiz:
  Fix Committed
Status in Compiz Core:
  Fix Committed
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Precise:
  Fix Released

Bug description:
  [Impact]

  If I plug in external monitor, move a window to it, maximize window and 
remove external monitor, window is moved to the same workspace primary screen - 
this is correct behavior, but when I un-maximize it - window moves to different 
workspace. This most likely is because original window positions are not 
updated after removing the monitor and un-maximize still uses those old values 
to move the window to supposedly original position.
  Another use case is when window movement is somewhat wrong - external monitor 
plugged in, window is maximized on primary screen, move focus to different 
workspace, unplug the monitor, move back to the workspace when we have 
fullscreen window, unmaximize it - window un-maximizes not to original 
position, it's moved away by the same mount of pixels as external monitor width 
is.

  I expect that window stays on the same workspace - once it's on it it
  should not move unless I do that manually, also I expect that un-
  maximizing moves window to original position, not different.

  This is continuation of bug
  https://bugs.launchpad.net/compiz/+bug/763148, fullscreen window bug
  was separated as per "Christopher Townsend (townsend) wrote on
  2013-04-18".

  P.S. Most likely bug can be fixed quite easy as behavior is similar to
  bug I mentioned, hopefully this can be included in the same SRU.

  thanks in advance
  Eduards

  [Test Case]

  ** Test Case 1

  1. plug in external monitor and move a windows to it
  2. maximize window
  3. unplug external monitor
  4. window moves to the primary display of the same workspace (this is correct)
  5. un-maximize window
  6. window un-maximizes to a different workspace (this is incorrect)

  ** Test Case 2

  1. plug in external monitor
  2. maximize window on primary (laptop display)
  3. change to a different workspace
  4. unplug external monitor
  5. return to workspace with maximized window
  6. un-maximize window
  7. window un-maximizes to wrong position. instead of the original position it 
is shifted over by the same number of pixels as the width of the external 
monitor (also incorrect)

  [Other information]

  The bug fix also address bug LP: #763148 on precise.

  [Regression]

  None determined && expected.

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

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

[Desktop-packages] [Bug 763148] Update Released

[Chris J Arges]

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

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

Title:
  Adding/Removing an external monitor causes open windows to move to
  another workspace

Status in Compiz:
  Fix Released
Status in Compiz 0.9.9 series:
  Fix Committed
Status in Compiz Core:
  Fix Committed
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  Many users will put different windows in different workspaces for better work 
flow.  If a user connects and/or disconnects an external monitor or projector, 
all of these windows will be put in the first workspace.  Having to go back and 
move all of the windows back to their workspaces is very frustrating and time 
consuming.

  [Test Case]
  #. Open some applications in different workspaces.
  #. Plug in an external monitor.

  [Regression Potential]
  Very low possibility that a window still ends up in the wrong workspace.

  

  Original description:
  well, i plug in my external screen.

  expected behaviour would be, if all of my windows would stay in the
  workspaces i aligned them to, and if they'd be on the same screen i
  had them in the first place.

  unfortunatly in unity, if i plug-in (or plug-off) my external screen
  the windows are all around, but not where i'd expect them to be
  (namely in the same place they were before). so i always have to
  toggle expo-mode and re-align all of my windows.

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

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

[Desktop-packages] [Bug 1171878] Update Released

[Chris J Arges]

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

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

Title:
  Adding/Removing an external monitor causes maximized windows to move
  to another workspace

Status in Compiz:
  Fix Committed
Status in Compiz Core:
  Fix Committed
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Precise:
  Fix Released

Bug description:
  [Impact]

  If I plug in external monitor, move a window to it, maximize window and 
remove external monitor, window is moved to the same workspace primary screen - 
this is correct behavior, but when I un-maximize it - window moves to different 
workspace. This most likely is because original window positions are not 
updated after removing the monitor and un-maximize still uses those old values 
to move the window to supposedly original position.
  Another use case is when window movement is somewhat wrong - external monitor 
plugged in, window is maximized on primary screen, move focus to different 
workspace, unplug the monitor, move back to the workspace when we have 
fullscreen window, unmaximize it - window un-maximizes not to original 
position, it's moved away by the same mount of pixels as external monitor width 
is.

  I expect that window stays on the same workspace - once it's on it it
  should not move unless I do that manually, also I expect that un-
  maximizing moves window to original position, not different.

  This is continuation of bug
  https://bugs.launchpad.net/compiz/+bug/763148, fullscreen window bug
  was separated as per "Christopher Townsend (townsend) wrote on
  2013-04-18".

  P.S. Most likely bug can be fixed quite easy as behavior is similar to
  bug I mentioned, hopefully this can be included in the same SRU.

  thanks in advance
  Eduards

  [Test Case]

  ** Test Case 1

  1. plug in external monitor and move a windows to it
  2. maximize window
  3. unplug external monitor
  4. window moves to the primary display of the same workspace (this is correct)
  5. un-maximize window
  6. window un-maximizes to a different workspace (this is incorrect)

  ** Test Case 2

  1. plug in external monitor
  2. maximize window on primary (laptop display)
  3. change to a different workspace
  4. unplug external monitor
  5. return to workspace with maximized window
  6. un-maximize window
  7. window un-maximizes to wrong position. instead of the original position it 
is shifted over by the same number of pixels as the width of the external 
monitor (also incorrect)

  [Other information]

  The bug fix also address bug LP: #763148 on precise.

  [Regression]

  None determined && expected.

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

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

[Desktop-packages] [Bug 1273498] Re: cant load digital camera to computer

[tiar]

I updated Ubuntu about a week ago and now Ubuntu will recognise my
digital camera. Fixed?

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

Title:
  cant load digital camera to computer

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  cant load my fuji finepix 3300 camera to computer can you tell me why

  ProblemType: Bug
  Architecture: lpia
  Date: Tue Jan 28 01:05:59 2014
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/nautilus
  NonfreeKernelModules: wl
  Package: nautilus 1:2.22.5.1-0ubuntu1netbook1
  PackageArchitecture: lpia
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.24-29-lpia i686
  UnreportableReason: This is not a genuine Ubuntu package

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

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

[Desktop-packages] [Bug 1349009] Re: Renamed program name locally and Software Center & Apps Directory replaced original name with local one

[Matthew Paul Thomas]

sam, thanks for the report. Launchpad shows that the executable was already 
called "pdfsam" in 12.04, and as far back as 10.04.



So I don't know how you got a PDF Split and Merge executable that wasn't
called "pdfsam" to begin with, but you can rest easy that your renaming
didn't cause any changes to the app directory.

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

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

Title:
  Renamed program name locally and Software Center & Apps Directory
  replaced original name with local one

Status in “software-center” package in Ubuntu:
  Invalid

Bug description:
  I'm under shock. In my local Ubuntu 12.04 I installed plenty of time (years) 
ago the package PDF Split and Merge through the Ubuntu Software Center. 
Locally, I renamed the executable name to "pdfsam". I know, a very bad 
practice, but for some reasons it was the quickest for me at that time. I might 
have rated/commented on the software in the USC, I don't remember. Now, with 
another computer and Ubuntu 14.04, I'm shocked to see in the USC the software 
"pdfsam" listed. Moreover, it's also in the Apps Directory:
  https://apps.ubuntu.com/cat/applications/pdfsam/

  I imagine that somehow when I rated the software, it took the name
  locally and uploaded a new entry in the db with such name? Or even
  replaced the original!? Is that possible? I cannot understand
  otherwise what's going on here.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 26 23:23:11 2014
  InstallationDate: Installed on 2014-07-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Raymond]

http://www.intel.com/support/motherboards/desktop/sb/CS-034206.htm


 for desktop, those rear panel line out jacks output support multi channel 
playback and the front panel headphone can support multi streaming on some hda 
codec

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions

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

[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Raymond]

ode 0x08 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Headphone Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Device: name="VT1802 Analog", type="Audio", device=0
  Device: name="VT1802 Alt Analog", type="Audio", device=2


the two devices cannot share   headphone audio output

when multistreaming playback,

alt analog device can play another audio stream for the headphone while
analog device play  audio stream on line out

did you disable independent headphone since it is a bug in hda_generic
to allow independent headphone when HP nid was put in multiout.dac  ?

HP should be put into multiout.hp

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions

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

[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon

[Martin Spacek]

@ Alistair,

I don't explicitly have Unity installed (I'm on Xubuntu 14.04), but a
search via synaptic shows that I do have these Unity-related packages
installed, possibly as dependencies for some piece of software I was
compiling:

gir1.2-unity-5.0 7.1.4+14.04.20140210-0ubuntu1
libunity-protocol-private0 7.1.4+14.04.20140210-0ubuntu1
libunity-scopes-json-def-desktop 7.1.4+14.04.20140210-0ubuntu1
libunity9 7.1.4+14.04.20140210-0ubuntu1
unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1
unity-gtk2-module 0.0.0+14.04.20140403-0ubuntu1
unity-gtk3-module 0.0.0+14.04.20140403-0ubuntu1

Also, I don't have any overlay-scrollbar packages installed, but I do
have these dbusmenu packages installed:

gir1.2-dbusmenu-glib-0.4 12.10.3+14.04.20140612-0ubuntu1
libdbusmenu-qt-dev 0.9.3+14.04.20140314-0ubuntu1
libdbusmenu-qt2 0.9.3+14.04.20140314-0ubuntu1

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

Title:
  Several XFCE applications appear unresponsive after communicating with
  a daemon

Status in pixbuf library for gtk+:
  New
Status in One Hundred Papercuts:
  Triaged
Status in System policy:
  Confirmed
Status in Thunar file manager:
  Confirmed
Status in xfce4-appfinder:
  Confirmed
Status in Xfce4 Power Manager:
  Confirmed
Status in xfce4-settings:
  Fix Released
Status in Volume management daemon for Xfce:
  Confirmed
Status in “gdk-pixbuf” package in Ubuntu:
  Triaged
Status in “policykit-1” package in Ubuntu:
  Triaged
Status in “thunar” package in Ubuntu:
  Triaged
Status in “xfce4-appfinder” package in Ubuntu:
  Triaged
Status in “xfce4-power-manager” package in Ubuntu:
  Triaged
Status in “xfce4-settings” package in Ubuntu:
  Triaged
Status in “xfce4-volumed” package in Ubuntu:
  Triaged

Bug description:
  Several programs in Xfce have a daemon mode call gtk_init() before
  fork()ing.

  This is unsafe, and when it goes wrong this will typically manifest as
  the daemon hanging shortly after forking, and appearing to simply do
  nothing at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions

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