[Desktop-packages] [Bug 1275198] Re: [HP EliteBook 8560w, IDT 92HD81B1X5, Speaker, Internal] No sound at all

2014-02-04 Thread Raymond
how did you upgrade ?

seem fail to open card 1 device 0

(   0.038|   0.000) I: [pulseaudio] (alsa-lib)pcm_hw.c: open
'/dev/snd/pcmC1D0p' failed (-2)

post output of alsa-info.sh

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

Title:
  [HP EliteBook 8560w, IDT 92HD81B1X5, Speaker, Internal] No sound at
  all

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

Bug description:
  After an update a few weeks ago the internal speakers on my laptop
  stopped working.  Audio from headphones works fine.  Tried upgrading
  version of Ubuntu but still won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1933 F pulseaudio
   /dev/snd/controlC0:  user   1933 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1933 F...m pulseaudio
  Date: Fri Jan 31 23:25:21 2014
  InstallationDate: Installed on 2012-01-10 (752 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1933 F pulseaudio
   /dev/snd/controlC0:  user   1933 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1933 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 8560w, IDT 92HD81B1X5, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to saucy on 2014-02-01 (0 days ago)
  dmi.bios.date: 05/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.02
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.02:bd05/10/2011:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.33:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-01-31T23:12:02.568169

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

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


[Desktop-packages] [Bug 1275960] Re: [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd

2014-02-04 Thread Raymond
http://voices.canonical.com/david.henningsson/2012/07/13/top-five-wrong-
ways-to-fix-your-audio/

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

Title:
  [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error:
  command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1',
  '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p',
  '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
  '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p',
  '/dev/snd/seq', '/dev/snd/timer'] failed with exit

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  Having trouble getting sound to work in ubuntu (saucy) unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  Uname: Linux 3.8.11 x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Mon Feb  3 17:16:59 2014
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [Peppy, Realtek ALC283, Speaker, Internal] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: coreboot
  dmi.bios.version: Google_Peppy.4389.81.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvncoreboot:bvrGoogle_Peppy.4389.81.0:bd10/29/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1276041] Re: HDMI output number doubled

2014-02-04 Thread Raymond
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_hdmi.c?id=75fae117a5dbde5ab984fa5c60705758cfbc6433


http://mailman.alsa-project.org/pipermail/alsa-
devel/2014-February/072017.html

your Nvidia GPU 16 is in the list


Codec: Nvidia GPU 16 HDMI/DP
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x10de0016
Subsystem Id: 0x10de0101


** Package changed: pulseaudio (Ubuntu) = alsa-driver (Ubuntu)

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

Title:
  HDMI output number doubled

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

Bug description:
  I have GTX560Ti with only one HDMI output but KDE settings show two
  HDMI outputs + two HDMI 5.1 outputs. Only one of them works.

  Additional info: https://bugs.kde.org/show_bug.cgi?id=330713

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  i  2090 F pulseaudio
   /dev/snd/pcmC1D7p:   i  2090 F...m pulseaudio
   /dev/snd/controlC0:  i  2090 F pulseaudio
  Date: Tue Feb  4 10:25:34 2014
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD53 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/02/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD53(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI

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

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


[Desktop-packages] [Bug 1276041] [NEW] HDMI output number doubled

2014-02-04 Thread Serhiy Zahoriya
Public bug reported:

I have GTX560Ti with only one HDMI output but KDE settings show two HDMI
outputs + two HDMI 5.1 outputs. Only one of them works.

Additional info: https://bugs.kde.org/show_bug.cgi?id=330713

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: pulseaudio 1:4.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  i  2090 F pulseaudio
 /dev/snd/pcmC1D7p:   i  2090 F...m pulseaudio
 /dev/snd/controlC0:  i  2090 F pulseaudio
Date: Tue Feb  4 10:25:34 2014
MarkForUpload: True
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P67A-GD53 (MS-7681)
dmi.board.vendor: MSI
dmi.board.version: 1.0/2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0/2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/02/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD53(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
dmi.product.name: MS-7681
dmi.product.version: 1.0/2.0
dmi.sys.vendor: MSI

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


** Tags: apport-bug i386 saucy

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

Title:
  HDMI output number doubled

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  I have GTX560Ti with only one HDMI output but KDE settings show two
  HDMI outputs + two HDMI 5.1 outputs. Only one of them works.

  Additional info: https://bugs.kde.org/show_bug.cgi?id=330713

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  i  2090 F pulseaudio
   /dev/snd/pcmC1D7p:   i  2090 F...m pulseaudio
   /dev/snd/controlC0:  i  2090 F pulseaudio
  Date: Tue Feb  4 10:25:34 2014
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD53 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/02/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD53(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI

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

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


[Desktop-packages] [Bug 1275960] Re: [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd

2014-02-04 Thread Raymond
it is  strange that the devices belong to hwaudio

you have to ask the ubuntu audio dev team

!!ALSA Device nodes
!!-

crw-rw 1 root hwaudio 116,  6 Feb  3 16:54 /dev/snd/controlC0
crw-rw 1 root hwaudio 116, 11 Feb  3 16:54 /dev/snd/controlC1
crw-rw 1 root hwaudio 116,  5 Feb  3 16:54 /dev/snd/hwC0D0
crw-rw 1 root hwaudio 116, 10 Feb  3 16:54 /dev/snd/hwC1D0
crw-rw 1 root hwaudio 116,  4 Feb  3 16:54 /dev/snd/pcmC0D3p
crw-rw 1 root hwaudio 116,  3 Feb  3 16:54 /dev/snd/pcmC0D7p
crw-rw 1 root hwaudio 116,  2 Feb  3 16:54 /dev/snd/pcmC0D8p
crw-rw 1 root hwaudio 116,  9 Feb  3 17:16 /dev/snd/pcmC1D0c
crw-rw 1 root hwaudio 116,  8 Feb  3 17:15 /dev/snd/pcmC1D0p
crw-rw 1 root hwaudio 116,  7 Feb  3 16:54 /dev/snd/pcmC1D2c
crw--- 1 root root116,  1 Feb  3 16:54 /dev/snd/seq
crw-rw 1 root hwaudio 116, 33 Feb  3 16:54 /dev/snd/timer


** Summary changed:

- [Peppy, Realtek ALC283, Speaker, Internal] Pulseaudio fails to detect card
+ [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error: command 
['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit

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

Title:
  [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error:
  command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1',
  '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p',
  '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
  '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p',
  '/dev/snd/seq', '/dev/snd/timer'] failed with exit

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  Having trouble getting sound to work in ubuntu (saucy) unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  Uname: Linux 3.8.11 x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Mon Feb  3 17:16:59 2014
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [Peppy, Realtek ALC283, Speaker, Internal] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: coreboot
  dmi.bios.version: Google_Peppy.4389.81.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvncoreboot:bvrGoogle_Peppy.4389.81.0:bd10/29/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 224458] Re: Implement GTK+ RGBA colormap to give the window an alpha value

2014-02-04 Thread Bug Watch Updater
** Changed in: gtk
   Status: Fix Released = Confirmed

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

Title:
  Implement GTK+ RGBA colormap to give the window an alpha value

Status in GTK+ GUI Toolkit:
  Confirmed
Status in LibGTK - GIMP Toolkit set of widgets for X:
  Invalid
Status in “gtk+2.0” package in Ubuntu:
  Triaged

Bug description:
  Please support this project and provide a patch for GTK+ ...

  Using RGBA colormaps will give the window an alpha value, useful to draw 
fancy things, from transparent widgets till rounded menus/tooltips.
  
http://www.cimitan.com/blog/2008/02/17/rgba-colormap-by-default-in-gtk-call-for 
-a-coder/

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

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


[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-04 Thread Dimitri John Ledkov
lightdm should also clear console on pre-stopping.

** Changed in: lightdm (Ubuntu)
   Status: Fix Released = Triaged

** Changed in: lightdm (Ubuntu)
 Assignee: Brian Murray (brian-murray) = Dimitri John Ledkov (xnox)

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

** Changed in: upstart (Ubuntu)
   Status: New = Triaged

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

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) = Dimitri John Ledkov (xnox)

** Also affects: upstart (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: plymouth (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Precise)
   Status: New = Triaged

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: plymouth (Ubuntu Precise)
   Status: New = Triaged

** Changed in: plymouth (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: upstart (Ubuntu Precise)
   Status: New = Triaged

** Changed in: upstart (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: plymouth (Ubuntu Precise)
 Assignee: (unassigned) = Dimitri John Ledkov (xnox)

** Changed in: lightdm (Ubuntu Precise)
 Assignee: (unassigned) = Dimitri John Ledkov (xnox)

** Changed in: upstart (Ubuntu Precise)
 Assignee: (unassigned) = Dimitri John Ledkov (xnox)

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

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “plymouth” source package in Precise:
  Triaged
Status in “upstart” source package in Precise:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  

[Desktop-packages] [Bug 1275990] Re: [gm45] GPU lockup IPEHR: 0x02000004 - on youtube

2014-02-04 Thread Chris Wilson
*** This bug is a duplicate of bug 1273246 ***
https://bugs.launchpad.net/bugs/1273246

** This bug has been marked a duplicate of bug 1273246
   [gen4] gpu hang due to batch overflow

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

Title:
  [gm45] GPU lockup  IPEHR: 0x0204 - on youtube

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

Bug description:
  Happened twice, both on youtube within Firefox (v26):
  ubuntu gnome 14.04 alpha 2 + updates running gnome-shell
  1) Video starts playing, I clicked to change the playing position - crash
  2) Video finished playing, I clicked on a related video in the side bar (not 
inside the player)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Chipset: gm45
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  3 14:09:06 2014
  DistUpgraded: 2014-01-30 16:33:04,253 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: [gm45] GPU lockup  IPEHR: 0x0204 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20e4]
 Subsystem: Lenovo Device [17aa:20e4]
  InstallationDate: Installed on 2013-07-22 (196 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130626)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2774A29
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=9f5d933d-b1d3-4500-acb2-446ef8fc699e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [gm45] GPU lockup  IPEHR: 0x0204
  UpgradeStatus: Upgraded to trusty on 2014-01-31 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6EET52WW (3.12 )
  dmi.board.name: 2774A29
  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:bvr6EET52WW(3.12):bd08/10/2010:svnLENOVO:pn2774A29:pvrThinkPadX301:rvnLENOVO:rn2774A29:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2774A29
  dmi.product.version: ThinkPad X301
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
10.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Feb  3 14:51:29 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module vesa (module does not exist, 0)
   Failed to load module fbdev (module does not exist, 0)
   Failed to load module vesa (module does not exist, 0)
   Failed to load module fbdev (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16500 
   vendor LEN
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 1276072] [NEW] Language selection always falls back to English

2014-02-04 Thread A. Scheuer
Public bug reported:

I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that 
the language is set to English (whereas I selected French language at the 
beginning of the upgrade).
Moreover, each time I set it back to French, dragging both French (France and 
Canada) and some English (UK  US) on top of the default English in the 
language selection list, default English comes back on top at next login.

I even tried to modify my .pam_environment (in console mode) and the
/etc/environment to set fr_FR as the default, no way: gnome-language-
selector seems to force default English as default at each connection!

Hopefully, I do understand English, but this is turning me mad.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: language-selector-gnome 0.116
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Feb  4 10:48:33 2014
InstallationDate: Installed on 2013-07-29 (190 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: language-selector
UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago)

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

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

Title:
  Language selection always falls back to English

Status in “language-selector” package in Ubuntu:
  New

Bug description:
  I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both 
that the language is set to English (whereas I selected French language at the 
beginning of the upgrade).
  Moreover, each time I set it back to French, dragging both French (France and 
Canada) and some English (UK  US) on top of the default English in the 
language selection list, default English comes back on top at next login.

  I even tried to modify my .pam_environment (in console mode) and the
  /etc/environment to set fr_FR as the default, no way: gnome-language-
  selector seems to force default English as default at each connection!

  Hopefully, I do understand English, but this is turning me mad.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.116
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Feb  4 10:48:33 2014
  InstallationDate: Installed on 2013-07-29 (190 days ago)
  InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions

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


[Desktop-packages] [Bug 1169143] Re: Headset support on some Dell machines

2014-02-04 Thread David Henningsson
** Changed in: hwe-next
   Status: In Progress = Fix Released

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

Title:
  Headset support on some Dell machines

Status in HWE Next Project:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Won't Fix
Status in “pulseaudio” package in Ubuntu:
  Fix Released
Status in “pulseaudio” source package in Precise:
  Fix Released
Status in “pulseaudio” source package in Raring:
  Won't Fix

Bug description:
  [SRU Justification]
  Several new hardware has either headset jacks or headphone-or-mic jacks, 
where the system cannot detect what has been plugged in. E g, for such a 
headset jack you can either plug in a headphone or a headset, but since the 
system cannot tell which one it is, you have to manually tell the system 
whether you want to use the internal or external mic.
  In the case of a headphone-or-mic jack, you can have the jack functioning as 
either a headphone or a mic, but not as a headset.

  Without this patch, PulseAudio would not detect the jack correctly,
  and not making all options available to the user.

  [Regression Potential] is very low: this only affects machines with
  the specific name Headphone Mic Jack or Headset Mic Jack, which
  started to appear for a few machines in the 3.5 kernel. People who are
  running 12.04.0 or 12.04.1 will be unaffected. More machines are
  coming in the 3.10 kernel, so this is also a preparation for making
  certification easier later on.

  [Test case] On an affected machine, plug in something into the jack.
  Then go to Sound Settings and note what options there are: e g, for
  a headset jack, you should be able to select both external and
  internal mic manually.

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

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


[Desktop-packages] [Bug 1188571] Re: The list of printers should be searchable/sortable

2014-02-04 Thread Ritesh Khadgaray
patch against gtk2, based off upstream

** Patch added: proposed patch for precise
   
https://bugs.launchpad.net/gtk/+bug/1188571/+attachment/3968502/+files/gtk2.debdiff

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

Title:
  The list of printers should be searchable/sortable

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  With the current GTK dialog (as in 3.6.4).

  Users, working on a lan with many printers, report that it's difficult for 
them
  to find the printer they want to use because GTK provide no way to
  search/filter/sort the list of printers.

  Typeahead is working, but it's not really obvious (so some users don't know
  about it) and only works on the printer names, not on their location.

  Some possible improvements:
  - providing a way to search/filter in the list, taking into account names and
  locations
  - make the columns sortable, that would allow users to, at least, sort by
  location
  - sort the most used printers always first

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

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


[Desktop-packages] [Bug 1188571] Re: The list of printers should be searchable/sortable

2014-02-04 Thread Ritesh Khadgaray
** Patch added: proposed patch for precise against gtk3
   
https://bugs.launchpad.net/gtk/+bug/1188571/+attachment/3968504/+files/gtk3.debdiff

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

Title:
  The list of printers should be searchable/sortable

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  With the current GTK dialog (as in 3.6.4).

  Users, working on a lan with many printers, report that it's difficult for 
them
  to find the printer they want to use because GTK provide no way to
  search/filter/sort the list of printers.

  Typeahead is working, but it's not really obvious (so some users don't know
  about it) and only works on the printer names, not on their location.

  Some possible improvements:
  - providing a way to search/filter in the list, taking into account names and
  locations
  - make the columns sortable, that would allow users to, at least, sort by
  location
  - sort the most used printers always first

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

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


[Desktop-packages] [Bug 1188571] Re: The list of printers should be searchable/sortable

2014-02-04 Thread Ritesh Khadgaray
patch against gtk3

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

Title:
  The list of printers should be searchable/sortable

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  With the current GTK dialog (as in 3.6.4).

  Users, working on a lan with many printers, report that it's difficult for 
them
  to find the printer they want to use because GTK provide no way to
  search/filter/sort the list of printers.

  Typeahead is working, but it's not really obvious (so some users don't know
  about it) and only works on the printer names, not on their location.

  Some possible improvements:
  - providing a way to search/filter in the list, taking into account names and
  locations
  - make the columns sortable, that would allow users to, at least, sort by
  location
  - sort the most used printers always first

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

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


[Desktop-packages] [Bug 1021517] Re: Xorg-server crashes reproducible with GIMP usage

2014-02-04 Thread Peter Belz
I have lenovo l700 with Ubuntu 12.04 and I temporarily fixed this
problem. Gimp crashes everytime when my 'touchpad-indicator' app is
working. It works just fine if I turn the app off and optionally disable
touchpad using cmd 'synclient TouchpadOff=1'.

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

Title:
  Xorg-server crashes reproducible with GIMP usage

Status in The GNU Image Manipulation Program (GIMP):
  Invalid
Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in X.Org X server:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  Fatal X server crash when using GIMP, which is a regression caused by recent 
xserver SRU changes.

  [Test Case]
  Steps to reproduce:

  step1: open Gimp in Ubuntu
  step2: create new image
  step3: choosing tool (e.g. pencil)
  step4: applying pencil to image
  step5: crash (login window appears)

  [Stable Fix]
  For now, simply revert the patches added in versions 2:1.11.4-0ubuntu10.2 and 
.3.

  [Regression Discussion]
  The 10.2 SRU was intended to fix a touchpad issue on certain macbooks.  10.3 
attempted to fix a regression caused by 10.2, but caused this bug.  Reverting 
these changes should bring us back to a less crashy xserver.

  This will regress the touchpad on macbooks, but the scope and severity
  of that bug are much less than the X server crashes being seen.
  Macbook users suffering from that issue have the option to run an
  earlier xserver version until a better tested fix becomes available.

  [Original Report]
  Here's the GIMP output:
  gimp: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
  (script-fu:3569): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

  Here is the xorg-server backtrace(see comment #35):

  in XorgLogOld.txt:

  [ 51063.179] (II) intel(0): Modeline 1366x768x0.0 69.30 1366 1414 1446 1454 
768 771 777 793 -hsync -vsync (47.7 kHz)
  [ 51072.829]
  Backtrace:
  [ 51072.829] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f99d5fa4996]
  [ 51072.829] 1: /usr/bin/X (0x7f99d5e1c000+0x18c83a) [0x7f99d5fa883a]
  [ 51072.829] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f99d5142000+0xfcb0) 
[0x7f99d5151cb0]
  [ 51072.829] 3: /usr/bin/X (0x7f99d5e1c000+0x5e71a) [0x7f99d5e7a71a]
  [ 51072.829] 4: /usr/bin/X (0x7f99d5e1c000+0x58070) [0x7f99d5e74070]
  [ 51072.829] 5: /usr/bin/X (0x7f99d5e1c000+0x1230ef) [0x7f99d5f3f0ef]
  [ 51072.829] 6: /usr/bin/X (0x7f99d5e1c000+0x4e8b1) [0x7f99d5e6a8b1]
  [ 51072.829] 7: /usr/bin/X (0x7f99d5e1c000+0x3d6da) [0x7f99d5e596da]
  [ 51072.829] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7f99d3fd776d]
  [ 51072.829] 9: /usr/bin/X (0x7f99d5e1c000+0x3d9d1) [0x7f99d5e599d1]
  [ 51072.829] Segmentation fault at address 0x28
  [ 51072.829]
  Caught signal 11 (Segmentation fault). Server aborting
  [ 51072.829]
  Please consult the The X.Org Foundation support
    at http://wiki.x.org
   for help.
  [ 51072.829] Please also check the log file at /var/log/Xorg.0.log for 
additional information.
  [ 51072.829]
  [ 51072.832] (II) evdev: Power Button: Close
  [ 51072.832] (II) UnloadModule: evdev

  In kernel.log:

  Jul 8 12:55:49 foobar gnome-session[2111]: Gdk-WARNING: gnome-session: Fatal 
IO error 11 (Resource temporarily unavailable) on X server :0.#012
  Jul 8 12:55:49 foobar acpid: client 1221[0:0] has disconnected
  Jul 8 12:55:49 foobar acpid: client connected from 12308[0:0]
  Jul 8 12:55:49 foobar acpid: 1 client rule loaded

  Am using GNU/Linux Ubuntu 12.04 amd64 with kernel 3.2.0-26
  ---
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  Package: gimp 2.6.12-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Tags:  precise
  Uname: Linux 3.2.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  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]
  CompositorRunning: compiz
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  

