[Desktop-packages] [Bug 1238346] Re: on bootup wrong keyboard layout is recognized

[Thierry Seewald]

Just to give some precision:

when I display the Présentation de l'agencement (keyboard layout or
layout  presentation or whatever) who displays a keyboard, its a french
keyboard which is displayed and when I hit the left corner alphabetical
key on the keyboard it shows that the left corner key is hit and that it
is an a but in all programs it's a q which appears.

And when I deselect and reselect French keyboard on the new keyboard
icon (and french is the only one that appears as a choice in this icon),
then the keyboard is correct.

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

Title:
  on bootup wrong keyboard layout is recognized

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

Bug description:
  This is a regression. 
  I have two keyboard layouts activated, the Dvorak and the English US. The 
Dvorak should be the default keyboard. That is the way I have it set up, and it 
 shows up in the task bar on top as En1, which is the Dvorak.
  However, when I start to type, it starts in QUERTY. 
  ??
  To correct this, I go to the task bar (where it shows EN1, or Dvorak), 
re-select the Dvorak, and then everything is fine. 
  ??

  I have another minor problem which should probably go on another bug, but 
happened at the same time. 
  CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm 
using.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Oct 10 21:20:39 2013
  InstallationDate: Installed on 2013-08-12 (60 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1232575] Re: chrome.extension not available when called from extension scripts in Chromium but works on Chrome

[Martin Endres]

OS: Ubuntu 13.10
Affected package: chromium-browser (29.0.1547.65-0ubuntu2)

The following addons are affected by this issue as well: Adblock,
iReader, SlickRSS and Flashblock, which are all of my installed addons.

Since I'm relying on Google Sync and it seems a bit risky to me to
switch over to development builds, I didn't test the fix above. This
should get fixed in Ubuntu's repositories.

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

Title:
  chrome.extension not available when called from extension scripts in
  Chromium but works on Chrome

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  In Progress

Bug description:
  When I updated to 13.10 and Chromium 29.0.1547.65-0ubuntu2, a few
  extensions stopped working properly. The easiest to reproduce is
  Reddit Enhancement Suite 4.3.0.1, it immediately fails on loading the
  extension with this error:

  chrome.extension is not available: 'extension' is not allowed for
  specified context type content script,  extension page, web page,
  etc.). [VM] binding (22):427

  Following from anywhere that called chrome.extension.sendMessage or
  chrome.extension.onMessage in the extension. Chromium's own bug
  tracker says this usage is deprecated (replaced by chrome.runtime
  namespace which does work) but testing against Chrome 29.0.1547.76 on
  the stable channel, the older namespace works correctly with the
  extensions.

  chromium-browser:
Installed: 29.0.1547.65-0ubuntu2
Candidate: 29.0.1547.65-0ubuntu2
Version table:
   *** 29.0.1547.65-0ubuntu2 0
  500 http://mirrors.cat.pdx.edu/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

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

[asmodey]

Guys, this bug is critical! How can it be, that it isn't being fixed in
months?

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

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

[zhum]

Please, fix!!!

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1242524] [NEW] No sound after suspend HP Notebook 6530b

[Thomas]

Public bug reported:

After upgrading from Raring to Saucy, I got no sound when returning from 
suspend.
From boot to suspend, sound is working well.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: pulseaudio 1:4.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u0949672517 F pulseaudio
 /dev/snd/pcmC0D0p:   u0949672517 F...m pulseaudio
Date: Mon Oct 21 07:57:23 2013
EcryptfsInUse: Yes
MarkForUpload: True
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago)
dmi.bios.date: 12/02/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.17
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.23
dmi.chassis.asset.tag: CNU0095MXM
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.17:bd12/02/2010:svnHewlett-Packard:pnHPCompaq6530b(GW688AV):pvrF.17:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6530b (GW688AV)
dmi.product.version: F.17
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug saucy

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

Title:
  No sound after suspend HP Notebook 6530b

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  After upgrading from Raring to Saucy, I got no sound when returning from 
suspend.
  From boot to suspend, sound is working well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u0949672517 F pulseaudio
   /dev/snd/pcmC0D0p:   u0949672517 F...m pulseaudio
  Date: Mon Oct 21 07:57:23 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.17
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU0095MXM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.17:bd12/02/2010:svnHewlett-Packard:pnHPCompaq6530b(GW688AV):pvrF.17:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6530b (GW688AV)
  dmi.product.version: F.17
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1242524] Re: No sound after suspend HP Notebook 6530b

[Raymond]

try latest alsa driver

https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS


post the output of alsa-info.sh 

pactl stat

pactl list

and

pulseaudio verbose log

https://wiki.ubuntu.com/PulseAudio/Log

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

Title:
  No sound after suspend HP Notebook 6530b

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  After upgrading from Raring to Saucy, I got no sound when returning from 
suspend.
  From boot to suspend, sound is working well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u0949672517 F pulseaudio
   /dev/snd/pcmC0D0p:   u0949672517 F...m pulseaudio
  Date: Mon Oct 21 07:57:23 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.17
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU0095MXM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.17:bd12/02/2010:svnHewlett-Packard:pnHPCompaq6530b(GW688AV):pvrF.17:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6530b (GW688AV)
  dmi.product.version: F.17
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Sergio]

I used CapsLock for switching for years (Shift+CapsLock for capitals
locking), it must be fixed. I've temporarily set Ctrl+Shift+Space (as
Super+Space does not work!) for switching and noticed that NumLock turns
off every time i switch!

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1242418] Re: unity no background

[Timo Aaltonen]

nautilus didn't start for some reason

** Package changed: xorg (Ubuntu) = nautilus (Ubuntu)

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

Title:
  unity no background

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  install lubuntu-desktop and gnome

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.12.5-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: Sun Oct 20 14:15:43 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, i686: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3642]
  InstallationDate: Installed on 2013-10-18 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=es_PA:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_PA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=ca9ae5da-2982-4c26-880e-ec9e7f07aafb ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2009
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3642
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 40.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd12/10/2009:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvr049E212412101:rvnHewlett-Packard:rn3642:rvr40.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv4 Notebook PC
  dmi.product.version: 049E212412101
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Oct 20 14:13:41 2013
  xserver.configfile: default
  xserver.errors:
   open /dev/fb0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2

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

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

[Desktop-packages] [Bug 1242478] Re: Multiple graphics problems, regression

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu)

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

Title:
  Multiple graphics problems, regression

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

Bug description:
  Graphics driver will regularly freeze for ~30 seconds, emitting this
  type of messages over and over:

  [ 1652.976556] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CC98 (len 62, WS 0, PS 0) @ 0xCCB4
  [ 1652.976562] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing C372 (len 861, WS 0, PS 0) @ 0xC3CF
  [ 1657.984602] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more 
than 5secs aborting
  [ 1657.984611] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing D024 (len 72, WS 0, PS 0) @ 0xD053
  [ 1662.992448] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more 
than 5secs aborting
  [ 1662.992456] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CC98 (len 62, WS 0, PS 0) @ 0xCCB4

  I can reproduce this failure at any time by changing the screen
  brightness on the laptop. It sometimes happens spontaneously as well,
  and sometimes when I start the Screen Display settings app.

  When it finally unfreezes, I get incorrect screen resolutions,
  incorrect number of monitors, a frozen mouse pointer on screen (on top
  of everything else, even on top of the real mouse pointer), and
  sometimes rendering glitches. It will continue emitting this type of
  message:

  [ 2747.265512] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
  [ 2747.310454] radeon :01:00.0: couldn't schedule ib
  [ 2747.310460] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
  [ 2747.339220] radeon :01:00.0: couldn't schedule ib
  [ 2747.339226] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
  [ 2747.371411] radeon :01:00.0: couldn't schedule ib

  These messages will not cease unless I reboot, adding 50 lines/second
  to my logs.

  This is a clean install of Ubuntu 13.10, running Gnome shell (I
  installed gnome-core). Previously this laptop ran 12.10 and while I
  did see the occasional glitch it was never this severe.

  I should also add that I have a script which switches off the discrete
  graphics chip on startup (through echo OFF 
  /sys/kernel/debug/vgaswitcheroo/switch). I will deactivate this to see
  if it make any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 21 01:50:04 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0359]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-10-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 4820TG
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.25:bd03/16/2011:svnAcer:pnAspire4820TG:pvrV1.25:rvnAcer:rnJM41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4820TG
  dmi.product.version: V1.25
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1242422] Re: Xorg freeze

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu)

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

Title:
  Xorg freeze

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

Bug description:
  I hace just clean install the Ubuntu 13.10 release . Some times the
  whole screen freezes and i have to rebooting using the power off
  button of my laptop. I believe it's a X.org Problem. Notice that no
  Open-GL application is running.

  Thank you for your Time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 20 22:39:28 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218M [GeForce G210M] [10de:0a74] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0296]
  InstallationDate: Installed on 2013-10-17 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 7736
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=a13ed582-ddb0-4d39-bc22-881be829f81b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V2.01
  dmi.board.name: JV50
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV2.01:bd10/06/2009:svnAcer:pnAspire7736:pvr0100:rvnAcer:rnJV50:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 7736
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Oct 20 21:09:18 2013
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1241894] Re: Network History no longer works in System Monitor on 13.10

[Launchpad Bug Tracker]

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

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New = Confirmed

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

Title:
  Network History no longer works in System Monitor on 13.10

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

Bug description:
  The graph for Network History in Resources tab does not update.
  Neither does the received and sent data relating to Network History
  get updated. All the data is just stuck at 0.

  This started happening after an upgrade to 13.10 from 13.04. It worked
  perfectly well on 13.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-system-monitor 3.8.2.1-2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 19 06:39:18 2013
  InstallationDate: Installed on 2013-07-06 (104 days ago)
  InstallationMedia: This
  MarkForUpload: True
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1242275] Re: Extreme load times after installing and setting up nvidia-319

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) = nvidia-graphics-drivers-319
(Ubuntu)

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

Title:
  Extreme load times after installing and setting up nvidia-319

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

Bug description:
  1) I'm using Ubuntu GNOME 13.10
  2) Latest Packages (Okt 20)
  3) I expected it load normally
  4) lots of things broke:
- It took extremely long to load (before installation it was extremely 
quick)
- GTK themes is broken (Look like classic X almost)

  Thing that are borken that I didn't check before installation:
- Shortcut keys don't work
   

  How to reproduce:
  After a clean installation of Ubuntu GNOME 13.10
  I installed vim (to edit text files) and nvidia-319
  I set xorg.conf as specified by nvidia
  I added the lines
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
  to the top of the /etc/gcm/Init/Default file (nvidia said xinitrc, but that 
is not run when running gdm)
  reboot and then problems appear

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Oct 20 10:26:59 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5105]
   NVIDIA Corporation GK104M [GeForce GTX 675MX] [10de:11a7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5105]
  InstallationDate: Installed on 2013-10-19 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: CLEVO P15xEMx
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=391583ce-8803-4e00-8321-60d9b764 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: P15xEMx
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: CLEVO
  dmi.chassis.version: Not Applicable
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/19/2012:svnCLEVO:pnP15xEMx:pvrNotApplicable:rvnCLEVO:rnP15xEMx:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable:
  dmi.product.name: P15xEMx
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Oct 20 10:21:03 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/libglamoregl.so: 
/usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
   Failed to load module glamoregl (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2

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

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

[Desktop-packages] [Bug 1241973] Re: Xorg server crashes during reboot when Modesetting is active on Radeon 7790

[Timo Aaltonen]

install xdiagnose and run 'apport-collect 1241973' after it has crashed

** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu)

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New = Incomplete

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

Title:
  Xorg server crashes during reboot when Modesetting is active on Radeon
  7790

Status in “xserver-xorg-video-ati” package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Kubuntu 13.10 Xorg crashes during startup unless
  I deactivate Modesetting support in grub. I am using the free radeon
  driver (not the proprietary one).

  The lspci output for the graphics card is:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Bonaire XT [Radeon HD 7790/8770]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 19 10:48:43 2013
  InstallationDate: Installed on 2011-05-21 (881 days ago)
  InstallationMedia: Kubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  MarkForUpload: True
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)

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

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

[Desktop-packages] [Bug 1216094] nimbus: audio connector issues

[andreas]

Dear Felix,

I was able to get the microphone to work as described here:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1216094

Raymond has many comments/suggestions about how to make the pink jack 
switchable between mic and line in (and the green between line out and 
speakers or headphones).

May I presume this affects many of your customers? So perhaps you could 
have a look at this?

Best wishes,
Andreas Demey

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

Title:
  [Cirrus7 Nimbus, Realtek ALC892, Pink Line In, Rear] No sound at all

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

Bug description:
  I cannot get a microphone to work (attached to back, pink line-in). I
  hope all neccessary information is in automated attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas2221 F pulseaudio
  Date: Fri Aug 23 22:06:07 2013
  InstallationDate: Installed on 2013-07-08 (46 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Intern geluid - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas2221 F pulseaudio
  Symptom_Jack: Pink Line In, Rear
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC892, Pink Line In, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KBQ7710H.86A.0051.2013.0329.1350
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ77KB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG81483-500
  dmi.chassis.type: 81
  dmi.chassis.vendor: cirrus7 computing
  dmi.chassis.version: rev1
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKBQ7710H.86A.0051.2013.0329.1350:bd03/29/2013:svncirrus7computing:pnnimbus:pvrrev1:rvnIntelCorporation:rnDQ77KB:rvrAAG81483-500:cvncirrus7computing:ct81:cvrrev1:
  dmi.product.name: nimbus
  dmi.product.version: rev1
  dmi.sys.vendor: cirrus7 computing

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

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

[Desktop-packages] [Bug 1241894] Re: Network History no longer works in System Monitor on 13.10

[Gal Miara]

ubuntu 13.10, 64 bit

0 net activity on the monitor.
same on the devices tab in network tools.
netstat -s --raw seems to work fine.

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

Title:
  Network History no longer works in System Monitor on 13.10

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

Bug description:
  The graph for Network History in Resources tab does not update.
  Neither does the received and sent data relating to Network History
  get updated. All the data is just stuck at 0.

  This started happening after an upgrade to 13.10 from 13.04. It worked
  perfectly well on 13.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-system-monitor 3.8.2.1-2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 19 06:39:18 2013
  InstallationDate: Installed on 2013-07-06 (104 days ago)
  InstallationMedia: This
  MarkForUpload: True
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

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

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

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

[Povilas Balzaravičius aka Pawka]

Impossible to work while this bug exist. I can't believe this was
released along with stable release. One more drop to switch to other
distro.

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1241745] Re: Changing the screen brightness does not work anymore in 13.10

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) = nvidia-graphics-drivers-319
(Ubuntu)

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

Title:
  Changing the screen brightness does not work anymore in 13.10

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

Bug description:
  Changing the screen brightness always used to work on my HP Elitebook
  8560w -- both with the function keys and in the dialog Brightness 
  Lock in the system settings. The environment light sensor also used
  to work IIRC.

  Since the update to 13.10, this stopped working. Methods I have tried
  for adapting the brightness are:

  * Adding GRUB_CMDLINE_LINUX=acpi_backlight=vendor to /etc/default/grub
  * Adding GRUB_CMDLINE_LINUX=”acpi_osi=!Windows 2012 to /etc/default/grub

  None of them worked.

  Currently I am changing the brightness manually using  xrandr --output
  LVDS-0 --brightness 0.9. However, AFAIK this does not really change
  the brightness, but only changes the contrast.

  Workarounds would be much appreciated.

  ===
  Opened a related question on AskUbuntu:
  
