[Desktop-packages] [Bug 1245347] Re: Screen keeps blinking after boot

2013-10-27 Thread Ashish
For some reason it was filled under xorg. Please ignore.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/238193

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

Title:
  Screen keeps blinking after boot

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  Please see here. 
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064

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

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


[Desktop-packages] [Bug 1245349] [NEW] After waking up from sleep mode, active window moves to first display

2013-10-27 Thread kolen
Public bug reported:

- Connect two monitors (I use builtin laptop monitor (first) and one external 
(second))
- Start some programs, move some window to second monitor and make it active
- Go into sleep mode
- Wake up the computer
- Now last active window had moved to first monitor (and possibly resized)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.1
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: Mon Oct 28 10:18:40 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21bb]
InstallationDate: Installed on 2013-10-23 (4 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 4403RP2
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET60WW (1.36 )
dmi.board.name: 4403RP2
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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4403RP2
dmi.product.version: ThinkPad L412
dmi.sys.vendor: LENOVO
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 25 17:34:23 2013
xserver.configfile: default
xserver.errors: RADEON(0): failed to set mode: Permission denied(II) RADEON(0): 
VRAM usage limit set to 451580K
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.3-3ubuntu2
xserver.video_driver: radeon

** Affects: compiz
 Importance: Undecided
 Status: New

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


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

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

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

Title:
  After waking up from sleep mode, active window moves to first display

Status in Compiz:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  - Connect two monitors (I use builtin laptop monitor (first) and one external 
(second))
  - Start some programs, move some window to second monitor and make it active
  - Go into sleep mode
  - Wake up the computer
  - Now last active window had moved to first monitor (and possibly resized)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  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: Mon Oct 28 10:18:40 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz

[Desktop-packages] [Bug 1245347] [NEW] Screen keeps blinking after boot

2013-10-27 Thread Ashish
Public bug reported:

Please see here. 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064

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

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

Title:
  Screen keeps blinking after boot

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  Please see here. 
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064

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

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


[Desktop-packages] [Bug 1241007] Re: FTBFS in saucy

2013-10-27 Thread Jackson Doak
Arm64 builds are usually fixed by running dh_autoreconf or autotools-dev
from the debian/rules file. While this may have worked, i wouldn't
recommend it.

** Description changed:

- Not sure if libgnome-media profile will be replaced in Ubuntu Saucy but
- I fixed ftbs.
+ Not sure if libgnome-media-profiles will be replaced in Ubuntu Saucy but
+ I fixed ftbfs.
  
  See ftbs buildlog (2013-10-16): https://launchpadlibrarian.net/153893423
  /buildlog_ubuntu-saucy-arm64.libgnome-media-
  profiles_3.0.0-1ubuntu1_FAILEDTOBUILD.txt.gz

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

Title:
  FTBFS in saucy

Status in “libgnome-media-profiles” package in Ubuntu:
  New

Bug description:
  Not sure if libgnome-media-profiles will be replaced in Ubuntu Saucy
  but I fixed ftbfs.

  See ftbs buildlog (2013-10-16):
  https://launchpadlibrarian.net/153893423/buildlog_ubuntu-saucy-arm64
  .libgnome-media-profiles_3.0.0-1ubuntu1_FAILEDTOBUILD.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-media-profiles/+bug/1241007/+subscriptions

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


[Desktop-packages] [Bug 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working

2013-10-27 Thread Raymond
setup the speaker pin complex 0x16 if the subwoofer is connected before
boot


+static void alc663_fixup_asus_sonicmaster(struct hda_codec *codec,
+  const struct hda_fixup *fix, int action)
+{
+   if (action != HDA_FIXUP_ACT_PRE_PROBE)
+   return;
+   if (snd_hda_pin_sense(codec, 0x18) == AC_PINSENSE_PRESENCE)
+   snd_hda_codec_set_pincfg(codec, 0x16,  0x99130111);
+}

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

Title:
  [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all:
  Subwoofer not working

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

Bug description:
  Hi,

  this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/871808 because #871808 stands for a different hardware
  with a different solution, so people may get confused.

  Here is a summary (see post #48 to #54 of #871808):
  The subwoofer of Asus N56VZ laptop doesn't work "out of the box".

  #sudo hda-jack-sense-test -a :
  *** Without subwoofer:
  Pin 0x1e (Black SPDIF Out): present = No
  *** With subwoofer:
  Pin 0x1e (Black SPDIF Out): present = Yes

  http://www.alsa-
  project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a

  --> There are two ways of making it work:

  #1
  a. Add to rc.local :
  echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs
  echo 1 > /sys/class/sound/hwC0D0/reconfig
  b. Add options snd-hda-intel model=asus-mode4 in 
/etc/modprobe.d/alsa-base.conf
  c. Reboot
  d. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1 
output" in the sound settings panel. You have to do this each time you reboot!!!

  #2
  a. Add to rc.local :
  echo 0x16 0x99130111 > /sys/class/sound/hwC0D0/user_pin_configs
  echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs
  echo 1 > /sys/class/sound/hwC0D0/reconfig
  b. Reboot
  c. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1 
output" in the sound settings panel. You have to do this each time you reboot!!!

  Both give the same results and fix the bug.

  --> Can you make it work out of the box?

  There is still two other bugs on this laptop :
  - crackling audio when playing with sound volume: see 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867
  - When I put the omputer in sleep mode, there is no way to get sound working 
on resume: should I open a new bug to investigate this?

  Regards
  Sam

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam1898 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
     Mixer name : 'Realtek ALC663'
     Components : 'HDA:10ec0663,10431477,0012'
     Controls  : 23
     Simple ctrls  : 13
  CheckboxSubmission: 54021779511d0213081a2b1707bf951c
  CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
  Date: Thu Aug 23 22:38:00 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   1898  sam   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ

[Desktop-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy

2013-10-27 Thread Ahmed Essam
hi ,this is only my second day using ubuntu , so don't laugh at me .
all the above workaround didn't work for me , however launching eclipse as root 
did work flawlessly for me . so may be a permission problem ?
Version: Kepler Service Release 1
Build id: 20130919-0819
ubuntu 13.10

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in “eclipse” package in Ubuntu:
  Triaged
Status in “unity-gtk-module” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Run Eclipse.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  Expected: The content of the submenus show up

  Actual: Only the top-level headers seem to be available. Nothing
  happens when I click on them either. They don't show up in the HUD
  either.

  It worked fine on 13.04, so I'm not sure what changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245344] Re: package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2013-10-27 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package texlive-base 2009-15 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

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

Bug description:
  i have probleme with texlive-base install, i don't know why.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: texlive-base 2009-15
  ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
  Uname: Linux 3.2.0-55-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   texlive-base: Configure
   texlive-luatex: Configure
  Architecture: i386
  Date: Sun Oct 27 11:17:31 2013
  DuplicateSignature: package:texlive-base:2009-15:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: texlive-base
  Title: package texlive-base 2009-15 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago)

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

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


[Desktop-packages] [Bug 1245344] [NEW] package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2013-10-27 Thread younes
Public bug reported:

i have probleme with texlive-base install, i don't know why.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: texlive-base 2009-15
ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
Uname: Linux 3.2.0-55-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
AptOrdering:
 texlive-base: Configure
 texlive-luatex: Configure
Architecture: i386
Date: Sun Oct 27 11:17:31 2013
DuplicateSignature: package:texlive-base:2009-15:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
MarkForUpload: True
PackageArchitecture: all
SourcePackage: texlive-base
Title: package texlive-base 2009-15 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 precise

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

Title:
  package texlive-base 2009-15 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

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

Bug description:
  i have probleme with texlive-base install, i don't know why.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: texlive-base 2009-15
  ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
  Uname: Linux 3.2.0-55-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   texlive-base: Configure
   texlive-luatex: Configure
  Architecture: i386
  Date: Sun Oct 27 11:17:31 2013
  DuplicateSignature: package:texlive-base:2009-15:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: texlive-base
  Title: package texlive-base 2009-15 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago)

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

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


[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

2013-10-27 Thread Jeffery To
I've filed this issue with upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=710986

** Bug watch added: GNOME Bug Tracker #710986
   https://bugzilla.gnome.org/show_bug.cgi?id=710986

** Changed in: gvfs
   Importance: Undecided => Unknown

** Changed in: gvfs
   Status: New => Unknown

** Changed in: gvfs
 Remote watch: None => GNOME Bug Tracker #710986

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

Title:
  gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Status in GVFS:
  Unknown
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Unmounting share from nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 27 15:58:03 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb
  InstallationDate: Installed on 2013-07-20 (6 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=fr_FR
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fad3ebbfff1:cmpb   $0x0,(%rax)
   PC (0x7fad3ebbfff1) ok
   source "$0x0" ok
   destination "(%rax)" (0x0170) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
  UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

2013-10-27 Thread Jeffery To
I can reproduce this issue with the following steps:

1.  Open a Nautilus window. (It defaults to my home directory.)
2.  Open a new tab or window. (This also opens to my home directory.)
3.  In the new tab/window, navigate to a Samba share. (I have one bookmarked so 
I click on the bookmark in the left side panel.) A new entry for the share 
appears under Network in the left side panel.
4.  Close the new tab/window.
5.  In the left side panel, under Network, click the unmount icon next to Samba 
share entry.

At this point, gvfsd-smb crashes. I also get two alert boxes (I believe
from Nautilus):

1.  Oops! Something went wrong.
Unhandled error message: The connection is closed

2.  Unable to unmount 
The connection is closed

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

Title:
  gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Unmounting share from nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 27 15:58:03 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb
  InstallationDate: Installed on 2013-07-20 (6 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=fr_FR
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fad3ebbfff1:cmpb   $0x0,(%rax)
   PC (0x7fad3ebbfff1) ok
   source "$0x0" ok
   destination "(%rax)" (0x0170) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
  UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1169904] Re: "Save screenshot" dialog window has wrong focus

2013-10-27 Thread Graham Inggs
@Norbert: That sounds like a different problem.  Please file a new bug
report against Unity.

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

Title:
  "Save screenshot" dialog window has wrong focus

Status in One Hundred Papercuts:
  In Progress
Status in “gnome-screenshot” package in Ubuntu:
  Fix Released
Status in “gnome-screenshot” source package in Raring:
  Fix Released

Bug description:
  [SRU] The debdiff attached to comment #7 backports the upstream fix
  for Raring.

  [IMPACT] After taking a screenshot users should immediately be able to
  type in a filename, instead they need to use the mouse to give focus
  to the filename field which then loses the highlight of the suggested
  filename.

  [Test Case] Take a screenshot by pressing PrintScreen or Alt-
  PrintScreen then attempt to enter a filename.

  [Regression Potential]
  Low, the single-line-fix has been in upstream for 3 months already.

  
  When you take a screenshot with the Print Screen key, you get a dialog asking 
you to name the file.

  It *looks* like the focus is on the name of the file (selected in
  orange like the File Rename dialog in Nautilus), but you can't type -
  I suspect focus is really on the Save button.

  Nor can you tab to the filename field, so you have to use your mouse
  to select what is already visually selected in order to type a name.

  Correct behaviour would be to let the user directly type to this
  dialog box without any further action.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-screenshot 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Apr 17 12:35:26 2013
  InstallationDate: Installed on 2011-12-09 (494 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to quantal on 2012-11-09 (158 days ago)

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

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


[Desktop-packages] [Bug 1174648] Re: network settings, vpn modules don't load.

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

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

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

Title:
  network settings, vpn modules don't load.

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

Bug description:
  gnome-control-center fails to find the Network-managers vpn modules.

  gnome-control-center is looking for the modules in /usr/lib/x86_64
  -linux-gnu/NetworkManager/

  However network manager + plugins packages install these modules too,
  /usr/lib/NetworkManager/. Which was changed due to Bug LP: #985788.

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

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


[Desktop-packages] [Bug 1174648] Re: network settings, vpn modules don't load.

2013-10-27 Thread DiegoRivera
I can confirm that on Ubuntu Saucy with gnome-control-
center-3.8.5-0ubuntu1~saucy the problem persists. A workaround was to
hard-link the files to the correct location (/usr/lib/x86_64-linux-
gnu/NetworkManager/) from the installation location from the plugin
packages (/usr/lib/NetworkManager/).

Of note: I'm not using Unity - I'm using gnome-shell.

Another secondary issue is that the VPN indicator for an OpenConnect VPN
on the NetworkManager drop-down doesn't accurately reflect the status of
the VPN. The full dialog from Network Settings does reflect it
accurately, and allow control over the link. As a result, the NM icon on
the notification bar remains as a lock (i.e. indicating the VPN is on)
regardless of the actual status.

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

Title:
  network settings, vpn modules don't load.

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

Bug description:
  gnome-control-center fails to find the Network-managers vpn modules.

  gnome-control-center is looking for the modules in /usr/lib/x86_64
  -linux-gnu/NetworkManager/

  However network manager + plugins packages install these modules too,
  /usr/lib/NetworkManager/. Which was changed due to Bug LP: #985788.

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

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


[Desktop-packages] [Bug 902344] Re: [Upstream] Headless soffice failure condition

2013-10-27 Thread ekasit
** Description changed:

- Command line executed:
+ Command line executed:iku iku
  "/usr/lib/libreoffice/program/soffice.bin" 
"-accept=socket,host=127.0.0.1,port=2003,tcpNoDelay=1;urp;" 
"-env:UserInstallation=file:///tmp/.jodconverter_socket_host-127.0.0.1_port-2003"
 "-headless" "-nocrashreport" "-nodefault" "-nofirststartwizard" "-nolockcheck" 
"-nologo" "-norestore"
  
  This will return on the first run. The soffice process doesn't stick around.
  This will work on subsequent runs (process doesn't return).
  If the "env:UserInstallation" 
(/tmp/.jodconverter_socket_host-127.0.0.1_port-2003) directory is removed, it 
will fail again at the next execution.
  
  A LibreOffice 3.4 package on Windows doesn't show the same behaviour
  (works every time), though it may not be the same build of LibreOffice
  3.4.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Dec  9 22:01:41 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100323)
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-05-16 (207 days ago)

** Description changed:

- Command line executed:iku iku
+ Command line executed:
  "/usr/lib/libreoffice/program/soffice.bin" 
"-accept=socket,host=127.0.0.1,port=2003,tcpNoDelay=1;urp;" 
"-env:UserInstallation=file:///tmp/.jodconverter_socket_host-127.0.0.1_port-2003"
 "-headless" "-nocrashreport" "-nodefault" "-nofirststartwizard" "-nolockcheck" 
"-nologo" "-norestore"
  
  This will return on the first run. The soffice process doesn't stick around.
  This will work on subsequent runs (process doesn't return).
  If the "env:UserInstallation" 
(/tmp/.jodconverter_socket_host-127.0.0.1_port-2003) directory is removed, it 
will fail again at the next execution.
  
  A LibreOffice 3.4 package on Windows doesn't show the same behaviour
  (works every time), though it may not be the same build of LibreOffice
  3.4.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Dec  9 22:01:41 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100323)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-05-16 (207 days ago)

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

Title:
  [Upstream] Headless soffice failure condition

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

Bug description:
  Command line executed:
  "/usr/lib/libreoffice/program/soffice.bin" 
"-accept=socket,host=127.0.0.1,port=2003,tcpNoDelay=1;urp;" 
"-env:UserInstallation=file:///tmp/.jodconverter_socket_host-127.0.0.1_port-2003"
 "-headless" "-nocrashreport" "-nodefault" "-nofirststartwizard" "-nolockcheck" 
"-nologo" "-norestore"

  This will return on the first run. The soffice process doesn't stick around.
  This will work on subsequent runs (process doesn't return).
  If the "env:UserInstallation" 
(/tmp/.jodconverter_socket_host-127.0.0.1_port-2003) directory is removed, it 
will fail again at the next execution.

  A LibreOffice 3.4 package on Windows doesn't show the same behaviour
  (works every time), though it may not be the same build of LibreOffice
  3.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Dec  9 22:01:41 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100323)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-05-16 (207 days ago)

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

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


[Desktop-packages] [Bug 1245258] Re: Alt+Shift hotkey for keyboard layout switching do not work unity-greeter in Saucy

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

** Changed in: unity-greeter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Alt+Shift hotkey for keyboard layout switching do not work unity-
  greeter in Saucy

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

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Alt+Shift
  keyboard layout change hotkey does not work in in Unity greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 23:18:32 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245258/+subscriptions

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


[Desktop-packages] [Bug 1242259] Re: Thinkpad x1 Volume up down and mute keys stopped working after upgrade to Ubuntu 13.10

2013-10-27 Thread harrychillboy
Some updates : Looks like the volume and other shortcut keys in Ubuntu
are handled by some core unity session or process which also handles
keys like ctrl + alt + l ( lock screen ) other keys too. I am not a big
fan of unity and the buggy global menu so I stopped using unity and
thats what caused my keys to stop working. If I use plain vanilla unity
shell then all keys work perfectly but that creates some annoying issues
of dealing with buggy global menu and slow dash ( even with i7 + 6GB ram
machine. )

Workaround : Install CCM ( Compiz Config Manager ) then enable "Commands" 
module plugin then add following commands to your commands list :
* Increase volume : /usr/bin/pactl set-sink-volume 0 -- +20%
* Decrease volume : /usr/bin/pactl set-sink-volume 0 -- -20%
* Mute : /usr/bin/pactl set-sink-mute 0 toggle
* Lock screen : bash -c "xset dpms force off; DISPLAY=:0 
gnome-screensaver-command -l"

Then using same module shortcuts, map them to whichever keys and it
works perfectly ( and always even after boot ).

I use "Synapse" tool which is mapped to my Meta ( Windows) keys and I use it to 
launch all my apps ( much faster than unity dash ). I used help here to get 
ride of ubuntu gloabl menu : 
http://askubuntu.com/questions/10481/how-do-i-disable-the-global-application-menu

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

Title:
  Thinkpad x1 Volume up down and mute keys stopped working after upgrade
  to Ubuntu 13.10

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  My thinkpad x1 laptop special keys for volume up , down and mute
  stopped working after upgrade to Ubuntu 13.10 from 13.04. They were
  working properly on 13.04 version. The keys are still recognized and
  can be used for other custom shortcuts but the default volume up /
  down and mute does not work. I have tried setting these keys
  explicitly in systems settings -> keyboard shortcut but even after
  doing so it did not work. Neither of volume indicator icons are shown
  nor it controls volume.

  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 14:57:02 2013
  DistUpgraded: 2013-10-18 15:48:37,655 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 20130623, 3.11.0-12-generic, x86_64: installed
   acpi-call, 20130623, 3.8.0-31-generic, x86_64: installed
   tp-smapi, 0.41, 3.11.0-12-generic, x86_64: installed
   tp-smapi, 0.41, 3.8.0-31-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: Lenovo Device [17aa:21f9]
  InstallationDate: Installed on 2013-04-24 (178 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 3460AJ1
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=e349a24b-5273-4413-9fa8-f12654c182c3 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (1 days ago)
  dmi.bios.date: 11/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET66WW (2.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3460AJ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET66WW(2.10):bd11/20/2012:svnLENOVO:pn3460AJ1:pvrThinkPadX1Carbon:rvnLENOVO:rn3460AJ1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3460AJ1
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  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-in

[Desktop-packages] [Bug 1245272] Re: Can't set keyboard layout change to Shift+Shift

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

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

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

Title:
  Can't set keyboard layout change to Shift+Shift

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

Bug description:
  In Ubuntu 12.04 I was able to set keyboard layout switching shortcut to 
Shift+Shift.
  In Ubuntu 13.10 I can't set it from gnome-control-center keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:32:03 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1245272/+subscriptions

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


[Desktop-packages] [Bug 1245278] Re: Shift+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy

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

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

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

Title:
  Shift+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Shift+Shift hotkey for keyboard layout change does not work in GNOME 
screensaver of Ubuntu 13.10.
  This hotkey combination is set with packages from ppa:attente/1218322.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:15:08 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245268] Re: Ctrl+Shift hotkey for keyboard layout switching does not work unity-greeter in Saucy

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

** Changed in: unity-greeter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ctrl+Shift hotkey for keyboard layout switching does not work unity-
  greeter in Saucy

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

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Ctrl+Shift
  keyboard layout change hotkey does not work in in Unity greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:10:19 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245268/+subscriptions

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


[Desktop-packages] [Bug 1245270] Re: Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy

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

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

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

Title:
  Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Ctrl+Shift hotkey for keyboard layout change does not work in GNOME
  screensaver of Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:15:19 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245280] Re: Shift+Shift hotkey for keyboard layout switching does not work unity-greeter in Saucy

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

** Changed in: unity-greeter (Ubuntu)
   Status: New => Confirmed

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

Title:
   Shift+Shift hotkey for keyboard layout switching does not work unity-
  greeter in Saucy

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

Bug description:
  Shift+Shift hotkey for keyboard layout change does not work in unity-greeter 
of Ubuntu 13.10.
  This hotkey combination is set with packages from ppa:attente/1218322.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:19:24 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245280/+subscriptions

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


[Desktop-packages] [Bug 1082935] Re: Context menu doesn't appear by default when navigating between applications

2013-10-27 Thread Launchpad Bug Tracker
[Expired for gimp (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Context menu doesn't appear by default when navigating between
  applications

Status in “gimp” package in Ubuntu:
  Expired

Bug description:
  Context menu doesn't appear by default when navigating between
  applications, because when GIMP regains focus the window being
  selected by default is “Toolbox” not the main one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gimp 2.8.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sun Nov 25 19:21:21 2012
  InstallationDate: Installed on 2012-11-02 (22 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Desktop-packages] [Bug 879328] Re: Equalizer option is disabled / grayed out

2013-10-27 Thread Chow Loong Jin
On Mon, Oct 28, 2013 at 03:15:13AM -, Eric Ongerth wrote:
> Same problem, fresh new install (not upgrade) of 13.10, really wasn't
> happy with rhythmbox under 13.10 so I installed banshee.  When first
> installed, two days ago, banshee's Equalizer was available.  I changed
> one or two extensions (I did NOT enable anything connected with
> Last.fm.).  I cannot remember exactly which extensions I checked or
> unchecked but both of the extensions relating to Last.fm are UNchecked.
> 
> gst-inspect-0.10 | grep equalizer shos 10 band, 3 band, and N band
> equalizer in place and yes, gstreamer0.10-plugins-good is installed.

Try `gst-inspect-1.0 | grep equalizer` instead, and check for
gstreamer1.0-plugins-good.

> Any other ideas on this?  I hope I don't have to (a) reinstall Banshee
> or (b) play a guessing game with all possible combinations of
> extensions.  Thanks in advance.

It's not something to do with extensions, I believe.

-- 
Kind regards,
Loong Jin

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

Title:
  Equalizer option is disabled / grayed out

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Unsure as to the reason, there doesn't seem to be an option for it on
  the preferences menu (or anywhere that doesn't require me to look at
  code or recompile the whole thing) , but the equalizer option is
  inaccessible and has been since the 2.2 update (it was working
  before).

  Hopefully it's a real life bug and not a bad case of user n00bism (me)
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 21 10:49:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (49 days ago)

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

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


[Desktop-packages] [Bug 1087851] Re: Uses deprecated GTK3 API

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

** Changed in: libgnome-media-profiles (Ubuntu)
   Status: New => Confirmed

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

Title:
  Uses deprecated GTK3 API

Status in GNOME Media Profiles library:
  New
Status in “libgnome-media-profiles” package in Ubuntu:
  Confirmed

Bug description:
  libgnome-media-profiles uses same deprecated GTK3 API

  See: https://launchpadlibrarian.net/125123060/buildlog_ubuntu-
  raring-i386.libgnome-media-profiles_3.0.0-1ubuntu1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgnome-media-profiles/+bug/1087851/+subscriptions

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


[Desktop-packages] [Bug 1245155] Re: Menus are very slow to load

2013-10-27 Thread Andrew Anderson
Same here, on 13.10 64-bit. It worked great in 13.04, then I did a clean
install of Ubuntu 13.10, leaving only /home partition intact, and GIMP
has had these menu problems ever since.

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

Title:
  Menus are very slow to load

Status in “gimp” package in Ubuntu:
  Confirmed

Bug description:
  When trying to use menu (File - Edit - Select - etc) it takes at time
  over 10 sec to appear and further 3-5sec to load the drop down menus.
  Often when switching from another program the previous program is
  still there. This does not happen in other programs. This happens with
  one small file and with many big files open in Gimp. Gimp used to be
  nice and fast, even in 13.10. Not sure which update caused it to slow
  down, been running 13.10 beta for a while.

  Shortcuts work just fine, I just can't remember them all and therefore
  has to use the menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gimp 2.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 27 10:29:30 2013
  ExecutablePath: /usr/bin/gimp-2.8
  InstallationDate: Installed on 2013-08-04 (83 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gimp
  UpgradeStatus: Upgraded to saucy on 2013-08-19 (68 days ago)

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

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


[Desktop-packages] [Bug 1245155] Re: Menus are very slow to load

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

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

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

Title:
  Menus are very slow to load

Status in “gimp” package in Ubuntu:
  Confirmed

Bug description:
  When trying to use menu (File - Edit - Select - etc) it takes at time
  over 10 sec to appear and further 3-5sec to load the drop down menus.
  Often when switching from another program the previous program is
  still there. This does not happen in other programs. This happens with
  one small file and with many big files open in Gimp. Gimp used to be
  nice and fast, even in 13.10. Not sure which update caused it to slow
  down, been running 13.10 beta for a while.

  Shortcuts work just fine, I just can't remember them all and therefore
  has to use the menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gimp 2.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 27 10:29:30 2013
  ExecutablePath: /usr/bin/gimp-2.8
  InstallationDate: Installed on 2013-08-04 (83 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gimp
  UpgradeStatus: Upgraded to saucy on 2013-08-19 (68 days ago)

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

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


[Desktop-packages] [Bug 1244817] Re: nvidia-304 304.88-0ubuntu1: nvidia-304 kernel module failed to build

2013-10-27 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1184691 ***
https://bugs.launchpad.net/bugs/1184691

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


** This bug has been marked a duplicate of bug 1184691
   nvidia kernel module fails to build with kernel 3.10 or later [error: void 
value not ignored as it ought to be]

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

Title:
  nvidia-304 304.88-0ubuntu1: nvidia-304 kernel module failed to build

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

Bug description:
  appeared right after updating my xubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-304
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.11.0-12-generic
  Date: Sat Oct 26 00:44:03 2013
  DuplicateSignature: 
dkms:nvidia-304:304.88-0ubuntu1:/var/lib/dkms/nvidia-304/304.88/build/nv-i2c.c:327:14:
 error: void value not ignored as it ought to be
  InstallationDate: Installed on 2010-08-10 (1172 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  PackageVersion: 304.88-0ubuntu1
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.88-0ubuntu1: nvidia-304 kernel module failed to build
  UpgradeStatus: Upgraded to saucy on 2013-10-25 (0 days ago)

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

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


[Desktop-packages] [Bug 1244881] Re: nvidia-319 black screen after upgrade from 13.04 to 13.10

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

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

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

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

Title:
  nvidia-319 black screen after upgrade from 13.04 to 13.10

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

Bug description:
  I was on Ubuntu 13.04, just changed from nvidia-current to nvidia-319
  a few days ago.

  Today, I decided to upgrade to 13.10, after reboot, 
  1. The login screen was in low resolution.
  2. Then right after login, an error dialog pop-up saying detected system 
problem, asking me whether to report the problem. 
  3. Further to proceed, then black screen with only mouse pointer freely to 
move.
  4. Switched to command terminal tty1 (ctrl + alt + F1), logged in and used 
apt-get to remove nvidia-319 and re-install nvidia-current & nvidia-settings.
  5. Rebooted and seems fine, the "Report System Problem" dialog pop-up again 
and now being directed to here to report the problem.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 3.11.0-12-generic
  Date: Sat Oct 26 14:04:59 2013
  InstallationDate: Installed on 2013-01-19 (279 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageVersion: 319.49-0ubuntu1~raring~xup1
  SourcePackage: nvidia-graphics-drivers-319
  Title: nvidia-319 319.49-0ubuntu1~raring~xup1: nvidia-319 kernel module 
failed to build
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (0 days ago)

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

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


[Desktop-packages] [Bug 879328] Re: Equalizer option is disabled / grayed out

2013-10-27 Thread Eric Ongerth
Same problem, fresh new install (not upgrade) of 13.10, really wasn't
happy with rhythmbox under 13.10 so I installed banshee.  When first
installed, two days ago, banshee's Equalizer was available.  I changed
one or two extensions (I did NOT enable anything connected with
Last.fm.).  I cannot remember exactly which extensions I checked or
unchecked but both of the extensions relating to Last.fm are UNchecked.

gst-inspect-0.10 | grep equalizer shos 10 band, 3 band, and N band
equalizer in place and yes, gstreamer0.10-plugins-good is installed.

Any other ideas on this?  I hope I don't have to (a) reinstall Banshee
or (b) play a guessing game with all possible combinations of
extensions.  Thanks in advance.

** Changed in: banshee (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Equalizer option is disabled / grayed out

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Unsure as to the reason, there doesn't seem to be an option for it on
  the preferences menu (or anywhere that doesn't require me to look at
  code or recompile the whole thing) , but the equalizer option is
  inaccessible and has been since the 2.2 update (it was working
  before).

  Hopefully it's a real life bug and not a bad case of user n00bism (me)
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 21 10:49:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (49 days ago)

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

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


[Desktop-packages] [Bug 6934] Re: mozilla-firefox: postinstall script failure

2013-10-27 Thread glen cunningham
** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => glen cunningham (glencunningham7510)

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

Title:
  mozilla-firefox: postinstall script failure

Status in “firefox” package in Ubuntu:
  Invalid
Status in “firefox” package in Debian:
  Fix Released

Bug description:
  Automatically imported from Debian bug report #238705
  http://bugs.debian.org/238705

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

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


[Desktop-packages] [Bug 1245315] [NEW] alacarte fails to write a proper "Categories=<>; " line to .desktop files

2013-10-27 Thread Leo H
Public bug reported:

When creating a new menu entry in the Applications Menu of Xubuntu using
the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not
enable the writing of a "Categories=<>;" attribute in the new .desktop
file created in /home/<>/local/share/applications/.

Without a recognized and meaningful "Categories=<>;" attribute, the new
menu entry is relegated by default to the non-specific "Other" menu
category in the Applications Menu of Xubuntu.

Moving the newly-created menu entry in question to a more meaningful
Applications Menu category (such as, eg, "Applications", "Office",
"Systems", etc) by dragging and dropping then fails in alacarte due to
the very absence of any "Categories=<>;" attribute in the .desktop file.

Instead,

First, when creating a new menu entry in, for example, "Applications",
then alacarte should write a corresponding "Categories=<>;" attribute
line in the newly-made .desktop file.

Second, when dragging and dropping the newly-created menu entry in
alacarte from, for example, "Applications" to, for instance, "System",
then alacarte should amend the "Categories=<>;" attribute line in the
.desktop file accordingly.


Note 1: If alacarte cannot do these things automatically, then it should at 
least allow the user to choose the Application Menu category, say, from a 
drop-down list, when creating or editing a menu entry, and write this choice to 
the corresponding .desktop file in the form of a suitable "Categories=<>;" 
attribute line.

Note 2: Resolving this issue by manually editing .desktop files, of
course, wholly defeats the very raison d'être of Menu Editor programs
such as alacarte.


--
System: xubuntu 13.10 32-bit fully up-to-date

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


** Tags: alacarte category edit menu

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

Title:
  alacarte fails to write a proper "Categories=<>;" line to .desktop
  files

Status in “alacarte” package in Ubuntu:
  New

Bug description:
  When creating a new menu entry in the Applications Menu of Xubuntu
  using the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does
  not enable the writing of a "Categories=<>;" attribute in the new
  .desktop file created in /home/<>/local/share/applications/.

  Without a recognized and meaningful "Categories=<>;" attribute, the
  new menu entry is relegated by default to the non-specific "Other"
  menu category in the Applications Menu of Xubuntu.

  Moving the newly-created menu entry in question to a more meaningful
  Applications Menu category (such as, eg, "Applications", "Office",
  "Systems", etc) by dragging and dropping then fails in alacarte due to
  the very absence of any "Categories=<>;" attribute in the .desktop
  file.

  Instead,

  First, when creating a new menu entry in, for example, "Applications",
  then alacarte should write a corresponding "Categories=<>;" attribute
  line in the newly-made .desktop file.

  Second, when dragging and dropping the newly-created menu entry in
  alacarte from, for example, "Applications" to, for instance, "System",
  then alacarte should amend the "Categories=<>;" attribute line in the
  .desktop file accordingly.

  
  Note 1: If alacarte cannot do these things automatically, then it should at 
least allow the user to choose the Application Menu category, say, from a 
drop-down list, when creating or editing a menu entry, and write this choice to 
the corresponding .desktop file in the form of a suitable "Categories=<>;" 
attribute line.

  Note 2: Resolving this issue by manually editing .desktop files, of
  course, wholly defeats the very raison d'être of Menu Editor programs
  such as alacarte.

  
  --
  System: xubuntu 13.10 32-bit fully up-to-date

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

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


[Desktop-packages] [Bug 1245315] [NEW] alacarte fails to write a proper "Categories=<>; " line to .desktop files

2013-10-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Leo H (leo-h-hildebrandt):

When creating a new menu entry in the Applications Menu of Xubuntu using
the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not
enable the writing of a "Categories=<>;" attribute in the new .desktop
file created in /home/<>/local/share/applications/.

Without a recognized and meaningful "Categories=<>;" attribute, the new
menu entry is relegated by default to the non-specific "Other" menu
category in the Applications Menu of Xubuntu.

Moving the newly-created menu entry in question to a more meaningful
Applications Menu category (such as, eg, "Applications", "Office",
"Systems", etc) by dragging and dropping then fails in alacarte due to
the very absence of any "Categories=<>;" attribute in the .desktop file.

Instead,

First, when creating a new menu entry in, for example, "Applications",
then alacarte should write a corresponding "Categories=<>;" attribute
line in the newly-made .desktop file.

Second, when dragging and dropping the newly-created menu entry in
alacarte from, for example, "Applications" to, for instance, "System",
then alacarte should amend the "Categories=<>;" attribute line in the
.desktop file accordingly.


Note 1: If alacarte cannot do these things automatically, then it should at 
least allow the user to choose the Application Menu category, say, from a 
drop-down list, when creating or editing a menu entry, and write this choice to 
the corresponding .desktop file in the form of a suitable "Categories=<>;" 
attribute line.

Note 2: Resolving this issue by manually editing .desktop files, of
course, wholly defeats the very raison d'être of Menu Editor programs
such as alacarte.


--
System: xubuntu 13.10 32-bit fully up-to-date

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


** Tags: alacarte category edit menu
-- 
alacarte fails to write a proper "Categories=<>;" line to .desktop files
https://bugs.launchpad.net/bugs/1245315
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to the bug report.

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


[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-27 Thread Tong Sun
I remember reading the following but it took me more than 3 rounds of
careful reading to find it again. So, re-posting again:

Evan Huus (eapache) wrote:

> it's not even a NetworkManager bug - whatever is supposed to be
> sending that signal to nm isn't sending it (correctly...)
> 
> I have noticed that in cases where this bug appears, other power
> management options also fail - trying to suspend again from the
> gear menu does nothing, I have to run pm-suspend from the
> cli. This indicates to me that some whole underlying subsystem is
> getting confused, and that other components may also need to be
> kicked - NetworkManager is just the most obvious one people
> notice right away.

I believe this is the most accurate description of the problem:

- it's not merely a NetworkManager bug
- the whole suspend/wake up mechanize is not working properly
- NetworkManager is just the most obvious one people notice right away

On my machine, Acer Aspire AS5536, if I close the lid then open & wake
it up, my wired & wireless network will be gone. If I close the lid a
second time, the machine won't even go to the suspend stage again.

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

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

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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


[Desktop-packages] [Bug 1002480] Re: [Asus P8P67, Realtek ALC892, playback] Underruns, dropouts or crackling sound

2013-10-27 Thread knet
Yes i have seen that everywhere, i read it in other posts you answered
too but cant make any sense of it. Sorry.

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

Title:
  [Asus P8P67, Realtek ALC892, playback] Underruns, dropouts or
  crackling sound

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  It's started when I updated Ubuntu to 12.04.
  For a while, the sound is good. Then it turns into a crackling noise. After 
killing pulseaudio and starting it again, the sound is good again for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   3510 F pulseaudio
   /dev/snd/pcmC0D0p:   john   3510 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfb50 irq 68'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 44
 Simple ctrls  : 21
  Date: Mon May 21 23:08:32 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HDA-Intel - HDA Intel PCH, playback] Underruns, dropouts or crackling 
sound
  UpgradeStatus: Upgraded to precise on 2012-04-27 (24 days ago)
  dmi.bios.date: 03/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 1245213] Re: Wine doesn't find 32-bit OpenGL drivers

2013-10-27 Thread Quinn Balazs
Is this with wine 1.4.1-0ubuntu7?

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

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

Title:
  Wine doesn't find 32-bit OpenGL drivers

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

Bug description:
  Wine doesn't find the 32-bit opengl drivers on a 64bit system.  I have
  to use LD_PRELOAD to tell where the 32-bit opengl libs are, like this:

  $ LD_PRELOAD=/usr/lib32/nvidia-319-updates/libGL.so wine exefile.exe

  If I don't use this, I get this:

  X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely
  your 32-bit OpenGL drivers haven't been installed correctly (using GL
  renderer "GeForce 8800 GT/PCIe/SSE2", version "1.4 (2.1.2 NVIDIA
  319.32)")

  
  Here's the needed info:
  1)
  $ lsb_release -rd
  Description:Ubuntu 12.04.3 LTS
  Release:12.04

  2)
  $ apt-cache policy nvidia-319-updates
  nvidia-319-updates:
Installed: 319.32-0ubuntu0.0.1
Candidate: 319.32-0ubuntu0.0.1
Version table:
   *** 319.32-0ubuntu0.0.1 0
  500 http://ftp.astral.ro/mirrors/ubuntu.com/ubuntu/ 
precise-updates/restricted amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the 32-bit opengl to be automatically loaded and the application 
to work

  4)
  The app never loaded, and I found this in the output:

  err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most 
likely your 32-bit OpenGL drivers haven't been installed correctly (using GL 
renderer "GeForce 8800 GT/PCIe/SSE2", version "1.4 (2.1.2 NVIDIA 319.32)").
  err:d3d:WineD3D_CreateFakeGLContext Failed to find a suitable pixel format.
  err:d3d:wined3d_adapter_init Failed to get a GL context for adapter 0x1794f8.
  err:d3d:WineD3D_CreateFakeGLContext Failed to find a suitable pixel format.
  err:d3d:wined3d_adapter_init Failed to get a GL context for adapter 0x1794f8.

  I found another bug, #764200, that was opened against Natty, and
  expired.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-319-updates 319.32-0ubuntu0.0.1 [modified: 
usr/lib/nvidia-319-updates/alt_ld.so.conf]
  ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
  Uname: Linux 3.2.0-55-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Oct 27 17:56:11 2013
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120327)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-319-updates
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 615549] Re: gdm/kdm starting too early for DRM modules to load, no video

2013-10-27 Thread Adolfo Jayme Barrientos
** Changed in: kdebase-workspace (Ubuntu Lucid)
   Status: Triaged => Won't Fix

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

Title:
  gdm/kdm starting too early for DRM modules to load, no video

Status in “gdm” package in Ubuntu:
  Fix Released
Status in “kdebase-workspace” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Lucid:
  Fix Released
Status in “kdebase-workspace” source package in Lucid:
  Won't Fix
Status in “gdm” source package in Maverick:
  Fix Released
Status in “kdebase-workspace” source package in Maverick:
  Fix Released

Bug description:
  Using "nomodeset" at boot works as a workaround

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-14-generic 2.6.35-14.20
  Regression: Yes
  ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
  Uname: Linux 2.6.35-14-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Aug  9 15:59:55 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100809)
  ProcEnviron:
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: linux
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1529 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xf088 irq 17'
 Mixer name : 'Nvidia MCP79/7A HDMI'
 Components : 'HDA:111d7675,10280271,00100103 
HDA:10de0007,10280271,00100100'
 Controls  : 20
 Simple ctrls  : 11
  DistroRelease: Ubuntu 10.10
  HibernationDevice: RESUME=UUID=724430c8-4097-40d3-835b-e1538cba4bf7
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100809)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 05ca:18a0 Ricoh Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Studio XPS 1340
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic 
root=UUID=7e251ff1-0717-43ca-b496-8a11f8bc48ca ro rootdelay=60 nomodeset 
initcall_debug
  ProcEnviron:
   LANG=en_US
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
  Regression: No
  RelatedPackageVersions: linux-firmware 1.37
  Reproducible: Yes
  RfKill:
   0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags: maverick graphics needs-upstream-testing
  Uname: Linux 2.6.35-14-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0K183D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0K183D:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

  --- 
  Architecture: i386
  DRM.card0.VGA.1:
   status: connected
   enabled: disabled
   dpms: On
   modes: 1024x768 800x600 800x600 848x480 640x480
   edid-base64:
  DRM.card1.DisplayPort.3:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DRM.card1.LVDS.2:
   status: connected
   enabled: disabled
   dpms: On
   modes: 1280x800 1024x768 800x600 640x480 720x400 640x400 640x350
   edid-base64: 
AP///wBMo0NUAAASAQOQGhF4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAwIDYAK8MQAAAa7hoAgFAgEDAwIDYAK8MQAAAa/gBHTjI2NIAxMzNBVAogAAEBCiAgAOw=
  DRM.card1.VGA.2:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DistroRelease: Ubuntu 10.10
  DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.35-14-generic, i686: installed
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100811)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 05ca:18a0 Ricoh Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Studio XPS 1340
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:0.0.16+git20100805+b96170a-0ubuntu1
  PackageArchitecture: i386
  Pro

[Desktop-packages] [Bug 1245161] Re: REPARAR CATALOGO DE PAQUETE

2013-10-27 Thread Adolfo Jayme Barrientos
** Changed in: software-center (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/software-center/+question/238183

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

Title:
  REPARAR CATALOGO DE PAQUETE

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

Bug description:
  HE INSERTADO EN LA TERMINAL LO QUE ME INDICAS Y ME INDICA ARCHIVO NO
  ENCONTRADO 404



  Hola, cuando accedo al gestor de programas,  Me sale una ventana con
  el siguiente error:

  NO SE PUEDE ISNTALAR NI DESINSTALAR ELEMENTOS HASTA QUE SE REPARE EL
  CATÁLOGO DE PAQUETES.

  Le doy a la opción reparar ahora  y me sale el siguiente error.

  FALLO AL DESCARGAR LOS ARCHIVOS DE PAQUETE.

  A qué es debido y cómo puedo solucionarlo. Gracias

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

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


[Desktop-packages] [Bug 1241811] Re: USB disk not automatically mounted after upgrade to 13.10

2013-10-27 Thread Romano Giannetti
I have dome more tests, but I could not find the conditions under which it 
worked some days ago. 
Summarizing, no automatic mount of USB drives. Anyone can give some hint on 
debugging it?

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in Ubuntu GNOME:
  New
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “nautilus-udisks” package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade to 13.10, my laptop stopped mounting the USB devices
  (and SD cards too) automatically.

  Inserting the USB I have in the log:

  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.570340] usb 3-2: new 
high-speed USB device number 3 using xhci_hcd
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593170] usb 3-2: New USB 
device found, idVendor=090c, idProduct=1000
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593181] usb 3-2: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593187] usb 3-2: Product: 
Flash Disk
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593192] usb 3-2: 
Manufacturer: USB
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593196] usb 3-2: 
SerialNumber: FBF1009232400790
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593492] usb 3-2: ep 0x81 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593501] usb 3-2: ep 0x2 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.595232] scsi7 : 
usb-storage 3-2:1.0
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: checking bus 3, device 3: 
"/sys/devices/pci:00/:00:1c.4/:04:00.0/usb3/3-2"
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: bus: 3, device: 3 was not an 
MTP device
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.834382] scsi 7:0:0:0: 
Direct-Access USB  Flash Disk   1100 PQ: 0 ANSI: 0 CCS
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.835894] sd 7:0:0:0: 
Attached scsi generic sg3 type 0
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836227] sd 7:0:0:0: [sdc] 
3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836910] sd 7:0:0:0: [sdc] 
Write Protect is off
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836926] sd 7:0:0:0: [sdc] 
Mode Sense: 43 00 00 00
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837665] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837676] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843552] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843562] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.844609]  sdc: sdc1
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846982] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846990] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846997] sd 7:0:0:0: [sdc] 
Attached SCSI removable disk

  But after that nothing happens. I checked the dconf variables as per
  https://help.ubuntu.com/community/Mount/USB but it's all correctly
  set. I can mount the disk by hand:

  % sudo mount /dev/sdc1 /mnt
  % mount | grep mnt
  /dev/sdc1 on /mnt type vfat (rw)

  ...and it works ok.

  Add: using from command line udisks works, too:

  (0)samsung-romano:~% udisks --mount /dev/sdc1
  Mounted /org/freedesktop/UDisks/devices/sdc1 at /media/PENDRIVE

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

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


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