[Desktop-packages] [Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)

2014-02-04 Thread Stefan Hengelein
the Bug seems to persist on saucy (13.10) but i don't have a blinking
numlock.

furthermore, it seems like the goa-daemon comsumes 90-100% on a cpu for
every user that is logged in, therefore locking a cpu per user that is
logged in.


$ dpkg -l | grep gnome-settings-daemon
ii  gnome-settings-daemon  3.8.5-0ubuntu11.2
 amd64daemon handling the GNOME session settings
$ uname -a
Linux faui49y 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux


afaik, this didn't happen on 13.04.

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

Title:
  [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking
  numlock)

Status in Gnome Settings Daemon:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” source package in Precise:
  Fix Released
Status in “gnome-settings-daemon” source package in Quantal:
  Fix Released
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  Impact:
  gnome-settings-daemon uses 100% cpu for ever in some cases

  Test Case:
  Seems to happen sometimes after docking or connecting with vnc, try to 
connect to the machine using a vnc client a few times and check there is no 
numlock cycle and cpu usage loop starting

  Regression potential:
  The numlock state could be wrongly set,restored on login in some cases

  -

  Original message:
  -

  I don't know how to reproduce this bug, but after varying amounts of
  normal usage of my laptop, I notice gnome-settings-daemon is consuming
  100% (approx) CPU.

  I am not sure how to restart gnome-settings-daemon, I tried opening a
  terminal and running gnome-settings-daemon again but this crashes my
  system - my external monitor switches off and my laptop locks up. I am
  able to reboot with SysRq+REISUB.

  Sorry I cannot provide more information - it happens twice now, maybe
  someone can tell me how to get more information for the next time this
  happens.

  $ lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  $ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
    Installed: 3.4.0-0ubuntu2
    Candidate: 3.4.0-0ubuntu2
    Version table:
   *** 3.4.0-0ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 17:16:02 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1275540] Re: Problems with likes

2014-02-04 Thread Kai Mast
Oh I found the following in my log:

  raise FriendsError(message or str(error))