http://askubuntu.com/questions/362894/changing-the-brightness-stopped-working-in-13-10-saucy-salamander
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 19:50:36 2013
  DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
   nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-01-06 (285 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash 
acpi_osi=!Windows 2012
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.27
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Fri Oct 18 19:39:07 2013
  xserver.configfile: default
  

[Desktop-packages] [Bug 1241745] Re: Changing the screen brightness does not work anymore in 13.10

[Ingo Gerth]

** Description changed:

  Changing the screen brightness always used to work on my HP Elitebook
  8560w -- both with the function keys and in the dialog Brightness 
  Lock in the system settings. The environment light sensor also used to
  work IIRC.
  
  Since the update to 13.10, this stopped working. Methods I have tried
  for adapting the brightness are:
  
  * Adding GRUB_CMDLINE_LINUX=acpi_backlight=vendor to /etc/default/grub
  * Adding GRUB_CMDLINE_LINUX=”acpi_osi=!Windows 2012 to /etc/default/grub
  
  None of them worked.
  
  Currently I am changing the brightness manually using  xrandr --output
  LVDS-0 --brightness 0.9. However, AFAIK this does not really change the
  brightness, but only changes the contrast.
  
  Workarounds would be much appreciated.
  
+ ===
+ Opened a related question on AskUbuntu:
+ 
http://askubuntu.com/questions/362894/changing-the-brightness-stopped-working-in-13-10-saucy-salamander
+ ===
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
-  GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
+  GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 19:50:36 2013
  DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
-  nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
+  nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
+  nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:1631]
+  NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-01-06 (285 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  JockeyStatus:
-  kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
-  kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
-  kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
-  kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
+  kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
+  kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
+  kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
+  kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash 
acpi_osi=!Windows 2012
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.27
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  

[Desktop-packages] [Bug 1240870] Re: nautilus performance when copying several files from smbnetfs (fuse)

[muzzol]

** Description changed:

  I'm using smbnetfs for accesing a remote fileserver:
  
-smbnetfs on /tmp/test type fuse.smbnetfs
+    smbnetfs on /tmp/test type fuse.smbnetfs
  (rw,nosuid,nodev,user=e1)
  
  when I copy a directory with several (hundreds) of files performance is
  really bad and it takes lot of time.
  
  for example a directori with 300 files takes 5 seconds with `cp' command
  
-$ time cp -r USMT301/ /tmp/
+    $ time cp -r USMT301/ /tmp/
  
-real   0m4.671s
-user   0m0.020s
-sys0m0.128s
+    real   0m4.671s
+    user   0m0.020s
+    sys0m0.128s
  
  and with nautilus takes about 10 minutes. so it's clearly a problem with 
nautilus, not smbnetfs.
  if you copy just one big file (for example an ISO) performance is OK.
  
  to replicate just launch smbnetfs and copy a dir with several files with
  nautilus.
  
  I'm not sure if it affects other fuse filesystems and it seems related
  to nautilus not recognizing fuse mount point as a remote filesystem.
  
  maybe related:
  
  https://bbs.archlinux.org/viewtopic.php?id=101691
+ https://bugzilla.gnome.org/show_bug.cgi?id=657208
+ 
  
  this is a critical stopper for me as I already migrated 50 desktops to linux 
in my department and I just discovered this.
  any solution or workaround will be really wellcome.
  
  please, ask for further info.
  
+    $ lsb_release -rd
+    Description:   Ubuntu 12.04.3 LTS
+    Release:   12.04
  
-$ lsb_release -rd
-Description:   Ubuntu 12.04.3 LTS
-Release:   12.04
- 
- 
-ii  nautilus  1:3.4.2-0ubuntu8  file manager and graphical shell 
for GNOME
-ii  smbnetfs  0.5.3a-1  User-space 
filesystem for SMB/NMB (Windows) network servers
+    ii  nautilus  1:3.4.2-0ubuntu8  file manager and graphical shell 
for GNOME
+    ii  smbnetfs  0.5.3a-1  User-space 
filesystem for SMB/NMB (Windows) network servers

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

Title:
  nautilus performance when copying several files from smbnetfs (fuse)

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  I'm using smbnetfs for accesing a remote fileserver:

     smbnetfs on /tmp/test type fuse.smbnetfs
  (rw,nosuid,nodev,user=e1)

  when I copy a directory with several (hundreds) of files performance
  is really bad and it takes lot of time.

  for example a directori with 300 files takes 5 seconds with `cp'
  command

     $ time cp -r USMT301/ /tmp/

     real   0m4.671s
     user   0m0.020s
     sys0m0.128s

  and with nautilus takes about 10 minutes. so it's clearly a problem with 
nautilus, not smbnetfs.
  if you copy just one big file (for example an ISO) performance is OK.

  to replicate just launch smbnetfs and copy a dir with several files
  with nautilus.

  I'm not sure if it affects other fuse filesystems and it seems related
  to nautilus not recognizing fuse mount point as a remote filesystem.

  maybe related:

  https://bbs.archlinux.org/viewtopic.php?id=101691
  https://bugzilla.gnome.org/show_bug.cgi?id=657208

  
  this is a critical stopper for me as I already migrated 50 desktops to linux 
in my department and I just discovered this.
  any solution or workaround will be really wellcome.

  please, ask for further info.

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

     ii  nautilus  1:3.4.2-0ubuntu8  file manager and graphical shell 
for GNOME
     ii  smbnetfs  0.5.3a-1  User-space 
filesystem for SMB/NMB (Windows) network servers

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

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

[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name

[Kyle Gordon]

This bug is also present in Ubuntu 13.10

network-manager, 0.9.8.0-0ubuntu22
network-manager-dev, 0.9.8.0-0ubuntu22
network-manager-gnome, 0.9.8.0-1ubuntu5
network-manager-openvpn, 0.9.8.2-1ubuntu2
network-manager-openvpn-gnome, 0.9.8.2-1ubuntu2
network-manager-pptp, 0.9.8.2-1ubuntu2
network-manager-pptp-gnome, 0.9.8.2-1ubuntu2

Kyle

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

Title:
  Network indicator displays random text for bluetooth network name

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

Bug description:
  The attached images tell most of the story.

  I set up Bluetooth tethering on my phone with name Searle. I boot my
  Ubuntu laptop. Searle is shown in the network indicator menu. After
  I connect nm-applet is shown. After I disconnect _Configure VPN...
  is shown. At other times I have seen the words separator, Label
  Empty and I have also een undisplayable characters.

  network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to
  Ubuntu 13.04.

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

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

[Desktop-packages] [Bug 1238346] Re: on bootup wrong keyboard layout is recognized

[Kachanovich Siargey]

Same problem.

It is likely to go back to qwerty when the layout is changed via
keyboard layout change shortcut. When you change it with Super+Space it
is often stuck on one keyboard layout and sometimes it corresponds with
the selected layout, sometimes not.

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

Title:
  on bootup wrong keyboard layout is recognized

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

Bug description:
  This is a regression. 
  I have two keyboard layouts activated, the Dvorak and the English US. The 
Dvorak should be the default keyboard. That is the way I have it set up, and it 
 shows up in the task bar on top as En1, which is the Dvorak.
  However, when I start to type, it starts in QUERTY. 
  ??
  To correct this, I go to the task bar (where it shows EN1, or Dvorak), 
re-select the Dvorak, and then everything is fine. 
  ??

  I have another minor problem which should probably go on another bug, but 
happened at the same time. 
  CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm 
using.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Oct 10 21:20:39 2013
  InstallationDate: Installed on 2013-08-12 (60 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Valera Lewontyev]

Fix extremely needed!

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1209092] Re: network : gnome-control-center crashed with SIGABRT in g_assertion_message

[jan2ary]

The bug is still here as for gnome-control-center version
3.6.3-0ubuntu44.

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

Title:
   network : gnome-control-center crashed with SIGABRT in
  g_assertion_message

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  The problem arised after upgrade to 13.10.
  To reproduce:
  1. Click on System Settings
  2. Gnome Control Center window appears
  3. Click on Network under Hardware section
  4. At this point Gnome Control Center window crashes.

  Thanks.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu30
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug  7 09:30:30 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2010-03-26 (1229 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so
   ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so
  Title: [network]: gnome-control-center crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to saucy on 2013-08-07 (0 days ago)
  UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare
  usr_lib_gnome-control-center:
   activity-log-manager0.9.7-0ubuntu4
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.19~13.04-0ubuntu1
   indicator-datetime  12.10.3+13.10.20130731-0ubuntu1

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

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

[Desktop-packages] [Bug 1235785] Re: Light Display Manager is offered as login option

[Shaharil Ahmad]

still on saucy.

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

Title:
  Light Display Manager is offered as login option

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

Bug description:
  Test case:
  Fresh install of current image (10/05 here
  Log in to guest account, log out
  Light Display Manager is now a login option

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 17:10:44 2013
  InstallationDate: Installed on 2013-10-05 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131005)
  MarkForUpload: True
  SourcePackage: unity-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

[Filippos Kolyvas]

I confirm that the bug is fixed for GTK core applications (gedit, nautilus) and 
Mozilla Firefox.
Well done @ all who worked in this!

I can also confirm that the bug still affects typing when using
LibreOffice and when using KDE applications (such as kate text editor)
on Ubuntu with standard Unity desktop environment.

I haven' tested this on UbuntuGnome.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10

Status in IBus:
  New
Status in Indicator keyboard:
  Fix Committed
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Fix Released

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout. 
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly. 

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters-keyboard-hotkeys-windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.

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

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

[Desktop-packages] [Bug 1241745] Re: Changing the screen brightness does not work anymore in 13.10

[Ingo Gerth]

As per Timo's hint, I reverted back to nvidia-graphics-drivers-304 from
the repos and am not experiencing this issue anymore. Of course, it
would be desirable to have working 319 drivers, to get all the
performance fixes crucial to OpenGL applications etc.

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

Title:
  Changing the screen brightness does not work anymore in 13.10

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

Bug description:
  Changing the screen brightness always used to work on my HP Elitebook
  8560w -- both with the function keys and in the dialog Brightness 
  Lock in the system settings. The environment light sensor also used
  to work IIRC.

  Since the update to 13.10, this stopped working. Methods I have tried
  for adapting the brightness are:

  * Adding GRUB_CMDLINE_LINUX=acpi_backlight=vendor to /etc/default/grub
  * Adding GRUB_CMDLINE_LINUX=”acpi_osi=!Windows 2012 to /etc/default/grub

  None of them worked.

  Currently I am changing the brightness manually using  xrandr --output
  LVDS-0 --brightness 0.9. However, AFAIK this does not really change
  the brightness, but only changes the contrast.

  Workarounds would be much appreciated.

  ===
  Opened a related question on AskUbuntu:
  
http://askubuntu.com/questions/362894/changing-the-brightness-stopped-working-in-13-10-saucy-salamander
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 19:50:36 2013
  DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
   nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-01-06 (285 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash 
acpi_osi=!Windows 2012
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.27
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

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

[Serj Kondrashov]

Please, fix it!

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

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

[Launchpad Bug Tracker]

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

** Changed in: evolution-data-server (Ubuntu)
   Status: New = Confirmed

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

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

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

Bug description:
  About 2 minutes after loging into ubuntu 13.04 this faultmessage
  appear.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evolution-data-server 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  Date: Thu Mar  7 19:33:40 2013
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2013-02-03 (31 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130202)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
  Title: evolution-calendar-factory crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1241745] Re: Changing the screen brightness does not work anymore in 13.10

[Timo Aaltonen]

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

** Changed in: nvidia-graphics-drivers-319 (Ubuntu)
   Status: New = Triaged

** Summary changed:

- Changing the screen brightness does not work anymore in 13.10
+ [regression] Changing the screen brightness does not work anymore in 319.xx

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

Title:
  [regression] Changing the screen brightness does not work anymore in
  319.xx

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

Bug description:
  Changing the screen brightness always used to work on my HP Elitebook
  8560w -- both with the function keys and in the dialog Brightness 
  Lock in the system settings. The environment light sensor also used
  to work IIRC.

  Since the update to 13.10, this stopped working. Methods I have tried
  for adapting the brightness are:

  * Adding GRUB_CMDLINE_LINUX=acpi_backlight=vendor to /etc/default/grub
  * Adding GRUB_CMDLINE_LINUX=”acpi_osi=!Windows 2012 to /etc/default/grub

  None of them worked.

  Currently I am changing the brightness manually using  xrandr --output
  LVDS-0 --brightness 0.9. However, AFAIK this does not really change
  the brightness, but only changes the contrast.

  Workarounds would be much appreciated.

  ===
  Opened a related question on AskUbuntu:
  
http://askubuntu.com/questions/362894/changing-the-brightness-stopped-working-in-13-10-saucy-salamander
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 19:50:36 2013
  DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
   nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-01-06 (285 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash 
acpi_osi=!Windows 2012
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.27
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)

[dino99]

** Tags removed: oneiric
** Tags added: i386 nouveau saucy

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

Title:
  LightDM fails to start after nvidia-current or nvidia-current-updates
  are installed (upstart job issue)

Status in Light Display Manager:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged

Bug description:
  Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX
  485M, GTX 560M or GTX 580M.

  Appears to be a race condition. LightDM attempts to start before
  /dev/nvidiactrl is created. As a workaround add sleep 1  service
  lightdm start to /etc/rc.local to start the service.

  ### This workaround is insufficient. Some users have reported that
  their systems do not start after initial user setup. Deleting the
  contents of /var/run/dbus/* resolves the issue in these cases. ###

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Oct 13 11:05:18 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5102]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: System76, Inc. Serval Professional
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Serval Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serp7
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: serp7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7:
  dmi.product.name: Serval Professional
  dmi.product.version: serp7
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1242359] Re: Always puts LANGUAGE=en into seesion environment despite German locale

[Gunnar Hjalmarsson]

Okej

But the combination of environment variables you stated still confuses
me. User accounts does not set session env. vars, and if nothing is
stored in accountsservice - which is correct since ~/.pam_environment
isn't there - accountsservice should respond with de or de_DE in your
case when queried for Language (assuming that you edited
/etc/default/locale manually).

Just curious, since I was involved in the the changed lightdm behavior
above, and you made me fear that we overlooked something.

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

Title:
  Always puts LANGUAGE=en into seesion environment despite German locale

Status in “lightdm” package in Ubuntu:
  Invalid

Bug description:
  A few weeks ago, my session started to be in English. I can't pinpoint
  when that started, with some lightdm upgrade or a reinstallation of my
  laptop, but my session in lightdm now always has

  LANG=de_DE.UTF-8
  GDM_LANG=en
  LANGUAGE=en

  in its environment, and there seems to be no way to change it. I have
  no idea where this is coming from, my configuration files:

  $ cat /etc/default/locale 
  LANG=de_DE.UTF-8
  $ cat /etc/environment 
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  $ cat ~/.pam_environment
  cat: /home/martin/.pam_environment: No such file or directory
  $ cat .dmrc 
  [Desktop]
  Session=ubuntu
  $ sudo cat /var/cache/lightdm/dmrc/martin.dmrc
  [Desktop]
  Session=ubuntu

  I don't know of another file which should be relevant for lightdm and
  contain the LANGUAGE=en, so I assume lightdm just somehow invents
  this. I even tried to change lightdm's keyboard selector from en (I
  use US keyboard layout) to de. This properly changed the keyboard
  layout, but doesn't drop/change LANGUAGE.

  I also confirmed this with another local user, the very same problem
  happens for that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 20 16:26:58 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-14 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013)
  MarkForUpload: True
  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/1242359/+subscriptions

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

[Desktop-packages] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)

[dino99]

Here are my bad experiences on Saucy i386:

- have made 2 fresh installations on a desktop (old one with bios) via the 
saucy'netinstall iso  this weekend
- one used as saucy with nouveau works as expected
- the othersaucy ready for a trusty dist-upgrade, only display a black 
screen after having popped boot in low graphic mode

- have also made a dist-upgrade from raring i386 (which was working) to
saucy (no ppa around) and also get that issue failing  to a black
screen. This is on an old  laptop (bios) with radeon, even vesa
fails

note: maybe that discussion can help (i will investigate it)
http://askubuntu.com/questions/346738/13-04-lightdm-crashing-black-screen-flashing-cursor

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

Title:
  LightDM fails to start after nvidia-current or nvidia-current-updates
  are installed (upstart job issue)

Status in Light Display Manager:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged

Bug description:
  Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX
  485M, GTX 560M or GTX 580M.

  Appears to be a race condition. LightDM attempts to start before
  /dev/nvidiactrl is created. As a workaround add sleep 1  service
  lightdm start to /etc/rc.local to start the service.

  ### This workaround is insufficient. Some users have reported that
  their systems do not start after initial user setup. Deleting the
  contents of /var/run/dbus/* resolves the issue in these cases. ###

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Oct 13 11:05:18 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5102]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: System76, Inc. Serval Professional
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Serval Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serp7
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: serp7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7:
  dmi.product.name: Serval Professional
  dmi.product.version: serp7
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  

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

[Norbert]

1. I installed gnome-panel in fresh 13.10 and I can switch layouts with 
Super+Space and Shift+Super+Space.
What is interesting if I login (on boot) to Gnome Flashback session I can use 
Super+Space and Shift+Super+Space for layout switching.
If then I logout and login to Ubuntu (Unity) session I can switch layouts with 
Alt+Shift (scroll lock indicates layout, but indicator-keyboard in gnome panel 
is not change).
As far I can understand - Alt+Shift combination is created by installer and 
stored in /etc/default/keyboard (commented lines removed):
#...
XKBMODEL=pc105
XKBLAYOUT=us,ru
XKBVARIANT=,
XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll
#...

2. I also installed fresh Ubuntu GNOME 13.10 and I unable to set
Ctrl+Shift or Alt+Shift for layout switching in it. Alt+Shift works only
if it is defined in /etc/default/keyboard (by ubiquity). Super+Space and
Shift+Super+Space works normally.

3. @Lockal
installing GNOME 3.10 from PPA is not a solution for this bug.
The solution is to fix it before release or drop indicator-keyboard away now as 
not-well-tested alpha stage application. Or, of course, use 12.04.3 LTS.


So there are configuration problems between indicator-keyboard, xkbswitch, ibus 
and so on.

And it seems that ubiquity is also related to this bug - it wrote
Alt+Shift combination to /etc/config/keyboard , while on first login
there is a small notification about Ibus and Super+Space for layout
switching. See https://launchpad.net/bugs/1242572 .

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

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

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1215836] Re: Sync xfonts-terminus 4.38-1 (universe) from Debian unstable (main)

[Daniel Holbach]

Sitting in the queue now, please close manually.

 xfonts-terminus (4.38-1fakesync1) trusty-proposed; urgency=low
 .
   * Fake sync due to mismatching orig tarball.
 .
 xfonts-terminus (4.38-1) unstable; urgency=low
 .
   * New upstream releases (4.36 and 4.38), closes: #716800.
 - Some new symbols (quotedblreversed, I/i/U/u dotbelow)
 - Changes in few symbols.
 - New 22 pseudographic symbols.
   * Run xset fp rehash in the postinst if possible.  Thanks to
 gennady.kupava, closes: #690549.


** Changed in: xfonts-terminus (Ubuntu)
   Status: New = Fix Committed

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

Title:
  Sync xfonts-terminus 4.38-1 (universe) from Debian unstable (main)

Status in “xfonts-terminus” package in Ubuntu:
  Fix Committed

Bug description:
  Please sync xfonts-terminus 4.38-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* New upstream releases (4.36 and 4.38). 
  The ubuntu delta was created just so we had a garantee for saucy. Since 
debian now has the latest version, this is a sync.

  Changelog entries since current saucy version 4.38-0ubuntu1:

  xfonts-terminus (4.38-1) unstable; urgency=low

* New upstream releases (4.36 and 4.38), closes: #716800.
  - Some new symbols (quotedblreversed, I/i/U/u dotbelow)
  - Changes in few symbols.
  - New 22 pseudographic symbols.
* Run xset fp rehash in the postinst if possible.  Thanks to
  gennady.kupava, closes: #690549.

   -- Anton Zinoviev zinov...@debian.org  Thu, 01 Aug 2013 23:23:21
  +0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-terminus/+bug/1215836/+subscriptions

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

[Desktop-packages] [Bug 1234469] Re: Network does not come up after resuming from suspend.

[Catalin Hritcu]

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

I've tried suggested by pitti. After the first suspend and resume I get this:
Lid closed.
Suspending...
Failed to send delayed message: Message did not receive a reply (timeout by 
message bus)
Lid opened.

Networking was disabled so I brought it back up with nmcli nm sleep
false. Then I suspended again. After the second suspend trying to
resume just led to another suspend I didn't ask for. Had to force
another resume (power button) before the thing actually resumed:

Lid closed.
Suspending...
Failed to execute operation: Message did not receive a reply (timeout by 
message bus)
Suspending...
Operation finished.
Lid opened.

Earlier today it happened to me that I couldn't resume at all because of
this problem happening many times in a row. I would get to the login
prompt but the machine would go back to sleep so fast that I wouldn't
even have time to enter my password. I had to power off and restart the
machine to take it out of that state. I'm on a Dell Latitude E6400.

BTW. Should I stop commenting here and switch to #1184262 instead?

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

Title:
  Network does not come up after resuming from suspend.

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

Bug description:
  When my computer wakes up from being suspended, the wireless network 
connection doesn't come back up.
  I'm able to fix the problem by running nmcli nm sleep false, which causes 
the wireless card to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 20:21:33 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (54 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  IpRoute:
   default via 192.168.125.1 dev wlan0  proto static 
   192.168.125.0/24 dev wlan0  proto kernel  scope link  src 192.168.125.8  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90   
802-3-ethernet1380753272   Wed 02 Oct 2013 05:34:32 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   9739  172c6f5c-b69c-40dd-ac1b-a279c84a17f8   
802-11-wireless   1380763079   Wed 02 Oct 2013 08:17:59 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled enabled

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

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

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

[Norbert]

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

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

Status in Indicator keyboard:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1217091] Re: getUserMedia doesn't work in Firefox/Unity in Ubuntu 13.10

[Rocko]

Perhaps this is related to http://support.mozilla.org/en-
US/questions/967768? That points to an alsa-lib issue in
snd_device_name_hint reported as bug #1008600. There is apparently a fix
for that resolves the issue. But bug #1008600 is only flagged as fix-
committed, not fix-released.

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

Title:
  getUserMedia doesn't work in Firefox/Unity in Ubuntu 13.10

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Firefox doesn't ask for permission to use my camera or microphone when
  calling getUserMedia. Instead, it just does nothing. None of the tests
  here work: http://mozilla.github.io/webrtc-landing/

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 23.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  BuildID: 20130807180628
  Channel: Unavailable
  Date: Mon Aug 26 22:35:55 2013
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.104  metric 
1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-3081eb08-2163-454d-b541-5572f2121104
  Plugins:
   Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
  PrefSources:
   prefs.js
   
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
   
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
   
[Profile]/extensions/zoteroopenofficeintegrat...@zotero.org/defaults/preferences/zoteroOpenOfficeIntegration.js
  Profiles: Profile0 (Default) - LastVersion=23.0/20130807180628 (In use)
  RelatedPackageVersions:
   gnome-shell   3.8.4-0ubuntu1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-3081eb08-2163-454d-b541-5572f2121104
   bp-3ab5a053-9a78-4948-a5ca-a56372121010
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to saucy on 2013-06-17 (70 days ago)
  dmi.bios.date: 09/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785GM-E51 (MS-7596)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd09/28/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7596:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785GM-E51(MS-7596):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7596
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Desktop-packages] [Bug 1024508] Re: WPA authentication - regression on 12.04 / ath9k

[Oleksij Rempel]

Hi,
can you please test it with Ubuntu 13.10.

** Tags added: ath9k-htc

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

Title:
  WPA authentication - regression on 12.04 / ath9k

Status in “wpasupplicant” package in Ubuntu:
  New

Bug description:
  Since I upgraded my desktop to 12.04, I have observed a bad regression w.r.t. 
my WiFi access. Everything else the same, I used to be very happy with my 
USB-dongle TP-Link TL-WN721N (Atheros AR9271). I was connected always, 
immediately, and reliably for days on a go. 
  After the upgrade, it connects only once out of 3, and asks repeatedly for 
the WiFi key, over and over. Even when entering the correct one, it will not 
connect and ask again ... .

  To debug, I have released the strict WPA2, AES only on the access point to 
any WPA*. The same thing can be observed, still, under these relaxed conditions:
  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
  Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
  Mode:Master
  Extra:tsf=ca0b7181
  Extra: Last beacon: 25856ms ago
  IE: Unknown: 00057769726173
  IE: Unknown: 010882848B0C12961824
  IE: Unknown: 030108
  IE: IEEE 802.11i/WPA2 Version 1
  Group Cipher : TKIP
  Pairwise Ciphers (2) : CCMP TKIP
  Authentication Suites (1) : PSK
  IE: WPA Version 1
  Group Cipher : TKIP
  Pairwise Ciphers (2) : CCMP TKIP
  Authentication Suites (1) : PSK
  IE: Unknown: 2A0100
  IE: Unknown: 32043048606C

  In order to provide clear information, I have switched between a
  dongle TP-Link TL-WN321G and the one mentioned above; just by plugging
  in and out; not touching anything else.

  I attach the syslog, showing how quickly the tr73usb connects after I removed 
the ath9k from the previous swap of the dongles  From 19:40:44 it takes around 
7 seconds to authenticate.
  Then I remove this dongle and plug back the one with ath9k. The syslog 
clearly shows that it takes close to one minute, until after a good handful 
number of trials, to get it connected. I repeat: in most cases it doesn't. My 
grouses are not on the long time, but that it usually times out before a trial 
becomes successful.

  I don't say this is a strong signal:
  Mode:Managed  Frequency:2.447 GHz  Access Point: 00:11:F5:22:24:40

   
Bit Rate=11 Mb/s   Tx-Power=20 dBm  

 
Retry  long limit:7   RTS thr:off   Fragment thr:off

 
Power Management:off

 
Link Quality=37/70  Signal level=-73 dBm

 
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

 
Tx excessive retries:0  Invalid misc:559   Missed beacon:0  
  , but too strong to blame it. Especially since the said rt73usb and an even 
older zd1211 (3Com) connect favourably.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: wpasupplicant 0.7.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jul 13 20:05:08 2012
  InstallationMedia: Kubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpasupplicant
  UpgradeStatus: Upgraded to precise on 2012-06-14 (29 days ago)

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

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

[Desktop-packages] [Bug 1229484] Re: Thunderbird freezes for 30s, rendering it unusable

[Launchpad Bug Tracker]

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

** Changed in: thunderbird (Ubuntu)
   Status: New = Confirmed

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

Title:
  Thunderbird freezes for 30s, rendering it unusable

Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Thunderbird, the main MailNews pane freezes while
  polling Inboxes on my 2 IMAP accounts.

  The main window freezes (graying out) for 30s, then comes back for
  10s, then freezes again. In the 10s it is not grayed out, it is not
  really responsive. CPU is at 100%, and memory consumption is high.

  I have observed this already on Raring, but it is present in the Saucy
  version as well. I have tried to restart in safe mode, disabling all
  add-ons, without any improvement.

  On a side note, I have a lot of folders and my inbox has  8000
  messages, and I'm doing this over a high latency link (I'm in APAC, my
  mail server is in Europe, so ~350ms RTT).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: thunderbird 1:24.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  BuildID: 20130917155107
  Date: Tue Sep 24 09:00:25 2013
  InstallationDate: Installed on 2013-03-19 (188 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318)
  MarkForUpload: True
  Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date)
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to saucy on 2013-09-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1214021] Re: Thunderbird freezes when viewing emails, clicking Get Mail, and other tasks

[Launchpad Bug Tracker]

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

** Changed in: thunderbird (Ubuntu)
   Status: New = Confirmed

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

Title:
  Thunderbird freezes when viewing emails, clicking Get Mail, and
  other tasks

Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  See above

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 17.0.8+build1-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16
  Uname: Linux 3.5.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rajiv  1983 F pulseaudio
  BuildID: 20130803235212
  Channel: Unavailable
  Date: Mon Aug 19 12:18:30 2013
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.19  metric 
9
  MarkForUpload: True
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: 17.0.8 (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.database.lastMaintenance: 1375673204 (prefs.js)
   places.history.expiration.transient_current_max_pages: 29717 (prefs.js)
   print_printer: Brother-MFC-7840W (prefs.js)
  Profiles: Profile0 (Default) - LastVersion=17.0.8/20130803235212 (In use)
  RelatedPackageVersions:
   google-talkplugin 4.4.2.0-1
   rhythmbox-mozilla 2.97-1ubuntu6.1
   totem-mozilla 3.4.3-0ubuntu5
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6EET21WW (1.02 )
  dmi.board.name: 2776L9U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6EET21WW(1.02):bd10/09/2008:svnLENOVO:pn2776L9U:pvrThinkPadX301:rvnLENOVO:rn2776L9U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2776L9U
  dmi.product.version: ThinkPad X301
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 192508] Re: mouse keys too easy to accidently turn on

[Id2ndR]

In saucy the combination is Alt + LShift + NumLock. The problem is that it is 
not listed in Settings  Keyboard  Shortcuts  Universal Access.
It's also difficult to find Settings  Universal Access  Pointing and Clicking 
 Mouse Keys (Control the pointer using the keypad) to go back to normal 
behavior after using the combination by mistake.
In fact it was easier for me to find 
org/gnome/desktop/a11y/keyboard/mousekeys-enable=true using dconf dump / (this 
is a paradox about accessibility! )

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

Title:
  mouse keys too easy to accidently turn on

Status in GNOME Control Center:
  New
Status in One Hundred Paper Cuts:
  Confirmed
Status in GNOME Remote Desktop:
  New
Status in X.Org X server:
  In Progress
Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  I am using Hardy Heron and several times now I have tried to use my
  number pad only to discover that they now move the mouse. I don't know
  if there is a short cut key I am hitting on accident, but it is rather
  annoying. Then sometimes when I disable mouse keys, the numlock
  becomes switched so that the system thinks numlock is on when the
  light is off and vice-versa.

  Update: the shortcut is: shift+num-lock

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

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

[Desktop-packages] [Bug 1241220] [NEW] after upgrade my touchpad scrolling did not work on my Acer Aspire

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

no problems before upgrade on I believe 13.06.  after upgrade and
reboot, didn't work.  went to system settings mouse and touchpad,
everything looked OK.  enabled natural scrolling and it still did not
work.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
CrashDB: ubuntu
Date: Thu Oct 17 16:21:35 2013
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to saucy on 2013-10-17 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: apport-bug dist-upgrade i386 saucy
-- 
after upgrade my touchpad scrolling did not work on my Acer Aspire 
https://bugs.launchpad.net/bugs/1241220
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xserver-xorg-input-synaptics 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 197589] Re: Numeric keypad no longer works after upgrade

[Id2ndR]

Alt + LShift + NumLock works on saucy (bug #192508 comments #91).

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

Title:
  Numeric keypad no longer works after upgrade

Status in GNOME Control Center:
  Unknown
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “xserver-xorg-input-keyboard” package in Ubuntu:
  Invalid

Bug description:
  I have standard ps2 keyboard and ps2-to-usb adapter. Numeric keys
  section stopped to work after updating to hardy. Num Lock on or off
  doesn't help. The numeric keys above letters work ok.

  If I log in to virtual konsole (Ctrl-Alt-F2) numeric keys work.

  xorg.conf:
  Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout fi
  EndSection
  [lspci]
  00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge 
[1106:0204]
Subsystem: Acer Incorporated [ALI] Unknown device [1025:006e]
  01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. S3 Unichrome 
Pro VGA Adapter [1106:3108] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Unknown device [1025:006e]

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

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

[Desktop-packages] [Bug 1241220] Re: after upgrade my touchpad scrolling did not work on my Acer Aspire

[Jean-Baptiste Lallement]

** Package changed: ubuntu-release-upgrader (Ubuntu) = xserver-xorg-
input-synaptics (Ubuntu)

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

Title:
  after upgrade my touchpad scrolling did not work on my Acer Aspire

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

Bug description:
  no problems before upgrade on I believe 13.06.  after upgrade and
  reboot, didn't work.  went to system settings mouse and touchpad,
  everything looked OK.  enabled natural scrolling and it still did not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubuntu-release-upgrader-core 1:0.205
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  CrashDB: ubuntu
  Date: Thu Oct 17 16:21:35 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1242402] Re: error while loading shared libraries: libturbojpeg.so

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New = Confirmed

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

Title:
  error while loading shared libraries: libturbojpeg.so

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

Bug description:
  chromium-browser fails to start with error message:
  /bin/sh: error while loading shared libraries: libturbojpeg.so: cannot open 
shared object file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 20 20:18:40 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-08-23 (422 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)

[Silvan Wehrli]

I had the same issue, but the glib from saucy proposed fixed it for me
as well. Thank you very much.

Btw: I don't know if this problem is related to it, but if I right click
in the digital camera folder and select open in terminal, a terminal
pops up quickly and is immediatly closed again. This only occurs in the
camera folder, otherwise this feature works. If it doesn't relate to
this problem, I will make another bug report.

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

Title:
  [Regression] Can't copy files from digital camera (Operation not
  supported by backend)

Status in GVFS:
  Invalid
Status in “glib2.0” package in Ubuntu:
  In Progress
Status in “glib2.0” source package in Saucy:
  Confirmed
Status in “glib2.0” source package in Trusty:
  In Progress
Status in “gvfs” package in Debian:
  Fix Released
Status in “gvfs” package in Fedora:
  Unknown

Bug description:
  [ Description ]

  Copying from some devices is broken over gvfs

  [ Test case ]

  - browse a directory with a .tar.gz, using nautilus
  - right click on the file, select open with archive mounter 

  - that makes the archive being listed as a mount in the sidebar/unity
  launcher

  - browse that mount, find a file to copy in there
  - try to copy it to your user directory

  - if the fix is doing its job, the copy should work without error

  [ Proposed fix ]

  Cherry-pick upstream commit 44edc3829d6db3fabe22d837eaaf2638003516c9
  to fall back to g_file_query_info if query_info_on_read isn't
  supported.

  [ Regression potential ]

  Adds an extra step into file copying over gvfs. Check all previous
  gvfs copies still work.

  [ Original report ]

  Hello,

  on Saucy I can't copy files from my digital camera to my PC anymore
  via file manager. This is a serious regression since it worked on all
  previous version of Ubuntu since Lucid at least (even earlier versions
  not tested because I didn't own the camera at that time).

  It is easy to reproduce:
  - Start PC from USB stick with current Saucy daily live image
  - Connect and turn on camera
  - Open Nautilus, browse the files on the camera, select one of them and 
right-click - copy
  - Now when I try to paste the file into my home directory, I get an error 
dialog saying copying failed with the reason Operation not supported by 
backend (see attached screenshot)

  I get the same error message if I try to copy the file on terminal
  with the command gvfs-copy.

  However, if I try to copy a file on terminal with the gphoto2 tool,
  e.g. 'gphoto2 --get-file 1', this works.

  It also works if I copy files with cp in a terminal from gvfs-
  mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint .

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgphoto2-6 2.5.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 07:18:22 2013
  LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130826)
  MarkForUpload: True
  SourcePackage: libgphoto2
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-08-02 (34 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802)
  MarkForUpload: True
  Package: gvfs 1.17.90-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Tags:  saucy
  Uname: Linux 3.11.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1242612] [NEW] Unable to change Backlight level while using Nvidia driver

[Norbert]

Public bug reported:

I have Sony VAIO F13Z1R laptop with discrete Nvidia GT425M:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 425M] 
(rev a1)

On fresh Ubuntu 13.10 (or 13.10 GNOME) I'm unable to change backlight level 
while using Nvidia 304 driver (304.88-0ubuntu8).
I see backlight desktop indicator, it reacts on fn+backlight keys, but level is 
not changed.

Nouveau driver controls my backlight level normally.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nvidia-current 304.88-0ubuntu8
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Mon Oct 21 14:01:54 2013
InstallationDate: Installed on 2013-10-20 (0 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-304
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 saucy

** Summary changed:

- Unable to chanfge Backlight level while using Nvidia driver
+ Unable to change Backlight level while using Nvidia driver

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

Title:
  Unable to change Backlight level while using Nvidia driver

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

Bug description:
  I have Sony VAIO F13Z1R laptop with discrete Nvidia GT425M:
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 
425M] (rev a1)

  On fresh Ubuntu 13.10 (or 13.10 GNOME) I'm unable to change backlight level 
while using Nvidia 304 driver (304.88-0ubuntu8).
  I see backlight desktop indicator, it reacts on fn+backlight keys, but level 
is not changed.

  Nouveau driver controls my backlight level normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-current 304.88-0ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 21 14:01:54 2013
  InstallationDate: Installed on 2013-10-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1236025] Re: Please merge bittorrent (3.4.2-11.5) from Debian unstable

[Daniel Holbach]

I updated the changelog entry to have this bug number and target it to
trusty instead. Thanks.

** Changed in: bittorrent (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Please merge bittorrent (3.4.2-11.5) from Debian unstable

Status in “bittorrent” package in Ubuntu:
  Fix Committed

Bug description:
  Debian changelog since last merge:

  bittorrent (3.4.2-11.5) unstable; urgency=low

* Non-maintainer upload.
* Drop useless dh_python call (Closes: #715296).
* Drop useless XB-Python-Version fields.
* Drop useless pycompat file.

   -- Luca Falavigna dktrkr...@debian.org  Sun, 14 Jul 2013 02:30:02
  +0200

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

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

[Desktop-packages] [Bug 1242612] Re: Unable to change Backlight level while using Nvidia driver

[Norbert]

Screen resolution is correct (full-hd 1920x1080).
Backlight control works after manually creation of /etc/X11/xorg.conf by 
nvidia-xconfig and adding
{
Option RegistryDwords EnableBrightnessControl=1
}
to the Device section.

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

Title:
  Unable to change Backlight level while using Nvidia driver

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

Bug description:
  I have Sony VAIO F13Z1R laptop with discrete Nvidia GT425M:
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 
425M] (rev a1)

  On fresh Ubuntu 13.10 (or 13.10 GNOME) I'm unable to change backlight level 
while using Nvidia 304 driver (304.88-0ubuntu8).
  I see backlight desktop indicator, it reacts on fn+backlight keys, but level 
is not changed.

  Nouveau driver controls my backlight level normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-current 304.88-0ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 21 14:01:54 2013
  InstallationDate: Installed on 2013-10-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors

[Launchpad Bug Tracker]

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

** Changed in: at-spi2-core (Ubuntu)
   Status: New = Confirmed

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

Title:
  at-spi2 daemon error messages in .xsession-errors

Status in “at-spi2-core” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the following messages in .xsession-errors

  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd respawning too fast, stopped

  I use a Lenovo Thinkpad Twist convertible with touch screen, using
  Onboard in tablet mode.

  Can perhaps have a relation with bug 1227173.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions

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

[Desktop-packages] [Bug 1193084] Re: libreoffice email as pdf does not attach anything

[Robert Hrovat]

Same problem with 13.10. Changing default mail client helps.

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

Title:
  libreoffice email as pdf does not attach anything

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  When working on an ODF document and needing to send to MS windows users, I 
file/send/email as pdf and it would bring up an email window with an attached 
pdf of the ODF I was working on. 
  Now, it only opens an email window with no attachment or pdf, but the subject 
line is thenameofthedocument.pdf
  I cannot confirm, but I remember this working well in 12.10 and 12.04. Seems 
to be an issue recently with 13.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-core 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Thu Jun 20 11:54:29 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-01-02 (168 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to raring on 2013-04-03 (77 days ago)

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

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

[Desktop-packages] [Bug 1242616] [NEW] empathy-account crash

[Juha Siltala]

Public bug reported:

Crash when trying to edit accounts.

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

** Attachment added: _usr_bin_empathy-accounts.1000.crash
   
https://bugs.launchpad.net/bugs/1242616/+attachment/3886051/+files/_usr_bin_empathy-accounts.1000.crash

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

Title:
  empathy-account crash

Status in “empathy” package in Ubuntu:
  New

Bug description:
  Crash when trying to edit accounts.

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

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

[Desktop-packages] [Bug 1242615] [NEW] [USB-Audio - U46DJ] Not correctly recognized and no outputs

[Han]

Public bug reported:

Description:Ubuntu 13.10
Release:13.10

After upgrading to Ubuntu/Xubuntu 13.10,  the ESI U46DJ is now
recognized as a Surround device, which it isn't.

http://i43.tinypic.com/juiogm.png

http://www.esi-audio.com/products/u46dj

Besides, if I turn on the ESI after booting to Ubuntu/Xubuntu, only the
inputs are recognized. I need to turn it on before booting to
Ubuntu/Xubuntu to use the outputs.

http://i39.tinypic.com/aetr8j.png

Before upgrading to 13.10 the U46DJ was perfectly recognized and worked
like a charm.

Regards.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  han2252 F pulseaudio
 /dev/snd/controlC1:  han2252 F pulseaudio
Date: Mon Oct 21 11:06:55 2013
InstallationDate: Installed on 2013-10-15 (5 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U46DJ failed
Symptom_Card: U46DJ - U46DJ
Symptom_Type: None of the above
Title: [USB-Audio - U46DJ, playback] Playback problem
UpgradeStatus: Upgraded to saucy on 2013-10-18 (2 days ago)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-DS3H
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.:bvrF9:bd09/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H: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.

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


** Tags: amd64 apport-bug saucy

** Attachment added: Screenshot - 191013 - 11:37:55.png
   
https://bugs.launchpad.net/bugs/1242615/+attachment/3886044/+files/Screenshot%20-%20191013%20-%2011%3A37%3A55.png

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

Title:
  [USB-Audio - U46DJ] Not correctly recognized and no outputs

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

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10

  After upgrading to Ubuntu/Xubuntu 13.10,  the ESI U46DJ is now
  recognized as a Surround device, which it isn't.

  http://i43.tinypic.com/juiogm.png

  http://www.esi-audio.com/products/u46dj

  Besides, if I turn on the ESI after booting to Ubuntu/Xubuntu, only
  the inputs are recognized. I need to turn it on before booting to
  Ubuntu/Xubuntu to use the outputs.

  http://i39.tinypic.com/aetr8j.png

  Before upgrading to 13.10 the U46DJ was perfectly recognized and
  worked like a charm.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  han2252 F pulseaudio
   /dev/snd/controlC1:  han2252 F pulseaudio
  Date: Mon Oct 21 11:06:55 2013
  InstallationDate: Installed on 2013-10-15 (5 days ago)
  InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U46DJ failed
  Symptom_Card: U46DJ - U46DJ
  Symptom_Type: None of the above
  Title: [USB-Audio - U46DJ, playback] Playback problem
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (2 days ago)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  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: 

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

[Norbert]

I commented out all four lines in /etc/default/keyboard and installed
packages from ppa:attente/1218322 and now I'm able to switch with
Ctrl+Shift or Alt+Shift or Caps Lock. Thank you, William Hua!

Tested on:
1. Ubuntu 13.10 (Unity and Gnome Flashback sessions).
2. Ubuntu 13.10 GNOME (GNOME, GNOME Classic, GNOME FlashBack sessions).

But shortcuts (such as Ctrl+Alt+T) on non-latin layout do not work (see
https://launchpad.net/bugs/1226962).

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

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

Status in Indicator keyboard:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

[Norbert]

I have installed latest packages from ppa:attente/1218322 (Ctrl+Shift or
Alt+Shift or Caps Lock - all work as layout switchers between English
and Russian), but shortcuts (such as Ctrl+Alt+T) on non-latin layout do
not work (UbuntuGnome, Ubuntu).

** Tags added: saucy

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10

Status in IBus:
  New
Status in Indicator keyboard:
  Fix Committed
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Fix Released

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout. 
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly. 

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters-keyboard-hotkeys-windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.

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

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

[Desktop-packages] [Bug 1131099] Re: Can not edit or add new bookmarks/places to nautilus

[Neal Cloud]

** Changed in: nautilus (Ubuntu)
   Status: Invalid = Confirmed

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

Title:
  Can not edit or add new bookmarks/places to nautilus

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Can not add a new bookmark.

Reproduce:

According to the help menu, Go the folder I want to add  menu 
  bookmarks  add new bookmark (but this does not exist)

or

Menu  Bookmarks  There is a minus sign to remove, but no plus sign
  to add new

  
  Can not edit bookmarks

 Reproduce:

 Menu  Bookmarks  Edit an existing entry to a new folder (Eg. 
/home/brucey/Pictures to /home/brucey/Test). Then double click the name on the 
left and you get an error message saying Unhandled error message: Error when 
getting information for file '/home/brucey/test': No such file or directory. 
And it is not added to the bookmarks/places in nautilus

  The unity quicklist menu also does not relate to the places listed in
  nautilus

  I know these should maybe be posted as separate bugs, but they seem
  related enough to be be together

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb 21 08:51:10 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'927x1028+66+24'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-02-11 (10 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1242355] Re: libreoffice base connection to mdb via odbc crashes on saving odb file

[Christopher M. Penalver]

magowiz, could you please attach the database file that demonstrates
this problem?

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

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

Title:
  libreoffice base connection to mdb via odbc crashes on saving odb file

Status in “libreoffice” package in Ubuntu:
  Incomplete

Bug description:
  I was trying to connect to an existing mdb (MS Access) database file using 
unixodbc and libreoffice-base,
  I've got unixodbc , undixodbc-bin and libmdbodbc1 packages installed
  I set the odbc as following :

  /etc/odbc.ini
  [Pippo]
  Description = mine database
  Driver = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
  Database = /home/magowiz/pippo.mdb

  /etc/odbcinst.ini
  [MDBTools]
  Description = MDBTools Driver
  Driver = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
  Setup = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
  Usage = 1
  FileUsage = 1
  UsageCount = 2

  I use the connection wizard into libreoffice base : I can successfully
  test mine connection but while I'm saving the odb file the whole
  program crashes and close itself

  It follows distro and software versions :

  $ lsb_release -rd
  Description: Ubuntu 13.10
  Release: 13.10

  apt-cache policy libreoffice-base
  libreoffice-base:
Installed: 1:4.1.2~rc3-0ubuntu1
Candidate: 1:4.1.2~rc3-0ubuntu1

  apt-cache policy unixodbc
  unixodbc:
Installed: 2.2.14p2-5ubuntu4
Candidate: 2.2.14p2-5ubuntu4

  apt-cache policy libmdbodbc1
  libmdbodbc1:
Installed: 0.7-3
Candidate: 0.7-3

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-core 1:4.1.2~rc3-0ubuntu1 [modified: 
usr/lib/libreoffice/program/libcomphelper.so 
usr/lib/libreoffice/program/libi18nlangtag.so 
usr/lib/libreoffice/program/libmergedlo.so 
usr/lib/libreoffice/program/libspalo.so 
usr/lib/libreoffice/program/libucbhelper.so 
usr/lib/libreoffice/program/libunopkgapp.so 
usr/lib/libreoffice/program/oosplash usr/lib/libreoffice/program/pluginapp.bin 
usr/lib/libreoffice/program/soffice.bin usr/lib/libreoffice/program/spadmin.bin 
usr/lib/libreoffice/program/unopkg.bin usr/lib/libreoffice/program/uri-encode]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Oct 20 16:19:16 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: libreoffice
  Stacktrace:
   No symbol __nih_abort_msg in current context.
   Python Exception class 'AttributeError' 'dict' object has no attribute 
'iteritems': 
   Python Exception class 'AttributeError' 'dict' object has no attribute 
'iteritems':
  StacktraceTop:
   
  Title: soffice.bin crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1232726] Re: Dash bg color doesn't match its surroundings

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/overlay-renderer-not-glsl-color-fix

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  Triaged
Status in Unity 7.1 series:
  Triaged
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Lately, after login the Dash keeps a black background even if the
  Launcher and panel follow the current wallpaper color. I've added a
  screenshot. If I change the wallpaper, Dash recovers its chameleonic
  effect (until next reboot).

  Also, this started happening at the same time that a new error message
  (at log time) appeared, I've attached this error message, too.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity:
    Installed: 7.1.1+13.10.20130927.1-0ubuntu1
    Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
    Version table:
   *** 7.1.1+13.10.20130927.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 29 08:00:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2013-08-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic 
root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0A
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7111JLR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (GF451LA#ABM)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  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.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Sep 29 07:53:46 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputTV-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1232726] Re: Dash bg color doesn't match its surroundings

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/overlay-renderer-not-glsl-color-
fix-7.1

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  In Progress
Status in Unity 7.1 series:
  In Progress
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Lately, after login the Dash keeps a black background even if the
  Launcher and panel follow the current wallpaper color. I've added a
  screenshot. If I change the wallpaper, Dash recovers its chameleonic
  effect (until next reboot).

  Also, this started happening at the same time that a new error message
  (at log time) appeared, I've attached this error message, too.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity:
    Installed: 7.1.1+13.10.20130927.1-0ubuntu1
    Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
    Version table:
   *** 7.1.1+13.10.20130927.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 29 08:00:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2013-08-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic 
root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0A
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7111JLR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (GF451LA#ABM)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  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.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Sep 29 07:53:46 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputTV-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: intel

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

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

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

[jadi]

Thank you @norbert, worked for me. Using Colemak+Farsi with Shift + Alt
L

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

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

Status in Indicator keyboard:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1131099] Re: Can not edit or add new bookmarks/places to nautilus

[Neal Cloud]

Installed a clean ubuntu 13.10
Got hdmi sound going, using additional drivers after reboot.
added my network shares in fstab then rebooted, added my bookmarks to the 
network share, worked ok...
Updated ubuntu then rebooted, system crashed. forced reboot.
only the server bookmark all others missing can delete this bookmark but carnt 
get it back...
Ctrl+D brings up search bar...

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

Title:
  Can not edit or add new bookmarks/places to nautilus

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Can not add a new bookmark.

Reproduce:

According to the help menu, Go the folder I want to add  menu 
  bookmarks  add new bookmark (but this does not exist)

or

Menu  Bookmarks  There is a minus sign to remove, but no plus sign
  to add new

  
  Can not edit bookmarks

 Reproduce:

 Menu  Bookmarks  Edit an existing entry to a new folder (Eg. 
/home/brucey/Pictures to /home/brucey/Test). Then double click the name on the 
left and you get an error message saying Unhandled error message: Error when 
getting information for file '/home/brucey/test': No such file or directory. 
And it is not added to the bookmarks/places in nautilus

  The unity quicklist menu also does not relate to the places listed in
  nautilus

  I know these should maybe be posted as separate bugs, but they seem
  related enough to be be together

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb 21 08:51:10 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'927x1028+66+24'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-02-11 (10 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 273695] Re: open office writer doesn't accept new bullet defaults

[Christopher M. Penalver]

R Becke, this will never be addressed in OpenOffice.org in Ubuntu as
this is not supported. Despite this, if this is reproducible in
LibreOffice, please give verbatim click-for-click instructions on how to
reproduce.

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

Title:
  open office writer doesn't accept new bullet defaults

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

Bug description:
  Binary package hint: openoffice.org

  OOo Writer:
  When changing the default spacing parameters in the bullet/numbering options, 
the new defaults are not automatically applied to subsequent bullet lists.
  Ubuntu 8.04 Hardy
  OOo 2.4

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Sep 23 19:55:17 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:2.4.1-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.24-19-generic x86_64

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

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

[Desktop-packages] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)

[dino99]

Wonder if that new black screen issue is due to that kernel trouble:
- regression in recent kernels not displaying X output, so cant see lightdm 
login

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483

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

Title:
  LightDM fails to start after nvidia-current or nvidia-current-updates
  are installed (upstart job issue)

Status in Light Display Manager:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged

Bug description:
  Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX
  485M, GTX 560M or GTX 580M.

  Appears to be a race condition. LightDM attempts to start before
  /dev/nvidiactrl is created. As a workaround add sleep 1  service
  lightdm start to /etc/rc.local to start the service.

  ### This workaround is insufficient. Some users have reported that
  their systems do not start after initial user setup. Deleting the
  contents of /var/run/dbus/* resolves the issue in these cases. ###

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Oct 13 11:05:18 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5102]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: System76, Inc. Serval Professional
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Serval Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serp7
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: serp7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7:
  dmi.product.name: Serval Professional
  dmi.product.version: serp7
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1057186] Re: Modem Huawei E173 works in 12.04 but not in 12.10

[BemNum]

Hello,
The same problem exists in Kubuntu 13.10 with Huawei E173 and Dell Latitude 
E6430. Only storage is active.

See the following scenario:
1) turn on the computer, log in
2) connect the USB modem Huawei E173
3) The modem is not detected (see the following commands):
% lsusb|grep -i huawei
Bus 001 Device 005: ID 12d1:1c0b Huawei Technologies Co., Ltd. E173s 3G 
broadband stick (modem off)
% ls /dev/ttyUSB*
no matches found: /dev/ttyUSB*

To activate modem run:
4) remove the USB modem Huawei E173

5) Run the following command to load usbserial module (see correct vendor and 
product code):
# modprobe -v usbserial vendor=0x12d1 product=0x1c08

6) You can also turn on usb_modeswitch logging:
# diff /etc/usb_modeswitch.conf-ORG /etc/usb_modeswitch.conf
19c19
 EnableLogging=0
---
 EnableLogging=1

7) connect the USB modem Huawei E173 again

8) The modem is properly detected:
# lsusb|grep Huawei
Bus 001 Device 007: ID 12d1:1c08 Huawei Technologies Co., Ltd. 
# ls /dev/ttyUSB*
/dev/ttyUSB0  /dev/ttyUSB1
# tail -n 20 /var/log/usb_modeswitch.log
Mode switch succeeded. Bye.

ok:12d1:1c08

(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
 Reading attributes ...
USB dir exists: /sys/bus/usb/devices/1-1.2
Warning: USB attribute serial not readable.
 All attributes matched
Mode switching was successful, found 12d1:1c08 (HUAWEI: HUAWEI Mobile)
Now checking for bound driver ...
 driver has bound, device is known
Checking for AVOID_RESET_QUIRK kernel attribute
 AVOID_RESET_QUIRK activated

All done, exiting

9) Now you can correctly connect using e.g. wvdial via /dev/ttyUSB0.

10) However NetworkManager detects the wrong device /dev/ttyUSB1
# nmcli dev|grep ttyUSB
ttyUSB1gsm   rozłączono

and it is not possible to connect the internet using the graphical
network manager in KDE (Kubuntu 13.10), but with wvdial and /dev/ttyUSB0
it works fine.

Regards,
Pawel.

PS. Sometimes running the following command works fine, but not always (I don't 
know why).
# usb_modeswitch --default-vendor 0x12d1 --default-product 1c0b --target-vendor 
0x12d1 --target-product 0x1c08
However when it finally activates modem properly, the network manager finds the 
correct device /dev/ttyUSB0.

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

Title:
  Modem Huawei E173 works in 12.04 but not in 12.10

Status in ModemManager (with NetworkManager support):
  Fix Committed
Status in “modemmanager” package in Ubuntu:
  Confirmed

Bug description:
  Modem Huawei E173 works in 12.04 but not work in 12.10.

  Otherwise, the modem itself is recognized by the modem-manager but
  fails to connect to Internet.

  In 12.04 it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: modemmanager 0.6~git201206221719.8289a64-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Wed Sep 26 23:37:21 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

  There is a potential fix in upstream branch 06-huawei.

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

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

[Desktop-packages] [Bug 1232726] Re: Dash bg color doesn't match its surroundings

[Treviño]

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

** Changed in: unity/7.1
   Status: Triaged = In Progress

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  In Progress
Status in Unity 7.1 series:
  In Progress
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Lately, after login the Dash keeps a black background even if the
  Launcher and panel follow the current wallpaper color. I've added a
  screenshot. If I change the wallpaper, Dash recovers its chameleonic
  effect (until next reboot).

  Also, this started happening at the same time that a new error message
  (at log time) appeared, I've attached this error message, too.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity:
    Installed: 7.1.1+13.10.20130927.1-0ubuntu1
    Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
    Version table:
   *** 7.1.1+13.10.20130927.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 29 08:00:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2013-08-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic 
root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0A
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7111JLR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (GF451LA#ABM)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  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.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Sep 29 07:53:46 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputTV-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1215836] Re: Sync xfonts-terminus 4.38-1 (universe) from Debian unstable (main)

[Colin Watson]

** Changed in: xfonts-terminus (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Sync xfonts-terminus 4.38-1 (universe) from Debian unstable (main)

Status in “xfonts-terminus” package in Ubuntu:
  Fix Released

Bug description:
  Please sync xfonts-terminus 4.38-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* New upstream releases (4.36 and 4.38). 
  The ubuntu delta was created just so we had a garantee for saucy. Since 
debian now has the latest version, this is a sync.

  Changelog entries since current saucy version 4.38-0ubuntu1:

  xfonts-terminus (4.38-1) unstable; urgency=low

* New upstream releases (4.36 and 4.38), closes: #716800.
  - Some new symbols (quotedblreversed, I/i/U/u dotbelow)
  - Changes in few symbols.
  - New 22 pseudographic symbols.
* Run xset fp rehash in the postinst if possible.  Thanks to
  gennady.kupava, closes: #690549.

   -- Anton Zinoviev zinov...@debian.org  Thu, 01 Aug 2013 23:23:21
  +0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-terminus/+bug/1215836/+subscriptions

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

[Desktop-packages] [Bug 1197921] Re: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled

[Norbert]

Reproduced this bug on Ubuntu 13.10 final i386, under Unity session,
with Nvidia proprietary driver (304.88-0ubuntu8).

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

Title:
  LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing
  enabled

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “pixman” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.13.3-0ubuntu6
Candidate: 2:1.13.3-0ubuntu6
Version table:
   *** 2:1.13.3-0ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) 3) What is expected to happen via a terminal:
  cd ~/Desktop  wget 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1197921/+attachment/3748789/+files/plantage-mai-only-empty.ods
  localc --nologo plantage-mai-only-empty.ods

  is that xorg does not crash.

  4) What happens instead is that it crashes. Reproducible on 12.04 and
  13.10 and with Libreoffice 3.5, 4.0.2,and  4.1-rc1.

  WORKAROUND: Open in Gnumeric.
  apt-cache policy gnumeric
  gnumeric:
Installed: 1.12.1-1ubuntu1
Candidate: 1.12.1-1ubuntu1
Version table:
   *** 1.12.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.13.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  NonfreeKernelModules: ip6table_filter ip6_tables ebtable_nat ebtables 
xt_state ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter fglrx 
ipt_MASQUERADE iptable_nat kvm_amd nf_nat nf_conntrack_ipv4 kvm nf_conntrack 
nf_defrag_ipv4 ip_tables x_tables bridge stp parport_pc ppdev rfcomm bnep 
bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo 
videodev v4l2_compat_ioctl32 edac_core k10temp soundcore dm_multipath 
edac_mce_amd snd_page_alloc mac_hid sp5100_tco serio_raw i2c_piix4 hwmon_vid lp 
parport usbhid firewire_ohci hid r8169 pata_atiixp firewire_core crc_itu_t 
pata_via
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jul  4 13:58:20 2013
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-05-05 (59 days ago)
  InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:

  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to saucy on 2013-05-14 (50 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1242633] [NEW] unity pointer barriers sru bug

[Maarten Lankhorst]

Public bug reported:

x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs
updates to work with the new pointer barrier api from x1.14.

[Impact]
 * Pointer barrier api has changed between 1.13 and 1.14. 
(xorg-server-lts-saucy)
 * Modifications in unity and unity-2d are required to support both api's.

[Test Case]
 * Update all packages.
 * Test pointer barriers on an old xorg-server, they should continue to work.
 * Test pointer barriers on the new xorg-server, they should work.

[Regression Potential]
  * Low, it enables a separate code path for pointer barriers. The code in 
unity is a bit different due to copying the rework from upstream unity and 
keeping the old paths for legacy pointer barriers. Upstream dropped the old 
paths.

[Other Info]
  * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, 
the new ones in libxi. Because of the overlap some modifications had to be made 
to allow both pointer barriers to be included. This works as well as it can.
 * Depending on the queried libxi2/libxfixes versions, old pointer barriers or 
new ones are used.

** Affects: libxfixes (Ubuntu)
 Importance: High
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: In Progress

** Affects: libxi (Ubuntu)
 Importance: High
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: In Progress

** Affects: unity (Ubuntu)
 Importance: High
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: In Progress

** Affects: unity-2d (Ubuntu)
 Importance: High
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: In Progress

** Affects: x11proto-input (Ubuntu)
 Importance: High
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: In Progress

** Changed in: unity-2d (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: unity-2d (Ubuntu)
Milestone: None = ubuntu-12.04.4

** Changed in: unity-2d (Ubuntu)
   Importance: Undecided = High

** Changed in: unity-2d (Ubuntu)
   Status: New = In Progress

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

** Also affects: x11proto-input (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: x11proto-input (Ubuntu)
   Status: New = In Progress

** Changed in: libxfixes (Ubuntu)
   Importance: Undecided = High

** Changed in: libxi (Ubuntu)
   Importance: Undecided = High

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

** Changed in: x11proto-input (Ubuntu)
   Importance: Undecided = High

** Changed in: libxfixes (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: libxi (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: x11proto-input (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Description changed:

  x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs
  updates to work with the new pointer barrier api from x1.14.
  
- [Impact] 
-  * Pointer barrier api has changed between 1.13 and 1.14. 
(xorg-server-lts-saucy)
-  * Modifications in unity and unity-2d are required to support both api's.
+ [Impact]
+  * Pointer barrier api has changed between 1.13 and 1.14. 
(xorg-server-lts-saucy)
+  * Modifications in unity and unity-2d are required to support both api's.
  
  [Test Case]
-  * Update all packages.
-  * Test pointer barriers on an old xorg-server, they should work.
-  * Test pointer barriers on the new xorg-server, they should still work.
+  * Update all packages.
+  * Test pointer barriers on an old xorg-server, they should continue to work.
+  * Test pointer barriers on the new xorg-server, they should work.
  
- [Regression Potential] 
-   * Low, it enables a separate code path for pointer barriers. The code in 
unity is a bit different due to copying the rework from upstream unity and 
keeping the old paths for legacy pointer barriers. Upstream dropped the old 
paths.
+ [Regression Potential]
+   * Low, it enables a separate code path for pointer barriers. The code in 
unity is a bit different due to copying the rework from upstream unity and 
keeping the old paths for legacy pointer barriers. Upstream dropped the old 
paths.
  
  [Other Info]
-   * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, 
the new ones in libxi. Because of the overlap some modifications had to be made 
to allow both pointer barriers to be included. This works as well as it can.
-  * Depending on the queried libxi2/libxfixes 

[Desktop-packages] [Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed

[Ritesh Khadgaray]

** Patch removed: proposed patch for precise
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1065979/+attachment/3823317/+files/follow-lid.debdiff

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

Title:
  external/internal monitors mirrored on boot when laptop lid is closed

Status in Gnome Settings Daemon:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” source package in Oneiric:
  Won't Fix
Status in “gnome-settings-daemon” source package in Precise:
  Fix Released
Status in “gnome-settings-daemon” source package in Quantal:
  Won't Fix
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed

Bug description:
  [Impact]

   * Booting laptop in docking station with lid closed results in low 
resolution (1024x768/aka clone mode) on external monitor
   * Low resolution desktop (1024x768) when user logs in, must be manually set 
to optimal resolution for external montior
   * non-technical users would find the default behaviour not the desired 
behaviour.

  [Test Case]
  Steps to Reproduce:
1. Connect an external monitor to laptop.
2. Boot system with lid closed with a clean new user
3. Login screen is shown at 1024x768 ( the highest common resolution 
supported by both the displays)

   The laptop display ( say 1366x768)  should have a lower resolution
  than the connected external monitor ( say 1920x1080 ) .

  
  [Regression Potential]
   * I dont see any regression potential here, as this does not change any 
default behaviour.
   * User must manually activate this new behaviour . 

  [Other Info]
   * test packages have been posted to - 
http://people.canonical.com/~ritesh/work/gsd/
   * Update to this, and update default to follow-lid
   $ gsettings set org.gnome.settings-daemon.plugins.xrandr \
 default-monitors-setup follow-lid
   * test as usual

  
-

  If I put my X220 in a dock, and plug in an external monitor. Then I
  close the lid and turn on the computer, the computer will boot up with
  both the internal laptop screen and external monitor on and mirror.
  Because I can't see the laptop screen, I would expect the external
  monitor to be only on at its maximum resolution. I've actually tried
  this without the dock by plugging in an external monitor to my laptop
  and shutting the lid during boot quickly, the same problem persists.
  This problem is exhibited on Precise/Oneiric as well as Quantal.

  In particular this specification mentions this behavior:
  https://wiki.ubuntu.com/X/Blueprints/MultiMonitor
  In this user story:
  Alan goes to the office, puts his laptop with the lid closed into a 
docking station and boots it up. The external display should be run at its 
native resolution. Later that day he needs to see a customer. He suspends the 
laptop and takes it out of the docking station. At the customer he wakes up the 
laptop and the internal screen is used at its native resolution. Finishing his 
visit the laptop is suspended, brought back to the office. There it is placed 
in the docking station, woken up and the external display should run again at 
its native resolution.

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

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

[Desktop-packages] [Bug 1242095] Re: keyboard layout switcher isn't functional

[Norbert]

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

** This bug has been marked a duplicate of bug 1218322
   Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

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

Title:
  keyboard layout switcher isn't functional

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

Bug description:
  After updating to Saucy, the Keyboard layout switcher defaulted to 
Super+Space which didn't actually work.
  when attempting to change the layout combination of switch to next/previous 
source - the change doesn't occur.

  screenshots added.
  http://i40.tinypic.com/v5yjr9.jpg
  http://i43.tinypic.com/sghfm8.jpg
  http://i42.tinypic.com/2lca1kk.jpg

  update: the layout switching works, but isn't written within the
  settings, and is relevant only to HEB and ENG (and not ARA).

  cheers.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 19 19:31:22 2013
  InstallationDate: Installed on 2013-09-20 (29 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed

[Ritesh Khadgaray]

** Patch added: proposed patch for precise
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1065979/+attachment/3886076/+files/follow-lid.debdiff

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

Title:
  external/internal monitors mirrored on boot when laptop lid is closed

Status in Gnome Settings Daemon:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” source package in Oneiric:
  Won't Fix
Status in “gnome-settings-daemon” source package in Precise:
  Fix Released
Status in “gnome-settings-daemon” source package in Quantal:
  Won't Fix
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed

Bug description:
  [Impact]

   * Booting laptop in docking station with lid closed results in low 
resolution (1024x768/aka clone mode) on external monitor
   * Low resolution desktop (1024x768) when user logs in, must be manually set 
to optimal resolution for external montior
   * non-technical users would find the default behaviour not the desired 
behaviour.

  [Test Case]
  Steps to Reproduce:
1. Connect an external monitor to laptop.
2. Boot system with lid closed with a clean new user
3. Login screen is shown at 1024x768 ( the highest common resolution 
supported by both the displays)

   The laptop display ( say 1366x768)  should have a lower resolution
  than the connected external monitor ( say 1920x1080 ) .

  
  [Regression Potential]
   * I dont see any regression potential here, as this does not change any 
default behaviour.
   * User must manually activate this new behaviour . 

  [Other Info]
   * test packages have been posted to - 
http://people.canonical.com/~ritesh/work/gsd/
   * Update to this, and update default to follow-lid
   $ gsettings set org.gnome.settings-daemon.plugins.xrandr \
 default-monitors-setup follow-lid
   * test as usual

  
-

  If I put my X220 in a dock, and plug in an external monitor. Then I
  close the lid and turn on the computer, the computer will boot up with
  both the internal laptop screen and external monitor on and mirror.
  Because I can't see the laptop screen, I would expect the external
  monitor to be only on at its maximum resolution. I've actually tried
  this without the dock by plugging in an external monitor to my laptop
  and shutting the lid during boot quickly, the same problem persists.
  This problem is exhibited on Precise/Oneiric as well as Quantal.

  In particular this specification mentions this behavior:
  https://wiki.ubuntu.com/X/Blueprints/MultiMonitor
  In this user story:
  Alan goes to the office, puts his laptop with the lid closed into a 
docking station and boots it up. The external display should be run at its 
native resolution. Later that day he needs to see a customer. He suspends the 
laptop and takes it out of the docking station. At the customer he wakes up the 
laptop and the internal screen is used at its native resolution. Finishing his 
visit the laptop is suspended, brought back to the office. There it is placed 
in the docking station, woken up and the external display should run again at 
its native resolution.

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

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

[Desktop-packages] [Bug 1242304] Re: Nouveau driver on MBPret 15

[Christopher M. Penalver]

Wolf Rogner, as each of the 3 issues mentioned would necessitate
separate reports, which one would you like this report to focus on?

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

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

Title:
  Nouveau driver on MBPret 15

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Using the nouveau drivers

  - Menu items restart and shutdown don't work
  - No wakeup from suspend to RAM (nothing new)

  slugish performance

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 20 12:42:10 2013
  DistUpgraded: 2013-10-20 12:21:36,841 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.8.0-32-generic, x86_64: installed
   vboxhost, 4.3.0, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.0, 3.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00f2]
  InstallationDate: Installed on 2013-05-17 (155 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac 
(20130424)
  MachineType: Apple Inc. MacBookPro10,1
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46+git20130910.58d00888-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Oct 20 12:40:44 2013
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1241776] Re: Black rectangle instead of wallpaper

[Treviño]

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

** This bug has been marked a duplicate of bug 1232726
   Dash bg color doesn't match its surroundings

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

Title:
  Black rectangle instead of wallpaper

Status in Unity:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  After update from 13.04 to 13.10 my desktop image disappeared and black 
rectangle are shown insted.
  Desktop image is displayer under launcher panel, though.
  Dash does not open when mouse cursor are over that black rectangle and I 
press Super key. It does open if I move mouse over one of the panels (without 
any clicking).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 21:36:34 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] [1002:9610] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GA-MA78GM-S2H Motherboard 
[1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/ubuntu-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-MA78GM-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA78GM-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  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.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Fri Oct 18 21:26:48 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputA4Tech RF USB Receiver KEYBOARD, id 8
   inputA4Tech RF USB Receiver KEYBOARD, id 9
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work on Ubuntu 13.10

[Treviño]

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

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

Title:
  Drag and drop from Dash to Desktop doesn't work on Ubuntu 13.10

Status in Unity:
  Triaged
Status in Unity 7.1 series:
  Triaged
Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When you try to drag and drop an app from Dash (both from app lens and
  home lens) system display an error and the shortcut isn't created.

  The error is:
  Error while copying - There was an error getting information about /. 
  More details: The specified location is not supported

  Then there are four buttons: Cancel - Skip all - Skip - Retry.

  Way to reproduce:
  - Open the dash
  - Drag an app icon and drop on desktop

  What happend:
  - An error is raised

  What expected:
  - A shortcut is created

  With file, music and photo is all ok.

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

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

[Desktop-packages] [Bug 1197921] Re: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled

[Ritesh Khadgaray]

Hi @Norbert

  Is this with the patch ?

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

Title:
  LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing
  enabled

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “pixman” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.13.3-0ubuntu6
Candidate: 2:1.13.3-0ubuntu6
Version table:
   *** 2:1.13.3-0ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) 3) What is expected to happen via a terminal:
  cd ~/Desktop  wget 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1197921/+attachment/3748789/+files/plantage-mai-only-empty.ods
  localc --nologo plantage-mai-only-empty.ods

  is that xorg does not crash.

  4) What happens instead is that it crashes. Reproducible on 12.04 and
  13.10 and with Libreoffice 3.5, 4.0.2,and  4.1-rc1.

  WORKAROUND: Open in Gnumeric.
  apt-cache policy gnumeric
  gnumeric:
Installed: 1.12.1-1ubuntu1
Candidate: 1.12.1-1ubuntu1
Version table:
   *** 1.12.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.13.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  NonfreeKernelModules: ip6table_filter ip6_tables ebtable_nat ebtables 
xt_state ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter fglrx 
ipt_MASQUERADE iptable_nat kvm_amd nf_nat nf_conntrack_ipv4 kvm nf_conntrack 
nf_defrag_ipv4 ip_tables x_tables bridge stp parport_pc ppdev rfcomm bnep 
bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo 
videodev v4l2_compat_ioctl32 edac_core k10temp soundcore dm_multipath 
edac_mce_amd snd_page_alloc mac_hid sp5100_tco serio_raw i2c_piix4 hwmon_vid lp 
parport usbhid firewire_ohci hid r8169 pata_atiixp firewire_core crc_itu_t 
pata_via
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jul  4 13:58:20 2013
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-05-05 (59 days ago)
  InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:

  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to saucy on 2013-05-14 (50 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1133626] Re: mouse is too sensitive

[Christopher M. Penalver]

ill, could you please execute the apport-collect in Precise?

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

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

Title:
  mouse is too sensitive

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  In ubuntu, I go to the mouse settings and move the sliders for mouse
  sensitivity all the way to the left, but the sensitivity is still way
  too high. I can move the mouse less than a centimeter before the
  cursor will be on the other side of the screen.

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

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

[Desktop-packages] [Bug 1242390] Re: ac-53 (a52 plugin) core dumps

[Launchpad Bug Tracker]

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

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

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

Title:
  ac-53 (a52 plugin) core dumps

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  This config worked on 13.04

  a52.conf:

  pcm.a52 {
@args [CARD]
@args.CARD {
  type string
}
type rate
slave {
  pcm {
type a52
bitrate 448
channels 6
card $CARD
  }
  #  rate 48000 #required somehow, otherwise nothing happens in PulseAudio
}
  }

  commenting out rate 48000 allows it to work, but stereo only; no
  surround.

  End of debug logging for pulseaudio from the command line:
  D: [pulseaudio] alsa-mixer.c: Looking at profile 
output:iec958-stereo+input:analog-stereo
  D: [pulseaudio] alsa-mixer.c: Checking for recording on Analog Stereo 
(analog-stereo)
  D: [pulseaudio] alsa-util.c: Trying front:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open front:0
  D: [pulseaudio] alsa-util.c: Maximum hw buffer size is 371 ms
  D: [pulseaudio] alsa-util.c: Set buffer size first (to 3528 samples), period 
size second (to 441 samples).
  D: [pulseaudio] alsa-mixer.c: Profile 
output:iec958-stereo+input:analog-stereo supported.
  D: [pulseaudio] alsa-mixer.c: Looking at profile 
output:iec958-stereo+input:iec958-stereo
  D: [pulseaudio] alsa-mixer.c: Checking for recording on Digital Stereo 
(IEC958) (iec958-stereo)
  D: [pulseaudio] alsa-util.c: Trying iec958:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open iec958:0
  D: [pulseaudio] alsa-util.c: Maximum hw buffer size is 371 ms
  D: [pulseaudio] alsa-util.c: Set buffer size first (to 3528 samples), period 
size second (to 441 samples).
  D: [pulseaudio] alsa-mixer.c: Profile 
output:iec958-stereo+input:iec958-stereo supported.
  D: [pulseaudio] alsa-mixer.c: Looking at profile output:iec958-ac3-surround-40
  D: [pulseaudio] alsa-mixer.c: Checking for playback on Digital Surround 4.0 
(IEC958/AC3) (iec958-ac3-surround-40)
  D: [pulseaudio] alsa-util.c: Trying a52:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open a52:0
  D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(4) failed: 
Invalid argument
  D: [pulseaudio] alsa-util.c: Trying a52:0 without SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open a52:0
  D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(4) failed: 
Invalid argument
  D: [pulseaudio] alsa-util.c: Trying plug:a52:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open plug:a52:0
  D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(4) failed: 
Invalid argument
  D: [pulseaudio] alsa-util.c: Trying plug:a52:0 without SND_PCM_NO_AUTO_FORMAT 
...
  D: [pulseaudio] alsa-util.c: Managed to open plug:a52:0
  D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(4) failed: 
Invalid argument
  I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on plug:a52:0: 
Invalid argument
  D: [pulseaudio] alsa-mixer.c: Caching failure to open 
output:iec958-ac3-surround-40
  D: [pulseaudio] alsa-mixer.c: Skipping profile 
output:iec958-ac3-surround-40+input:analog-mono - will not be able to open 
output:iec958-ac3-surround-40
  D: [pulseaudio] alsa-mixer.c: Skipping profile 
output:iec958-ac3-surround-40+input:analog-stereo - will not be able to open 
output:iec958-ac3-surround-40
  D: [pulseaudio] alsa-mixer.c: Skipping profile 
output:iec958-ac3-surround-40+input:iec958-stereo - will not be able to open 
output:iec958-ac3-surround-40
  D: [pulseaudio] alsa-mixer.c: Looking at profile output:iec958-ac3-surround-51
  D: [pulseaudio] alsa-mixer.c: Checking for playback on Digital Surround 5.1 
(IEC958/AC3) (iec958-ac3-surround-51)
  D: [pulseaudio] alsa-util.c: Trying a52:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open a52:0
  D: [pulseaudio] alsa-util.c: Maximum hw buffer size is 320 ms
  Floating point exception (core dumped)
  D: [pulseaudio] alsa-mixer.c: Looking at profile 
output:iec958-stereo+input:analog-stereo
  D: [pulseaudio] alsa-mixer.c: Checking for recording on Analog Stereo 
(analog-stereo)
  D: [pulseaudio] alsa-util.c: Trying front:0 with SND_PCM_NO_AUTO_FORMAT ...
  D: [pulseaudio] alsa-util.c: Managed to open front:0
  D: [pulseaudio] alsa-util.c: Maximum hw buffer size is 371 ms
  D: [pulseaudio] alsa-util.c: Set buffer size first (to 3528 samples), period 
size second (to 441 samples).
  D: [pulseaudio] alsa-mixer.c: Profile 
output:iec958-stereo+input:analog-stereo supported.
  D: [pulseaudio] alsa-mixer.c: Looking at profile 
output:iec958-stereo+input:iec958-stereo
  D: [pulseaudio] alsa-mixer.c: Checking for recording on Digital 

[Desktop-packages] [Bug 1205384] Re: Lock can be circumvented by switching to console

[baltasarq]

I can confirm this bug on lubuntu 13.10 amd64.

The workaround I chose (following #22) was to:

1) Install suckless-tools: sudo apt-get install suckless-tools
2) edit /usr/bin/lxlock (sudo nano /usr/bin/lxlock). It tries to trigger screen 
locking using various tools, one of them is in fact slock, the tool provided by 
suckless-tools. The whole contents can be erased and just write slock 
instead. What I did was to add the el prefix to the first if, and move the 
elif testing and triggering slock to the top (removing the el prefix).

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

Title:
  Lock can be circumvented by switching to console

Status in “lightdm” package in Ubuntu:
  Invalid
Status in “lxsession” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1)lock your screen using dm-tool switch-to-greeter or dm-tool lock
  2)switch to console via ctrl+alt+F1
  3)switch back to X via ctrl+alt+F7
  Result: session is unlocked without entering a password

  Expected behaviour:
  session should still be locked when switching back to X

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.7-0ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Fri Jul 26 17:30:23 2013
  InstallationDate: Installed on 2013-07-26 (0 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha i386 (20130723.1)
  MarkForUpload: True
  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/1205384/+subscriptions

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

[Desktop-packages] [Bug 1197921] Re: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled

[Norbert]

Hello, Ritesh!

No, it is without patch. All packages installed from binary form (Ubuntu
13.10 i686 repos).

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

Title:
  LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing
  enabled

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “pixman” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.13.3-0ubuntu6
Candidate: 2:1.13.3-0ubuntu6
Version table:
   *** 2:1.13.3-0ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) 3) What is expected to happen via a terminal:
  cd ~/Desktop  wget 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1197921/+attachment/3748789/+files/plantage-mai-only-empty.ods
  localc --nologo plantage-mai-only-empty.ods

  is that xorg does not crash.

  4) What happens instead is that it crashes. Reproducible on 12.04 and
  13.10 and with Libreoffice 3.5, 4.0.2,and  4.1-rc1.

  WORKAROUND: Open in Gnumeric.
  apt-cache policy gnumeric
  gnumeric:
Installed: 1.12.1-1ubuntu1
Candidate: 1.12.1-1ubuntu1
Version table:
   *** 1.12.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.13.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  NonfreeKernelModules: ip6table_filter ip6_tables ebtable_nat ebtables 
xt_state ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter fglrx 
ipt_MASQUERADE iptable_nat kvm_amd nf_nat nf_conntrack_ipv4 kvm nf_conntrack 
nf_defrag_ipv4 ip_tables x_tables bridge stp parport_pc ppdev rfcomm bnep 
bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo 
videodev v4l2_compat_ioctl32 edac_core k10temp soundcore dm_multipath 
edac_mce_amd snd_page_alloc mac_hid sp5100_tco serio_raw i2c_piix4 hwmon_vid lp 
parport usbhid firewire_ohci hid r8169 pata_atiixp firewire_core crc_itu_t 
pata_via
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jul  4 13:58:20 2013
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-05-05 (59 days ago)
  InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:

  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to saucy on 2013-05-14 (50 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 879838] Re: Keyboard Layout Germany Neo 2: Mod4 does not work if used as secondary keyboard layout

[Lothar Fausthenze]

I am affected by this bug on Precise. I can confirm the bug description
as a whole.

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

Title:
  Keyboard Layout Germany Neo 2: Mod4 does not work if used as
  secondary keyboard layout

Status in “xkeyboard-config” package in Ubuntu:
  Confirmed

Bug description:
  If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
  Mod4) don't work. To reproduce this bug, do the following:

  1: Neo 2 as primary keyboard layout
  - start gnome-keyboard-properties
  - Click Add...
  - Select Country: Germany and Variants: Germany Neo 2
  - Select Germany Neo 2 and move it to the top of the list.
  Try to use Neo Layer 4 or 6. E.g. type the number 4 which is Mod4 and n 
in Neo ( and j in standard German QWERTZ layout) or move the cursor left 
using Mod4 and i (AltGr and s in QWERTZ layot).  Works as expected.

  2: Neo as secondary layout
  - Now add Germany Eliminate dead keys to the list and move it to the top
  - Use Neo 2 as secondary layout
  - Click Options and select Scroll lock (or any other) as Key(s) to 
change layout
  Now switch to Neo using the selected key and try to type 4 or move the 
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is, 
you will be typing an n instead of a 4 and an i instead of moving the 
cursor left). 

  Choosing other keys for layout change or turning the compose key
  on/off does not change anything. Neither does applying Neo 2 as
  primary layout system wide and using Germany Eliminate dead keys
  with Neo 2 as a secondary keyboard layout as local user.

  Applying the patch suggested on neo-layout.org for a similar problem
  (http://wiki.neo-layout.org/ticket/174) does not have any effect.

  Description:  Ubuntu 11.04
  Release:  11.04
  xkb-data: 2.1-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+subscriptions

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

[Desktop-packages] [Bug 1242655] [NEW] ubuntu 13.10 hotkeys ctrl+alt+shift+up/down arrow doesn't function

[Mina]

Public bug reported:

ubuntu 13.10 hotkey ctrl+alt+shift+up/down arrow doesn't function.

the hotkeys that move windows across workspaces. on ubuntu 13.10 I can
only move windows to the left or right. I can't move them up or down.

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

** Description changed:

- ubuntu 13.10 hotkeys ctrl+alt+shift+up/down arrow doesn't function.
+ ubuntu 13.10 hotkey ctrl+alt+shift+up/down arrow doesn't function.
  
  the hotkeys that move windows across workspaces. on ubuntu 13.10 I can
  only move windows to the left or right. I can't move them up or down.

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

Title:
  ubuntu 13.10 hotkeys ctrl+alt+shift+up/down arrow doesn't function

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

Bug description:
  ubuntu 13.10 hotkey ctrl+alt+shift+up/down arrow doesn't function.

  the hotkeys that move windows across workspaces. on ubuntu 13.10 I can
  only move windows to the left or right. I can't move them up or down.

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

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

[Desktop-packages] [Bug 1166125] Re: Ubuntu (Xubuntu) 13.04 beta, broken fonts for Gtk based applications

[Alberto Salvia Novella]

Since the affected package is pango-graphite, it isn't gtk.

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided = Medium

** Changed in: gtk+2.0 (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided = Medium

** Changed in: pango-graphite (Ubuntu)
   Importance: Undecided = Medium

** Changed in: pango-graphite (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: gtk+2.0 (Ubuntu)
   Status: Triaged = Invalid

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged = Invalid

** Summary changed:

- Ubuntu (Xubuntu) 13.04 beta, broken fonts for Gtk based applications
+ Broken fonts for Gtk based applications

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

Title:
  Broken fonts for Gtk based applications

Status in GTK+ GUI Toolkit:
  New
Status in Pango - Layout and Text Rendering LIbrary:
  New
Status in “gtk+2.0” package in Ubuntu:
  Invalid
Status in “gtk+3.0” package in Ubuntu:
  Invalid
Status in “pango-graphite” package in Ubuntu:
  Triaged

Bug description:
  After upgrade from 12.10 to 13.04 beta of Ubuntu (Xubuntu), I am
  experiencing some issues. Like without me actually changing anything,
  my fonts are broken for some applications (most of them) and not for
  other (rxvt).

  See this http://i.imgur.com/ubVvr53.png

  As you can see, rxvt there is the only application with normal fonts.
  The Terminal application from Xfce suite is for some inexplicable
  reason using some kind of proportional font. See that the font in the
  Terminal Preferences is set to Liberation Mono. Also, please notice
  how in the Choose Terminal Font dialog the Courier New font Preview is
  not Courier New.

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

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

[Desktop-packages] [Bug 1239130] Re: Saucy Beta 2 Gedit Warning Messages

[jerrylamos]

First try comment #4 helped:

sudo apt-get install gir1.2-gtksource-3.0

That would turn the bug into :
Why isn't gir1.2.-gtksource-3.0 in the saucy RC .iso 
to match the gedit that's in saucy RC .iso?

Now sometimes I get a whole pile of error messages using gedit in saucy
so I'll keep my eye open.

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

Title:
  Saucy Beta 2 Gedit Warning Messages

Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Warning messages when running gedit with Saucy Beta 2:

  ** (gedit:2505): WARNING **: Could not load Gedit repository: Typelib
  file for namespace 'GtkSource', version '3.0' not found

  (gedit:2505): Gtk-WARNING **: Attempting to read the recently used
  resources file at `/home/jerry/.local/share/recently-used.xbel', but
  the parser failed: Failed to open file '/home/jerry/.local/share
  /recently-used.xbel': Permission denied.

  What's wrong with gnome and/or gedit and how do I fix these warnings?

  Thanks, Jerry

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gedit 3.8.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct 12 09:19:20 2013
  InstallationDate: Installed on 2013-09-28 (13 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  MarkForUpload: True
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries

[Cees]

Version 0.9.15-3git1ubuntu0.1 on precise fixed the problem for me. My
apple wireless mouse now reads as a mouse in stead of a laptop battery.

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

Title:
  Treats bluetooth input device batteries as batteries

Status in “gnome-power-manager” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” source package in Precise:
  Invalid
Status in “upower” source package in Precise:
  Fix Committed
Status in “gnome-power-manager” source package in Quantal:
  Invalid
Status in “upower” source package in Quantal:
  Confirmed
Status in “gnome-power-manager” source package in Raring:
  Invalid
Status in “upower” source package in Raring:
  Fix Committed
Status in “gnome-power-manager” source package in Saucy:
  Invalid
Status in “upower” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to Critically Low and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  SourcePackage: 

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

[Alberto Salvia Novella]

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntu-gnome
   Status: New = Confirmed

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: indicator-keyboard (Ubuntu)
   Status: Confirmed = Triaged

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

** Changed in: hundredpapercuts
   Status: New = Confirmed

** Changed in: hundredpapercuts
 Assignee: (unassigned) = Paper Cuts Ninja (papercuts-ninja)

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

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

Status in One Hundred Paper Cuts:
  Confirmed
Status in Indicator keyboard:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1241282] Re: [regression] Wall: keyboard bindings for 'Move up Move down' are being set to shift+super+prior shift+super+next' for Move with window with wall'

[Christopher Townsend]

*Sigh*  This must have slipped in at the last moment, because it was not
there when I fixed the other issue:/

Yeah, this will require an SRU.  I'll propose this and try to push folks
to get the SRU done in a timely manner.

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

Title:
  [regression] Wall: keyboard bindings for 'Move up  Move down' are
  being set to shift+super+prior   shift+super+next'  for Move with
  window with wall'

Status in “ubuntu-settings” package in Ubuntu:
  Confirmed

Bug description:
  This is just another issue as seen in Bug 1201405 which was fixed for moving 
workspaces
  In this case the same is happening with Move with window within wall'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubuntu-settings 13.10.9
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 17 21:16:34 2013
  InstallationDate: Installed on 2013-08-07 (71 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1196196] Re: [background]: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

[markb]

It says above that this bug was fixed in gnome-control-center
1:3.6.3-0ubuntu31 but I cleanly installed Ubuntu GNOME 13.10 today with
gnome-control-center 1:3.8.3-0ubuntu1~saucy2 and it still crashes as
soon as I try to change the background. I see the following segfault
each time in my syslog:

Oct 21 22:16:24 pc kernel: [17906.827359] gnome-control-c[8265]:
segfault at 7f416bf72000 ip 7f4162a1b664 sp 7fffdc71f880 error 4
in libgdk-3.so.0.1000.0[7f41629ee000+ab000]

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

Title:
  [background]: gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

Status in “gnome-control-center” package in Ubuntu:
  Fix Released

Bug description:
  Changing wallpaper, As this is a fresh install of Ubuntu-Gnome Saucy
  not sure if this is a new bug or a re-occurrence of an old one...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sun Jun 30 09:31:05 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130629)
  MarkForUpload: True
  ProcCmdline: gnome-control-center background
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0236567fec g_type_check_instance_cast+28:
mov(%rax),%rdi
   PC (0x7f0236567fec) ok
   source (%rax) (0x) not located in a known VMA region 
(needed readable region)!
   destination %rdi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libbackground.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: [background]: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

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

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

[Desktop-packages] [Bug 1242663] [NEW] Omnibox text jumps up and down while typing

[Marius Gedminas]

Public bug reported:

Steps to reproduce:
1. Type some text in the Chromium address bar

Expected behavior: text does not jump up and down

Actual behavior: text jumps up and down (see attached screencast).

Apologies for the large size of the screencast.  I tried to unplug my
external monitor to reduce the image size to 1366x768, but unfortunately
GNOME Shell produced a 2646x1024 video anyway (most of it black), and
the file size was larger in the end (3 megs instead of 1).  And Kazam
segfaulted when I tried to use it instead.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: chromium-browser 29.0.1547.65-0ubuntu2
Uname: Linux 3.12.0-031200rc1-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Mon Oct 21 15:17:54 2013
Desktop-Session:
 DESKTOP_SESSION = gnome
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
EcryptfsInUse: Yes
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2012-07-25 (452 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MarkForUpload: True
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
chromium-default: CHROMIUM_FLAGS=
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

** Affects: chromium-browser
 Importance: Unknown
 Status: Unknown

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


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

** Attachment added: screencast of the problem
   
https://bugs.launchpad.net/bugs/1242663/+attachment/3886109/+files/Ekrano%20vaizdo%20%C4%AFra%C5%A1as%20i%C5%A1%202013.10.21%2015%3A09%3A13.webm

** Bug watch added: code.google.com/p/chromium/issues #27103
   http://code.google.com/p/chromium/issues/detail?id=27103

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

Title:
  Omnibox text jumps up and down while typing

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Type some text in the Chromium address bar

  Expected behavior: text does not jump up and down

  Actual behavior: text jumps up and down (see attached screencast).

  Apologies for the large size of the screencast.  I tried to unplug my
  external monitor to reduce the image size to 1366x768, but
  unfortunately GNOME Shell produced a 2646x1024 video anyway (most of
  it black), and the file size was larger in the end (3 megs instead of
  1).  And Kazam segfaulted when I tried to use it instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 15:17:54 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-07-25 (452 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1242663] Re: Omnibox text jumps up and down while typing

[Marius Gedminas]

If I install the Adwaita theme[1] to make Chromium fit in with the rest
of my GNOME desktop, this problem comes back.

[1] https://chrome.google.com/webstore/detail/adwaita-
gnome-3/oojbknijfmdmidgcgchmojbildmbdamm?hl=en

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

Title:
  Omnibox text jumps up and down while typing

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Type some text in the Chromium address bar

  Expected behavior: text does not jump up and down

  Actual behavior: text jumps up and down (see attached screencast).

  Apologies for the large size of the screencast.  I tried to unplug my
  external monitor to reduce the image size to 1366x768, but
  unfortunately GNOME Shell produced a 2646x1024 video anyway (most of
  it black), and the file size was larger in the end (3 megs instead of
  1).  And Kazam segfaulted when I tried to use it instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 15:17:54 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-07-25 (452 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1242663] Re: Omnibox text jumps up and down while typing

[Marius Gedminas]

This is very similar to
https://code.google.com/p/chromium/issues/detail?id=27103, except that
bug was closed in 2009.   Also, I didn't see this with Chromium 28 in
raring.

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

Title:
  Omnibox text jumps up and down while typing

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Type some text in the Chromium address bar

  Expected behavior: text does not jump up and down

  Actual behavior: text jumps up and down (see attached screencast).

  Apologies for the large size of the screencast.  I tried to unplug my
  external monitor to reduce the image size to 1366x768, but
  unfortunately GNOME Shell produced a 2646x1024 video anyway (most of
  it black), and the file size was larger in the end (3 megs instead of
  1).  And Kazam segfaulted when I tried to use it instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 15:17:54 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-07-25 (452 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1242663] Re: Omnibox text jumps up and down while typing

[Marius Gedminas]

If I go to chrome://settings/ and click 'Use Gtk+ theme', this problem
goes away.

If I go to chrome://settings/ and click 'Use classic theme', this
problem comes back.

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

Title:
  Omnibox text jumps up and down while typing

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Type some text in the Chromium address bar

  Expected behavior: text does not jump up and down

  Actual behavior: text jumps up and down (see attached screencast).

  Apologies for the large size of the screencast.  I tried to unplug my
  external monitor to reduce the image size to 1366x768, but
  unfortunately GNOME Shell produced a 2646x1024 video anyway (most of
  it black), and the file size was larger in the end (3 megs instead of
  1).  And Kazam segfaulted when I tried to use it instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 15:17:54 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-07-25 (452 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1121379] Re: Multiple finger touch fails on Sony Vaio Duo 11 running Ubuntu 12.10 (N-Trig DuoSense MultiTouch)

[Sergio López del Pozo]

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

Installed 13.10 in my new Duo 11 and touch works just fine.

Now I'm trying to make the middle mouse button usable.

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

Title:
  Multiple finger touch fails on Sony Vaio Duo 11 running Ubuntu 12.10
  (N-Trig DuoSense MultiTouch)

Status in “linux-image-3.5.0-030500-generic” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  N-trig DuoSense multitouch screen on Sony Vaio Duo 11 (model
  SVD1121P2EB) ultrabook/tablet hybrid does not function as expected
  with ubuntu 12.10.

  How to reproduce the bug:

  1. Boot up Sony Vaio Duo 11 to Ubuntu 12.10 and login to untiy
  2. Use mouse/trackpad to Open a nautiuls window
  3. Use a mouse/trackpad to Open a terminal window and run tail -f 
/var/log/Xorg.0.log
  4. With the focus to the terminal window touch inside nautilus window with 
one finger. Nautilus window takes focus, as expected. Nothing is appended to 
Xorg.0.log.
  5. Touch with one finger inside terminal window. The terminal window takes 
the focus, as expected. Nothing is appended to Xorg.0.log.
  6. Touch with one finger inside nautilus window and do a drag gesture. A 
rectangle select area follows hand's move. Nothing is appended to Xorg.0.log.
  7. Touch again with one finger inside nautilus window and and do a drag 
gesture. Nautilus window is scrolling up and down, as expected.
  8. Touch with 2 fingers into nautilus window. The following Error line is 
appended to Xorg.0.log:

  (EE) [dix] N-trig DuoSense: unable to find touch point 1

  9. Do any gesture with the two fingers (eg. spread). The following
  error lines are repeated during the gesture:

  [  2530.712] (EE) BUG: triggered 'if (!(event-device_event.flags  (1  
5)))'
  [  2530.712] (EE) BUG: ../../dix/touch.c:628 in TouchConvertToPointerEvent()
  [  2530.712] (EE) Non-emulating touch event
  [  2530.712] (EE) 
  [  2530.713] (EE) Backtrace:
  [  2530.713] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f261cfadb76]
  [  2530.713] (EE) 1: /usr/bin/X (0x7f261ce05000+0x7dbdf) [0x7f261ce82bdf]
  [  2530.713] (EE) 2: /usr/bin/X (0x7f261ce05000+0x1380b9) [0x7f261cf3d0b9]
  [  2530.713] (EE) 3: /usr/bin/X (0x7f261ce05000+0x137c65) [0x7f261cf3cc65]
  [  2530.714] (EE) 4: /usr/bin/X (0x7f261ce05000+0x13a5d3) [0x7f261cf3f5d3]
  [  2530.714] (EE) 5: /usr/bin/X (0x7f261ce05000+0x15bc8f) [0x7f261cf60c8f]
  [  2530.714] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1b5) 
[0x7f261cf8f385]
  [  2530.714] (EE) 7: /usr/bin/X (mieqProcessInputEvents+0xf8) [0x7f261cf8f4a8]
  [  2530.714] (EE) 8: /usr/bin/X (ProcessInputEvents+0x9) [0x7f261ce98789]
  [  2530.714] (EE) 9: /usr/bin/X (0x7f261ce05000+0x557d2) [0x7f261ce5a7d2]
  [  2530.715] (EE) 10: /usr/bin/X (0x7f261ce05000+0x4456a) [0x7f261ce4956a]
  [  2530.715] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xed) [0x7f261adb076d]
  [  2530.715] (EE) 12: /usr/bin/X (0x7f261ce05000+0x448ad) [0x7f261ce498ad]
  [  2530.715] (EE) 

  10. Touch with one finger an other window. Focus is not transfered to the 
touched window. Expected behavior: The focus should be transfered to the 
touched window.
  11. Touch with one finger inside nautilus window and do a drag gesture. 
Window is scrolling up and down and the above error lines are repeated at 
Xorg.0.log. Expected behavior: No error messages should be generated.
  12. Remove the finger from the screen and move the mouse around the screen. 
Nautilus window is scrolling according to mouse movement. Expected behavior: no 
scrolling should happen at nautilus window.
  13. Click with the mouse inside nautilus window. The rectangle selector 
appears and follows mouse movement. Expected behavior: A single click should 
not trigger the rectangle selector.

  After these steps mouse and touch have a strange and unstable
  behavior: Mouse movement erroneously selects text without holding down
  the mouse button, clicks and touches at windows do not give focus,
  clicks and touches to buttons to not cause a press event, alt+tab is
  not functioning.

  Touching with more fingers (3 or 4) produces a similar error with
  point number varying from 0 to 3 (e.g. (EE) [dix] N-trig DuoSense:
  unable to find touch point 2), and after that any gesture fails
  producing the above error messages.

  I attach:
  * geistest output
  * lsb_release -a output
  * lshw output
  * lsinput output
  * lspci -vnvn output
  * mtdev-test output
  * ntrig-calibrator output
  * uname -a output
  * cat /proc/version_signature output
  * Xorg.0.log

  I can perform any testing and reporting on Sony VAIO Duo 11 device. I
  have quite advanced technical skills on ubuntu, compiling, config
  files e.t.c. I would appreciate any guidance in order to 

[Desktop-packages] [Bug 1242663] Re: Omnibox text jumps up and down while typing

[Marius Gedminas]

Submitted upstream as
https://code.google.com/p/chromium/issues/detail?id=309605

** Bug watch added: code.google.com/p/chromium/issues #309605
   http://code.google.com/p/chromium/issues/detail?id=309605

** Also affects: chromium-browser via
   http://code.google.com/p/chromium/issues/detail?id=309605
   Importance: Unknown
   Status: Unknown

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

Title:
  Omnibox text jumps up and down while typing

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Type some text in the Chromium address bar

  Expected behavior: text does not jump up and down

  Actual behavior: text jumps up and down (see attached screencast).

  Apologies for the large size of the screencast.  I tried to unplug my
  external monitor to reduce the image size to 1366x768, but
  unfortunately GNOME Shell produced a 2646x1024 video anyway (most of
  it black), and the file size was larger in the end (3 megs instead of
  1).  And Kazam segfaulted when I tried to use it instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 15:17:54 2013
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-07-25 (452 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (3 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1216094] Re: [Cirrus7 Nimbus, Realtek ALC892, Pink Line In, Rear] No sound at all

[Raymond]

!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!

00:1b.0 0403: 8086:1e20 (rev 04)
Subsystem: 8086:2036


if the PCI SSID cannot idenify it is a product of Cirrus 7

the driver only regard this is a computer using  Intel DQ77KB
motherboard

http://ark.intel.com/products/59046/Intel-Desktop-Board-DQ77KB

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

Title:
  [Cirrus7 Nimbus, Realtek ALC892, Pink Line In, Rear] No sound at all

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

Bug description:
  I cannot get a microphone to work (attached to back, pink line-in). I
  hope all neccessary information is in automated attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas2221 F pulseaudio
  Date: Fri Aug 23 22:06:07 2013
  InstallationDate: Installed on 2013-07-08 (46 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Intern geluid - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas2221 F pulseaudio
  Symptom_Jack: Pink Line In, Rear
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC892, Pink Line In, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KBQ7710H.86A.0051.2013.0329.1350
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ77KB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG81483-500
  dmi.chassis.type: 81
  dmi.chassis.vendor: cirrus7 computing
  dmi.chassis.version: rev1
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKBQ7710H.86A.0051.2013.0329.1350:bd03/29/2013:svncirrus7computing:pnnimbus:pvrrev1:rvnIntelCorporation:rnDQ77KB:rvrAAG81483-500:cvncirrus7computing:ct81:cvrrev1:
  dmi.product.name: nimbus
  dmi.product.version: rev1
  dmi.sys.vendor: cirrus7 computing

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

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

[Desktop-packages] [Bug 371897] Re: Occasional sound drops in Wine via PulseAudio

[Maarten Lankhorst]

** Changed in: wine (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: wine (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Occasional sound drops in Wine via PulseAudio

Status in Wine:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “wine” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine

  I'm running the Spotify Windows application on two laptops under Wine
  with both internal and external USB sound card. With both cards you
  get the occasional pop and click in the sound suggesting some data
  loss somewhere.

  I've selected the alsa drivers in winecfg and the whole thing is
  running via the alsa compatibility layer in pulseaudio.

  Jaunty 9.04 UNR and standard Ubuntu desktop.

  wine:
Installed: 1.0.1-0ubuntu6
Candidate: 1.0.1-0ubuntu6
Version table:
   *** 1.0.1-0ubuntu6 0
  500 http://gb.archive.ubuntu.com jaunty/universe Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Installed: 1:0.9.14-0ubuntu20
Candidate: 1:0.9.14-0ubuntu20
Version table:
   *** 1:0.9.14-0ubuntu20 0
  500 http://gb.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 596095] Re: /usr/lib/cups/filter/pstopdf failed for any PDF

[Launchpad Bug Tracker]

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

** Changed in: cups (Ubuntu)
   Status: New = Confirmed

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

Title:
  /usr/lib/cups/filter/pstopdf failed for any PDF

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  Seems like some of the last updates have broken my PDF printing.
  Printer is Samsung ML-2850D Foomatic/Postscript (recommended).
  A couple of weeks ago it certainly worked well, but now I get 
/usr/lib/cups/filter/pstopdf failed for any PDF file (downloaded or created 
by me with OOo or LaTeX). Printing directly from OOo works well. Please help, I 
can do any testing you suggest.

  I [19/Jun/2010:01:09:37 +0400] Listening to ::1:631 (IPv6)
  I [19/Jun/2010:01:09:37 +0400] Listening to 127.0.0.1:631 (IPv4)
  I [19/Jun/2010:01:09:37 +0400] Listening to /var/run/cups/cups.sock (Domain)
  I [19/Jun/2010:01:09:37 +0400] Remote access is disabled.
  D [19/Jun/2010:01:09:37 +0400] Added auto ServerAlias lightoze-tek
  I [19/Jun/2010:01:09:37 +0400] Loaded configuration file 
/etc/cups/cupsd.conf
  I [19/Jun/2010:01:09:37 +0400] Using default TempDir of /var/spool/cups/tmp...
  I [19/Jun/2010:01:09:37 +0400] Configured for up to 100 clients.
  I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 (IPv6)
  I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 (IPv4)
  I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock (Domain)
  I [19/Jun/2010:01:36:33 +0400] Remote access is disabled.
  D [19/Jun/2010:01:36:33 +0400] Added auto ServerAlias lightoze-tek
  I [19/Jun/2010:01:36:33 +0400] Loaded configuration file 
/etc/cups/cupsd.conf
  I [19/Jun/2010:01:36:33 +0400] Using default TempDir of /var/spool/cups/tmp...
  I [19/Jun/2010:01:36:33 +0400] Configured for up to 100 clients.
  I [19/Jun/2010:01:36:33 +0400] Allowing up to 100 client connections per host.
  I [19/Jun/2010:01:36:33 +0400] Using policy default as the default!
  I [19/Jun/2010:01:36:33 +0400] Full reload is required.
  I [19/Jun/2010:01:36:33 +0400] Loaded MIME database from 
/usr/share/cups/mime and /etc/cups: 37 types, 76 filters...
  D [19/Jun/2010:01:36:33 +0400] Loading printer LaserJet_2300...
  D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading 
/var/cache/cups/LaserJet_2300.ipp...
  D [19/Jun/2010:01:36:33 +0400] 
cupsdRegisterPrinter(p=0x7f53a74fe1e0(LaserJet_2300))
  D [19/Jun/2010:01:36:33 +0400] Loading printer ML-2850-Series...
  D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading 
/var/cache/cups/ML-2850-Series.ipp...
  D [19/Jun/2010:01:36:33 +0400] 
cupsdRegisterPrinter(p=0x7f53a74f1fe0(ML-2850-Series))
  D [19/Jun/2010:01:36:33 +0400] cupsdLoadRemoteCache: Not loading remote cache.
  I [19/Jun/2010:01:36:33 +0400] Loading job cache file 
/var/cache/cups/job.cache...
  D [19/Jun/2010:01:36:33 +0400] [Job 1] Loading from cache...
  ..
  D [19/Jun/2010:01:36:33 +0400] cupsdAddSubscription(mask=0, dest=(nil)(), 
job=(nil)(0), uri=(null))
  I [19/Jun/2010:01:36:33 +0400] Full reload complete.
  I [19/Jun/2010:01:36:33 +0400] Cleaning out old temporary files in 
/var/spool/cups/tmp...
  D [19/Jun/2010:01:36:33 +0400] Removed temporary file 
/var/spool/cups/tmp/foomatic-hZhpP2...
  I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 on fd 6...
  I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 on fd 7...
  I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock on fd 8...
  I [19/Jun/2010:01:36:33 +0400] Resuming new connection processing...
  D [19/Jun/2010:01:36:33 +0400] Discarding unused server-started event...
  D [19/Jun/2010:01:36:34 +0400] Report: clients=0
  D [19/Jun/2010:01:36:34 +0400] Report: jobs=117
  D [19/Jun/2010:01:36:34 +0400] Report: jobs-active=0
  D [19/Jun/2010:01:36:34 +0400] Report: printers=2
  D [19/Jun/2010:01:36:34 +0400] Report: printers-implicit=0
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-string-count=623
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-alloc-bytes=6712
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-total-bytes=12608
  D [19/Jun/2010:01:37:01 +0400] cupsdAcceptClient: 11 from localhost (Domain)
  D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 POST / HTTP/1.1
  D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Active clients
  D [19/Jun/2010:01:37:01 +0400] cupsdAuthorize: No authentication data 
provided.
  D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 1.1 CUPS-Get-Printers 1
  D [19/Jun/2010:01:37:01 +0400] CUPS-Get-Printers
  D [19/Jun/2010:01:37:01 +0400] Returning IPP successful-ok for 
CUPS-Get-Printers (no URI) from localhost
  D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Not busy
  D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 POST / HTTP/1.1
  D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Active clients
  D [19/Jun/2010:01:37:01 +0400] cupsdAuthorize: No 

[Desktop-packages] [Bug 1205384] Re: Lock can be circumvented by switching to console

[Jarno Suni]

If you don't want to change the original lxlock script, you can copy the
script to /usr/local/bin/ and change it there. The modified script will
be used, since the local directory is mentioned earlier in the
environment variable called PATH. Upgrading the operating system will
not change the script in the local directory, as far as I know.

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

Title:
  Lock can be circumvented by switching to console

Status in “lightdm” package in Ubuntu:
  Invalid
Status in “lxsession” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1)lock your screen using dm-tool switch-to-greeter or dm-tool lock
  2)switch to console via ctrl+alt+F1
  3)switch back to X via ctrl+alt+F7
  Result: session is unlocked without entering a password

  Expected behaviour:
  session should still be locked when switching back to X

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.7-0ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Fri Jul 26 17:30:23 2013
  InstallationDate: Installed on 2013-07-26 (0 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha i386 (20130723.1)
  MarkForUpload: True
  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/1205384/+subscriptions

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

[Desktop-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

[Alberto Salvia Novella]

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

** Changed in: linux-lts-raring (Ubuntu)
   Status: Triaged = Invalid

** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: Confirmed = Invalid

** Changed in: mesa (Ubuntu)
   Importance: Undecided = Critical

** Changed in: mesa (Ubuntu)
   Status: New = Triaged

** Changed in: linux (Ubuntu Precise)
 Assignee: Canonical Kernel Team (canonical-kernel-team) = (unassigned)

** Changed in: linux (Ubuntu Quantal)
 Assignee: Canonical Kernel Team (canonical-kernel-team) = (unassigned)

** Changed in: linux (Ubuntu Raring)
 Assignee: Canonical Kernel Team (canonical-kernel-team) = (unassigned)

** Changed in: mesa (Ubuntu Precise)
   Status: New = Triaged

** Changed in: mesa (Ubuntu Precise)
   Importance: Undecided = Critical

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in Direct Rendering Infrastructure:
  Confirmed
Status in The Linux Kernel:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “mesa” package in Ubuntu:
  Triaged
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-quantal” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  Invalid
Status in “mesa” source package in Precise:
  Triaged
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Invalid
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux” package in Debian:
  New
Status in “linux” package in Fedora:
  Unknown

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a system error.

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [81051bef] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [81051c4a] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [a02d32e6] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [a02954b4] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [8101257b] ? __switch_to+0x12b/0x420
  [26285.658612]  [a029a943] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [8107097a] process_one_work+0x12a/0x420
  [26285.658629]  [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [8107152e] worker_thread+0x12e/0x2f0
  [26285.658636]  [81071400] ? manage_workers.isra.26+0x200/0x200
  

[Desktop-packages] [Bug 596095] Re: /usr/lib/cups/filter/pstopdf failed for any PDF

[Catalin Hritcu]

I know this is an old one, but I'm getting the same error message
(/usr/lib/cups/filter/pstopdf failed) with Ubuntu 13.10, CUPS 1.7rc1,
and various TOSHIBA e-Studio printers with the recommended
Foomatic/pxlmono and Foomatic/Postscript drivers. Was this bug ever
fixed and this is a regression?

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

Title:
  /usr/lib/cups/filter/pstopdf failed for any PDF

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  Seems like some of the last updates have broken my PDF printing.
  Printer is Samsung ML-2850D Foomatic/Postscript (recommended).
  A couple of weeks ago it certainly worked well, but now I get 
/usr/lib/cups/filter/pstopdf failed for any PDF file (downloaded or created 
by me with OOo or LaTeX). Printing directly from OOo works well. Please help, I 
can do any testing you suggest.

  I [19/Jun/2010:01:09:37 +0400] Listening to ::1:631 (IPv6)
  I [19/Jun/2010:01:09:37 +0400] Listening to 127.0.0.1:631 (IPv4)
  I [19/Jun/2010:01:09:37 +0400] Listening to /var/run/cups/cups.sock (Domain)
  I [19/Jun/2010:01:09:37 +0400] Remote access is disabled.
  D [19/Jun/2010:01:09:37 +0400] Added auto ServerAlias lightoze-tek
  I [19/Jun/2010:01:09:37 +0400] Loaded configuration file 
/etc/cups/cupsd.conf
  I [19/Jun/2010:01:09:37 +0400] Using default TempDir of /var/spool/cups/tmp...
  I [19/Jun/2010:01:09:37 +0400] Configured for up to 100 clients.
  I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 (IPv6)
  I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 (IPv4)
  I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock (Domain)
  I [19/Jun/2010:01:36:33 +0400] Remote access is disabled.
  D [19/Jun/2010:01:36:33 +0400] Added auto ServerAlias lightoze-tek
  I [19/Jun/2010:01:36:33 +0400] Loaded configuration file 
/etc/cups/cupsd.conf
  I [19/Jun/2010:01:36:33 +0400] Using default TempDir of /var/spool/cups/tmp...
  I [19/Jun/2010:01:36:33 +0400] Configured for up to 100 clients.
  I [19/Jun/2010:01:36:33 +0400] Allowing up to 100 client connections per host.
  I [19/Jun/2010:01:36:33 +0400] Using policy default as the default!
  I [19/Jun/2010:01:36:33 +0400] Full reload is required.
  I [19/Jun/2010:01:36:33 +0400] Loaded MIME database from 
/usr/share/cups/mime and /etc/cups: 37 types, 76 filters...
  D [19/Jun/2010:01:36:33 +0400] Loading printer LaserJet_2300...
  D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading 
/var/cache/cups/LaserJet_2300.ipp...
  D [19/Jun/2010:01:36:33 +0400] 
cupsdRegisterPrinter(p=0x7f53a74fe1e0(LaserJet_2300))
  D [19/Jun/2010:01:36:33 +0400] Loading printer ML-2850-Series...
  D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading 
/var/cache/cups/ML-2850-Series.ipp...
  D [19/Jun/2010:01:36:33 +0400] 
cupsdRegisterPrinter(p=0x7f53a74f1fe0(ML-2850-Series))
  D [19/Jun/2010:01:36:33 +0400] cupsdLoadRemoteCache: Not loading remote cache.
  I [19/Jun/2010:01:36:33 +0400] Loading job cache file 
/var/cache/cups/job.cache...
  D [19/Jun/2010:01:36:33 +0400] [Job 1] Loading from cache...
  ..
  D [19/Jun/2010:01:36:33 +0400] cupsdAddSubscription(mask=0, dest=(nil)(), 
job=(nil)(0), uri=(null))
  I [19/Jun/2010:01:36:33 +0400] Full reload complete.
  I [19/Jun/2010:01:36:33 +0400] Cleaning out old temporary files in 
/var/spool/cups/tmp...
  D [19/Jun/2010:01:36:33 +0400] Removed temporary file 
/var/spool/cups/tmp/foomatic-hZhpP2...
  I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 on fd 6...
  I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 on fd 7...
  I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock on fd 8...
  I [19/Jun/2010:01:36:33 +0400] Resuming new connection processing...
  D [19/Jun/2010:01:36:33 +0400] Discarding unused server-started event...
  D [19/Jun/2010:01:36:34 +0400] Report: clients=0
  D [19/Jun/2010:01:36:34 +0400] Report: jobs=117
  D [19/Jun/2010:01:36:34 +0400] Report: jobs-active=0
  D [19/Jun/2010:01:36:34 +0400] Report: printers=2
  D [19/Jun/2010:01:36:34 +0400] Report: printers-implicit=0
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-string-count=623
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-alloc-bytes=6712
  D [19/Jun/2010:01:36:34 +0400] Report: stringpool-total-bytes=12608
  D [19/Jun/2010:01:37:01 +0400] cupsdAcceptClient: 11 from localhost (Domain)
  D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 POST / HTTP/1.1
  D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Active clients
  D [19/Jun/2010:01:37:01 +0400] cupsdAuthorize: No authentication data 
provided.
  D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 1.1 CUPS-Get-Printers 1
  D [19/Jun/2010:01:37:01 +0400] CUPS-Get-Printers
  D [19/Jun/2010:01:37:01 +0400] Returning IPP successful-ok for 
CUPS-Get-Printers (no URI) from localhost
  D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Not busy
  D 

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

[Maxim Kuznetsov]

Thank You William and Norbert, it works on my laptop (Sony VPCEC1S1R, 64 bit, 
fresh install) (i've changed only Switch to previous source field to left 
Ctrl-Shift).
Now i'm searching the way to get back ability to change layout with Caps while 
it's pressed. It was possible in 13.04.

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

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

Status in One Hundred Paper Cuts:
  Confirmed
Status in Indicator keyboard:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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