2013-10-27 Thread Aurosutru
Upgrading to kernel 3.8.0-32-generic actually made this problem much
worse, but last night's auto-upgrade including the error reporting
software (apport, python files, etc.) along with the Intel 9xx and 8xx
driver upgrade, etc. seems to have solved this.  Thanks.

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Hi,

  After the latest automatic kernel upgrade to 3.8.0-31-generic my
  Ubuntu 13.04 system again has graphics instability, especially when an
  external monitor is connected to or disconnected from the laptop.
  Sometime system text messages on a black screen will appear on the
  monitor or laptop screen when the graphical output quits.  This
  problem happened with previous kernel upgrades this year and was
  resolved when a new display manager file was installed in a subsequent
  small auto upgrade.  Reverting to 3.8.0-30 at start up now gets rid of
  the problem.

  The system is an ASUS K55A laptop with an i7 3630QM CPU having Intel
  HD 4000 on-chip graphics.

  I can help with some technical detective work to help solve this
  problem, but due to  a slow EDGE Inet connection kernel bisections are
  not feasible.

  Thanks for your help.

  Aurosutru

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.3
  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: Sun Oct 13 06:54:19 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:2102]
  InstallationDate: Installed on 2013-06-17 (117 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. K55A
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=440d36e9-d062-454d-bbc6-f718f29b97ad ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.404
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sun Oct 13 06:51:54 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1245300] [NEW] alacarte does not delete deleted application menu entries