friends.errors.FriendsError: [{'message': 'You have already favorited this 
status.', 'code': 139}]

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

Title:
  Problems with likes

Status in “friends” package in Ubuntu:
  New

Bug description:
  The displayed like count is often wrong.  E.g. friends show 2 people
  like this when in fact 15 like it.

  Also when I try to like a post I sometimes get the following error:
  ** (process:27031): CRITICAL **: file 
/build/buildd/libfriends-0.1.2+14.04.20131108.1/src/dispatcher.vala: line 146: 
uncaught error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not 
receive a reply (timeout by message bus) (g-dbus-error-quark, 4)

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

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


[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-04 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/trusty-proposed/lightdm

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

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “plymouth” source package in Precise:
  Triaged
Status in “upstart” source package in Precise:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 1276085] [NEW] Update to 0.9.26

2014-02-04 Thread Robert Ancell
Public bug reported:

Update to 0.9.26

** Affects: harfbuzz (Ubuntu)
 Importance: Wishlist
 Assignee: Sebastien Bacher (seb128)
 Status: Triaged


** Tags: upgrade-software-version

** Changed in: harfbuzz (Ubuntu)
   Importance: Undecided = Wishlist

** Changed in: harfbuzz (Ubuntu)
   Status: New = Triaged

** Changed in: harfbuzz (Ubuntu)
 Assignee: (unassigned) = Sebastien Bacher (seb128)

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

Title:
  Update to 0.9.26

Status in “harfbuzz” package in Ubuntu:
  Triaged

Bug description:
  Update to 0.9.26

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

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


[Desktop-packages] [Bug 1276082] [NEW] Update to 0.9.8.8

2014-02-04 Thread Robert Ancell
Public bug reported:

Update to 0.9.8.8

** Affects: network-manager-applet (Ubuntu)
 Importance: Wishlist
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
 Status: Triaged


** Tags: upgrade-software-version

** Changed in: network-manager-applet (Ubuntu)
   Status: New = Triaged

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided = Wishlist

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  Update to 0.9.8.8

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

Bug description:
  Update to 0.9.8.8

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

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


[Desktop-packages] [Bug 1276087] [NEW] Update to 3.10.1

2014-02-04 Thread Robert Ancell
Public bug reported:

Update to 3.10.1

** Affects: gnome-session (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version

** Changed in: gnome-session (Ubuntu)
   Status: New = Triaged

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  Update to 3.10.1

Status in “gnome-session” package in Ubuntu:
  Triaged

Bug description:
  Update to 3.10.1

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

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


[Desktop-packages] [Bug 1276087] Re: Update to 3.10.1

2014-02-04 Thread Robert Ancell
We are currently stuck on an unstable 3.9 release since 3.10 contains
changes that drop something we need (?)

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

Title:
  Update to 3.10.1

Status in “gnome-session” package in Ubuntu:
  Triaged

Bug description:
  Update to 3.10.1

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

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


[Desktop-packages] [Bug 1276089] [NEW] Update to 0.9.8.8

2014-02-04 Thread Robert Ancell
Public bug reported:

Update to 0.9.8.8

** Affects: network-manager-applet (Ubuntu)
 Importance: Wishlist
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
 Status: Triaged


** Tags: upgrade-software-version

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

Title:
  Update to 0.9.8.8

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

Bug description:
  Update to 0.9.8.8

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

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


[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-04 Thread Dimitri John Ledkov
** Changed in: lightdm (Ubuntu)
   Status: Triaged = Fix Committed

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

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

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Fix Committed
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  In Progress
Status in “lightdm” source package in Precise:
  Triaged
Status in “plymouth” source package in Precise:
  Triaged
Status in “upstart” source package in Precise:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-04 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/lightdm

** Branch linked: lp:~xnox/lightdm/archive-upload

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

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “plymouth” source package in Precise:
  Triaged
Status in “upstart” source package in Precise:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 1276095] [NEW] Update to 2.39.4

2014-02-04 Thread Robert Ancell
Public bug reported:

Update to 2.39.4

** Affects: glib2.0 (Ubuntu)
 Importance: Wishlist
 Assignee: Iain Lane (laney)
 Status: Triaged


** Tags: upgrade-software-version

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

Title:
  Update to 2.39.4

Status in “glib2.0” package in Ubuntu:
  Triaged

Bug description:
  Update to 2.39.4

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

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

2014-02-04 Thread William Hua
Hi, were any of the packages from the PPA superceded? If you do 'apt-
cache policy compiz unity gnome-settings-daemon', do you have the same
versions as from https://launchpad.net/~attente/+archive/modifier-only-
input-switch?

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

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

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

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

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

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

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

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

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

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

  === compiz ===

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

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

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

  === unity ===

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

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

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

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 1245256);
     * ubiquity installer (bug 1242572).

  Alt+Shift:
     * Unity greeter (bug 1245258)
     * Can't set keyboard layout change to Alt+Shift (bug 1245926)
 * Shift must be pressed pressed first (bug 1266179)

  Ctrl+Shift:
     * lock screen - 

[Desktop-packages] [Bug 1272859] Re: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()

2014-02-04 Thread Robert Ancell
** Information type changed from Private to Public

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

Title:
  unity-greeter crashed with signal 5 in
  atspi_dbus_connection_setup_with_g_main()

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

Bug description:
  This happened when I logged into Ubuntu14.04 Alpha1 after upgrading
  from 13.10, it caused some of the display to blank for a time but
  seemed to recover after a few seconds.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-greeter 14.04.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Jan 26 08:18:36 2014
  ExecutablePath: /usr/sbin/unity-greeter
  InstallationDate: Installed on 2013-09-27 (120 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  ProcCmdline: /usr/sbin/unity-greeter
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: unity-greeter
  StacktraceTop:
   atspi_dbus_connection_setup_with_g_main () from 
/usr/lib/x86_64-linux-gnu/libatspi.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: unity-greeter crashed with signal 5 in 
atspi_dbus_connection_setup_with_g_main()
  UpgradeStatus: Upgraded to trusty on 2013-12-17 (39 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1273989] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

2014-02-04 Thread Robert Ancell
** Information type changed from Private to Public

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  I run Ubuntu Studio 14.04 in Virtualbox on a Macbook. Every time I log
  in I get this error about the keyboard.

  lsb_release -rd:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  apt-cache policy ibus:
  ibus:
Installed: 1.5.4-1ubuntu1
Candidate: 1.5.4-1ubuntu1
Version table:
   *** 1.5.4-1ubuntu1 0
  500 http://se.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.4-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.4-lowlatency 3.11.3
  Uname: Linux 3.11.0-11-lowlatency x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jan 29 09:03:18 2014
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2014-01-07 (21 days ago)
  InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha amd64 (20131212)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1268482] Re: software-center crashed with ValueError in _strptime(): time data '2011-11-24T15:02:15.514Z' does not match format '%Y-%m-%d %H:%M:%S'

2014-02-04 Thread Robert Ancell
** Information type changed from Private to Public

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

Title:
  software-center crashed with ValueError in _strptime(): time data
  '2011-11-24T15:02:15.514Z' does not match format '%Y-%m-%d %H:%M:%S'

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

Bug description:
  Opened the software center, searched for VRML and bam. Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.10-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Jan 12 22:58:08 2014
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2012-01-06 (738 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  PythonArgs: ['/usr/bin/software-center']
  SourcePackage: software-center
  Title: software-center crashed with ValueError in _strptime(): time data 
'2011-11-24T15:02:15.514Z' does not match format '%Y-%m-%d %H:%M:%S'
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (81 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare 
vboxusers

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

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

2014-02-04 Thread Dmitry Pashkevich
@William I wasn't using your PPA, Alt+Shift for layout switching used to
work for me, supposedly from the official repos. But I'll check when I
get to my 13.10 machine

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

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

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

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

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

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

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

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

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

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

  === compiz ===

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

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

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

  === unity ===

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

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

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

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 1245256);
     * ubiquity installer (bug 1242572).

  Alt+Shift:
     * Unity greeter (bug 1245258)
     * Can't set keyboard layout change to Alt+Shift (bug 1245926)
 * Shift must be pressed pressed first (bug 1266179)

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
  

[Desktop-packages] [Bug 1272561] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_unix64()

2014-02-04 Thread Robert Ancell
*** This bug is a duplicate of bug 1232419 ***
https://bugs.launchpad.net/bugs/1232419

** This bug is no longer a duplicate of bug 1272029
   [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
notify_have_shell()
** This bug has been marked a duplicate of bug 1232419
   [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
notify_have_shell()

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  ffi_call_unix64()

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

Bug description:
  crashes at boot

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-settings-daemon 3.8.6.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 21 21:37:54 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2013-12-27 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131227)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f06e84f57f7:mov(%rax),%rdi
   PC (0x7f06e84f57f7) ok
   source (%rax) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1154561] Re: software-center crashed with /home/username/Downloads/virtualbox-4.2_4.2.8-83876~Ubuntu~quantal_amd64.deb in _run_transaction()

2014-02-04 Thread Robert Ancell
** Information type changed from Private to Public

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

Title:
  software-center crashed with
  /home/username/Downloads/virtualbox-4.2_4.2.8-83876~Ubuntu~quantal_amd64.deb
  in _run_transaction()

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

Bug description:
  I was trying to install the .deb file downloaded from VirtualBox
  website. The software center gave me an error or two and crashed!

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 13.04
  Package: software-center 5.5.4
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Wed Mar 13 17:38:21 2013
  DuplicateSignature: software-center:trans-failed:error-unreadable-package-file
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2013-02-28 (13 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130209)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center 
/home/username/Downloads/virtualbox-4.2_4.2.8-83876~Ubuntu~quantal_amd64.deb
  SourcePackage: software-center
  Title: software-center crashed with  
/home/username/Downloads/virtualbox-4.2_4.2.8-83876~Ubuntu~quantal_amd64.deb in 
_run_transaction()
  Traceback:
   Traceback (most recent call last):
 File 
/usr/share/software-center/softwarecenter/backend/installbackend_impl/aptd.py,
 line 990, in _run_transaction
   yield trans.run(defer=True)
   TransactionFailed: Transaction failed: Package file could not be opened
/home/username/Downloads/virtualbox-4.2_4.2.8-83876~Ubuntu~quantal_amd64.deb
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1272029] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

2014-02-04 Thread Robert Ancell
*** This bug is a duplicate of bug 1232419 ***
https://bugs.launchpad.net/bugs/1232419

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1232419
   [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
notify_have_shell()

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  notify_have_shell()

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

Bug description:
  I just booted.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Jan 23 20:19:30 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2014-01-22 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f0e152da7f7:mov(%rax),%rdi
   PC (0x7f0e152da7f7) ok
   source (%rax) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1273808] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_unix64()

2014-02-04 Thread Robert Ancell
*** This bug is a duplicate of bug 1232419 ***
https://bugs.launchpad.net/bugs/1232419

** This bug is no longer a duplicate of bug 1272029
   [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
notify_have_shell()
** This bug has been marked a duplicate of bug 1232419
   [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
notify_have_shell()

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  ffi_call_unix64()

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

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-settings-daemon 3.8.6.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 28 19:57:29 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2014-01-28 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131219)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f9abe35c7f7:mov(%rax),%rdi
   PC (0x7f9abe35c7f7) ok
   source (%rax) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1271710] Re: doesn't list compiz/unity keybindings

2014-02-04 Thread Sebastien Bacher
** Package changed: unity-control-center (Ubuntu) = compiz (Ubuntu)

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

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

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

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

** Changed in: compiz (Ubuntu)
   Status: New = Fix Committed

** Changed in: compiz (Ubuntu)
   Importance: Undecided = Low

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Low

** Changed in: unity-control-center (Ubuntu)
   Status: New = Invalid

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

Title:
  doesn't list compiz/unity keybindings

Status in “compiz” package in Ubuntu:
  Fix Committed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Invalid

Bug description:
  The unity-control-center keybinding dialog doesn't list things like
  the HUD control (seems like other sections are missing as well). Could
  it be that it's not looking in the right directory for those? (or do
  we need to migrate things shipping a custom .xml to install those in a
  new location?)

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

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

2014-02-04 Thread Sebastien Bacher
** Tags added: ubuntu-desktop-trusty

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

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

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

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

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

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

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

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

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

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

  === compiz ===

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

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

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

  === unity ===

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

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

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

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 1245256);
     * ubiquity installer (bug 1242572).

  Alt+Shift:
     * Unity greeter (bug 1245258)
     * Can't set keyboard layout change to Alt+Shift (bug 1245926)
 * Shift must be pressed pressed first (bug 1266179)

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
     * Can't set keyboard layout change to Ctrl+Shift (bug 1245991)
     * If keyboard layout switching hotkey is set to Ctrl+Shift, 

[Desktop-packages] [Bug 1203357] [NEW] Additional user(s) that log out of a any session still show as being logged in

2014-02-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Test case:
Create a new user
Log out, log in to new user 

Log out from new user, log back in to orig user
New user will still be shown as logged in in the session indicator even though 
they aren't

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: indicator-session 12.10.5+13.10.20130717-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sat Jul 20 14:33:09 2013
InstallationDate: Installed on 2013-07-13 (6 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130712)
MarkForUpload: True
SourcePackage: indicator-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-session
 Importance: Undecided
 Assignee: Charles Kerr (charlesk)
 Status: New

** Affects: indicator-sound
 Importance: Undecided
 Status: New

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

** Affects: indicator-session (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug saucy third-party-packages
-- 
Additional user(s) that log out of a any session still show as being logged in
https://bugs.launchpad.net/bugs/1203357
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity-greeter in Ubuntu.

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


[Desktop-packages] [Bug 1276098] [NEW] Sound: Background tints around listboxes and sliders

2014-02-04 Thread Matthew Paul Thomas
Public bug reported:

gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10

1. Open the Sound panel.
2. Flip through the tabs and look at the listboxes and sliders.

What you see: the background is tinted darker than the rest of the tab
(a) above all listboxes
(b) to the right of the Play sound through listbox
(c) to the right of the Record sound from listbox
(d) behind all sliders.

What you should see: The background color in these areas is the same as
the rest of the tab.

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

** Affects: unity-control-center (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: ubuntu-desktop-trusty

** Attachment added: screenshot with contrast increased to highlight the 
problem
   
https://bugs.launchpad.net/bugs/1276098/+attachment/3968544/+files/system-settings-sound.gif

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10
  
  1. Open the Sound panel.
  2. Flip through the tabs and look at the listboxes and sliders.
  
  What you see: the background is tinted darker than the rest of the tab
  (a) above all listboxes
  (b) to the right of the Play sound through listbox
  (c) to the right of the Record sound from listbox
  (d) behind all sliders.
+ 
+ What you should see: The background color in these areas is the same as
+ the rest of the tab.

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

Title:
  Sound: Background tints around listboxes and sliders

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

Bug description:
  gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10

  1. Open the Sound panel.
  2. Flip through the tabs and look at the listboxes and sliders.

  What you see: the background is tinted darker than the rest of the tab
  (a) above all listboxes
  (b) to the right of the Play sound through listbox
  (c) to the right of the Record sound from listbox
  (d) behind all sliders.

  What you should see: The background color in these areas is the same
  as the rest of the tab.

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

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


[Desktop-packages] [Bug 1266465] [NEW] Cannot set static background in 13.10

2014-02-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Steps to reproduce:

 * Open dconf editor
 * Set background to '/usr/share/backgrounds/somebackground.jpg' (file is 
root:root)
 * Set draw-user-backgrounds to false (unticked)
 * Close
 * Set desktop (user) background to inaccessible.jpg (file that cannot be read 
by lightdm)
 * Restart machine

What should happen:

Greeter loads. Greeter background is somebackground.jpg - does not
change if different user is selected, does not change if user background
is changed.

What happens instead:

Greeter loads. Greeter background is warty-final-ubuntu.png (default).

Notes:

Could be related to these reports attempting the same from the command
line? http://askubuntu.com/questions/379965/lightdm-unity-greeter-
wallpaper-will-not-set and http://askubuntu.com/questions/381479/how-to-
change-login-screen-background-on-13-10

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


** Tags: background static
-- 
Cannot set static background in 13.10
https://bugs.launchpad.net/bugs/1266465
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity-greeter in Ubuntu.

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


[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-04 Thread Launchpad Bug Tracker
This bug was fixed in the package lightdm - 1.9.6-0ubuntu2

---
lightdm (1.9.6-0ubuntu2) trusty; urgency=medium

  * Clear default tty on lightdm shutdown, to avoid brief display of text
messages on shutdown. (LP: #967229)
 -- Dimitri John Ledkov x...@ubuntu.com   Tue, 04 Feb 2014 10:12:05 +

** Changed in: lightdm (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  In Progress
Status in “lightdm” source package in Precise:
  Triaged
Status in “plymouth” source package in Precise:
  Triaged
Status in “upstart” source package in Precise:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 1249781] Re: System reboots and shutdown even if someone is logged in

2014-02-04 Thread Sebastien Bacher
** Tags added: ubuntu-desktop-trusty

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

Title:
  System reboots and shutdown even if someone is logged in

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

Bug description:
  The system can be rebooted from login screen even if another user is logged 
in, this could cause that user to loose changes to open files or cause some 
other kind of damage.
  How to reproduce:
  1) Log in to your account
  2) Lock screen (CTR+ALT+L)
  3) Move the mouse to show password prompt
  4) Click Switch User - it takes you to lightdm login prompt
  5) Click restart in the power menu (upper right corner)
  What should happen: lightdm would demand that all users log out before 
rebooting
  What happens: system reboots

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 10 15:10:58 2013
  InstallationDate: Installed on 2013-05-17 (176 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (14 days ago)

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

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


[Desktop-packages] [Bug 1271953] Re: Num Lock is not actived in lightdm, even if it is actived in the bios

2014-02-04 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu)

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

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

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

Title:
  Num Lock is not actived in lightdm, even if it is actived in the bios

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

Bug description:
  Num Lock is not actived in lightdm, even if it is actived in the bios.

  After login, Num Lock is actived.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 23 16:33:42 2014
  InstallationDate: Installed on 2014-01-09 (13 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1255558] Re: Can't type my password after cold boot

2014-02-04 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu)

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

** Tags added: ubuntu-desktop-trusty

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

Title:
  Can't type my password after cold boot

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

Bug description:
  Can't type my password after cold boot unless I change my keyboard
  layout to next (or change and then re-change to same layout)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1
  Uname: Linux 3.12.0-4-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Wed Nov 27 16:27:13 2013
  InstallationDate: Installed on 2013-11-19 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131119)
  SourcePackage: lightdm
  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/128/+subscriptions

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Sebastien Bacher
** Tags added: ubuntu-desktop-trusty

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in Unity Greeter:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1261818] Re: Can't type user password in lightdm

2014-02-04 Thread Robert Ancell
*** This bug is a duplicate of bug 128 ***
https://bugs.launchpad.net/bugs/128

** This bug has been marked a duplicate of bug 128
   Can't type my password after cold boot

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

Title:
  Can't type user password in lightdm

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

Bug description:
  If I want to log in to Ubuntu in lightdm I can't type a password in
  the box.

  This is if you boot and you want to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 17 17:08:41 2013
  InstallationDate: Installed on 2013-12-16 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131216)
  SourcePackage: lightdm
  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/1261818/+subscriptions

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


[Desktop-packages] [Bug 1276098] Re: Sound: Background tints around listboxes and sliders

2014-02-04 Thread Sebastien Bacher
** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Low

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

** Tags added: ubuntu-desktop-trusty

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

Title:
  Sound: Background tints around listboxes and sliders

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

Bug description:
  gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10

  1. Open the Sound panel.
  2. Flip through the tabs and look at the listboxes and sliders.

  What you see: the background is tinted darker than the rest of the tab
  (a) above all listboxes
  (b) to the right of the Play sound through listbox
  (c) to the right of the Record sound from listbox
  (d) behind all sliders.

  What you should see: The background color in these areas is the same
  as the rest of the tab.

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

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


[Desktop-packages] [Bug 1249781] Re: System reboots and shutdown even if someone is logged in

2014-02-04 Thread Robert Ancell
** Changed in: unity-greeter (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  System reboots and shutdown even if someone is logged in

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

Bug description:
  The system can be rebooted from login screen even if another user is logged 
in, this could cause that user to loose changes to open files or cause some 
other kind of damage.
  How to reproduce:
  1) Log in to your account
  2) Lock screen (CTR+ALT+L)
  3) Move the mouse to show password prompt
  4) Click Switch User - it takes you to lightdm login prompt
  5) Click restart in the power menu (upper right corner)
  What should happen: lightdm would demand that all users log out before 
rebooting
  What happens: system reboots

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 10 15:10:58 2013
  InstallationDate: Installed on 2013-05-17 (176 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (14 days ago)

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

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


[Desktop-packages] [Bug 1271953] Re: Num Lock is not actived in lightdm, even if it is actived in the bios

2014-02-04 Thread Sebastien Bacher
** Tags added: ubuntu-desktop-trusty

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

Title:
  Num Lock is not actived in lightdm, even if it is actived in the bios

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

Bug description:
  Num Lock is not actived in lightdm, even if it is actived in the bios.

  After login, Num Lock is actived.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 23 16:33:42 2014
  InstallationDate: Installed on 2014-01-09 (13 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1276098] Re: Sound: Background tints around listboxes and sliders

2014-02-04 Thread Robert Ancell
Marking the g-c-c task as wont fix since we will just be using vanilla
upstream. If someone wants to do the same fix in g-c-c then feel free to
reopen that task.

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed = Triaged

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged = Won't Fix

** 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/1276098

Title:
  Sound: Background tints around listboxes and sliders

Status in “gnome-control-center” package in Ubuntu:
  Won't Fix
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10

  1. Open the Sound panel.
  2. Flip through the tabs and look at the listboxes and sliders.

  What you see: the background is tinted darker than the rest of the tab
  (a) above all listboxes
  (b) to the right of the Play sound through listbox
  (c) to the right of the Record sound from listbox
  (d) behind all sliders.

  What you should see: The background color in these areas is the same
  as the rest of the tab.

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

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


[Desktop-packages] [Bug 1245474] [NEW] [regression] on login screen, monitor stays on forever

2014-02-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I am not sure which package sould be responsible for that, probably
either xorg-server or lightdm.

Previously, up to raring, when you left the computer alone while it was
showing the login screen (lightdm in my case), the monitor would turn
off after five or ten minutes. Since upgrade from raring to saucy,
monitor stays on indefinitely, after boot and after logout likewise.
This is on two machines, one a notebook with Intel graphics, another
desktop with Radeon using open source driver.

I guess maybe setting up DPMS got broken in the process of migration to Mir and 
back to xorg.
--- 
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
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]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
DistroCodename: saucy
DistroRelease: Ubuntu 13.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Tags:  saucy ubuntu compiz-0.9
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
dmi.bios.date: 10/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-M LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
 Failed to load module fglrx (loader failed, 7)
 Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
 Failed to load module fglrx (loader failed, 7)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.3-3ubuntu2