2013-10-27 Thread Leo H
Public bug reported:

When a menu entry in the Applications Menu of Xubuntu is deleted using
the Alacarte Menu Editor, then alacarte (3.10.0-1) does NOT delete its
.desktop file. Instead alacarte writes a new "Hidden=true" line in its
.desktop file in /home/<>/local/share/applications/ and it only deletes
the entry from the list of menu entries which are shown in alacarte
itself.

This is wrong. Delete and Hidden are two different things:

.desktop files with the attribute "Hidden=true" should be shown in
alacarte as unticked menu entries.

Further, by failing actually to delete, alacarte populates
/home/<>/local/share/applications/ with increasing numbers of obsolete
and dysfunctional .desktop entries. These are difficult to identify and
delete manually when browsing /home/<>/local/share/applications/,
because alacarte gives all .desktop files which it makes non-specific
generic names of the type alacarte-made-nn.desktop.

--
System: xubuntu 13.10 32-bit fully up-to-date

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


** Tags: alacarte delete hide

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

Title:
  alacarte does not delete deleted application menu entries

Status in “alacarte” package in Ubuntu:
  New

Bug description:
  When a menu entry in the Applications Menu of Xubuntu is deleted using
  the Alacarte Menu Editor, then alacarte (3.10.0-1) does NOT delete its
  .desktop file. Instead alacarte writes a new "Hidden=true" line in its
  .desktop file in /home/<>/local/share/applications/ and it only
  deletes the entry from the list of menu entries which are shown in
  alacarte itself.

  This is wrong. Delete and Hidden are two different things:

  .desktop files with the attribute "Hidden=true" should be shown in
  alacarte as unticked menu entries.

  Further, by failing actually to delete, alacarte populates
  /home/<>/local/share/applications/ with increasing numbers of obsolete
  and dysfunctional .desktop entries. These are difficult to identify
  and delete manually when browsing /home/<>/local/share/applications/,
  because alacarte gives all .desktop files which it makes non-specific
  generic names of the type alacarte-made-nn.desktop.

  --
  System: xubuntu 13.10 32-bit fully up-to-date

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

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