xserver.video_driver: radeon

** Affects: hundredpapercuts
 Importance: Medium
 Status: Confirmed

** Affects: ubuntu-power-consumption
 Importance: Undecided
 Status: Confirmed

** Affects: unity-greeter (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: apport-collected bot-comment compiz-0.9 dpms regression-release saucy 
ubuntu ubuntu-desktop-trusty
-- 
[regression] on login screen, monitor stays on forever
https://bugs.launchpad.net/bugs/1245474
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity-greeter in Ubuntu.

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Robert Ancell
** Changed in: unity-greeter
   Importance: Undecided = High

** Changed in: unity-greeter
   Status: Confirmed = Triaged

** No longer affects: lightdm (Ubuntu)

** No longer affects: lightdm

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in Unity Greeter:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1266465] Re: Cannot set static background in 13.10

2014-02-04 Thread Robert Ancell
** Project changed: unity-greeter = unity-greeter (Ubuntu)

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

Title:
  Cannot set static background in 13.10

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

Bug description:
  Steps to reproduce:

   * Open dconf editor
   * Set background to '/usr/share/backgrounds/somebackground.jpg' (file is 
root:root)
   * Set draw-user-backgrounds to false (unticked)
   * Close
   * Set desktop (user) background to inaccessible.jpg (file that cannot be 
read by lightdm)
   * Restart machine

  What should happen:

  Greeter loads. Greeter background is somebackground.jpg - does not
  change if different user is selected, does not change if user
  background is changed.

  What happens instead:

  Greeter loads. Greeter background is warty-final-ubuntu.png (default).

  Notes:

  Could be related to these reports attempting the same from the command
  line? http://askubuntu.com/questions/379965/lightdm-unity-greeter-
  wallpaper-will-not-set and http://askubuntu.com/questions/381479/how-
  to-change-login-screen-background-on-13-10

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

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Robert Ancell
** Project changed: unity-greeter = unity-greeter (Ubuntu)

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 921097] Re: No session-change icon after logout visible

2014-02-04 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/921097

Title:
  No session-change icon after logout visible

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

Bug description:
  I can not see the icon to change the session (eg from ubuntu to gnome) when i 
logout.
  When i select a different user and then select my user again, the icon is 
visible.

  Steps to reproduce:
  1) login (currently i use the gnome-shell)
  2) logout
  3) see that there is no icon to change the session

  No the steps to be able to change the session
  4) select a different user
  5) select your user again
  6) now the icon is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
  Uname: Linux 3.2.0-10-generic i686
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Tue Jan 24 18:35:03 2012
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-01-20 (4 days ago)

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

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


[Desktop-packages] [Bug 1203357] Re: Additional user(s) that log out of a any session still show as being logged in

2014-02-04 Thread Robert Ancell
** Project changed: unity-greeter = unity-greeter (Ubuntu)

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

Title:
  Additional user(s) that log out of a any session still show as being
  logged in

Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in “indicator-session” package in Ubuntu:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  Test case:
  Create a new user
  Log out, log in to new user 

  Log out from new user, log back in to orig user
  New user will still be shown as logged in in the session indicator even 
though they aren't

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-session 12.10.5+13.10.20130717-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 20 14:33:09 2013
  InstallationDate: Installed on 2013-07-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130712)
  MarkForUpload: True
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1203357] Re: Additional user(s) that log out of a any session still show as being logged in

2014-02-04 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/1203357

Title:
  Additional user(s) that log out of a any session still show as being
  logged in

Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in “indicator-session” package in Ubuntu:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  Test case:
  Create a new user
  Log out, log in to new user 

  Log out from new user, log back in to orig user
  New user will still be shown as logged in in the session indicator even 
though they aren't

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-session 12.10.5+13.10.20130717-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 20 14:33:09 2013
  InstallationDate: Installed on 2013-07-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130712)
  MarkForUpload: True
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 921097] Re: No session-change icon after logout visible

2014-02-04 Thread Robert Ancell
** Project changed: unity-greeter = unity-greeter (Ubuntu)

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

** Changed in: unity-greeter (Ubuntu)
   Importance: Undecided = Low

** No longer affects: lightdm (Ubuntu)

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

Title:
  No session-change icon after logout visible

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

Bug description:
  I can not see the icon to change the session (eg from ubuntu to gnome) when i 
logout.
  When i select a different user and then select my user again, the icon is 
visible.

  Steps to reproduce:
  1) login (currently i use the gnome-shell)
  2) logout
  3) see that there is no icon to change the session

  No the steps to be able to change the session
  4) select a different user
  5) select your user again
  6) now the icon is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
  Uname: Linux 3.2.0-10-generic i686
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Tue Jan 24 18:35:03 2012
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-01-20 (4 days ago)

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

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


[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-04 Thread Bruce Pieterse
** Attachment added: GPU Crash Log on Card 1
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1274779/+attachment/3968562/+files/gpu-hang2.tar.bz2

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

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  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.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-04 Thread Bruce Pieterse
I had another lockup today, but this time using an HDMI connection
instead of VGA. This occurred while watching a Vimeo video which is
slightly different from my first gpu hang.

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

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  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.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Robert Ancell
Unity greeter doesn't do anything to control the power management. It
runs gnome-settings-daemon to do this. It seems likely the problem is
either unity-greeter not configuring / running the correct plugin in
g-s-d or g-s-d being broken.

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1182522] Re: Replugging a Usb headphone does not restore the previous output and level

2014-02-04 Thread Ekimia
Can't anyone at least confirm this ? this is very Dangerous for the ears
of the user !!

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

Title:
  Replugging a Usb headphone does not restore the previous output and
  level

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  ubuntu 12.04.2 (Upgraded from ubuntu 12.04.1 )

  How to reproduce the problem:

  - Plug a USB headset, select it in the sound prefs  and set the
  volume.

  - Unplug/replug the headset

  - Open the sound preferences : the headset is not selected but the
  sound is output through the usb headset at maximum volume.

  This killed my ears several times, I'm almost deaf now 

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

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


[Desktop-packages] [Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open

2014-02-04 Thread Robert Ancell
** Tags added: ubuntu-desktop-trusty

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

Title:
  Shutdown from greeter does nothing when multiple accounts open

Status in The Session Menu:
  Triaged
Status in LightDM GTK+ Greeter:
  Triaged
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in “gnome-session” package in Ubuntu:
  Confirmed
Status in “indicator-session” package in Ubuntu:
  In Progress
Status in “policykit” package in Ubuntu:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Invalid
Status in “gnome-session” source package in Precise:
  New
Status in “indicator-session” source package in Precise:
  New
Status in “policykit” source package in Precise:
  New
Status in “unity-greeter” source package in Precise:
  New
Status in “gnome-session” source package in Saucy:
  New
Status in “indicator-session” source package in Saucy:
  New
Status in “policykit” source package in Saucy:
  New
Status in “unity-greeter” source package in Saucy:
  New

Bug description:
  [Impact]

   * A user tries to shut down their machine. They get confused because nothing 
happens
     when they click shutdown.
   * If someone else is logged in, they will have to ask that person to Switch 
User to
     log in and log out
   * If someone else is logged in and you don't know the password of the 
account, you
     can't shut down

  [Test Case]

   * Have two login accounts
   * Log both people in, via power cog-lock screen-switch user
   * lock the screen on current account, via power cog-lock screen
   * get back to lightdm via switch user
   * log in to an already logged in account, and try to power off the machine

  [Regression Potential]

   * It wasn't possible to shutdown at all before
   * I can't see a case for a regression, since it never worked to begin with

  [Original Report]

  Selecting shutdown from the greeter does nothing when multiple
  accounts are open.

  This is because the lightdm user (which the greeter runs as) does not
  have permission to shutdown while sessions are open.  Inside a normal
  session this would just return you to the login screen.

  The solution is either for the indicator to say not allowed or to
  run a PolicyKit frontend in the greeter than can get the required
  permissions to perform the shutdown.s

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

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


[Desktop-packages] [Bug 1116497] Re: Can't configure visibility of my name in the menu bar

2014-02-04 Thread Robert Ancell
** Package changed: gnome-control-center (Ubuntu) = unity-control-
center (Ubuntu)

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Medium

** Tags added: ubuntu-desktop-trusty

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

Title:
  Can't configure visibility of my name in the menu bar

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

Bug description:
  indicator-session has the ability to show your name in the menu bar,
  alongside the system icon. But there is no visible interface to
  configure this.

  https://wiki.ubuntu.com/SystemMenu#title-setting: In the System
  Settings “User Accounts” panel, at the bottom of the pane for your own
  account should be a checkbox, “Show my login name in the menu bar”,
  that is unchecked by default for a new user account.

  (This is the sequel to bug 964678.)

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

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


[Desktop-packages] [Bug 1276116] [NEW] shut down or restart

2014-02-04 Thread Robson Dantas de Aguiar
Public bug reported:

Both appear in the same window of information indicating the closure.
The option restart appears as shut down.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
 GCC version:  gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-14ubuntu4)
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg:
 [   17.068596] forcedeth :00:07.0 eth0: MSI enabled
 [   19.762812] nvidia :02:00.0: irq 44 for MSI/MSI-X
Date: Tue Feb  4 08:47:20 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-6-generic, i686: installed
 nvidia-331, 331.38, 3.13.0-6-generic, i686: installed
GraphicsCard:
 NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Device [19da:5044]
InstallationDate: Installed on 2014-01-12 (23 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140111)
Lsusb:
 Bus 001 Device 002: ID 090c:6300 Silicon Motion, Inc. - Taiwan (formerly Feiya 
Technology Corp.) 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic 
root=UUID=1ae91858-2184-43a8-843d-30d15da31308 ro locale=pt_BR quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: P01
dmi.board.name: M61PMV
dmi.board.version: FAB 1.0
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP01:bd09/30/2008:svn:pnM61PMV:pvrFAB1.0:rvn:rnM61PMV:rvrFAB1.0:cvn:ct3:cvr:
dmi.product.name: M61PMV
dmi.product.version: FAB 1.0
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
xserver.bootTime: Tue Feb  4 08:42:43 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.14.5-1ubuntu4

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


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

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

Title:
  shut down or restart

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Both appear in the same window of information indicating the closure.
  The option restart appears as shut down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-14ubuntu4)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   17.068596] 

[Desktop-packages] [Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open

2014-02-04 Thread Robert Ancell
** Changed in: gnome-session (Ubuntu)
   Importance: Undecided = Medium

** Changed in: gnome-session (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: indicator-session (Ubuntu)
   Status: In Progress = Triaged

** No longer affects: indicator-session (Ubuntu Precise)

** No longer affects: indicator-session (Ubuntu Saucy)

** No longer affects: policykit (Ubuntu Precise)

** No longer affects: policykit (Ubuntu Saucy)

** No longer affects: unity-greeter (Ubuntu Precise)

** No longer affects: unity-greeter (Ubuntu Saucy)

** No longer affects: gnome-session (Ubuntu Precise)

** No longer affects: gnome-session (Ubuntu Saucy)

** Also affects: gnome-session (Ubuntu Raring)
   Importance: Undecided
   Status: New

** Also affects: policykit (Ubuntu Raring)
   Importance: Undecided
   Status: New

** Also affects: indicator-session (Ubuntu Raring)
   Importance: Undecided
   Status: New

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

** No longer affects: gnome-session (Ubuntu Raring)

** No longer affects: indicator-session (Ubuntu Raring)

** No longer affects: policykit (Ubuntu Raring)

** No longer affects: unity-greeter (Ubuntu Raring)

** No longer affects: unity-greeter (Ubuntu)

** Changed in: policykit (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: policykit (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Shutdown from greeter does nothing when multiple accounts open

Status in The Session Menu:
  Triaged
Status in LightDM GTK+ Greeter:
  Triaged
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in “gnome-session” package in Ubuntu:
  Triaged
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “policykit” package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * A user tries to shut down their machine. They get confused because nothing 
happens
     when they click shutdown.
   * If someone else is logged in, they will have to ask that person to Switch 
User to
     log in and log out
   * If someone else is logged in and you don't know the password of the 
account, you
     can't shut down

  [Test Case]

   * Have two login accounts
   * Log both people in, via power cog-lock screen-switch user
   * lock the screen on current account, via power cog-lock screen
   * get back to lightdm via switch user
   * log in to an already logged in account, and try to power off the machine

  [Regression Potential]

   * It wasn't possible to shutdown at all before
   * I can't see a case for a regression, since it never worked to begin with

  [Original Report]

  Selecting shutdown from the greeter does nothing when multiple
  accounts are open.

  This is because the lightdm user (which the greeter runs as) does not
  have permission to shutdown while sessions are open.  Inside a normal
  session this would just return you to the login screen.

  The solution is either for the indicator to say not allowed or to
  run a PolicyKit frontend in the greeter than can get the required
  permissions to perform the shutdown.s

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

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


[Desktop-packages] [Bug 1085340] Re: totem's next prev buttons in sound indicator are non-functional

2014-02-04 Thread Robert Ancell
** Changed in: totem (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: totem (Ubuntu)
   Importance: Undecided = Medium

** Tags added: ubuntu-desktop-trusty

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

Title:
  totem's next  prev buttons in sound indicator are non-functional

Status in “totem” package in Ubuntu:
  Triaged

Bug description:
  Videos  (totem), is now in the sound menu. The pause/play button
  works, the prev/next ones don't.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Sat Dec  1 01:32:48 2012
  InstallationDate: Installed on 2012-10-23 (38 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 878836] Re: Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions

2014-02-04 Thread Robert Ancell
** Tags added: ubuntu-desktop-trusty

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

Title:
  Unity Greeter - Use Unity Greeter to fulfil lock screen as well as
  login functions

Status in Ayatana Design:
  Fix Committed
Status in The Session Menu:
  Fix Released
Status in Light Display Manager:
  Triaged
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “unity-greeter” package in Ubuntu:
  Triaged
Status in “indicator-session” source package in Precise:
  Fix Released

Bug description:
  Use Unity Greeter to fulfil lock screen as well as login functions.

  Desired Solution:
  - Replace the current lock screen with the Unity Greeter
  - perhaps use 'light locker', see 
http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
  - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/878836/+subscriptions

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


[Desktop-packages] [Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back

2014-02-04 Thread Sebastien Bacher
** Tags added: ubuntu-desktop-trusty

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

Title:
  Open with on folders was removed, Ubuntu should consider patching back

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Note, bug has been open long enough to be fixed so who cares ... -
  If you wish this back,  ppa here -
  https://launchpad.net/~mc3man/+archive/nauty-open

  This rev removed the context option.
  http://bazaar.launchpad.net/~vcs-imports/nautilus/master-git/revision/16061

  While unlikely to be reconsidered upstream I know many Ubuntu users find the 
option handy.
  I guess this report could be considered an Opinion  like other opinions in 
Ubuntu land the validity of such rests solely on 'who' agrees or disagrees

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.3-0ubuntu4
  Architecture: amd64
  Date: Wed Jul 18 13:22:46 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'1043x619+132+204'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'165'
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1260971] Re: Nautilus does not save all user settings show/hide sidebar

2014-02-04 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1265401 ***
https://bugs.launchpad.net/bugs/1265401

Thank you for your bug report, that's an known issue and resolved in
newer versions, see bug #1265401

** This bug has been marked a duplicate of bug 1265401
   Incorrect sidebar status with start-with-sidebar false config

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

Title:
  Nautilus does not save all user settings show/hide sidebar

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Nautilus saves some user settings and not others. 
  For instance, it saves my preference for list view. 
  But it does not save my preference for hiding the sidebar. 
  It should save all user preferences.
  :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.8.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 14 07:53:01 2013
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b['name']
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2013-10-25 (50 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 947919] Re: Can't change brightness with keyboard or with Brightness and Lock settings panel

2014-02-04 Thread Robert Ancell
** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Can't change brightness with keyboard or with Brightness and Lock
  settings panel

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

Bug description:
  gnome-settings-daemon 3.3.91-0ubuntu1, gnome-control-center
  1:3.3.90-0ubuntu5, Ubuntu 12.04 beta

  1. Press the Brightness keys on the keyboard.
  2. In System Settings, click Brightness and Lock.

  What happens:
  1. Nothing.
  2. The Brightness and Lock panel does not contain any brightness settings.

  What should happen:
  1. The brightness changes.
  2. The Brightness and Lock panel contains a brightness slider.

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

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


[Desktop-packages] [Bug 1267462] Re: nautilus does not save setting show sidebar do not show sidebar

2014-02-04 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1265401 ***
https://bugs.launchpad.net/bugs/1265401

** This bug has been marked a duplicate of bug 1265401
   Incorrect sidebar status with start-with-sidebar false config

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

Title:
  nautilus does not save setting show sidebar do not show sidebar

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Nautilus seems to save all user settings except one: the toggle to disable 
the sidebar view. 
  The user should be able to disable the sidebar view and have it stay that way.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.8.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.12.7-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  9 07:57:28 2014
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b['name']
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2013-10-25 (76 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1276123] [NEW] Xorg loads wrong libglx.so

2014-02-04 Thread PhilippeSeidel
Public bug reported:

This bug concerns all versions of the nvidia-packages I have tested so
far, actually since ubuntu 8.something...

If I install the proprietary nvidia drivers, I can properly set up my
xorg.conf and the Xorg driver as well as the kernel module load
correctly. However, when using unity or anything requiring libglx.so, X
simply crashes. The reason is that X is loading the wrong libglx.so:

grep glx /var/log/Xorg.0.log

[ 11312.722] (II) glx will be loaded. This was enabled by default and also 
specified in the config file.
[ 11312.722] (II) LoadModule: glx
[ 11312.722] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 11312.722] (II) Module glx: vendor=X.Org Foundation

My first solution was to move /usr/lib/xorg/modules/extensions/libglx.so
out of the way and to replace it with a symlink to /usr/lib/nvidia-
VERSION/xorg/libglx.so. However, as you might imagine, this quick-and-
dirty fix has to be redone each time that MESA gets updated, as my
symlink is destroyed. I have now found a better solution, which consists
in telling Xorg where the right library is in /etc/X11/xorg.conf

Section Files
ModulePath  /usr/lib/nvidia-VERSION/xorg
ModulePath  /usr/lib/xorg/modules
...
EndSection

nvidia-VERSION has to be replaced by the proper nvidia version (such as
nvidia-current). As a result, X loads the right libglx.so.

This solution could be included in all nvidia- packages, so that the
problem does not occur any longer. I have found other bug reports from
other distributions about this, but most are solved by moving libglx.so
out of the way.

Just for information, here's some details about my system:
philippe@saaba:~$ dpkg -l xorg
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
 Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name   Version  Architektur  Beschreibung
+++-==---=
ii  xorg   1:7.7+1ubunt amd64X.Org X Window System

philippe@saaba:~$ lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9600M GT] 
(rev a1)

philippe@saaba:/var/log$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10

nvidia-current is at 304.88-0ubuntu8 0, I also had the problem with
nvidia-319-updates 319.60-0ubuntu1 0

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


** Tags: libglx.so module nvidia path

** Attachment added: xorg.conf
   https://bugs.launchpad.net/bugs/1276123/+attachment/3968621/+files/xorg.conf

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

Title:
  Xorg loads wrong libglx.so

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

Bug description:
  This bug concerns all versions of the nvidia-packages I have tested so
  far, actually since ubuntu 8.something...

  If I install the proprietary nvidia drivers, I can properly set up my
  xorg.conf and the Xorg driver as well as the kernel module load
  correctly. However, when using unity or anything requiring libglx.so,
  X simply crashes. The reason is that X is loading the wrong libglx.so:

  grep glx /var/log/Xorg.0.log

  [ 11312.722] (II) glx will be loaded. This was enabled by default and also 
specified in the config file.
  [ 11312.722] (II) LoadModule: glx
  [ 11312.722] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [ 11312.722] (II) Module glx: vendor=X.Org Foundation

  My first solution was to move
  /usr/lib/xorg/modules/extensions/libglx.so out of the way and to
  replace it with a symlink to /usr/lib/nvidia-VERSION/xorg/libglx.so.
  However, as you might imagine, this quick-and-dirty fix has to be
  redone each time that MESA gets updated, as my symlink is destroyed. I
  have now found a better solution, which consists in telling Xorg where
  the right library is in /etc/X11/xorg.conf

  Section Files
  ModulePath  /usr/lib/nvidia-VERSION/xorg
  ModulePath  /usr/lib/xorg/modules
  ...
  EndSection

  nvidia-VERSION has to be replaced by the proper nvidia version (such
  as nvidia-current). As a result, X loads the right libglx.so.

  This solution could be included in all nvidia- packages, so that the
  problem does not occur any longer. I have found other bug reports from
  other distributions about this, but most are solved by moving
  libglx.so out of the way.

  Just for information, here's some details about my system:
  philippe@saaba:~$ dpkg -l xorg
  Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
  | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
   Halb installiert/Trigger erWartet/Trigger 

[Desktop-packages] [Bug 947919] Re: Can't change brightness with keyboard or with Brightness and Lock settings panel

2014-02-04 Thread Robert Ancell
** Tags added: ubuntu-desktop-trusty

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

Title:
  Can't change brightness with keyboard or with Brightness and Lock
  settings panel

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

Bug description:
  gnome-settings-daemon 3.3.91-0ubuntu1, gnome-control-center
  1:3.3.90-0ubuntu5, Ubuntu 12.04 beta

  1. Press the Brightness keys on the keyboard.
  2. In System Settings, click Brightness and Lock.

  What happens:
  1. Nothing.
  2. The Brightness and Lock panel does not contain any brightness settings.

  What should happen:
  1. The brightness changes.
  2. The Brightness and Lock panel contains a brightness slider.

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

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


[Desktop-packages] [Bug 1276116] Re: shut down or restart

2014-02-04 Thread Robson Dantas de Aguiar
** Attachment added: restart and shut down, both are identical.
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1276116/+attachment/3968624/+files/restart.png

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

Title:
  shut down or restart

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Both appear in the same window of information indicating the closure.
  The option restart appears as shut down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-14ubuntu4)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   17.068596] forcedeth :00:07.0 eth0: MSI enabled
   [   19.762812] nvidia :02:00.0: irq 44 for MSI/MSI-X
  Date: Tue Feb  4 08:47:20 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-6-generic, i686: installed
   nvidia-331, 331.38, 3.13.0-6-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Device [19da:5044]
  InstallationDate: Installed on 2014-01-12 (23 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140111)
  Lsusb:
   Bus 001 Device 002: ID 090c:6300 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic 
root=UUID=1ae91858-2184-43a8-843d-30d15da31308 ro locale=pt_BR quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: P01
  dmi.board.name: M61PMV
  dmi.board.version: FAB 1.0
  dmi.chassis.asset.tag: Unknow
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP01:bd09/30/2008:svn:pnM61PMV:pvrFAB1.0:rvn:rnM61PMV:rvrFAB1.0:cvn:ct3:cvr:
  dmi.product.name: M61PMV
  dmi.product.version: FAB 1.0
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Tue Feb  4 08:42:43 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.5-1ubuntu4

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

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


[Desktop-packages] [Bug 1276085] Re: Update to 0.9.26

2014-02-04 Thread Sebastien Bacher
https://launchpad.net/ubuntu/+source/harfbuzz/0.9.26-3

** Changed in: harfbuzz (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Update to 0.9.26

Status in “harfbuzz” package in Ubuntu:
  Fix Released

Bug description:
  Update to 0.9.26

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

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


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

2014-02-04 Thread William Hua
** Tags added: ubuntu-desktop-trusty

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

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

Status in LibreOffice Productivity Suite:
  Invalid
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Mutter:
  New
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “indicator-keyboard” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

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

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

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

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

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

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


[Desktop-packages] [Bug 1186273] Re: DUN via bluetooth with a password fails

2014-02-04 Thread Jonathan Davies
** Tags removed: verification-failed verification-needed
** Tags added: verification-done

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

Title:
  DUN via bluetooth with a password fails

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Precise:
  Fix Committed
Status in “network-manager” source package in Quantal:
  Fix Committed
Status in “network-manager” source package in Raring:
  Fix Released

Bug description:
  [Impact]

   * Unable to connect to a DUN n/w via bluetooth .

  [Test Case]

   * Create a bluetooth connection via DUN capable device ( Nokia 6680) using 
bluetooth settings from gnome-control-center . 
   * I have posted a sample connection created below, with username and 
password keyed in manually

  $ cat /etc/NetworkManager/system-connection/example
  [connection]
  id=Mobil-BT connection
  uuid=c57749ea-92fb-4297-8db4-875b66b3319a
  type=bluetooth
  autoconnect=false

  [bluetooth]
  bdaddr=00:16:4E:24:EA:2F
  type=dun

  [gsm]
  number=*99#
  apn=apn.example.com
  username=userexample
  password=secret

  [serial]
  baud=115200

   * Click on the connection from network icon in panel

  
  [Regression Potential] 

   * I dont see any regression potential with the patch for 
precise/raring/saucy. 
   * This looks good as per upstream
   * Fixes issue with dun connection, and works fine with PAN (bt) and phone as 
modem.

  [Other Info]
   
   * Upstream - https://bugzilla.gnome.org/show_bug.cgi?id=701507 .

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

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


[Desktop-packages] [Bug 947919] Re: Can't change brightness with keyboard or with Brightness and Lock settings panel

2014-02-04 Thread Robert Ancell
According to the XRANDR spec [1] the correct property is Backlight.

[1]
http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt

** Package changed: gnome-settings-daemon (Ubuntu) = gnome-desktop3
(Ubuntu)

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

Title:
  Can't change brightness with keyboard or with Brightness and Lock
  settings panel

Status in “gnome-desktop3” package in Ubuntu:
  Triaged

Bug description:
  gnome-settings-daemon 3.3.91-0ubuntu1, gnome-control-center
  1:3.3.90-0ubuntu5, Ubuntu 12.04 beta

  1. Press the Brightness keys on the keyboard.
  2. In System Settings, click Brightness and Lock.

  What happens:
  1. Nothing.
  2. The Brightness and Lock panel does not contain any brightness settings.

  What should happen:
  1. The brightness changes.
  2. The Brightness and Lock panel contains a brightness slider.

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

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


[Desktop-packages] [Bug 1188571] Re: The list of printers should be searchable/sortable

2014-02-04 Thread Ubuntu Foundations Team Bug Bot
The attachment proposed patch for precise seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the patch flag from the attachment, remove the
patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  The list of printers should be searchable/sortable

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  With the current GTK dialog (as in 3.6.4).

  Users, working on a lan with many printers, report that it's difficult for 
them
  to find the printer they want to use because GTK provide no way to
  search/filter/sort the list of printers.

  Typeahead is working, but it's not really obvious (so some users don't know
  about it) and only works on the printer names, not on their location.

  Some possible improvements:
  - providing a way to search/filter in the list, taking into account names and
  locations
  - make the columns sortable, that would allow users to, at least, sort by
  location
  - sort the most used printers always first

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

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


[Desktop-packages] [Bug 878836] Re: Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions

2014-02-04 Thread Bence Lukács
This bug is still active since Oneiric, it should be fixed by now...
There were videos about this feature during the developement of Precise.
The gnome-screensaver is uglier than the current unity-greeter, why can't we 
use it as a lock screen?

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

Title:
  Unity Greeter - Use Unity Greeter to fulfil lock screen as well as
  login functions

Status in Ayatana Design:
  Fix Committed
Status in The Session Menu:
  Fix Released
Status in Light Display Manager:
  Triaged
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “unity-greeter” package in Ubuntu:
  Triaged
Status in “indicator-session” source package in Precise:
  Fix Released

Bug description:
  Use Unity Greeter to fulfil lock screen as well as login functions.

  Desired Solution:
  - Replace the current lock screen with the Unity Greeter
  - perhaps use 'light locker', see 
http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
  - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/878836/+subscriptions

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


[Desktop-packages] [Bug 947919] Re: Can't change brightness with keyboard or with Brightness and Lock settings panel

2014-02-04 Thread Robert Ancell
The upstream code for this moved into Mutter.

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

** Changed in: mutter (Ubuntu)
   Status: New = Triaged

** Changed in: mutter (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Can't change brightness with keyboard or with Brightness and Lock
  settings panel

Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “mutter” package in Ubuntu:
  Triaged

Bug description:
  gnome-settings-daemon 3.3.91-0ubuntu1, gnome-control-center
  1:3.3.90-0ubuntu5, Ubuntu 12.04 beta

  1. Press the Brightness keys on the keyboard.
  2. In System Settings, click Brightness and Lock.

  What happens:
  1. Nothing.
  2. The Brightness and Lock panel does not contain any brightness settings.

  What should happen:
  1. The brightness changes.
  2. The Brightness and Lock panel contains a brightness slider.

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

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


[Desktop-packages] [Bug 1182522] Re: Replugging a Usb headphone does not restore the previous output and level

2014-02-04 Thread Raymond
you have to dump pulseaudio database to find out whether the volume have
been stored after each adjustment

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

Title:
  Replugging a Usb headphone does not restore the previous output and
  level

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  ubuntu 12.04.2 (Upgraded from ubuntu 12.04.1 )

  How to reproduce the problem:

  - Plug a USB headset, select it in the sound prefs  and set the
  volume.

  - Unplug/replug the headset

  - Open the sound preferences : the headset is not selected but the
  sound is output through the usb headset at maximum volume.

  This killed my ears several times, I'm almost deaf now 

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

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


[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2014-02-04 Thread Gerlof Fokkema
Seems like this bug is still present.

gnome-open http://launchpad.net
gives me a new Chromium screen with a blank page and no url.

chromium-browser http://launchpad.net
gives me a new tab in a present Chromium screen displaying http://launchpad.net

dconf-editor:
/desktop/gnome/url-handlers/http/command = chromium-browser %s
/desktop/gnome/url-handlers/https/command = chromium-browser %s

any logs i need to attach or commands i need to run to supply more info?

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Eugene Crosser
Robert, my observations show that the problem is not that proper setting
are *not applied*, but that they are *overridden* with wrong values
afterwards.

(It conceivable though that g-s-d may be applying the wrong values
after my display-setup-script has applied the right ones. Can you tell
where to check the settings that are applied by g-s-d run from the
greeter?)

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5105:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.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: Mon Oct 28 12:00:05 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
   Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so: 
/usr/lib/xorg/modules/drivers/fglrx_drv.so: cannot open shared object file: No 
such file or directory
   Failed to load module fglrx (loader failed, 7)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1276143] [NEW] Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

2014-02-04 Thread Ikuya Awashiro
Public bug reported:

Please merge ibus 1.5.5-1ubuntu1. It has very important feature
property panel.

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Assignee: Ikuya Awashiro (ikuya-fruitsbasket)
 Status: In Progress

** Changed in: nagios-plugins (Ubuntu)
   Status: New = In Progress

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

** No longer affects: nagios-plugins (Ubuntu)

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

** Changed in: ibus (Ubuntu)
 Assignee: (unassigned) = Ikuya Awashiro (ikuya-fruitsbasket)

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

Title:
  Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

Status in “ibus” package in Ubuntu:
  In Progress

Bug description:
  Please merge ibus 1.5.5-1ubuntu1. It has very important feature
  property panel.

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

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


[Desktop-packages] [Bug 1248211] Re: After upgrade from 13.04 to 13.10 no auto mount, unable to shutdown/reboot from menu, empty network list, etc ...

2014-02-04 Thread Tim Band
Yes, I'm experiencing the same thing. Also pulseaudio is reporting only Dummy 
Output, which I assume is connected.
None of the googleable solutions to the pulseaudio problem fix it. I understand 
that I'm supposed to see my user ID when I type getfacl /dev/snd/*
Instead I get this:
tim@sileo:~$ getfacl /dev/snd/*
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/by-id
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/by-path
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/controlC1
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/controlC2
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/hwC0D2
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/midiC1D0
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D0p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D1c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D1p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D2c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC1D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC1D0p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC2D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/seq
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/timer
# owner: root
# group: audio
user::rw-
group::rw-
other::---

Does this help?

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

Title:
  After upgrade from 13.04 to 13.10 no auto mount, unable to
  shutdown/reboot from menu, empty network list, etc ...

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

Bug description:
  Recently I upgraded my laptop from 13.04 to 13.10. After that I am
  facing the following issues.

  . No automount for usb devices
  . Unable to shutdown/reboot from the menu (unless from commandline with sudo)
  . Network list is empty (but via sudo the network list are there 
(nm-connection-editor))
  . In the notification panel(systray) the network icon is missing.
  . unable to edit User manager, the unlock button is grayed out always.

  While opening Network from gnome-control-center, it showing the following 
error message.
  The system network services are not compatible with this version.

  In the terminal the following error messages printed while running 
gnome-control-center = Network
  (gnome-control-center:3748): Clutter-WARNING **: Locale not supported by C 
library.
  Using the fallback 'C' locale.

  ** (gnome-control-center:3748): WARNING **: Could not initialize
  NMClient /org/freedesktop/NetworkManager: Rejected send message, 3
  matched rules; type=method_call, sender=:1.88 (uid=1000 pid=3748
  comm=gnome-control-center )
  interface=org.freedesktop.DBus.Properties member=GetAll error
  name=(unset) requested_reply=0
  destination=org.freedesktop.NetworkManager (uid=0 pid=1666
  comm=NetworkManager )

  (gnome-control-center:3748): network-cc-panel-WARNING **: Could not
  open RFKILL control device, please verify your installation

  ** (gnome-control-center:3748): WARNING **:
  _nm_remote_settings_ensure_inited: (NMRemoteSettings) error
  initializing: Rejected send message, 3 matched rules;
  type=method_call, sender=:1.88 (uid=1000 pid=3748 comm=gnome-
  control-center ) interface=org.freedesktop.DBus.Properties
  member=GetAll error name=(unset) requested_reply=0
  destination=org.freedesktop.NetworkManager (uid=0 pid=1666
  comm=NetworkManager )


  If I open the Software Updater, its showing this error
  You are not allowed to perform this action
  You don't have the required privileges to perform this action

  
  jj@jjux64:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  jj@jjux64:~$ id
  uid=1000(jj) gid=1000(jj) 
groups=1000(jj),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),104(fuse),109(lpadmin),119(pulse),120(pulse-access),124(sambashare),130(vboxusers),131(nm-openconnect)

  Please let me know, if any more info required from my side.

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

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

[Desktop-packages] [Bug 1174197] Re: gnome-system-monitor freezes when reordering columns in procs view

2014-02-04 Thread Boris de Laage
Fixed in 3.10

** Package changed: gnome-control-center (Ubuntu) = gnome-system-
monitor (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/1174197

Title:
  gnome-system-monitor freezes when reordering columns in procs view

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

Bug description:
  In process view, when I reorder columns g-s-m freezes and the x server
  doesn't accept any input. After a few seconds, I can switch to a
  virtual console, log in  kill g-s-m.

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

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


[Desktop-packages] [Bug 1276143] Re: Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

2014-02-04 Thread Ikuya Awashiro
** Patch added: ibus_1.5.5-1.5.5-1ubuntu1.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276143/+attachment/3968675/+files/ibus_1.5.5-1.5.5-1ubuntu1.debdiff

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

Title:
  Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Please merge ibus 1.5.5-1ubuntu1. It has very important feature
  property panel.

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

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


[Desktop-packages] [Bug 1276143] Re: Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

2014-02-04 Thread Ikuya Awashiro
** Attachment added: ibus_1.5.4-1ubuntu1-1.5.5-1ubuntu1.debdiff.gz
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276143/+attachment/3968676/+files/ibus_1.5.4-1ubuntu1-1.5.5-1ubuntu1.debdiff.gz

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

** Changed in: ibus (Ubuntu)
 Assignee: Ikuya Awashiro (ikuya-fruitsbasket) = (unassigned)

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

Title:
  Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Please merge ibus 1.5.5-1ubuntu1. It has very important feature
  property panel.

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

-- 
Mailing list: https://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 1244884] Re: URL doesn't open from other application in chromium-browser

2014-02-04 Thread Chad Miller
What do these show?

$ gconftool --get /desktop/gnome/url-handlers/http/command |od -x
$ dconf read /desktop/gnome/url-handlers/http/command |od -x

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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


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

2014-02-04 Thread David Henningsson
https://code.launchpad.net/~diwic/gnome-settings-daemon/what-did-you-
plug-in/+merge/204680

** Changed in: pulseaudio (Ubuntu Precise)
   Status: Confirmed = Won't Fix

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

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

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  In Progress
Status in “pulseaudio” source package in Precise:
  Won't Fix

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1245474] Re: [regression] on login screen, monitor stays on forever

2014-02-04 Thread Ted Felix
Robert Ancell:
 It seems likely the problem is either unity-greeter not configuring / running 
 the correct plugin in g-s-d

  It appears that the power plugin is indeed running in both 13.04 and
13.10 as I am seeing logging from it in /var/log/lightdm/x-0-greeter.log
in both 13.04 and 13.10.

 or g-s-d being broken.

  One key thing that is different between the two logs is that this line
appears in 13.10, but not in 13.04:

(gnome-settings-daemon:1507): power-plugin-WARNING **: Failed to run
GetActive() function on screensaver:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
'org.gnome.ScreenSaver' on object at path /org/gnome/ScreenSaver

  I do know that the power plugin's dpms feature is driven by
org.gnome.screensaver, so since connecting to that is failing in 13.10,
that might be related to the issue.

Eugene Crosser:
 my observations show that the problem is not that proper setting are *not 
 applied*, but that they are *overridden* with wrong values afterwards.

  This is not what I'm seeing.  The DPMS timeouts are not used at the
login screen in 13.04 to power off the monitor.  The screensaver
timeouts are used instead.  And the screensaver timeouts are not being
modified by anyone when lightdm is running.  You can verify this by
modifying the display-setup-script and session-setup-script to do an
xset q before and after the 10 second sleep and log this someplace
where it can be easily found.  Then examine the screensaver timeouts
(not the DPMS) timeouts.  The screensaver timeouts stay at 600 for the
login screen.

  Certainly, the DPMS timeouts can be used as a successful workaround.
However, that's not how 13.04 did it.  With 13.04, the DPMS timeouts are
0, and the screen still powers off at the login screen.

  My plan at this point is to try and run g-s-d in debug mode.  I'm not
sure how to do that elegantly.  I'm going to try pointing /usr/bin/g-s-d
to a script that adds on --debug.  If anyone has a better suggestion,
I'd love to hear it.  Once g-s-d is running in debug, I should be able
to see it power the monitor on/off in 13.04 and perhaps some additional
clues in 13.10.  Worst case. I have been doing some power plugin hacking
recently, so I can easily drop in a replacement with further logging.

  As always, no guarantee this will get me anywhere.  I've run into many
brick walls trying to figure this out over the past few weeks.

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

Title:
  [regression] on login screen, monitor stays on forever

Status in One Hundred Papercuts:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  I am not sure which package sould be responsible for that, probably
  either xorg-server or lightdm.

  Previously, up to raring, when you left the computer alone while it
  was showing the login screen (lightdm in my case), the monitor would
  turn off after five or ten minutes. Since upgrade from raring to
  saucy, monitor stays on indefinitely, after boot and after logout
  likewise. This is on two machines, one a notebook with Intel graphics,
  another desktop with Radeon using open source driver.

  I guess maybe setting up DPMS got broken in the process of migration to Mir 
and back to xorg.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  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]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2013-10-26 13:27:24,614 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroRelease: Ubuntu 13.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic 
root=UUID=72283a55-e0f7-4036-af5e-be1174497a35 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy ubuntu compiz-0.9
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (2 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  

[Desktop-packages] [Bug 1251165] Re: Boot-up typically opens to blank gray greeter screen

2014-02-04 Thread Dallman Ross
apport information

** Tags added: apport-collected has-workaround reproducible trusty

** Description changed:

  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes I
  can't -- because I can't see the underlying screens and have to guess
  what field I'm typing into, etc.
  
  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then the
  greeter screen is normal and I can log in normally.
  
  Also, between screen modes at boot-up and on entering the GDM, there is
  ugly flickering and screen garbage that lasts a good second or so.
  
  /d
  
  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
+ --- 
+ ApportVersion: 2.13.2-0ubuntu2
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ DistUpgraded: Fresh install
+ DistroCodename: trusty
+ DistroRelease: Ubuntu 14.04
+ DistroVariant: ubuntu
+ EcryptfsInUse: Yes
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
+Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
+ InstallationDate: Installed on 2014-02-01 (3 days ago)
+ InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: xorg 1:7.7+1ubuntu8
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
+ ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
+ Tags:  trusty ubuntu reproducible has-workaround
+ Uname: Linux 3.13.0-6-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 10/12/2009
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.40
+ 

[Desktop-packages] [Bug 1251165] CurrentDmesg.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1251165/+attachment/3968714/+files/CurrentDmesg.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1251165] Lsusb.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1251165/+attachment/3968718/+files/Lsusb.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1251165] UdevLog.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1251165/+attachment/3968724/+files/UdevLog.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1251165] BootLog.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: BootLog.txt
   
https://bugs.launchpad.net/bugs/1251165/+attachment/3968713/+files/BootLog.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2014-02-04 Thread Gerlof Fokkema
$ gconftool --get /desktop/gnome/url-handlers/http/command |od -x
000 752f 7273 622f 6e69 632f 7268 6d6f 7569
020 2d6d 7262 776f 6573 2072 7325 000a
035
$ dconf read /desktop/gnome/url-handlers/http/command |od -x
000

Something else worth noting:
When I go to
system-settings - details - default applications
and change 'web' to 'Firefox Web Browser' instead of 'Chrome'
then the Chrome option disappears...

I can only set Chromium default again by closing all Chromium windows and 
restarting it.
It will then ask to be default again.

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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


[Desktop-packages] [Bug 1251165] Lspci.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1251165/+attachment/3968717/+files/Lspci.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1251165] Dependencies.txt

2014-02-04 Thread Dallman Ross
apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1251165/+attachment/3968715/+files/Dependencies.txt

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

Title:
  Boot-up typically opens to blank gray greeter screen

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  ...But not always. Sometimes the boot-up gets to a normal greeter
  screen. Often as not, though, I get a blank gray greeter screen. I can
  type my password blindly and get in to the GDM, usually. But sometimes
  I can't -- because I can't see the underlying screens and have to
  guess what field I'm typing into, etc.

  I can go to a console via Ctr+{[1-6]}  and restart the GDM and then
  the greeter screen is normal and I can log in normally.

  Also, between screen modes at boot-up and on entering the GDM, there
  is ugly flickering and screen garbage that lasts a good second or so.

  /d

  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
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 14 10:19:27 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.3.2, 3.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2013-10-21 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=nomotek-usg ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: ALiveNF7G-GLAN
  dmi.board.vendor: ASRock
  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.:bvrP1.40:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnALiveNF7G-GLAN:rvr: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: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.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: Thu Nov 14 10:15:43 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_sn9c20xKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: radeon
  --- 
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e990]
  InstallationDate: Installed on 2014-02-01 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=hostname ro quiet splash
  ProcVersionSignature: Ubuntu 

  1   2   3   >