[Desktop-packages] [Bug 1245300] [NEW] alacarte does not delete deleted application menu entries

2013-10-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Leo H (leo-h-hildebrandt):

When a menu entry in the Applications Menu of Xubuntu is deleted using
the Alacarte Menu Editor, then alacarte (3.10.0-1) does NOT delete its
.desktop file. Instead alacarte writes a new "Hidden=true" line in its
.desktop file in /home/<>/local/share/applications/ and it only deletes
the entry from the list of menu entries which are shown in alacarte
itself.

This is wrong. Delete and Hidden are two different things:

.desktop files with the attribute "Hidden=true" should be shown in
alacarte as unticked menu entries.

Further, by failing actually to delete, alacarte populates
/home/<>/local/share/applications/ with increasing numbers of obsolete
and dysfunctional .desktop entries. These are difficult to identify and
delete manually when browsing /home/<>/local/share/applications/,
because alacarte gives all .desktop files which it makes non-specific
generic names of the type alacarte-made-nn.desktop.

--
System: xubuntu 13.10 32-bit fully up-to-date

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


** Tags: alacarte delete hide
-- 
alacarte does not delete deleted application menu entries
https://bugs.launchpad.net/bugs/1245300
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to the bug report.

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


[Desktop-packages] [Bug 1002480] Re: [Asus P8P67, Realtek ALC892, playback] Underruns, dropouts or crackling sound

2013-10-27 Thread Raymond
Early Patching
~~
When CONFIG_SND_HDA_PATCH_LOADER=y is set, you can pass a "patch" as a
firmware file for modifying the HD-audio setup before initializing the
codec.  This can work basically like the reconfiguration via sysfs in
the above, but it does it before the first codec configuration.

A patch file is a plain text file which looks like below:


  [codec]
  0x12345678 0xabcd1234 2

  [model]
  auto

  [pincfg]
  0x12 0x41f0

  [verb]
  0x20 0x500 0x03
  0x20 0x400 0xff

  [hint]
  jack_detect = no


The file needs to have a line `[codec]`.  The next line should contain
three numbers indicating the codec vendor-id (0x12345678 in the
example), the codec subsystem-id (0xabcd1234) and the address (2) of
the codec.  The rest patch entries are applied to this specified codec
until another codec entry is given.  Passing 0 or a negative number to
the first or the second value will make the check of the corresponding
field be skipped.  It'll be useful for really broken devices that don't
initialize SSID properly.

The `[model]` line allows to change the model name of the each codec.
In the example above, it will be changed to model=auto.
Note that this overrides the module option.

After the `[pincfg]` line, the contents are parsed as the initial
default pin-configurations just like `user_pin_configs` sysfs above.
The values can be shown in user_pin_configs sysfs file, too.

Similarly, the lines after `[verb]` are parsed as `init_verbs`
sysfs entries, and the lines after `[hint]` are parsed as `hints`
sysfs entries, respectively.

Another example to override the codec vendor id from 0x12345678 to
0xdeadbeef is like below:

  [codec]
  0x12345678 0xabcd1234 2

  [vendor_id]
  0xdeadbeef


In the similar way, you can override the codec subsystem_id via
`[subsystem_id]`, the revision id via `[revision_id]` line.
Also, the codec chip name can be rewritten via `[chip_name]` line.

  [codec]
  0x12345678 0xabcd1234 2

  [subsystem_id]
  0x

  [revision_id]
  0x10

  [chip_name]
  My-own NEWS-0002


The hd-audio driver reads the file via request_firmware().  Thus,
a patch file has to be located on the appropriate firmware path,
typically, /lib/firmware.  For example, when you pass the option
`patch=hda-init.fw`, the file /lib/firmware/hda-init.fw must be
present.

The patch module option is specific to each card instance, and you
need to give one file name for each instance, separated by commas.
For example, if you have two cards, one for an on-board analog and one 
for an HDMI video board, you may pass patch option like below:

options snd-hda-intel patch=on-board-patch,hdmi-patch


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

Title:
  [Asus P8P67, Realtek ALC892, playback] Underruns, dropouts or
  crackling sound

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  It's started when I updated Ubuntu to 12.04.
  For a while, the sound is good. Then it turns into a crackling noise. After 
killing pulseaudio and starting it again, the sound is good again for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   3510 F pulseaudio
   /dev/snd/pcmC0D0p:   john   3510 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfb50 irq 68'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 44
 Simple ctrls  : 21
  Date: Mon May 21 23:08:32 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HDA-Intel - HDA Intel PCH, playback] Underruns, dropouts or crackling 
sound
  UpgradeStatus: Upgraded

[Desktop-packages] [Bug 1165653] Re: Firefox html5 video performance

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

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

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

Title:
  Firefox html5 video performance

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  I have been experimenting with youtube videos on html5 technology and
  the same using flash player. I have noticed that html5 videos tend to
  be heavy on my processor with CPU usage shooting upto 70% on html5.
  With flash, however, the usage by fiefox + plugin-container isnt as
  much.

  Also another conclusive proof of more usage is that my computer
  (slightly old) heats up much more in a html5 video compared to a flash
  video.

  This bug is similar to
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/871412 , but
  different in the fact that I observe poor performance only in html5
  videos.

  (Is this issue perhaps because firefox fails to utilize my GPU, a
  nVidia 105M running nouveau driver, while flash does use it? Any how I
  can debug this and add to the report here?)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: firefox 20.0+build1-0ubuntu0.12.10.3
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bha1   2340 F pulseaudio
  BuildID: 20130329030352
  Channel: Unavailable
  Date: Sun Apr  7 10:41:47 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (170 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.4.1.1 dev eth0  proto static 
   10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.4.1.121  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  Plugins:
   Google Talk Plugin Video Accelerator - 
/opt/google/talkplugin/libnpgtpo3dautoplugin.so (google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   IcedTea-Web Plugin (using IcedTea-Web 1.3 (1.3-1ubuntu1.1)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{bb6bc1bb-f824-4702-90cd-35e2fb24f25d}/defaults/preferences/cookiemanagerplus-preferences.js
  Profiles: Profile0 (Default) - LastVersion=20.0/20130329030352 (In use)
  RelatedPackageVersions:
   google-talkplugin 3.17.0.0-1
   icedtea-7-plugin  1.3-1ubuntu1.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: JV50_MV
  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:bvrV1.34:bd09/24/2010:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50_MV:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5738
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  http_proxy: http://127.0.0.1:8080/
  no_proxy: localhost,127.0.0.0/8

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

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


[Desktop-packages] [Bug 1245277] Re: toda hora ta travando

2013-10-27 Thread Adolfo Jayme Barrientos
Thank you for reporting this bug to Ubuntu. Ubuntu 10.10 reached End of Life 
(EOL) on April 10, 2012.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

Please upgrade to a supported version of Ubuntu, such as 12.04 or 13.10,
and re-test. Do feel free to report any other bugs you may find.

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

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

Title:
  toda hora ta travando

Status in “firefox” package in Ubuntu:
  Invalid

Bug description:
  fica travando direto

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  Date: Sun Oct 27 19:04:38 2013
  FirefoxPackages:
   firefox 3.6.10+build1+nobinonly-0ubuntu3
   firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
   firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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


[Desktop-packages] [Bug 1245295] [NEW] shouldn't list logind's "closing" sessions

2013-10-27 Thread Sebastien Bacher
Public bug reported:

Using saucy, users stay marked as logged-in after their logout

Steps:
- start a session
- close it out
- look if the user is marked with ">"

That's because some processes are left around after the session closing
(e.g some indicators), logind keeps listing the session because of those

** Affects: lightdm (Ubuntu)
 Importance: Low
 Assignee: Iain Lane (laney)
 Status: Confirmed

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  shouldn't list logind's "closing" sessions

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Using saucy, users stay marked as logged-in after their logout

  Steps:
  - start a session
  - close it out
  - look if the user is marked with ">"

  That's because some processes are left around after the session
  closing (e.g some indicators), logind keeps listing the session
  because of those

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

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


[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-27 Thread CBrider
I am having similar issues with networking, and sometimes the sound
card, and the video drivers. I also noticed that the time for this
computer to boot, log-out, and log in is significantly (5-10 times)
longer than it was when I was running 13.04. At first I had upgraded
without a re-format. Today I re-installed after a reformat, and so far
there have not been any videa or sound card issues, just the networking
issue.

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

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

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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


[Desktop-packages] [Bug 1174394] Re: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1

2013-10-27 Thread Sebastien Bacher
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

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

Title:
  package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回了错误号 1

Status in “lightdm” package in Ubuntu:
  Invalid

Bug description:
  。

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: lightdm 1.6.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  AptOrdering:
   alltray: Install
   man-db: Configure
   libpam-winbind: Configure
   lightdm: Configure
   alltray: Configure
  Architecture: i386
  Date: Mon Apr 29 23:14:24 2013
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1
  InstallationDate: Installed on 2013-04-25 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   autologin-user=
  MarkForUpload: True
  SourcePackage: lightdm
  Title: package lightdm 1.6.0-0ubuntu2.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回了错误号 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1165289] Re: package lightdm 1.2.3-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1

2013-10-27 Thread Sebastien Bacher
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

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

Title:
  package lightdm 1.2.3-0ubuntu2 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回了错误号 1

Status in “lightdm” package in Ubuntu:
  Invalid

Bug description:
  I don`t kown for more

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39
  Uname: Linux 3.2.0-39-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  Date: Fri Apr  5 20:11:28 2013
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  SourcePackage: lightdm
  Title: package lightdm 1.2.3-0ubuntu2 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回了错误号 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245194] Re: package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1

2013-10-27 Thread Sebastien Bacher
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

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

Title:
  package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: il
  sottoprocesso installato script di post-removal ha restituito lo stato
  di errore 1

Status in “lightdm” package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10

  Everytime lightdm freeze on log-in screen and it doesn't work at all.
  I have to log in command line (ctrl+alt+f1) to reinstall lightdm and next to 
reboot it work.
  But in a week i had to repeat this solution more than 3 times. Dunno what can 
be.
  Another problem is made by the background of log-in screen. I know is the 
same of proper wallpaper but it doesn't work and i see just a purple solid 
backgroud. I admit my guilty in (maybe) a cripted home.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  AptOrdering:
   ubuntu-desktop: Purge
   lightdm-remote-session-uccsconfigure: Purge
   lightdm: Purge
   lightdm-remote-session-freerdp: Purge
  Architecture: amd64
  Date: Sun Oct 27 15:17:31 2013
  DuplicateSignature: package:lightdm:1.8.2-0ubuntu1:il sottoprocesso 
installato script di post-removal ha restituito lo stato di errore 1
  ErrorMessage: il sottoprocesso installato script di post-removal ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2013-10-25 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  Title: package lightdm 1.8.2-0ubuntu1 failed to install/upgrade: il 
sottoprocesso installato script di post-removal ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1195481] Re: [power]: gnome-control-center crashes if indicator-power is not installed in Unity

2013-10-27 Thread Adolfo Jayme Barrientos
** No longer affects: unity (Ubuntu)

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

Title:
  [power]: gnome-control-center crashes if indicator-power is not
  installed in Unity

Status in One Hundred Papercuts:
  Triaged
Status in “gnome-control-center” package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  gnome-control-center's power panel crashes when indicator-power isn't
  installed.

  [ Test case ]

  1. Uninstall indicator-power
  2. Open System Settings and click Power
  3. System Settings crashes

  At 3 it shouldn't crash. If you have indicator-power installed, you
  should see the option to configure whether it shows.

  [ Regression potential ]

  This adds some new code to check if the GSettings schema is installed, since
  that's a reliable way to check for indicator-power's presence, and is what the
  code modifies. It also makes the option appear in DEs other than Unity.

  There's a chance that the GSettings schema-detection work could be wrong. It
  also wouldn't hurt to check non-Unity environments such as a gnome-panel
  session.

  [ Original report ]

  I see that unity recommends indicator-power; let's make it a depends
  instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs 
ext2 overlayfs nls_utf8 isofs pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
parport_pc ppdev rfcomm bnep dm_crypt intel_powerclamp coretemp kvm_intel kvm 
joydev crc32_pclmul ghash_clmulni_intel arc4 cryptd ath9k dm_multipath scsi_dh 
ath9k_common ath9k_hw uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core ath snd_hda_codec_hdmi snd_hda_codec_conexant mac80211 
snd_hda_intel videodev ath3k btusb snd_hda_codec bluetooth cfg80211 snd_hwdep 
snd_pcm psmouse microcode toshiba_acpi toshiba_bluetooth serio_raw 
sparse_keymap snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei soundcore lpc_ich mac_hid lp parport 
btrfs xor zlib_deflate raid6_pq libcrc32c dm_mirror dm_region_hash dm_log 
ums_realtek usb_storage i915 i2c_algo_bit drm_kms_helper drm atl1c ahci libahci 
wmi video
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jun 27 17:42:04 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-14 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130613)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  Signal: 5
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libpower.so
  Title: [power]: gnome-control-center crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.5-0ubuntu1
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3daily13.06.19-0ubuntu1

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

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


[Desktop-packages] [Bug 1229635] Re: Icon name is incorrectly defined in the .desktop file

2013-10-27 Thread Thaddäus Tintenfisch
** Also affects: gtkterm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Icon name is incorrectly defined in the .desktop file

Status in “driconf” package in Ubuntu:
  Confirmed
Status in “gtkorphan” package in Ubuntu:
  Confirmed
Status in “gtkterm” package in Ubuntu:
  New
Status in “xdiagnose” package in Ubuntu:
  Confirmed

Bug description:
  As the title says, the icon name is incorrectly defined in the
  .desktop file.

  The Icon field should have only the icon name (eg. gtkorphan), not a
  path or the icon name with the file extension.

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

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


[Desktop-packages] [Bug 1245199] Re: Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy

2013-10-27 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Unable to set Miscellaneous compatibility options in gnome-control-
  center keyboard in Saucy

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

Bug description:
  In Ubuntu 12.04 I was able to set Miscellaneous compatibility options in 
gnome-control-center keyboard (for example, I use "Shift with numeric keypad 
keys works as in MS Windows"). Here is a list of all missed feautures: 
  * Allow breaking grabs with keyboard actions (warning: security risk)
  * Apple Aluminium Keyboard: emulate PC keys (Print, Scroll Lock, Pause, Num 
Lock)
  * Both Shift-Keys together activate Caps Lock, one Shift-Keys deativates
  * Both Shift-Keys together toggle Caps Lock
  * Both Shift-Keys together toggle ShiftLock
  * Default numeric keypad keys
  * Enable extra typographic characters
  * Numeric keypad keys always enter digits (as in Mac OS)
  * Shift cancels Caps Lock
  * Shift does not cancel Num Lock, chooses 3rd level instead
  * Shift with numeric keypad keys works as in MS Windows
  * Special keys (Ctrl+Alt+) handled in a server
  * Toggle PointerKeys with Shift + NumLock

  In Ubuntu 13.10 I can't set them from gnome-control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 18:38:09 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1245199/+subscriptions

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


[Desktop-packages] [Bug 1195481] Re: [power]: gnome-control-center crashes if indicator-power is not installed in Unity

2013-10-27 Thread Iain Lane
That's nothing to do with this change

** Tags removed: verification-failed

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

Title:
  [power]: gnome-control-center crashes if indicator-power is not
  installed in Unity

Status in One Hundred Papercuts:
  Triaged
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  [ Description ]

  gnome-control-center's power panel crashes when indicator-power isn't
  installed.

  [ Test case ]

  1. Uninstall indicator-power
  2. Open System Settings and click Power
  3. System Settings crashes

  At 3 it shouldn't crash. If you have indicator-power installed, you
  should see the option to configure whether it shows.

  [ Regression potential ]

  This adds some new code to check if the GSettings schema is installed, since
  that's a reliable way to check for indicator-power's presence, and is what the
  code modifies. It also makes the option appear in DEs other than Unity.

  There's a chance that the GSettings schema-detection work could be wrong. It
  also wouldn't hurt to check non-Unity environments such as a gnome-panel
  session.

  [ Original report ]

  I see that unity recommends indicator-power; let's make it a depends
  instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs 
ext2 overlayfs nls_utf8 isofs pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
parport_pc ppdev rfcomm bnep dm_crypt intel_powerclamp coretemp kvm_intel kvm 
joydev crc32_pclmul ghash_clmulni_intel arc4 cryptd ath9k dm_multipath scsi_dh 
ath9k_common ath9k_hw uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core ath snd_hda_codec_hdmi snd_hda_codec_conexant mac80211 
snd_hda_intel videodev ath3k btusb snd_hda_codec bluetooth cfg80211 snd_hwdep 
snd_pcm psmouse microcode toshiba_acpi toshiba_bluetooth serio_raw 
sparse_keymap snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei soundcore lpc_ich mac_hid lp parport 
btrfs xor zlib_deflate raid6_pq libcrc32c dm_mirror dm_region_hash dm_log 
ums_realtek usb_storage i915 i2c_algo_bit drm_kms_helper drm atl1c ahci libahci 
wmi video
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jun 27 17:42:04 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-14 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130613)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  Signal: 5
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libpower.so
  Title: [power]: gnome-control-center crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.5-0ubuntu1
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3daily13.06.19-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-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.

2013-10-27 Thread giannis
In my case shortcut (alt-shift) it does change actual layout language
(English to Greek) but indicator still shows "en" whatever I choose.

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

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

Status in Gnome Settings Daemon:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Invalid
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
  > Shift+Shift
    * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
* lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278)
* Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280)

  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199)
    * Keyboard shortcut for changing keyboard layout does not work on lock 
screen
  (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548)
    * [FFe] indicator-keyboard not working under greeter 
(https://bugs.launchpad.net/unity-greeter/+bug/1228207)
    * Lost ability to remap Caps Lock to Ctrl
  (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/)
   

[Desktop-packages] [Bug 1236601] Re: wrong background color when editing icons on desktop

2013-10-27 Thread Doug McMahon
nautilus doesn't color any rename, it isn't the quite the issue in nautilus as 
the default bg is off-white
may as well dupe the ubuntu-themes bug that has languished for 3.5 months

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

Title:
  wrong background color when editing icons on desktop

Status in Nautilus:
  New
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “nautilus” source package in Saucy:
  Triaged

Bug description:
  When creating or renaming an icon on the desktop, nautilus no longers
  colors the background ellipse white, resulting in text being
  unreadable. See attached screenshot for comparison between Raring and
  Saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-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: Mon Oct  7 17:24:39 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1004x670+867+75'"
  InstallationDate: Installed on 2012-11-13 (328 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago)

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

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


[Desktop-packages] [Bug 689593] Re: 2x100% CPU and memory usage growth when performing partition modifications via udisks

2013-10-27 Thread midenok
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/694060

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

Title:
  2x100% CPU and memory usage growth when performing partition
  modifications via udisks

Status in abstraction for enumerating and managing block devices:
  New
Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed
Status in “usb-creator” package in Ubuntu:
  Confirmed

Bug description:
  When unsetting the bootable flag on a partition using palimpsest, the
  following things happen:

  - udisks-helper-modify-partition and udisks-daemon processes use 100% CPU each
  - udisks-daemon chews about 18MiB of memory each second

  This problem exists regardless of whether the partition is mounted or
  not.

  natty
  gnome-disk-utility 2.32.1-0ubuntu3
  udisks 1.0.2-1

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

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


[Desktop-packages] [Bug 1245200] Re: [HDA-Intel - HDA Intel, playback] No sound at all

2013-10-27 Thread Raymond
Seem BIOS did not setup pin default

no pin complex for speaker.and headphone Jack with no Jack detection

try hda-jack-sense-test to check whether HP really has Jack detection or
not


Node 0x0f [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Master Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Phantom Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0001003f: IN OUT HP EAPD Detect Trigger ImpSense
  EAPD 0x2: EAPD
  Pin Default 0x01214110: [Jack] HP Out at Ext Rear
Conn = 1/8, Color = Green
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=00, enabled=0
  Connection: 1
 0x08

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

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

Bug description:
  No sound on anything whether playing cd/dvd or listening to music /radio 
there's just no sound, 
  i have an  hda-intel ALC260  on a philips freevents  laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2187 F pulseaudio
  CurrentDmesg:
   [  142.597606] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
   [  226.036095] usb 3-1: USB disconnect, device number 2
   [  267.538113] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
  Date: Sun Oct 27 14:54:41 2013
  InstallationDate: Installed on 2013-10-26 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2187 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080013
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: DIXONSXP

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

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


[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-27 Thread Tong Sun
Contrary to Alfredo Pacheco's announce, my Lubuntu 13.10 is a fresh
install from downloaded ISO, after reformatted the HDD partition, yet I
get the same problem: wired & wireless network was not available. That's
why I'm here.

The 1st solution in the thread, killing the NetworkManager process using
"sudo killall NetworkManager" works for me. I think executing: 'nmcli nm
sleep false' would work as well.

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

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

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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


[Desktop-packages] [Bug 1244619] Re: Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1

2013-10-27 Thread Micah Gersten
Ubuntu doesn't use the lightning-extension source anymore, so removing
this task.

** No longer affects: lightning-extension (Ubuntu)

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

Title:
  Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1

Status in Lightning extension:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Confirmed
Status in “thunderbird” package in Gentoo Linux:
  Fix Released
Status in “thunderbird” package in openSUSE:
  Confirmed

Bug description:
  Since the upgrade of Lightning 2.6.0 to Lightning 2.6.1, this
  extension need Thunderbird 24.0.1 but Ubuntu only give Thunderbird
  24.0.0

  
https://blog.mozilla.org/calendar/2013/10/dont-upgrade-to-thunderbird-24-0-1-yet/
  "Update 4: Lightning 2.6.1 is now public. On Linux, it is compatible ONLY 
with Thunderbird 24.0.1, so go ahead and upgrade now."

  A lot of people don't use the Ubuntu package for Lightning  but those
  of Mozilla.

  Ubuntu should give an upgrade to Thunderbird 24.0.1 and Lightning
  2.6.1

  Step:
  1) Silent update of Lightning 2.6.0 to Lightning 2.6.1 on Thunderbird 24.0.0
  2) Open your calendar and see nothing (see screencast)

  A work form it's to downgrade to Lightning 2.6 until waiting Ubuntu upgrade 
to Thunderbird 24.0.1. You could find it here:
  
https://addons.mozilla.org/fr/thunderbird/addon/lightning/versions/?page=1#version-2.6

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 1:24.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  BuildID: 20130913160939
  Date: Fri Oct 25 12:30:44 2013
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MarkForUpload: True
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightning-extension/+bug/1244619/+subscriptions

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


[Desktop-packages] [Bug 1245287] [NEW] upower showing keyboard at 0% charge

2013-10-27 Thread Kevin Krafthefer
Public bug reported:

This bug is new upon upgrading to 13.10; bug did not exist on 13.04,
12.10 or 12.04.

I'm using an apple wireless keyboard. I have replaced the batteries and
confirmed they are fully charged with voltmeter.

Keyboard is working fine but indicator says it's 0% and is red
indicating some problem. Also upower says "keyboard not present";
bluetooth shows keyboards.

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

** Attachment added: "upower --dump"
   https://bugs.launchpad.net/bugs/1245287/+attachment/3893260/+files/upower.txt

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

Title:
  upower showing keyboard at 0% charge

Status in “upower” package in Ubuntu:
  New

Bug description:
  This bug is new upon upgrading to 13.10; bug did not exist on 13.04,
  12.10 or 12.04.

  I'm using an apple wireless keyboard. I have replaced the batteries
  and confirmed they are fully charged with voltmeter.

  Keyboard is working fine but indicator says it's 0% and is red
  indicating some problem. Also upower says "keyboard not present";
  bluetooth shows keyboards.

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

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


[Desktop-packages] [Bug 1088775] Re: gwibber does not refresh Facebook feeds

2013-10-27 Thread Ruben Rocha
There are problems again with gwibber and facebook. The error this time
is that there is no "count" key when receiving the facebook feed:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gwibber/microblog/dispatcher.py", line 
81, in run
message_data = PROTOCOLS[account["service"]].Client(account)(opname, **args)
  File "/usr/share/gwibber/plugins/facebook/__init__.py", line 253, in __call__
return getattr(self, opname)(**args)
  File "/usr/share/gwibber/plugins/facebook/__init__.py", line 268, in receive
return [self._message(post) for post in data["data"]]
  File "/usr/share/gwibber/plugins/facebook/__init__.py", line 224, in _message
m["likes"]["count"] = data["likes"]["count"]
KeyError: 'count'

My solution was to edit the file
/usr/share/gwibber/plugins/facebook/__init__.py and from line 224 to 231
delete any instance of ["count"]. Save file and reboot. The facebook
feed now refreshes and appears in gwibber.

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

Title:
  gwibber does not refresh Facebook feeds

Status in Gwibber:
  Fix Released
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “python-imaging” package in Ubuntu:
  Incomplete
Status in “gwibber” source package in Precise:
  Fix Released
Status in “gwibber” source package in Quantal:
  Fix Released
Status in “python-imaging” source package in Quantal:
  Invalid

Bug description:
  Since around November 28th, Gwibber stopped updating my Facebook
  feeds. First, I tried to delete my facebook account from online
  accounts and than uninstall and reinstall gwibber. Then, I removed
  ubuntu from facebook app settings after doing all of the above. Then I
  checked my proxy settings, and my proxy is on none. When I open
  gwibber, I see feeds that are 12-13 days old and when I try to
  refresh, it does not do anything. I mean it does not even write
  refreshing... at the bottom of the screen. When I check if gwibber-
  service is running correctly I get no mistake in the terminal. I've
  looked a lot around bugs sections in many sites but none of them had
  an answer.

  Steps to verify this SRU:
  [Test Case]
  Ensure gwibber-service has restarted since the update by either a 
logout/login or "killall gwibber-service", then verify there is feed data for 
your facebook account.

  [Regression Potential]
  Regression potential is really low, it simply checks that the dict returned 
has a key, and if it doesn't use an empty value for the result.

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

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


[Desktop-packages] [Bug 1166124] Re: Ubuntu minimum system requirements needs to be updated

2013-10-27 Thread Svetlana Belkin
** Changed in: ubuntu-docs
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu minimum system requirements needs to be updated

Status in Ubuntu Documentation:
  Fix Released
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  The specified minimum system requirements do not represent reality.
  According to 
https://help.ubuntu.com/community/Installation/SystemRequirements Ubuntu 
desktop needs :

  * 700 MHz processor (about Intel Celeron or better)
  * 512 MiB RAM (system memory)
  * 5 GB of hard-drive space (or USB stick, memory card or external drive but 
see LiveCD for an alternative approach)
  * VGA capable of 1024x768 screen resolution

  With the latest technologies introduced by Unity, not only the above
  is illogical but also, diminishes any chance of a good desktop
  experience with Ubuntu.

  Also if we take into consideration the tests that have been form
  https://wiki.ubuntu.com/DemystifyingUnityGraphicsHardwareRequirements
  it is obvious that for at least a bearable experience, a user will
  need :

  * 1000 ΜHz processor (about Intel Celeron or better)
  * 1024 MiB RAM (system memory)
  * 3D Acceleration Capable Videocard with at least 256 MB

  From experience, we all know that it is recommended to have 2048 MiB
  RAM to properly run a day to day Ubuntu.

  A good start should be with minimum 1024 and recommended 2048 MiB RAM.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.18.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr  8 12:55:26 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 943663] Re: [needs-packaging] Request for libreoffice-help-tr Package

2013-10-27 Thread Christopher M. Penalver
** Changed in: libreoffice (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  [needs-packaging] Request for libreoffice-help-tr Package

Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  Turkish help package of  LibreOffice is missing in the repos. [1-
  http://packages.ubuntu.com/oneiric/libreoffice-l10n-tr]

  It will be very nice to have Turkish embed help for LibreOffice. [2-
  https://translations.documentfoundation.org/tr/]

  TDF's (.deb)help packages cannto be installed due to the dependencies
  
[3-http://download.documentfoundation.org/libreoffice/stable/3.5.0/deb/x86/LibO_3.5
  .0_Linux_x86_helppack-deb_tr.tar.gz]

  1-I am using 11.10 Oneric
  2-LibreOffice 3.5
  3- Having Turkish embed help in LibreOffice
  4- Unfortunately l10n package has no tr-help

  Best regards,
  Zeki

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

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


[Desktop-packages] [Bug 1090170] Re: WifiDocs/Driver/Ndiswrapper has wrong info about Network Admin

2013-10-27 Thread Svetlana Belkin
I can't seem to find the refenence.

** Changed in: ubuntu-docs
   Status: In Progress => Incomplete

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

Title:
  WifiDocs/Driver/Ndiswrapper has wrong info about Network Admin

Status in Ubuntu Documentation:
  Incomplete
Status in “gnome-system-tools” package in Ubuntu:
  New
Status in “ndiswrapper” package in Ubuntu:
  New

Bug description:
  WifiDocs/Driver/Ndiswrapper has wrong info about Network Admin

  Check in 
https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper#Configuring_Wireless_Network_Settings
  Networking Admin tool has no tab Connections in witch to open Wireless 
settings and check Enable roaming mode
  Thats couse of bug 570828

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

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


[Desktop-packages] [Bug 1245226] Re: HDMI: audio-video playback too fast

2013-10-27 Thread Daniel Letzeisen
Try this: https://wiki.ubuntu.com/Audio/PositionReporting

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

Title:
  HDMI: audio-video playback too fast

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

Bug description:
  After upgrading to Ubuntu 13.10, selecting HDMI as audio output device
  is broken.

  Audio is played back at high speed. When playing back video clips, the
  video frames are also too fast.

  This is similar to an old bug I reported some time ago,
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 . In that
  case, adding radeon.audio=1 to the kernel command line solved.

  Now, the configuration is unchanged since when Ubuntu 13.04 was
  running

  $cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 
vt.handoff=7

  yet audio is broken.

  Note that, when selecting headphone as audio output device, everything
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 27 18:00:53 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2010-11-07 (1085 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 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/1245226/+subscriptions

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


[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-10-27 Thread John Clark
** Tags added: saucy

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

Title:
  NetworkManager causes orphaned inodes

Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  On shutdown, dhclient isn't getting reaped by NetworkManager, despite being 
kept running through sendsigs so as not to disrupt remote filesystems (and 
their unmounting at shutdown). dhclient may be keeping open files for its lease 
files, which causes issues when unmounting /var/lib, which contains those lease 
files.

  [Development Fix]
  Remove support for connection assumption, which is meant to bring 
NetworkManager up to speed with connections that may have already be up during 
a restart of the daemon. Since we don't actually restart the daemon 
automatically (and instead suggest a restart of the system after upgrade) and 
the advantage is minimal compared to the impact on users of this interacting 
with the shutdown sequence, patch connection assumption out of the NM code and 
just always take down dhclient when NM stops.

  [Stable Fix]
  See above "Development fix".

  [Test Case]
  1) Shut down coputer.
  2) In the shutdown process, perhaps as a post-stop script in 
/etc/init/network-manager, track down open files for the dhclient pid (which 
should be available from /run/sendsigs.omit.d/network-manager.dhclient{6,}.pid)

  [Regression Potential]
  Minimal, only affects bringing NetworkManager up on a restart of the daemon 
(sudo restart network-manager or /etc/init.d/network-manager restart), which 
improves on the speed of this operation and avoid resetting the connection if 
it's already up.

  -

  During system shutdown, NetworkManager neither kills dhclient nor does
  it remove the dhclient pid file from the directory
  /var/run/sendsigs.omit.d.  As a result, dhclient continues to hold the
  pid file open for write and when /etc/init.d/umountroot tries to
  remount the root filesystem read-only, the remount fails.  The
  message:

  mount: / is busy

  is seen in the console, and the filesystem must be recovered at boot
  time:

  [8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
  [8.947057] EXT4-fs (sda1): write access will be enabled during recovery
  [   11.234075] EXT4-fs (sda1): recovery complete

  If shared libraries used by dhclient are updated before the reboot,
  orphaned inodes associated with the .so files are created.  For
  example, doing "sudo apt-get install --reinstall libc6" and then
  rebooting leads to:

  [8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
  [8.356521] EXT4-fs (sda1): write access will be enabled during recovery
  [8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
  [8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced 
inode 313749
  [8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced 
inode 313733
  [8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced 
inode 313725
  [8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
  [8.728544] EXT4-fs (sda1): recovery complete

  This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  running under 12.04.   I don't believe any actual data loss will occur
  as a result of this bug, but it's likely to produce much user anxiety.
  Also see Bug 952315, which misidentifies the cause of the problems as
  upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic i686
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Mar 23 07:42:20 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)

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

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


[Desktop-packages] [Bug 1245286] Re: package shared-mime-info 1.1-0ubuntu2 [modified: usr/bin/update-mime-database.real] failed to install/upgrade: subprocess installed post-installation script return

2013-10-27 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.1-0ubuntu2 [modified: usr/bin/update-mime-
  database.real] failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 139

Status in “shared-mime-info” package in Ubuntu:
  New

Bug description:
  this came up on the automatic update

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Sun Oct 27 17:02:04 2013
  DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]:subprocess installed post-installation 
script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-07-04 (115 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MarkForUpload: True
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real] failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1245286/+subscriptions

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


[Desktop-packages] [Bug 1245286] [NEW] package shared-mime-info 1.1-0ubuntu2 [modified: usr/bin/update-mime-database.real] failed to install/upgrade: subprocess installed post-installation script retu

2013-10-27 Thread zehyani
Public bug reported:

this came up on the automatic update

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
Date: Sun Oct 27 17:02:04 2013
DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]:subprocess installed post-installation 
script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2013-07-04 (115 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real] failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package raring

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

Title:
  package shared-mime-info 1.1-0ubuntu2 [modified: usr/bin/update-mime-
  database.real] failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 139

Status in “shared-mime-info” package in Ubuntu:
  New

Bug description:
  this came up on the automatic update

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Sun Oct 27 17:02:04 2013
  DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real]:subprocess installed post-installation 
script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-07-04 (115 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MarkForUpload: True
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.1-0ubuntu2 [modified: 
usr/bin/update-mime-database.real] failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1245286/+subscriptions

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


[Desktop-packages] [Bug 1243339] Re: lightdm no longer runs guest session through wrapper

2013-10-27 Thread Robert Ancell
I have the guest wrapper working in lp:~robert-ancell/lightdm/guest-
wrapper but Unity fails to start. Perhaps the AppArmor rule need
updating too...

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

Title:
  lightdm no longer runs guest session through wrapper

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “lightdm” source package in Saucy:
  Confirmed
Status in “lightdm” source package in Trusty:
  Confirmed

Bug description:
  Till 13.04 guest couldn't access home directory. In 13.10 guests can
  read the files in the /home-directory. Not sure if it is a problem of
  lightdm or AppArmor.

  Problem is the same on update from raring and fresh install of saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  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: Tue Oct 22 19:51:27 2013
  InstallationDate: Installed on 2011-10-27 (726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

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

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


[Desktop-packages] [Bug 1243339] Re: lightdm no longer runs guest session through wrapper

2013-10-27 Thread Launchpad Bug Tracker
** Branch linked: lp:~robert-ancell/lightdm/guest-wrapper

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

Title:
  lightdm no longer runs guest session through wrapper

Status in Light Display Manager:
  In Progress
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “lightdm” source package in Saucy:
  Confirmed
Status in “lightdm” source package in Trusty:
  Confirmed

Bug description:
  Till 13.04 guest couldn't access home directory. In 13.10 guests can
  read the files in the /home-directory. Not sure if it is a problem of
  lightdm or AppArmor.

  Problem is the same on update from raring and fresh install of saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  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: Tue Oct 22 19:51:27 2013
  InstallationDate: Installed on 2011-10-27 (726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

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

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


[Desktop-packages] [Bug 1245214] Re: Cannot manually arrange (drag and drop) url desktop launchers after upgrade from ubuntu 13.04 to 13.10

2013-10-27 Thread Wayne Perry
Don't know if this matters but the file type of the "offenders" is HTML
document (text/html). The "non offenders" have different and varied file
types.

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

Title:
  Cannot manually arrange (drag and drop) url desktop launchers after
  upgrade from ubuntu 13.04 to 13.10

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  I cannot manually arrange (drag and drop) url desktop launchers after
  upgrade from ubuntu 13.04 to 13.10.  I get error message (Error while
  copying "/") with details (Error opening file "/": is a directory).
  Keep aligned is turned off.  This only happens when trying to
  reposition url related launchers.  Some of the launchers were created
  by using Firefox "Create Deskcut" and some with the older Nautilus
  "Create-Launcher" script.

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

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


[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-27 Thread Id2ndR
After resuming, I got this bug. I tried $ sudo service networking
restart => it crashed compiz. Apparently it seems to kill dbus but I
don't know why. Am I the only one in this case ?

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

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

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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


[Desktop-packages] [Bug 1205384] Re: Lock can be circumvented by switching to console

2013-10-27 Thread amjjawad
In my case:

Lubuntu 13.10 amd64

Menu > Logout > Lock Screen

ctrl+alt+F1

ctrl+alt+F7

Result: session is unlocked without entering a password

-- 
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 LXDE - Lightweight X11 Desktop Environment:
  New
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “lxsession” package in Ubuntu:
  In Progress

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/lxde/+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 1205384] Re: Lock can be circumvented by switching to console

2013-10-27 Thread amjjawad
This bug affects me too!

-- 
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 LXDE - Lightweight X11 Desktop Environment:
  New
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “lxsession” package in Ubuntu:
  In Progress

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/lxde/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2013-10-27 Thread Norbert
So for today we have:
* Super+Space and Shift+Super+Space does not work at all;
* Alt+Shift works in Unity and GNOME, but does not work in unity-greeter and 
gnome-screensaver,
* Ctrl+Shift works in Unity and GNOME, but does not work in unity-greeter and 
gnome-screensaver,
* Shift+Shift may be set only with packages from ppa:attente/1218322, works in 
Unity and GNOME, but does not work in unity-greeter and gnome-screensaver.

I reported many separate bug reports, which belong to keyboard layout 
switching. They need confirmation.
I hope that all of them will be fixed soon and we get Ubuntu 14.04 LTS most 
functional and usable as Ubuntu 12.04.3 LTS now.

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

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

Status in Gnome Settings Daemon:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Invalid
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
  > Shift+Shift
    * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
* lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278)
* Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280)

  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-contro

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

2013-10-27 Thread Norbert
With latest packages from ppa:attente/1218322 (gnome-control-center
3.6.3-0ubuntu45ppa1, gnome-control-center-data 3.6.3-0ubuntu45ppa1,
libgnome-control-center1 3.6.3-0ubuntu45ppa1) I can set Shift+Shift for
keyboard layout switching, they are usable in GNOME and Unity sessions,
but Shift+Shift does not work on lock screen - gnome-screensaver
(https://bugs.launchpad.net/ubuntu/+source/gnome-
screensaver/+bug/1245278) and in Unity greeter
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280).

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

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

Status in Gnome Settings Daemon:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Invalid
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
  > Shift+Shift
    * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
* lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278)
* Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280)

  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199)
    * Keyboard shortcut for changing ke

[Desktop-packages] [Bug 1222718] Re: Using fglrx, chromium tabs not displaying titles

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

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

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

Title:
  Using fglrx, chromium tabs not displaying titles

Status in Chromium Browser:
  Unknown
Status in AMD fglrx video driver:
  New
Status in “chromium-browser” package in Ubuntu:
  Incomplete
Status in “fglrx-installer” package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My problem is that Chrome/Chromium (have both installed) are not displaying 
page titles rendering many pages.
  Actually, because of bug of keybindings in Gnome 3.9 I can't create 
screenshot, but with most pages I have favicon displayed and not any text like 
page title.

  It doesn't matter if GPU rendering is enabled or disabled.

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

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


[Desktop-packages] [Bug 1245278] Vacation reply

2013-10-27 Thread mikael hammarlind
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1245278

Title:
  Shift+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Shift+Shift hotkey for keyboard layout change does not work in GNOME 
screensaver of Ubuntu 13.10.
  This hotkey combination is set with packages from ppa:attente/1218322.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:15:08 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245280] [NEW] Shift+Shift hotkey for keyboard layout switching does not work unity-greeter in Saucy

2013-10-27 Thread Norbert
Public bug reported:

Shift+Shift hotkey for keyboard layout change does not work in unity-greeter of 
Ubuntu 13.10.
This hotkey combination is set with packages from ppa:attente/1218322.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Mon Oct 28 01:19:24 2013
InstallationDate: Installed on 2013-10-20 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
SourcePackage: unity-greeter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 saucy third-party-packages

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

Title:
   Shift+Shift hotkey for keyboard layout switching does not work unity-
  greeter in Saucy

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

Bug description:
  Shift+Shift hotkey for keyboard layout change does not work in unity-greeter 
of Ubuntu 13.10.
  This hotkey combination is set with packages from ppa:attente/1218322.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:19:24 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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.

2013-10-27 Thread Norbert
** Description changed:

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:
  
  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade
  
  === gnome-control-center ===
  
  Impact: the UI to change the layout switching keys doesn't work
  
  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys
  
  Regression potential: that UI was not working before, it should only be
  an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)
  
  === gnome-settings-daemon ===
  
  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work
  
  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change
  
  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.
  
  --
  
  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
  > Shift+Shift
-   * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
-  
-  
+   * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
+   * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278)
+   * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280)
  
  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199)
    * Keyboard shortcut for changing keyboard layout does not work on lock 
screen
  (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548)
    * [FFe] indicator-keyboard not working under greeter 
(https://bugs.launchpad.net/unity-greeter/+bug/1228207)
    * Lost ability to remap Caps Lock to Ctrl
  (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/)
    * gnome-control-center keyboard no longer has way to modify caps lock 
key behavior 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224575)
  
  --
  
  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 Au

[Desktop-packages] [Bug 990486] Re: onboard not shown in taskbar

2013-10-27 Thread marmuta
Yes, confirmed, the "GNOME Flashback" session uses compiz now. The fix was only 
for metacity. You can get the old behavior back when you start Onboard like 
this:
$ onboard -q metacity

I'm not sure yet if we can makes this more permanent. In the short time
I tested, I couldn't get the keyboard to become stuck invisible anymore,
but there is still the animation delay for minimizing/restoring. Also,
in order to be visible in the task-bar, force-top-top must be disabled,
which triggers new bug #1242625, where the keyboard resizes every time
it shows up. I have no workaround for this.

If you'd like to help, try running Onboard like above for some days and
report back on your experiences. If there aren't any other issues,
perhaps we can add a special quirks mode for only the GNOME Flashback
session.

** Changed in: onboard (Ubuntu)
   Status: New => Incomplete

** Changed in: onboard (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  onboard not shown in taskbar

Status in Onboard on-screen keyboard:
  Fix Released
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  Onboard (the on-screen keyboard) is not shown in taskbar in Gnome
  Classic anymore after upgrading to Precise Pangolin. When onboard is
  minimized, it disappears completely and can't be restored.

  It is possible to have the separate onboard icon that will then first
  hide onboard and bring it back, but I consider this as a workaround,
  not a fix.

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

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


[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-27 Thread Jean Marc
Same problems here after suspend.

I use "sudo nmcli nm sleep false" to restore the connection, "sudo
reboot" to reboot, "sudo shutdown -h now" to shutdown and "sudo pm-
suspend" to suspend.

Regards.

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

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

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

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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


[Desktop-packages] [Bug 1245278] [NEW] Shift+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy

2013-10-27 Thread Norbert
Public bug reported:

Shift+Shift hotkey for keyboard layout change does not work in GNOME 
screensaver of Ubuntu 13.10.
This hotkey combination is set with packages from ppa:attente/1218322.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-screensaver 3.6.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Mon Oct 28 01:15:08 2013
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 300
 org.gnome.desktop.session session-name 'ubuntu'
InstallationDate: Installed on 2013-10-20 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 saucy

** Description changed:

- Shift+Shift hotkey for keyboard layout change does not work in GNOME
- screensaver of Ubuntu 13.10.
+ Shift+Shift hotkey for keyboard layout change does not work in GNOME 
screensaver of Ubuntu 13.10.
+ This hotkey combination is set with packages from ppa:attente/1218322.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:15:08 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
-  org.gnome.desktop.session idle-delay uint32 300
-  org.gnome.desktop.session session-name 'ubuntu'
+  org.gnome.desktop.session idle-delay uint32 300
+  org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Shift+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Shift+Shift hotkey for keyboard layout change does not work in GNOME 
screensaver of Ubuntu 13.10.
  This hotkey combination is set with packages from ppa:attente/1218322.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 01:15:08 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245270] Re: Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy

2013-10-27 Thread Norbert
Installed packages from ppa:attente/1218322
(
gnome-control-center 3.6.3-0ubuntu45ppa1
gnome-control-center-data 3.6.3-0ubuntu45ppa1
libgnome-control-center1 3.6.3-0ubuntu45ppa1
)
bug still here.

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

Title:
  Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Ctrl+Shift hotkey for keyboard layout change does not work in GNOME
  screensaver of Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:15:19 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245268] Re: Ctrl+Shift hotkey for keyboard layout switching does not work unity-greeter in Saucy

2013-10-27 Thread Norbert
Installed packages from ppa:attente/1218322
(
gnome-control-center 3.6.3-0ubuntu45ppa1
gnome-control-center-data 3.6.3-0ubuntu45ppa1
libgnome-control-center1 3.6.3-0ubuntu45ppa1
)
bug still here.

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

Title:
  Ctrl+Shift hotkey for keyboard layout switching does not work unity-
  greeter in Saucy

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

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Ctrl+Shift
  keyboard layout change hotkey does not work in in Unity greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:10:19 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245268/+subscriptions

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


[Desktop-packages] [Bug 1245272] Re: Can't set keyboard layout change to Shift+Shift

2013-10-27 Thread Norbert
Installed packages from ppa:attente/1218322
(
gnome-control-center 3.6.3-0ubuntu45ppa1
gnome-control-center-data 3.6.3-0ubuntu45ppa1
libgnome-control-center1 3.6.3-0ubuntu45ppa1
)
Now I can set Shift+Shift (indicates as Shift+Shift R) and use them.

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

Title:
  Can't set keyboard layout change to Shift+Shift

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

Bug description:
  In Ubuntu 12.04 I was able to set keyboard layout switching shortcut to 
Shift+Shift.
  In Ubuntu 13.10 I can't set it from gnome-control-center keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:32:03 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1245272/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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.

2013-10-27 Thread Jean Marc
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262

This bug seems to be also a duplicate of bug 1242679 :
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1242679

Regards

-- 
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 1245188] Re: Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy

2013-10-27 Thread Norbert
I confirm this in non fall-back too.

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

Title:
  Unable to set keyboard LED to show alternative layout in gnome-
  control-center keyboard in Saucy

Status in GNOME Control Center:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04 I was able to set keyboard LED to show alternative layout in 
gnome-control-center keyboard (Caps Lock, Num Lock or Scroll Lock). 
  In Ubuntu 13.10 I can't set it from gnome-control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 17:11:41 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/gnome-control-center/+bug/1245188/+subscriptions

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


[Desktop-packages] [Bug 1245258] Re: Alt+Shift hotkey for keyboard layout switching do not work unity-greeter in Saucy

2013-10-27 Thread Norbert
Installed packages from ppa:attente/1218322
(
gnome-control-center 3.6.3-0ubuntu45ppa1
gnome-control-center-data 3.6.3-0ubuntu45ppa1
libgnome-control-center1 3.6.3-0ubuntu45ppa1
)
bug still here.

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

Title:
  Alt+Shift hotkey for keyboard layout switching do not work unity-
  greeter in Saucy

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

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Alt+Shift
  keyboard layout change hotkey does not work in in Unity greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 23:18:32 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  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/1245258/+subscriptions

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


[Desktop-packages] [Bug 1242679] Re: network manager unconfigured after wake from suspend

2013-10-27 Thread Jean Marc
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262

This bug seems to be also a duplicate of bug 1234469 :
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469

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

Title:
  network manager unconfigured after wake from suspend

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

Bug description:
  I started a thread on this bug
  http://ubuntuforums.org/showthread.php?t=2182128

  After I upgraded to 13.10 when the desktop suspends and then wakes the 
networks are unconfigured.
  The led lights come on on the builtin nic card, but no networking, the empty 
triangle shows.

  run this command  sudo nmcli nm sleep false
  I get a message that says network now offline.

  Then you click the network icon and you see all the network cards
  Then tell it to enable networking, by selecting 'Auto Ethernet'
  And it comes back working as it should.

  So is the network-manager not awakening from sleep?

  The nics are intel and the drivers are e100 and e1000

  scott875@scott875-desktop:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.8.0-0ubuntu22
Candidate: 0.9.8.0-0ubuntu22
Version table:
   *** 0.9.8.0-0ubuntu22 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  scott875@scott875-desktop:~$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10
  scott875@scott875-desktop:~$

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

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


[Desktop-packages] [Bug 1245256] Re: Alt+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy

2013-10-27 Thread Norbert
Installed packages from ppa:attente/1218322
(
gnome-control-center 3.6.3-0ubuntu45ppa1
gnome-control-center-data 3.6.3-0ubuntu45ppa1
libgnome-control-center1 3.6.3-0ubuntu45ppa1
)
bug still here.

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

Title:
  Alt+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Alt+Shift hotkey for keyboard layout change  does not work in GNOME
  screensaver of Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 23:07:25 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1245277] [NEW] toda hora ta travando

2013-10-27 Thread everton fontynelli oks
Public bug reported:

fica travando direto

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Sun Oct 27 19:04:38 2013
FirefoxPackages:
 firefox 3.6.10+build1+nobinonly-0ubuntu3
 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox

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


** Tags: amd64 apport-bug maverick

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

Title:
  toda hora ta travando

Status in “firefox” package in Ubuntu:
  New

Bug description:
  fica travando direto

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  Date: Sun Oct 27 19:04:38 2013
  FirefoxPackages:
   firefox 3.6.10+build1+nobinonly-0ubuntu3
   firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
   firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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


[Desktop-packages] [Bug 1200876] Re: Brasero Hangs at Normalizing Tracks when burning audio CD comprising of Mp3 and Ogg files

2013-10-27 Thread Francisco Reverbel
Same thing here, I ran into this bug when attempting to burn an audio
CD. I also had only MP3 files in the list of files to burn.

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

Title:
  Brasero Hangs at Normalizing Tracks when burning audio CD comprising
  of Mp3 and Ogg files

Status in “brasero” package in Ubuntu:
  Confirmed

Bug description:
  I wanted to create a CD, Audio CD with brasero and added few MP3 and Ogg 
files and commanded it to burn.
  Then it hanged at Normalizing tracks for hours and hours. I have read about 
normalizing plugin that it should be disabled but that is not a choice for now 
as files are coming from idfferent sources and they **should** be normalized in 
this case. So help!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: brasero 3.6.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Sat Jul 13 11:58:51 2013
  InstallationDate: Installed on 2013-04-29 (74 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1231588] Re: Firefox windows don't accept focus

2013-10-27 Thread Carlos Eduardo Moreira dos Santos
If I use a new firefox profile, it works as expected. The old profile
still has focus issues.

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

Title:
  Firefox windows don't accept focus

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  I have found in the last day or so that Firefox windows do not accept
  focus when they are clicked upon. The focus (and key and mouse events)
  are still sent to a different window even after it has been selected
  for the foreground by click or ALT+TAB,ALT+`.

  Initially I experienced this on a dual-head display, but even when the
  window is moved from the external monitor to the built-in laptop
  monitor, events are routed to the wrong firefox window.

  This issue has survived an apt-get upgrade and a reboot, and is still
  occurring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 24.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cefn   4062 F pulseaudio
  BuildID: 20130917154333
  Channel: Unavailable
  Date: Thu Sep 26 18:07:55 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-15 (42 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 
(20130626)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.23  metric 
9
  MarkForUpload: True
  Plugins:
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   Java(TM) Plug-in 10.40.2 - 
/usr/lib/jvm/java-7-oracle/jre/lib/i386/libnpjp2.so
   Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
   Silverlight Plug-In - /usr/lib/pipelight/libpipelight.so (pipelight)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources:
   prefs.js
   
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=24.0/20130917154333 (In use)
  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.
  RelatedPackageVersions:
   gnome-shell   3.8.4-0ubuntu5
   pipelight 0.1-4-0~ubuntu13.10.1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.50
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.50:bd10/23/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R600
  dmi.product.version: PPR61E-00Q00CEN
  dmi.sys.vendor: TOSHIBA

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

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


[Desktop-packages] [Bug 1245010] Re: HPLIP crashes missing libnetsnmp.so.15

2013-10-27 Thread Jan Ott
Kubuntu 13.10, AMD64: 
I am affected by a similar problem since upgrade from raring. All command line 
programs provided by hplip do not start, e.g. hp-setup:

Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 45, in 
from base import device, utils, tui, models, module, services, os_utils
  File "/usr/share/hplip/base/device.py", line 42, in 
import status
  File "/usr/share/hplip/base/status.py", line 59, in 
import hpmudext
ImportError: libnetsnmp.so.15: cannot open shared object file: No such file or 
directory

Moreover, my HP LaserJet 400 MFP M425dn does not print any longer since
upgrade from raring.

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

Title:
  HPLIP crashes missing libnetsnmp.so.15

Status in “hplip” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10, HPLIP 3.13.9 with simple-scan and xsane

  HPLIP crashes when started with diagnostic "ImportError in
  /usr/share/hplip/base/status.py:libnetsnmp.so.15: cannot open shared
  object file: No such file or directory".

  I have tried to remove and reinstall in Ubuntu Software Center but
  that did not make any difference.

  I have tried to dwonload HPLIP 3.13.10, but the download did not
  start.

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

-- 
Mailing list: https://launchpad.net/~desktop-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.

2013-10-27 Thread Norbert
Gnome-control-center from proposed updates does not allow to set
Shift+Shift for layout switching
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1245272).

** Description changed:

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:
  
  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade
  
  === gnome-control-center ===
  
  Impact: the UI to change the layout switching keys doesn't work
  
  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys
  
  Regression potential: that UI was not working before, it should only be
  an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)
  
  === gnome-settings-daemon ===
  
  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work
  
  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change
  
  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.
  
  --
  
  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
+ > Shift+Shift
+   * Can't set keyboard layout change to Shift+Shift 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272)
+  
+  
  
  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199)
    * Keyboard shortcut for changing keyboard layout does not work on lock 
screen
  (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548)
-   * [FFe] indicator-keyboard not working under greeter 
(https://bugs.launchpad.net/unity-greeter/+bug/1228207)
+   * [FFe] indicator-keyboard not working under greeter 
(https://bugs.launchpad.net/unity-greeter/+bug/1228207)
    * Lost ability to remap Caps Lock to Ctrl
  (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/)
    * gnome-control-center keyboard no longer has way to modify caps lock 
key behavior 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224575)
  
  --
  
  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 20

[Desktop-packages] [Bug 1245270] Vacation reply

2013-10-27 Thread mikael hammarlind
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1245270

Title:
  Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-
  screensaver in Saucy

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

Bug description:
  Ctrl+Shift hotkey for keyboard layout change does not work in GNOME
  screensaver of Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:15:19 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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.

2013-10-27 Thread Norbert
** Description changed:

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:
  
  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade
  
  === gnome-control-center ===
  
  Impact: the UI to change the layout switching keys doesn't work
  
  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys
  
  Regression potential: that UI was not working before, it should only be
  an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)
  
  === gnome-settings-daemon ===
  
  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work
  
  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change
  
  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.
  
  --
  
  Separate bug reports for individual layout switching hotkey combinations:
  > Super+Space and Shift+Super+Space, found in:
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137);
    * Unity session 
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136);
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138);
    * ubiquity installer 
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572).
  > Alt+Shift
    * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256)
    * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258)
  > Ctrl+Shift
-   * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
-   * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
+   * lock screen - gnome-screensaver 
(https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270)
+   * Unity greeter 
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268)
  
  Bugs which belong to keyboard layout switching:
    * Hotkeys not functional in non-latin keyboard layout in 13.10 
(https://bugs.launchpad.net/unity/+bug/1226962)
    * Keyboard Layout Options window is missed in gnome-control-center 
keyboard
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064)
    * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188)
    * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199)
    * Keyboard shortcut for changing keyboard layout does not work on lock 
screen
  (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548)
+   * [FFe] indicator-keyboard not working under greeter 
(https://bugs.launchpad.net/unity-greeter/+bug/1228207)
    * Lost ability to remap Caps Lock to Ctrl
  (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/)
    * gnome-control-center keyboard no longer has way to modify caps lock 
key behavior 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224575)
  
  --
  
  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=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash

[Desktop-packages] [Bug 1228207] Re: [FFe] indicator-keyboard not working under greeter

2013-10-27 Thread Norbert
It seems, that unity-greeter in Ubuntu 13.10 do not react on keyboard
layout change hotkeys - Super+Space and Shift+Super+Space
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137),
Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1245258) and Ctrl+Shift
(https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268).
I have proposed updates enabled.

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

Title:
  [FFe] indicator-keyboard not working under greeter

Status in Unity Greeter:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released

Bug description:
  Rationale:

  This cycle we introduced a new keyboard indicator which runs in the
  session, but does not currently run in unity-greeter without the
  proposed bug fix.

  The reason we should be using the new indicator is because the method
  of storing the user's keyboard layouts has been changed this cycle,
  and the new indicator already reads those settings from their proper
  location. Continued use of the old indicator would require the user to
  maintain two separate keyboard layout lists.

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

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


[Desktop-packages] [Bug 943663] Re: [needs-packaging] Request for libreoffice-help-tr Package

2013-10-27 Thread Kobzeci
Hi Björn,

As libreoffice-help-tr package is now served, this bug is fixed.

Thanks.
Zeki

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

Title:
  [needs-packaging] Request for libreoffice-help-tr Package

Status in “libreoffice” package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  Turkish help package of  LibreOffice is missing in the repos. [1-
  http://packages.ubuntu.com/oneiric/libreoffice-l10n-tr]

  It will be very nice to have Turkish embed help for LibreOffice. [2-
  https://translations.documentfoundation.org/tr/]

  TDF's (.deb)help packages cannto be installed due to the dependencies
  
[3-http://download.documentfoundation.org/libreoffice/stable/3.5.0/deb/x86/LibO_3.5
  .0_Linux_x86_helppack-deb_tr.tar.gz]

  1-I am using 11.10 Oneric
  2-LibreOffice 3.5
  3- Having Turkish embed help in LibreOffice
  4- Unfortunately l10n package has no tr-help

  Best regards,
  Zeki

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

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


  1   2   3   4   >