date:20131022

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

** Changed in: sane-backends (Ubuntu)
   Status: New => Confirmed

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

Title:
  scanimage crashed with SIGSEGV in __libc_message()

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  Yet another crash in a different section
  This crash occurred yesterday, all i did was print out a list of devices and 
try to get help data output from the device

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: sane-utils 1.0.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in `scanimage': double free or corruption (top): 
0x02058f50 ***
  CrashCounter: 1
  Date: Thu Sep 12 22:48:40 2013
  ExecutablePath: /usr/bin/scanimage
  InstallationDate: Installed on 2013-07-27 (47 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
  MarkForUpload: True
  ProcCmdline: scanimage --help -d net:10.0.0.50:plustek:libusb:004:002
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f502e96a6a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x2058f50, str=0x7f502e96a7b0 "double free or 
corruption (top)", action=3) at malloc.c:4902
   _int_free (av=, p=0x2058f40, have_lock=0) at malloc.c:3758
   _IO_new_fclose (fp=0x2058f50) at iofclose.c:85
   internal_endent () at nss_files/files-XXX.c:161
  Title: scanimage crashed with SIGSEGV in __libc_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1225027/+subscriptions

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

[Desktop-packages] [Bug 1243544] [NEW] create -dev bin package

2013-10-22 Thread Pascal Greliche

Public bug reported:

You should create one (or multiple) -dev packages to have .h files. So
tools using libraries for ex can be built without needing the complete
source code (which is very big).

Thanks

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  create -dev bin package

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

Bug description:
  You should create one (or multiple) -dev packages to have .h files. So
  tools using libraries for ex can be built without needing the complete
  source code (which is very big).

  Thanks

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

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

[Desktop-packages] [Bug 752674] Re: GtkRecentChooserMenu always selects first entry

2013-10-22 Thread Atsawin Chaowanakritsanakul

This bug is resurfaced in 13.10.

OS: Ubuntu 13.10 64bit
Application: Gitg 0.2.7

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

Title:
  GtkRecentChooserMenu always selects first entry

Status in The Application Menu:
  Invalid
Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in DBus Menu:
  Fix Committed
Status in OpenShot Video Editor:
  Invalid
Status in “gitg” package in Ubuntu:
  Invalid
Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “inkscape” package in Ubuntu:
  Invalid
Status in “libdbusmenu” package in Ubuntu:
  Fix Released

Bug description:
  A GtkRecentChooserMenu is a submenu with recently used documents. It
  is used in Anjuta and I also use it in my own code (a patch to
  Xournal:
  
http://sourceforge.net/tracker/?func=detail&aid=3249971&group_id=163434&atid=827735).
  It is probably being used by many more applications.

  When using the global menu, it is always the first entry that is
  opened, no matter which one you click. Looking at the source,
  GtkRecentChooserMenu uses gtk_menu_get_active to select the item. I'm
  guessing that the active item is not updated when using the global
  menu. It probably should be.

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

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

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

2013-10-22 Thread Archisman Panigrahi

Will this bug ever be fixed in Saucy or would we have to wait for
Trusty?

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  Fix Committed
Status in Unity 7.1 series:
  In Progress
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity” source package in Saucy:
  In Progress

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1240673] Re: Reports 0% charged for fully charged batteries

2013-10-22 Thread Martin Pitt

** Also affects: upower (Ubuntu Saucy)
   Importance: Undecided
   Status: New

** Also affects: upower (Ubuntu Trusty)
   Importance: High
 Assignee: Martin Pitt (pitti)
   Status: Fix Committed

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

Title:
  Reports 0% charged for fully charged batteries

Status in “upower” package in Ubuntu:
  Fix Committed
Status in “upower” source package in Saucy:
  New
Status in “upower” source package in Trusty:
  Fix Committed

Bug description:
  See the following upower dump:

  $ upower --dump
  Device: /org/freedesktop/UPower/devices/line_power_AC
native-path:  AC
power supply: yes
updated:  Wed 16 Oct 2013 12:58:28 PM EDT (7198 seconds ago)
has history:  no
has statistics:   no
line-power
  online: yes

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   SMP
model:DELL Y61CV22
serial:   3840
power supply: yes
updated:  Wed 16 Oct 2013 12:58:33 PM EDT (7193 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  energy:  66.6 Wh
  energy-empty:0 Wh
  energy-full: 66.6 Wh
  energy-full-design:  66.6 Wh
  energy-rate: 0.0111 W
  voltage: 12.836 V
  percentage:  0%
  capacity:76.9167%
  technology:  lithium-ion

  Device: /org/freedesktop/UPower/devices/battery_BAT2
native-path:  BAT2
vendor:   Samsung SDI
model:DELL W1GGM26
serial:   12515
power supply: yes
updated:  Wed 16 Oct 2013 12:58:33 PM EDT (7193 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  energy:  31.08 Wh
  energy-empty:0 Wh
  energy-full: 31.08 Wh
  energy-full-design:  31.08 Wh
  energy-rate: 0.0111 W
  voltage: 12.428 V
  percentage:  0%
  capacity:81.2857%
  technology:  lithium-ion

  Note that state is fully-charged, but percentage is o% on both batteries.  
This worked fine on 13.04.
  Daemon:
daemon-version:  0.9.22
can-suspend: yes
can-hibernate:   no
on-battery:  no
on-low-battery:  no
lid-is-closed:   no
lid-is-present:  yes
is-docked:   no

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upower 0.9.22-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Wed Oct 16 15:02:33 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-04-04 (925 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
  MarkForUpload: True
  SourcePackage: upower
  UpgradeStatus: Upgraded to saucy on 2013-10-16 (0 days ago)

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

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

[Desktop-packages] [Bug 1243061] Re: bangla joint letter problem

2013-10-22 Thread shantanu saha

Is it that the default font doesn't support bangla? No

Which one or ones is it that solved your problem? I changed only
standard font to bangla first. but it didn't work. After that i changed
all four to bangl font. I will check all possible combination and let
you know.

do you mind attaching a screenshot of the corrupted text here? I
attached a screenshot of corrupted text in chromium. I post this bug
using firefox. Now i am using chromium.

Not screenshot of corrupted, but of uncorrupted. Sorry I didn't get
this.

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

Title:
  bangla joint letter problem

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

Bug description:
  Bangla joint letters is not corrctly visible in chromium-browser. Bangla 
fonts are already installed. Firefox, google-chrome are working just fine. I am 
attaching a screenshot. Related word should be 
  "দুর্দান্ত বক্তব্য"

  chromium-browser encoding setting is UTF-8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 12:32:54 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
  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''/desktop/gnome/interface/gtk_theme 
= b''

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

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

[Desktop-packages] [Bug 1061195] Re: Can't create EWS or MAPI account

2013-10-22 Thread Giovanni Lovato

Confirmed on Ubuntu 13.10 64bit.

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

Title:
  Can't create EWS or MAPI account

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

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2013-10-22 Thread Ratchanan Srirattanamet

Upgrade to:
gnome-control-center : 3.6.3-0ubuntu45
gnome-settings-daemon : 3.8.5-0ubuntu10

Now Alt+Shift worked. FYI, I've clear the xkb settings before upgrade
(as in comment #159). Is it possible to clear old settings during
upgrade package? (at least in /etc/default/keyboard)

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

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

2013-10-22 Thread Sergio

@William Hua, I have tested latest ppa updates,
1:3.6.3-0ubuntu45ppa1 amd64
3.8.5-0ubuntu10ppa1 amd64

NextGroup issue is now fixed, but CapsLock switching still works incorrectly. 
To sum up:
- setting CapsLock in TextEntry / Switch to next source using now works but 
when switching CAPS mode is also turned on (so it seems like "abc… [CapsLock] 
АБВГД… [CapsLock] abc…", that should be definitely fixed! Note though, 
Shift+CapsLock or Ctrl+CapsLock switches CAPS mode but not layout
- setting CapsLock in Keyboard / Shortcuts / Typing / Switch to next source 
results in Mod2+CapsLock and switching does NOT work
- hitting any modifier (Ctrl, Shift, Alt) switches NumLock light off, but 
CapsLock switches it back, omg :)

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

[Desktop-packages] [Bug 1243532] Re: Custom keyboard shortcuts don't work until logout

2013-10-22 Thread Doug McMahon

At this point the last ver. to work as expected is 3.6.4-0ubuntu19

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

Title:
  Custom keyboard shortcuts don't work until logout

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

Bug description:
  Doesn't affect gnome-shell (no surprise there

  Test case: Create any custom kb binding, try to use, not active
  After a logout will become active

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu10
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 23 01:41:02 2013
  InstallationDate: Installed on 2013-10-03 (20 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1243532] [NEW] Custom keyboard shortcuts don't work until logout

2013-10-22 Thread Doug McMahon

Public bug reported:

Doesn't affect gnome-shell (no surprise there

Test case: Create any custom kb binding, try to use, not active
After a logout will become active

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu10
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Wed Oct 23 01:41:02 2013
InstallationDate: Installed on 2013-10-03 (20 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed saucy third-party-packages

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

Title:
  Custom keyboard shortcuts don't work until logout

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

Bug description:
  Doesn't affect gnome-shell (no surprise there

  Test case: Create any custom kb binding, try to use, not active
  After a logout will become active

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu10
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 23 01:41:02 2013
  InstallationDate: Installed on 2013-10-03 (20 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1235933] Re: Evolution not translated to French

2013-10-22 Thread Lsf_lf

Same problem here, evolution (version 3.8) is in english (german is
preferred) after upgrading from UbuntuGNOME: 13.04 → 13.10 …

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

Title:
  Evolution not translated to French

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  My desktop is set up in the French language, but Evolution is the only
  installed application to be displayed in English. Gnome-language-
  selector doesn't suggest to install any missing package though. This
  is after upgrading to Saucy. It was in French when running Raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct  6 13:25:49 2013
  InstallationDate: Installed on 2010-09-15 (1116 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (919 days ago)

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

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

[Desktop-packages] [Bug 1242243] Re: In fullscreen, the buttons/overlays do not appear

2013-10-22 Thread Jonathan Meek

DOUBLE UPDATE: I would like to clarify that this issue does NOT exist in
VLC. Only fullscreen Totem.

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

Title:
  In fullscreen, the buttons/overlays do not appear

Status in “totem” package in Ubuntu:
  New

Bug description:
  This may be targetting the wrong thing because they do appear on
  another computer. Anyway:

  1. Play video in Totem
  2. Double click to fullscreen said video
  3. Move mouse.

  What happens:
  Nothing.

  What is expected:
  Overlays displaying the scrubber, pause, and leave fullscreen options/buttons 
should appear.

  Now, as I said, I DO NOT have this issue on another computer with
  Saucy installed. This issue also exists on Raring on the machine it's
  being reported on. I believe this may not be Totem that is the issue
  in that case, but I can't think of what else to solidly report the bug
  against.

  Will be more than happy to perform more tests to give more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: totem 3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 20 00:55:48 2013
  InstallationDate: Installed on 2013-08-03 (77 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: totem
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (1 days ago)

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

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

[Desktop-packages] [Bug 1242243] Re: In fullscreen, the buttons/overlays do not appear

2013-10-22 Thread Jonathan Meek

UPDATE: So, I plugged up my laptop to my TV to watch a video and
fullscreened it. Turns out, it prevents the mouse cursor from appearing
(this happened in the single-monitor scenario) but even after moving the
cursor to the non-fullscreened display, the cursor still did not appear.

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

Title:
  In fullscreen, the buttons/overlays do not appear

Status in “totem” package in Ubuntu:
  New

Bug description:
  This may be targetting the wrong thing because they do appear on
  another computer. Anyway:

  1. Play video in Totem
  2. Double click to fullscreen said video
  3. Move mouse.

  What happens:
  Nothing.

  What is expected:
  Overlays displaying the scrubber, pause, and leave fullscreen options/buttons 
should appear.

  Now, as I said, I DO NOT have this issue on another computer with
  Saucy installed. This issue also exists on Raring on the machine it's
  being reported on. I believe this may not be Totem that is the issue
  in that case, but I can't think of what else to solidly report the bug
  against.

  Will be more than happy to perform more tests to give more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: totem 3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 20 00:55:48 2013
  InstallationDate: Installed on 2013-08-03 (77 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: totem
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (1 days ago)

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

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

[Desktop-packages] [Bug 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled

2013-10-22 Thread gsbabil

I have nearly the same problem. I have recently upgraded to 13.10 and
the invisible-mouse-cursor problem immediately affected me. Basically, I
have the following:

- I have no visible cursor inside LightDM during login
- I have no visible cursor inside the Lubuntu session of LXDE. Although I can
click and perform all mouse activities.
- For a brief moment, after successful login between the Lightdm and LXDE
session, I can see the X server's default mouse cursor. But it disappears as
soon as LXDE is started.

I found a rather dumb way of fixing the problem and I have no clue why
it worked.

1. Created a new user called 'dummy'
2. Logged out from my default user session (where the mouse cursor is
invisible). Alternatively you could do 'sudo service restart lightdm' if
clicking the right button becomes tedious due to the "invisible" cursor
3. From LightDM, logged in as 'dummy' - great, mouse cursor is visible here.
4. Logged out from 'dummy' user session
5. From LightDM, Logged in as the default user - voila! mouse cursor is back!

Other tricks that I had tried:

- sudo update-alternatives --display x-cursor-theme ## make sure it is set to
a theme that you have installed on your machine
- Check ~/.config/lxsession/Lubuntu or ~/.config/lxsession/LXDE to make sure
it matches what you have set above

Hope it helps.

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

Title:
Inconsistent cursor visibility with cursor plugin enabled

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

Bug description:
On fresh boots the greeter & desktop may have the cursor visible or may not
until mouse is moved.
On a log out/in the cursor is almost always invisible until mouse is moved.
(unless made visible in greeter screen, then visible on Desktop

This is all well & good, maybe some intentional aesthetics/design
(https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the
cursor never becomes visible.
In that case hitting some keys or context menu can cause it to show, though
most times a log out is needed.
(with the removal of ctrl+alt+delete > log out this means most users will
need to either blindly find the session indicator or hit power button.

When the g-s-d cursor plugin is disabled then the cursor is always
visible, it the plugin has no use in an ubuntu session then maybe it
should be default disabled

There is also the possibility, particularly on ssd drives, of a login
with no session indicator. This occasionally combines with no visible
cursor.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Oct 11 00:38:16 2013
InstallationDate: Installed on 2013-10-03 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1186786] Re: nvidia-173 kernel module fails to build on kernels >= 3.10.x [error: implicit declaration of function ‘create_proc_entry’]

2013-10-22 Thread Daniel Letzeisen

@Dan Muresan: this bug pertains to kernels >= 3.10 and linux-generic-
lts-raring is a 3.8 kernel, so I have a feeling you're not talking about
this bug when you say "all these wonderful changes."

Anyway, this "wonderful change" is already available for precise
(currently  in proposed repo):


nvidia-graphics-drivers-173-updates (173.14.37-0ubuntu0.0.1) precise-proposed; 
urgency=low

  * New upstream release:
- Added support for xserver ABI 14 (xorg-server 1.14).
  * debian/control.in:
- Remove the dependency on the linux headers as with other
  drivers.
- Recommend nvidia-settings-304-updates.
- Add ${misc:Depends}.
  * debian/substvars:
- Add an alternative dependency on xserver-xorg-core-lts-raring.
  (LP: #1198942).
  * Add support for Linux 3.10.
 -- Alberto MiloneFri, 12 Jul 2013 11:12:01 
+0200

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

Title:
  nvidia-173 kernel module fails to build on kernels >= 3.10.x [error:
  implicit declaration of function ‘create_proc_entry’]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  Fix Released

Bug description:
  This bug is raised while attempting to install the nvidia driver onto
  an installation of the daily build from 28-05-2013 with on top the
  3.10.0 kernel. This actions was attempted to check for bug 1185911, to
  check whether or not bug 1185911 is still present int kernel 3.10.0.
  So please handle this bug report together with 1185911.

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

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-173 173.14.37-0ubuntu1
  Uname: Linux 3.10.0-031000rc3-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   56.384552] systemd-hostnamed[2494]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   65.737950] show_signal_msg: 42 callbacks suppressed
   [   65.737958] compiz[2227]: segfault at 0 ip aec73ebe sp bfb81ee0 error 4 
in libnux-4.0.so.0.0.0[aeba8000+166000]
  DKMSKernelVersion: 3.10.0-031000rc3-generic
  Date: Sun Jun  2 20:04:18 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-173, 173.14.37: added
  DuplicateSignature: 
dkms:nvidia-173:173.14.37-0ubuntu1:/var/lib/dkms/nvidia-173/173.14.37/build/nv.c:626:5:
 error: implicit declaration of function ‘create_proc_entry’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. V9520-X/TD/128M [1043:8180]
  InstallationDate: Installed on 2013-05-29 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130528.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  PackageVersion: 173.14.37-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-031000rc3-generic 
root=UUID=59766789-369c-4962-95f0-24be5e6ca9c4 ro recovery nomodeset
  SourcePackage: nvidia-graphics-drivers-173
  Title: nvidia-173 173.14.37-0ubuntu1: nvidia-173 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080009
  dmi.board.name: P4P800SE
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080009:bd01/23/2006:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.45-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.7-0ubuntu1
  ver

[Desktop-packages] [Bug 381017] Re: Cannot drag attachment from mail attachment pane to desktop

2013-10-22 Thread Ninaw de Leon

I'm getting this error when trying to Shift drag from the attachment
pane to my Documents folder:

There was an error getting information about "fetch>UID>.INBOX>2525".

Thunderbird 17.0.8

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in SeaMonkey: all-in-one Internet application suite:
  Confirmed
Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “gnome-common” package in Ubuntu:
  Confirmed
Status in “kde-baseapps” package in Ubuntu:
  Confirmed
Status in “seamonkey” package in Ubuntu:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

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

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

[Desktop-packages] [Bug 1186786] Re: nvidia-173 kernel module fails to build on kernels >= 3.10.x [error: implicit declaration of function ‘create_proc_entry’]

2013-10-22 Thread Dan Muresan

Is anybody backporting (or at least THINKING about backporting) all
these wonderful changes for us plebs on 12.04 LTS using the OFFICIAL
linux-generic-lts-raring series, or do we no longer count as real users,
despite LTS promises from Ubuntu?

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

Title:
  nvidia-173 kernel module fails to build on kernels >= 3.10.x [error:
  implicit declaration of function ‘create_proc_entry’]

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  Fix Released

Bug description:
  This bug is raised while attempting to install the nvidia driver onto
  an installation of the daily build from 28-05-2013 with on top the
  3.10.0 kernel. This actions was attempted to check for bug 1185911, to
  check whether or not bug 1185911 is still present int kernel 3.10.0.
  So please handle this bug report together with 1185911.

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

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-173 173.14.37-0ubuntu1
  Uname: Linux 3.10.0-031000rc3-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   56.384552] systemd-hostnamed[2494]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   65.737950] show_signal_msg: 42 callbacks suppressed
   [   65.737958] compiz[2227]: segfault at 0 ip aec73ebe sp bfb81ee0 error 4 
in libnux-4.0.so.0.0.0[aeba8000+166000]
  DKMSKernelVersion: 3.10.0-031000rc3-generic
  Date: Sun Jun  2 20:04:18 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-173, 173.14.37: added
  DuplicateSignature: 
dkms:nvidia-173:173.14.37-0ubuntu1:/var/lib/dkms/nvidia-173/173.14.37/build/nv.c:626:5:
 error: implicit declaration of function ‘create_proc_entry’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. V9520-X/TD/128M [1043:8180]
  InstallationDate: Installed on 2013-05-29 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130528.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  PackageVersion: 173.14.37-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-031000rc3-generic 
root=UUID=59766789-369c-4962-95f0-24be5e6ca9c4 ro recovery nomodeset
  SourcePackage: nvidia-graphics-drivers-173
  Title: nvidia-173 173.14.37-0ubuntu1: nvidia-173 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080009
  dmi.board.name: P4P800SE
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080009:bd01/23/2006:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.45-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sun Jun  2 18:20:07 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL Dell QuietKey Keyboard KEYBOARD, id 8
   inputsonixb   KEYBOARD, id 9
   inputImExPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

[Desktop-packages] [Bug 1213876] Re: printer not seen by CUPS

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

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

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

Title:
  printer not seen by CUPS

Status in “cups” package in Ubuntu:
  Expired

Bug description:
  Hi
  I am trying to report a bug with Ubuntu 13.04. From the looks of the forum I 
am not the only one with this problem. 

  I use a Dell 1720 level display Vostro with a P8700 64 bit processor @
  2.5GHz. The laptop also has 4GB. Ram & 300Gb. of hard drive. The OS as
  bought is Win7 pro. I use a Canon multifunctional, an MPS560 which has
  a wifi card. Access to the web is via virginmedia fibre link and
  router.

  I upgraded from 12.04-1 to 12.04-2 and then to 13.04, in the hope that
  I would be able to use the multifn. with the upgraded CUPS.

  All three parts work fine on Win7, including ink level display, both
  via USB and the wifi link; so all hardware is OK.

  Using Ubu13.04 and an USB cable all is fine, prints A4 text and DL
  envelopes ok.

  Ink level display does not work but I expected that.  XSane also finds
  the scanner without difficulty.

  With the USB cable removed it is a disaster.
  Xsane cannot see the scanner; Cups thinks the printer is available and sends 
the data, which shows as either 'completed' or 'held' on the 'view print queue' 
app.

  I went to 192.168.0.1 via Firefox found that the MPS is 192.168.0.2
  and the Dell is 192.168.03. I checked MAC and IP for the printer and
  printed them. I then went to the printer and printed the LAN settings,
  all matched the data from 192.168.02.report

  I then pinged both the router and the printer; both returned send
  times of about 2.0 mS. with a max./dev. of about 0.7mS. and returned
  no data losses.

  
  I have also been to CUPS Host:631 via Firefox, this was very interesting but 
unfortunately offered no solution.

  On two occasions whilst attempting to resolve the problem I got auto
  bug reports with a request to send to Ubuntu, which I did.


  Please help!

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

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

[Desktop-packages] [Bug 1215952] Re: nautilus uses 100% cpu and system shuts down

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

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

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

Title:
  nautilus uses 100% cpu and system shuts down

Status in “nautilus” package in Ubuntu:
  Expired

Bug description:
  Nautilus quickly climbs to 100% cpu usage upon login and after
  opening. Causes my system to shut down completely. I have a large
  collection of music, pictures and videos that are symlinked to my home
  folder. Although this should not cause any problems, it does. Killall
  nautilus works fine but cpu goes to 100% after opening nautilus again.
  This only seems to be an issue running nautilus as a user. Opening
  nautilus as a root user (gksudo nautilus) works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Fri Aug 23 10:19:02 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+238+156'"
  InstallationDate: Installed on 2013-08-22 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.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/1215952/+subscriptions

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

[Desktop-packages] [Bug 1216053] Re: PCI/internal sound card not detected

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

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

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

Title:
  PCI/internal sound card not detected

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

Bug description:
  ALSA fails to recognize the internal FCH Azalia Controller (rev 01) in
  my system. It was recognized and worked properly until a bunch of
  updates were installed last night.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Aug 23 10:55:08 2013
  InstallationDate: Installed on 2013-08-22 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-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.:bvr6401:bd07/18/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1243519] [NEW] since upgrade to 13.10, login screen displays Light Display Manager as its own user

2013-10-22 Thread Adam Gomulka

Public bug reported:

Since upgrading to Ubuntu 13.10, Light Display Manager has been listed
as its own user account on the login screen.  I have found a manual
workaround on a forum which involves adding user "lightdm" to the list
of 'hidden-users' in /etc/lightdm/lightdm.conf, but this should still be
addressed, perhaps through a software patch.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lightdm 1.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Wed Oct 23 00:04:07 2013
InstallationDate: Installed on 2013-08-31 (52 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1243519

Title:
  since upgrade to 13.10, login screen displays Light Display Manager as
  its own user

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 13.10, Light Display Manager has been listed
  as its own user account on the login screen.  I have found a manual
  workaround on a forum which involves adding user "lightdm" to the list
  of 'hidden-users' in /etc/lightdm/lightdm.conf, but this should still
  be addressed, perhaps through a software patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 23 00:04:07 2013
  InstallationDate: Installed on 2013-08-31 (52 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

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

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

[Desktop-packages] [Bug 1243517] [NEW] error copying files off camera

2013-10-22 Thread Ian Booth

Public bug reported:

I upgraded from raring to saucy and now I cannot copy photos off my
camera. The camera mounts ok and I can navigate to the files. I select a
file, copy it, and when it is pasted, an error occurs: "Operation not
supported by backend". This appears to me to be a regression in saucy as
it worked just fine in raring before I upgraded.

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

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

Title:
  error copying files off camera

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  I upgraded from raring to saucy and now I cannot copy photos off my
  camera. The camera mounts ok and I can navigate to the files. I select
  a file, copy it, and when it is pasted, an error occurs: "Operation
  not supported by backend". This appears to me to be a regression in
  saucy as it worked just fine in raring before I upgraded.

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

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

[Desktop-packages] [Bug 1240336] Re: Not authorized to perform operation....

2013-10-22 Thread Geoff Hickey

Another vote for comment #19 - solved it for me too. (Thanks!)

I ran into this after a normal update-manager upgrade from 13.04.

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

Title:
  Not authorized to perform operation

Status in “policykit-desktop-privileges” package in Ubuntu:
  Confirmed

Bug description:
  After a new install of 64 bit Ubuntu 13.10 on my second partition, I
  used dpkg to reinstall all the same packages I had on my 32 bit 13.04
  partition.  I copied all my home directory files over and updated all
  the packages.  I now find that I don't have permissions to change the
  network settings; I can't mount my other hard drive or any USB stick
  using nautilus, or (udisks without using sudo)' I can't run synaptic
  by clicking on the GUI (I have to go to a terminal and sudo synaptic);
  etc.  I can't find any documentation on the configuration of
  policykit-desktop-privileges, so I'm filing this bug.  For me it
  appears to be totally broken.  Maybe someone can help me out.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+subscriptions

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

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

can you try hda-analyzer to change those gpio as same as working alsa-
info


-State of AFG node 0x01:
-  Power states:  D0 D1 D2 D3 D3cold S3D3cold CLKSTOP EPSS
-  Power: setting=D0, actual=D0
 GPIO: io=5, o=0, i=0, unsolicited=1, wake=1
-  IO[0]: enable=1, dir=1, wake=0, sticky=0, data=1, unsol=0
+  IO[0]: enable=1, dir=1, wake=0, sticky=0, data=0, unsol=0
   IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
   IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
   IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
   IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso

2013-10-22 Thread Maurice Johnson

Read your post but I can't find "Download ubuntu-12.04-alternate-amd64.iso, 
sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb" 
there are other .iso's  websites i.e 
http://nl.releases.ubuntu.com/precise/
The issue seems to be md5sum failure or sha256sum failure to match. Where can I 
find your version?
Thanks,
M J

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

Title:
  IPv4 connectivity broken after installing from ubuntu-12.04-alternate-
  amd64.iso

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

Bug description:
  [Impact]
  IPv6 is becoming increasingly popular and installations on IPv6-ready 
networks are becoming more frequent; this issue affects installations of the 
Desktop image from the alternate image (or using d-i in any other way) when 
IPv6 autoconfiguration or DHCPv6 is used. These installations will fail to 
recognize that the interface should be managed by NetworkManager after the 
installation because only the "iface X inet dhcp" line would be commented out, 
leaving another valid "iface X" line for "inet6" causing NetworkManager to 
ignore the device. The solution was to comment out all lines in 
/etc/network/interfaces pertaining to interface X: "auto X", "iface X inet", 
and "iface X inet6".

  
  [Test Case]
  1a) With IPv6 autoconfiguration (for example, using radvd) or DHCPv6 
available on the network:
  1b) With no IPv6 available on the network:
  2) Install Ubuntu from the alternate CD; or using d-i via a netboot image.
  3) After the installation:
   a) Verify that NetworkManager properly handles all interfaces.
   b) Verify that the network interfaces configuration is commented out in 
/etc/network/interfaces.

  
  [Regression Potential]
  Untypical configurations may find devices that should be ignored by 
NetworkManager to be handled by it. Standard installations could fail to 
comment the necessary information from /etc/network/interfaces to allow for 
NetworkManager to do is job; or the file could be mangled to remove the "lo" 
interface, which would make unrelated services fail.

  ---

  To reproduce:
  - Download ubuntu-12.04-alternate-amd64.iso, sha256sum: 
f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb
  - Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS 
with UNetbootin
  - Install on a machine with both IPv4 and IPv6 connectivity
  - Log in to the newly installed system

  Current behaviour:
  - There is no IPv4 connectivity
  - NetworkManager doesn't show the wired interface in its dropdown

  Expected behaviour:
  - There is IPv4 connectivity
  - NetworkManager does show the wired interface in its dropdown

  Thoughts:
  I suspect this is because during the install my /etc/network/interfaces was 
created like so:
  ---BEGINS---
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eth0
  iface eth0 inet dhcp
  # This is an autoconfigured IPv6 interface
  iface eth0 inet6 auto
  ---ENDS---

  Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file 
to comment out a single line like so:
  #NetworkManager#iface eth0 inet dhcp

  i.e. the line
  iface eth0 inet6 auto
  remains intact

  This means that the /etc/network/interfaces file gives me IPv6
  connectivity but not IPv4 connectivity.  Furthermore, because there is
  an uncommented iface eth0 inet6 line, NetworkManager doesn't show me
  the interface in its dropdown.

  To fix:
  - The regular expression needs to be changed so that the iface eth0 inet6 
auto line is also commented out

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

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

[Desktop-packages] [Bug 1242193] Re: Xorg freeze "no signal" on display after upgrade to 13.10

2013-10-22 Thread glenn opdycke-hansen

After installing fglrx - Video driver for the AMD graphics accelerators
then video is working again.

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

Title:
  Xorg freeze "no signal" on display after upgrade to 13.10

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After the upgrade of ubuntu to 13.10 there were multiple problems.  There was 
a message that the swap was not ready.  (i believe that the swap was encrypted 
during the original install.)  I followed instructions to change the swap so it 
was not encrypted.  Then the boot would display "no signal" on the reboot.   I 
followed instructions to change the grub settings/params from "quiet splash" to 
"nomodeset".
  Now the system settings cannot detect the monitor (monitor is Acer S211HL)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 19 16:49:29 2013
  DistUpgraded: 2013-10-19 14:47:09,661 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed
   virtualbox, 4.2.16, 3.8.0-32-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:318c]
  InstallationDate: Installed on 2012-08-19 (425 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 004: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
   Bus 001 Device 003: ID 0409:0050 NEC Corp. 7-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP-Pavilion KJ377AA-ABA m8400f
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=85e9196d-79bf-4e9e-94e0-312e68154146 ro nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago)
  dmi.bios.date: 01/29/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.10
  dmi.board.name: Nettle3
  dmi.board.vendor: ECS
  dmi.board.version: 2.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd01/29/2008:svnHP-Pavilion:pnKJ377AA-ABAm8400f:pvr:rvnECS:rnNettle3:rvr2.1:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: KJ377AA-ABA m8400f
  dmi.sys.vendor: HP-Pavilion
  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 N/A
  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: Sat Oct 19 16:33:03 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Unifying Device. Wireless PID:1024 MOUSE, id 8
   inputLogitech Unifying Device. Wireless PID:2011 KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "ati" (module does not exist, 0)
   Failed to load module "modesetting" (module does not exist, 0)
   Failed to load module "ati" (module does not exist, 0)
   Failed to load module "modesetting" (module does not exist, 0)
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2

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

-- 
Mailing list: https://launchpad.net/~d

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

http://www.idt.com/products/audio-products/high-definition-hd-audio-
codecs/92hd91b-single-chip-pc-audio-system-codec-speaker-amplifier-
capless-hp-ldo


Understanding the Audio Processing Algorithms Available in the 92HD9x 
Products


The 92HD9x products featuring a mono output also have a hardware based 
band-pass filter, allowing easy
connection to integrated subwoofers with separate amplifiers.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen

2013-10-22 Thread Jamie Strandboge

+10

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

Title:
  after suspend/resume, the Unity HUD is always open when I unlock the
  screen

Status in Gnome Settings Daemon:
  Won't Fix
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Traveling at a conference, so I'm doing a lot of suspending and
  resuming of my laptop.  Every time I open my laptop back up after
  resume and unlock the desktop, the Unity dash is open.  This does not
  happen if I lock my screen using the "lock screen" hotkey, and does
  not happen if my screen is locked by a lid close event; only when the
  system suspends and resumes.  But it is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  Date: Thu Sep 19 17:51:29 2013
  InstallationDate: Installed on 2010-09-24 (1091 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago)

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

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

[Desktop-packages] [Bug 1243500] [NEW] Poor LibreOffice performance if open upon resuming from suspend (with nvidia graphics driver)

2013-10-22 Thread David

Public bug reported:

Same as bug #185600 or duplicates  Bug #397880  Bug #438080 or  Bug
#606558, except this bug report was produced using terminal.

System:
Ubuntu 13.10
LibreOffice 4.1.2.3
Nvidia-graphics-drivers-304 (nvidia-current as per 2013-10-23)

How to reproduce:
Open a document in LibreOffice (ideally several pages).
Suspend, then resume.
Scroll mouse down in LibreOffice (or try page up/down).
Bug: sluggish behavior, high CPU usage, takes half a second to a second on a 
good machine to execute command (vs. almost immediately normally).

The problem is resolved if libreoffice is completely closed and re-
opened after the resume.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nvidia-current 304.88-0ubuntu8
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Wed Oct 23 04:59:19 2013
InstallationDate: Installed on 2013-10-22 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-304
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug saucy

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

Title:
  Poor LibreOffice performance if open upon resuming from suspend (with
  nvidia graphics driver)

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

Bug description:
  Same as bug #185600 or duplicates  Bug #397880  Bug #438080 or  Bug
  #606558, except this bug report was produced using terminal.

  System:
  Ubuntu 13.10
  LibreOffice 4.1.2.3
  Nvidia-graphics-drivers-304 (nvidia-current as per 2013-10-23)

  How to reproduce:
  Open a document in LibreOffice (ideally several pages).
  Suspend, then resume.
  Scroll mouse down in LibreOffice (or try page up/down).
  Bug: sluggish behavior, high CPU usage, takes half a second to a second on a 
good machine to execute command (vs. almost immediately normally).

  The problem is resolved if libreoffice is completely closed and re-
  opened after the resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-current 304.88-0ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 23 04:59:19 2013
  InstallationDate: Installed on 2013-10-22 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 185600] Re: [Upstream] LibreOffice repeatedly freezes after resuming laptop from sleep

2013-10-22 Thread David

Just installed (clean install) ubuntu 13.10 saucy salamender and sorry
to say the bug is still present.

Tested with LibreOffice version 4.1.2.3
Nvidia-current version 304

Still slow performance of libreoffice if open after resuming from a
suspend

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

Title:
  [Upstream] LibreOffice repeatedly freezes after resuming laptop from
  sleep

Status in Compiz:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-180” package in Ubuntu:
  Incomplete
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  I've used Feisty and Gutsy but this problem has started happening only
  recently.  Here are the steps to reproduce:

  1. Open a document in oowriter.

  2. Put the laptop to sleep.

  3. Resume the laptop.

  Here are the symptoms:

  1. Scrolling in the openoffice document is jerky.  Basically, if I hit
  page up or page down, oowriter freezes for a few seconds and compiz
  grays the oowriter window (to show that the app is not responding),
  eventually oowriter unfreezes, refreshes its screen and is responsive
  again.  If I try to scroll again, the same freeze repeats.

  2. Sometimes oowriter seems to also cause other applications to
  temporarily be unresponsive.  The symptom here is that compiz grays
  *all* the windows on the screen for a few seconds until oowriter
  becomes reponsive again.

  3. No other application freezes like that after resume.  Note that
  symptom 2 above happens *only* when oowriter is running.

  WORKAROUND: Restart OOo/LO.

  WORKAROUND: Turn off compiz.

  + Possibly related to bug 745836.

  OO.org packages installed:

  $ dpkg-query -W openoffice.org-* | gawk '$2 {print;}'
  openoffice.org-base 1:2.3.0-1ubuntu5.3
  openoffice.org-calc 1:2.3.0-1ubuntu5.3
  openoffice.org-common   1:2.3.0-1ubuntu5.3
  openoffice.org-core 1:2.3.0-1ubuntu5.3
  openoffice.org-dev  1:2.3.0-1ubuntu5.3
  openoffice.org-draw 1:2.3.0-1ubuntu5.3
  openoffice.org-evolution1:2.3.0-1ubuntu5.3
  openoffice.org-filter-mobiledev 1:2.3.0-1ubuntu5
  openoffice.org-gnome1:2.3.0-1ubuntu5.3
  openoffice.org-gtk  1:2.3.0-1ubuntu5.3
  openoffice.org-help-en-gb   1:2.3.0-1ubuntu2
  openoffice.org-help-en-us   1:2.3.0-1ubuntu2
  openoffice.org-help-fr  1:2.3.0-1ubuntu2
  openoffice.org-help-hi-in   1:2.3.0-1ubuntu2
  openoffice.org-help-zh-cn   1:2.3.0-1ubuntu2
  openoffice.org-help-zh-tw   1:2.3.0-1ubuntu2
  openoffice.org-hyphenation  0.2
  openoffice.org-impress  1:2.3.0-1ubuntu5.3
  openoffice.org-java-common  1:2.3.0-1ubuntu5.3
  openoffice.org-l10n-common  1:2.3.0-1ubuntu2
  openoffice.org-l10n-en-gb   1:2.3.0-1ubuntu2
  openoffice.org-l10n-en-us   1:2.3.0-1ubuntu5.3
  openoffice.org-l10n-en-za   1:2.3.0-1ubuntu2
  openoffice.org-l10n-fr  1:2.3.0-1ubuntu2
  openoffice.org-l10n-hi-in   1:2.3.0-1ubuntu2
  openoffice.org-l10n-zh-cn   1:2.3.0-1ubuntu2
  openoffice.org-l10n-zh-tw   1:2.3.0-1ubuntu2
  openoffice.org-math 1:2.3.0-1ubuntu5.3
  openoffice.org-style-andromeda  1:2.3.0-1ubuntu5.3
  openoffice.org-style-crystal1:2.3.0-1ubuntu5.3
  openoffice.org-style-default1:2.3.0-1ubuntu5.3
  openoffice.org-style-human  1:2.3.0-1ubuntu5.3
  openoffice.org-style-industrial 1:2.3.0-1ubuntu5.3
  openoffice.org-style-tango  1:2.3.0-1ubuntu5.3
  openoffice.org-thesaurus-en-us  1:2.2.0-2ubuntu1
  openoffice.org-writer   1:2.3.0-1ubuntu5.3

  + Unreproducible in non-Unity Ubuntu 11.04 LibreOffice Writer, suspend
  to RAM via ATI proprietary drivers with Compiz enabled.

  lsb_release -rd
  Description: Ubuntu 11.04
  Release: 11.04

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

  apt-cache policy fglrx
  fglrx:
    Installed: 2:8.840-0ubuntu4
    Candidate: 2:8.840-0ubuntu4
    Version table:
   *** 2:8.840-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/restricted i386 
Packages
  100 /var/lib/dpkg/status

  apt-cache policy compiz
  compiz:
    Installed: 1:0.9.4+bzr20110415-0ubuntu2
    Candidate: 1:0.9.4+bzr20110415-0ubuntu2
    Version table:
   *** 1:0.9.4+bzr20110415-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status

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

Re: [Desktop-packages] [Bug 1240673] Re: Reports 0% charged for fully charged batteries

2013-10-22 Thread Scott Kitterman

On Tuesday, October 22, 2013 08:07:54 you wrote:
> Fixed upstream with a test case:
> http://cgit.freedesktop.org/upower/commit/?id=22da1a0bc Also cherry-picked
> into 0.9 branch.

I rebuilt the package locally with the patch and that (not surprisingly) 
solved the problem.  I think this should, in addition to being fixed in trusty, 
be an SRU for saucy.

Thanks.

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

Title:
  Reports 0% charged for fully charged batteries

Status in “upower” package in Ubuntu:
  Fix Committed

Bug description:
  See the following upower dump:

  $ upower --dump
  Device: /org/freedesktop/UPower/devices/line_power_AC
native-path:  AC
power supply: yes
updated:  Wed 16 Oct 2013 12:58:28 PM EDT (7198 seconds ago)
has history:  no
has statistics:   no
line-power
  online: yes

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   SMP
model:DELL Y61CV22
serial:   3840
power supply: yes
updated:  Wed 16 Oct 2013 12:58:33 PM EDT (7193 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  energy:  66.6 Wh
  energy-empty:0 Wh
  energy-full: 66.6 Wh
  energy-full-design:  66.6 Wh
  energy-rate: 0.0111 W
  voltage: 12.836 V
  percentage:  0%
  capacity:76.9167%
  technology:  lithium-ion

  Device: /org/freedesktop/UPower/devices/battery_BAT2
native-path:  BAT2
vendor:   Samsung SDI
model:DELL W1GGM26
serial:   12515
power supply: yes
updated:  Wed 16 Oct 2013 12:58:33 PM EDT (7193 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  energy:  31.08 Wh
  energy-empty:0 Wh
  energy-full: 31.08 Wh
  energy-full-design:  31.08 Wh
  energy-rate: 0.0111 W
  voltage: 12.428 V
  percentage:  0%
  capacity:81.2857%
  technology:  lithium-ion

  Note that state is fully-charged, but percentage is o% on both batteries.  
This worked fine on 13.04.
  Daemon:
daemon-version:  0.9.22
can-suspend: yes
can-hibernate:   no
on-battery:  no
on-low-battery:  no
lid-is-closed:   no
lid-is-present:  yes
is-docked:   no

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upower 0.9.22-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Wed Oct 16 15:02:33 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-04-04 (925 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
  MarkForUpload: True
  SourcePackage: upower
  UpgradeStatus: Upgraded to saucy on 2013-10-16 (0 days ago)

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

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

[Desktop-packages] [Bug 1111884] Re: nouveau fails at suspend/resume - PAGE_NOT_PRESENT

Launchpad has imported 33 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=67878.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-08-07T21:48:12+00:00 Ben Gamari wrote:

Created attachment 83798
dmesg output from boot to attempted resume

On a Dell Latitude E6400 with nVidia G98M and 3.10 kernel I find that
the machine will reproducibly resume from suspend with a non-responsive
X session. Given attempts I can eventually get to a somewhat functional
VT. dmesg output attached.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/16


On 2013-08-07T21:49:13+00:00 Ben Gamari wrote:

lspci gives the following device details,

01:00.0 VGA compatible controller: NVIDIA Corporation G98M [Quadro NVS 160M] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device 0233
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f500 (32-bit, non-prefetchable) [size=16M]
Memory at e000 (64-bit, prefetchable) [size=256M]
Memory at f200 (64-bit, non-prefetchable) [size=32M]
I/O ports at df00 [size=128]
[virtual] Expansion ROM at f400 [disabled] [size=128K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting 
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 

Kernel driver in use: nouveau

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/17


On 2013-08-07T21:50:00+00:00 Ben Gamari wrote:

It seems that Bug #62835
(https://bugs.freedesktop.org/show_bug.cgi?id=62835) might be related.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/18


On 2013-08-07T21:58:19+00:00 Ben Gamari wrote:

This thread might also be related http://www.spinics.net/lists/dri-
devel/msg32782.html.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/20


On 2013-08-07T22:23:06+00:00 Ben Gamari wrote:

Created attachment 83799
End of log from resume with debug=trace

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/21


On 2013-08-09T01:59:54+00:00 Ben Gamari wrote:

It seems 3D/compositing might be to blame here; suspending while running
metacity seems to resume correctly.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/22


On 2013-08-09T02:09:50+00:00 Ben Gamari wrote:

The same issue can be reproduced with 3.8.

Interestingly, 3.5 seems to work correctly, even with compiz.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/23


On 2013-08-09T02:24:17+00:00 Ben Gamari wrote:

>From discussions with xexaxo in #nouveau, it seems that this might be a
similar regression to what happened in 3.8 (described in bug #59057). My
plan is as follows,

 1) Verify that 3.8.11 works
 1.1) If not, verify that 3.8.1 works and bisect to find the broken release
 1.2) If so, check whether 3.9 works
 2) Bisect backwards from the first broken release to 3.8.11 (or whichever 
release was tested to work)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/24


On 2013-08-09T14:58:28+00:00 Ben Gamari wrote:

The 3.8.11 kernel fails in the same way that 3.10 does, trying 3.8.1
next.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/884/comments/25


On 2013-08-09T16:13:55+00:00 Ben Gamari wrote:

Rereading bugs #59057 and #62835, it's not entirely clear whether the
bug was actually ever fixed; it may be that the reporter simply worked
around it. Comment #33 of Bug #59057
(https://bugs.freedesktop.org/show_bug.cgi?id=59057#c33) actually refers
to commit e5a58edc94a20a7ef4b7db67c166c4ca0588b

[Desktop-packages] [Bug 1115669] Re: GNOME Printer Setup Tool: List of discovered printers should better describe duplicate entries

** Changed in: gnome-control-center
   Importance: High => Wishlist

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

Title:
  GNOME Printer Setup Tool: List of discovered printers should better
  describe duplicate entries

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

Bug description:
  When adding a printer a list of discovered printers is shown. If there
  are duplicate entries, for example if the same network printer is
  discovered with different network protocols (LPD, IPP, ...), these
  entries are usually grouped into one by using the D-Bus service of
  system-config-printer. system-config-printer groups entries coming
  from the network connection of the printer and groups entries coming
  from the USB connection of the printer, but it does not group network
  results with USB results, as system-config-printer separates them by a
  tree view. This means that when one connects one printer by both
  network and USB one gets two entries, one generated from all
  appearances under the discovered network printers and one from all
  appearances under the discovered USB printers (and if theis printer
  does Bluetooth there would be a third entry). Now the g-c-c printer
  tool lists these entries as

  
  -2

  This way the user does not know which is the network printer and which
  is the USB printer. The results dhould look like

   (USB)
   (Network)

  To reproduce connect a printer with both network and USB (or
  Bluetooth) input by both network and USB, then try to set it up with
  the preferred connection type.

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

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

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

2013-10-22 Thread Romano Giannetti

Tested (sorry for the comment below). Works for me with Alt+Shift_L
THANKS!

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

[Desktop-packages] [Bug 1014897] Re: [sound-nua] sound preference does not provide ac3 passthrough spdif in 5.1 speaker test

** Summary changed:

- [ASRock A75M-ITX, Realtek ALC892, Grey SPDIF Out, Rear] Surround output not 
working
+ [sound-nua] sound preference does not provide ac3 passthrough spdif in 5.1 
speaker test

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

Title:
  [sound-nua] sound preference does not provide ac3 passthrough spdif in
  5.1 speaker test

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

Bug description:
  This sound card (Realtek ALC892) is 7.1 channel capable via the digital out 
(SPDIF).
  However, Ubuntu is not recognizing it as such and on the sound configuration 
we can only see the stereo parameters (right and left).
  As you can see in the attached picture, the rear and subwoofer parameters are 
grayed out, as if the card didn't support it.

  I have connected it to a 5.1 amplifier and played a DTS suround file.
  Unfortunately the sound coming out is simply stereo. No 5.1 surround.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jabss  1592 F pulseaudio
jabss  3738 F alsamixer
   /dev/snd/controlC0:  jabss  1592 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfef44000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfef4 irq 16'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,18498892,00100302'
 Controls  : 40
 Simple ctrls  : 19
  Date: Tue Jun 19 00:29:21 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: Only some of outputs are working
  Title: [To Be Filled By O.E.M., Realtek ALC892, Grey SPDIF Out, Rear] 
Playback problem
  UpgradeStatus: Upgraded to precise on 2012-04-27 (52 days ago)
  dmi.bios.date: 02/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: A75M-ITX
  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.50:bd02/09/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75M-ITX: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.

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

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

[Desktop-packages] [Bug 1241881] Re: gnome-keyring depends on transitional package libgcr-3-1

2013-10-22 Thread Logan Rosen

I added a rationale. Impact really isn't necessary here.

** Description changed:

  According its package description, libgcr-3-1 version 3.8.2-4 in Saucy
  Salamander is a transitional package that should be safe to remove.
  However, an attempt to remove the package reveals that gnome-keyring
  (version 3.8.2-0ubuntu3) depends on it. I cannot tell if removing the
  dependency from gnome-keyring was forgotten or libgcr-3-1 has been
  wrongfully marked as transitional, but the latter seems highly unlikely.
  Either way this is a problem that should be fixed.
+ 
+ [Rationale]
+ People should be able to remove transitional packages without removing the 
packages that depend on their replacements. This is forbidding people from 
removing libgcr-3-1 without removing gnome-keyring as well.
  
  [Test Case]
  Install the gnome-keyring package, and then try removing the transitional 
libgcr-3-1 package. It forces the removal of gnome-keyring, even though 
gnome-keyring should depend on libgcr-base-3-1 instead.
  
  [Regression Potential]
  None. This is just a simple dependency change.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-keyring 3.8.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 19 01:43:15 2013
  InstallationDate: Installed on 2010-09-07 (1137 days ago)
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901)
  MarkForUpload: True
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

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

Title:
  gnome-keyring depends on transitional package libgcr-3-1

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

Bug description:
  According its package description, libgcr-3-1 version 3.8.2-4 in Saucy
  Salamander is a transitional package that should be safe to remove.
  However, an attempt to remove the package reveals that gnome-keyring
  (version 3.8.2-0ubuntu3) depends on it. I cannot tell if removing the
  dependency from gnome-keyring was forgotten or libgcr-3-1 has been
  wrongfully marked as transitional, but the latter seems highly
  unlikely. Either way this is a problem that should be fixed.

  [Rationale]
  People should be able to remove transitional packages without removing the 
packages that depend on their replacements. This is forbidding people from 
removing libgcr-3-1 without removing gnome-keyring as well.

  [Test Case]
  Install the gnome-keyring package, and then try removing the transitional 
libgcr-3-1 package. It forces the removal of gnome-keyring, even though 
gnome-keyring should depend on libgcr-base-3-1 instead.

  [Regression Potential]
  None. This is just a simple dependency change.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-keyring 3.8.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 19 01:43:15 2013
  InstallationDate: Installed on 2010-09-07 (1137 days ago)
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901)
  MarkForUpload: True
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

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

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

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

2013-10-22 Thread Marc Deslauriers

This is CVE-2013-4459

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-4459

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

Title:
  lightdm no longer runs guest session through wrapper

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 19:51:27 2013
  InstallationDate: Installed on 2011-10-27 (726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

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

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

[Desktop-packages] [Bug 739184] Re: [Libreoffice] Mnemonics do not work in Unity

2013-10-22 Thread Max Barry

I don't understand how this bug can persist throughout several Ubuntu
releases. It means Ubuntu doesn't have a functional office suite. You
have to choose between the Alt key or the windowing: only one will work.
(Without libreoffice-gtk, you can't maximize properly.) Is that not seen
as a major issue?

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

Title:
  [Libreoffice] Mnemonics do not work in Unity

Status in LibreOffice Productivity Suite:
  Won't Fix
Status in “indicator-appmenu” package in Ubuntu:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When lo-menubar is installed and LibreOffice is open with a document,
  the keyboard shortcuts to access menus like Alt + F for file etc do
  not work. Menu keyboard shortcuts are working for other apps via
  indicator-menu.

  WORKAROUND: Disable the global menu by removing the package
  "libreoffice-gtk".

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

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

[Desktop-packages] [Bug 1225895] Re: HUD activated upon return from lock screen

2013-10-22 Thread Jarred Casley

Also affects me. Happens on my Lenovo X1 Carbon when i close the lid to
sleep, open and type my password to log back in. Disabling HUD by
removing its keybinding prevents this.

- Ubuntu 13.10

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

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

Title:
  HUD activated upon return from lock screen

Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  When returning to the desktop from the lock screen by entering the
  user password, the HUD is activated as if the ALT key had been
  pressed.

  13.10 daily

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-power-manager 3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Mon Sep 16 09:39:06 2013
  InstallationDate: Installed on 2013-09-14 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130911)
  MarkForUpload: True
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2013-10-22 Thread Ara Pulido

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => Confirmed

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

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

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

Bug description:
  Steps to reproduce:

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen

2013-10-22 Thread Stephen M. Webb

** Changed in: unity
Milestone: 7.2.0 => None

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

Title:
  after suspend/resume, the Unity HUD is always open when I unlock the
  screen

Status in Gnome Settings Daemon:
  Won't Fix
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Traveling at a conference, so I'm doing a lot of suspending and
  resuming of my laptop.  Every time I open my laptop back up after
  resume and unlock the desktop, the Unity dash is open.  This does not
  happen if I lock my screen using the "lock screen" hotkey, and does
  not happen if my screen is locked by a lid close event; only when the
  system suspends and resumes.  But it is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  Date: Thu Sep 19 17:51:29 2013
  InstallationDate: Installed on 2010-09-24 (1091 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago)

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

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

[Desktop-packages] [Bug 1243484] [NEW] Incorrect handling of orientation when printing PDF files

2013-10-22 Thread Stephane Peter

Public bug reported:

There seems to be some problems in the CUPS filters handling PDF files,
which can be shown without having an actual printer hooked up (this
seems to be independent of the driver in use).

This happens on the latest Ubuntu 13.10 but I believe the real culprit
is in the cups-filters 1.0.40 package.

This happens when trying to print a PDF file (such as the CUPS test page
in /usr/share/cups/data/default.pdf) and trying to change its
orientation with the 'landscape' option, as such :

lp -d queue -o landscape /usr/share/cups/data/default.pdf

The result right now would be that the job is upside down, instead of
being in a landscape orientation.

This happens regardless of the driver. The same behavior doesn't happen
for documents such as PostScript files, which works as expected, at
least with a PS printer.

The easiest way to test this is to set up queues that print to file
(enable FileDevice in the CUPS config first) and look at the resulting
files with a document viewer such as evince :

- Create a new Generic Postscript queue using the default drivers, set it to 
print to a URI such as file:///tmp/test.ps
- Send a PDF job to the queue with the landscape option
- Look at the output in evince or Ghostview

I strongly suspect something is amiss with the pdftopdf filter's
handling of these options, especially in v1.0.40. Fedora 19 didn't
exhibit the same problem until the cups-filters package was brought up
to the same version just today.

I also suspect that more than the orientation options are affected, we
have had reports from customers having trouble with options handled
through the Collate PPD options.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: raring saucy

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

Title:
  Incorrect handling of orientation when printing PDF files

Status in “cups-filters” package in Ubuntu:
  New

Bug description:
  There seems to be some problems in the CUPS filters handling PDF
  files, which can be shown without having an actual printer hooked up
  (this seems to be independent of the driver in use).

  This happens on the latest Ubuntu 13.10 but I believe the real culprit
  is in the cups-filters 1.0.40 package.

  This happens when trying to print a PDF file (such as the CUPS test
  page in /usr/share/cups/data/default.pdf) and trying to change its
  orientation with the 'landscape' option, as such :

  lp -d queue -o landscape /usr/share/cups/data/default.pdf

  The result right now would be that the job is upside down, instead of
  being in a landscape orientation.

  This happens regardless of the driver. The same behavior doesn't
  happen for documents such as PostScript files, which works as
  expected, at least with a PS printer.

  The easiest way to test this is to set up queues that print to file
  (enable FileDevice in the CUPS config first) and look at the resulting
  files with a document viewer such as evince :

  - Create a new Generic Postscript queue using the default drivers, set it to 
print to a URI such as file:///tmp/test.ps
  - Send a PDF job to the queue with the landscape option
  - Look at the output in evince or Ghostview

  I strongly suspect something is amiss with the pdftopdf filter's
  handling of these options, especially in v1.0.40. Fedora 19 didn't
  exhibit the same problem until the cups-filters package was brought up
  to the same version just today.

  I also suspect that more than the orientation options are affected, we
  have had reports from customers having trouble with options handled
  through the Collate PPD options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1243484/+subscriptions

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

[Desktop-packages] [Bug 1222661] Re: deja-dup: failed with an unknown error: AssertionError: [(('README', ) reg), (('README', ) reg), (('README', ) reg)]

2013-10-22 Thread Disk1of5

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

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

Title:
  deja-dup: failed with an unknown error: AssertionError: [(('README',)
  reg), (('README',) reg), (('README',) reg)]

Status in Duplicity - Bandwidth Efficient Encrypted Backup:
  New
Status in “duplicity” package in Ubuntu:
  Confirmed

Bug description:
  deja-dup is failing consistently during backup.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: duplicity 0.6.21-0ubuntu1.1
  Uname: Linux 3.11.0-031100-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Sep  9 08:23:26 2013
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/duplicity
  InstallationDate: Installed on 2013-08-27 (12 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to raring on 2013-09-06 (2 days ago)

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

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

[Desktop-packages] [Bug 1243480] [NEW] evince no input in print dialog/insufficient logging

2013-10-22 Thread Karl-Philipp Richter

Public bug reported:

in evince 3.10.0 I have no possibilty to enter numbers into the pages field of 
the printing dialog. This is possibly related to another component than evince, 
but the log says 

WARNING **: Unimplemented action: POPPLER_ACTION_UNKNOWN, please post a bug 
report in Evince bugzilla (http://bugzilla.gnome.org) with a testcase.

This is not bugzilla.gnome.org and I don't have a testcase, but I guess it's 
worth mentioning. 
The issue is possibly related to missing permissions on a file 
(/home/richter/.config/gtk-3.0/settings.ini which is not very certain (see 
below) or another). The complete log is: 


(evince:4400): Gtk-WARNING **: Failed to parse
/home/richter/.config/gtk-3.0/settings.ini: Keine Berechtigung

(evince:4400): Gtk-WARNING **: Attempting to read the recently used
resources file at `/home/richter/.local/share/recently-used.xbel', but
the parser failed: Failed to open file '/home/richter/.local/share
/recently-used.xbel': Keine Berechtigung.

(evince:4400): EvinceDocument-CRITICAL **: ev_document_get_n_pages:
assertion 'EV_IS_DOCUMENT (document)' failed

** (evince:4400): WARNING **: Unimplemented action:
POPPLER_ACTION_UNKNOWN, please post a bug report in Evince bugzilla
(http://bugzilla.gnome.org) with a testcase.

** (evince:4400): WARNING **: Unimplemented action:
POPPLER_ACTION_UNKNOWN, please post a bug report in Evince bugzilla
(http://bugzilla.gnome.org) with a testcase.

(evince:4400): Gtk-WARNING **: Attempting to store changes into
`/home/richter/.local/share/recently-used.xbel', but failed: Failed to
create file '/home/richter/.local/share/recently-used.xbel.Y8SC5W':
Keine Berechtigung

(evince:4400): Gtk-WARNING **: Attempting to set the permissions of
`/home/richter/.local/share/recently-used.xbel', but failed: Keine
Berechtigung

** (evince:4400): WARNING **: Unimplemented action:
POPPLER_ACTION_UNKNOWN, please post a bug report in Evince bugzilla
(http://bugzilla.gnome.org) with a testcase.

** (evince:4400): WARNING **: Keine Berechtigung


(keine Berechtigung means no permission)

The permission issue is not clear. 
ls -la /home/richter/.config/gtk-3.0/settings.ini 
returns 
-rwxrwxrwx 1 richter richter 192 Jan 28  2013 
/home/richter/.config/gtk-3.0/settings.ini
where richter is the user executing evince.

ls -la /home/richter/.local/share/
returns

insgesamt 15620
drwx-- 44 richter richter  12288 Okt 23 03:17 .
drwx--  4 richter richter   4096 Jul 14 13:49 ..
drwxrwxr-x  3 richter richter   4096 Jul 14 15:30 akonadi
drwx--  4 richter richter   4096 Okt 18 21:54 applications
-rw---  1 richter richter  0 Mai  6  2011 .converted-launchers
drwxrwxr-x  4 richter richter   4096 Jun 30 19:59 data
drwx--  2 richter richter   4096 Okt 16 00:11 desktop-directories
drwxrwxr-x  2 richter richter   4096 Mai  1 11:32 diffuse
drwx--  7 richter richter   4096 Okt 11 23:56 evolution
drwx--  2 richter richter   4096 Okt 24  2012 folks
drwx--  3 richter richter   4096 Jan 20  2013 gegl-0.2
drwx--  3 richter richter   4096 Okt 24  2012 glchess
drwx--  3 richter richter   4096 Okt 24  2012 glipper
drwxr-xr-x  2 richter richter   4096 Apr 28 12:07 gnome-settings-daemon
drwx--  2 richter richter   4096 Jul 12 16:06 gnome-shell
-rw-r--r--  1 richter richter   1495 Okt 20 17:09 gsettings-data-convert
drwxr-xr-x  3 richter richter   4096 Jul  2 00:48 gstreamer-1.0
drwx--  2 richter richter   4096 Okt 23 03:32 gvfs-metadata
drwx--  2 richter richter   4096 Sep 14 19:24 icc
drwx--  4 richter richter   4096 Okt 31  2012 icons
drwxrwxr-x  2 richter richter   4096 Okt 23 03:25 keyrings
drwx--  2 richter richter   4096 Nov  9  2012 latexila
drwx--  2 richter richter   4096 Okt 24  2012 libgda
drwxrwxr-x  4 richter richter   4096 Jul 12 14:03 marble
drwx--  2 richter richter   4096 Okt 27  2012 mc
drwx--  9 richter richter   4096 Aug  8 18:35 mime
drwx--  3 richter richter   4096 Apr 27 12:00 nautilus
drwxr-xr-x  4 richter richter   4096 Okt 21 01:03 orca
drwx--  2 richter richter   4096 Jan  5  2013 pitivi
drwxrwxr-x  2 richter richter   4096 Okt 16 00:11 pixmaps
drwx--  2 richter richter   4096 Okt 23 00:09 previews
-rw---  1 richter richter   3811 Okt 23 03:17 recently-used.xbel
-rw---  1 richter richter218 Apr 14  2012 recently-used.xbel.0ED0CW
-rw---  1 richter richter 187129 Sep  4  2011 recently-used.xbel.0H5G1V
-rw---  1 richter richter 240591 Jun  3  2011 recently-used.xbel.195KWV
-rw---  1 richter richter 302028 Jun 16  2011 recently-used.xbel.1RA8WV
-rw---  1 richter richter 236357 Mai 31  2011 recently-used.xbel.1ZTBWV
-rw---  1 richter richter 291365 Jul 15  2011 recently-used.xbel.28XFYV
-rw---  1 richter richter919 Nov 27  2012 recently-used.xbel.2U3HOW
-rw---  1 richter richter 236233 Mai 31  2011 recently-used.xbel.38GNWV
-rw---  1 richter richter 308474 Jun 28  2011 recently-used.xbel.3B4IXV
-rw---  1 richter richter 272572 Jul

[Desktop-packages] [Bug 1199763] Re: rhythmbox crashed with SIGSEGV in g_type_check_instance()

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

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

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

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

Title:
  rhythmbox crashed with SIGSEGV in g_type_check_instance()

Status in “rhythmbox” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10 . RB Crashed while scanning my Music Collection for the
  first time .

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Wed Jul 10 14:21:11 2013
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2013-07-10 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ffe40711499 : mov
(%rax),%rdi
   PC (0x7ffe40711499) ok
   source "(%rax)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handlers_unblock_matched () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/librhythmbox-core.so.7
   ?? () from /usr/lib/librhythmbox-core.so.7
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen

2013-10-22 Thread Stephen M. Webb

If Gnome will not fix this brokenness on the grounds that it isn't a
problem in Gnome Shell and may be rewritten at some vague time in the
future to support a Wayland compositor, can we just distro-patch gnome-
settings-daemon to return to sanity?

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

Title:
  after suspend/resume, the Unity HUD is always open when I unlock the
  screen

Status in Gnome Settings Daemon:
  Won't Fix
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Traveling at a conference, so I'm doing a lot of suspending and
  resuming of my laptop.  Every time I open my laptop back up after
  resume and unlock the desktop, the Unity dash is open.  This does not
  happen if I lock my screen using the "lock screen" hotkey, and does
  not happen if my screen is locked by a lid close event; only when the
  system suspends and resumes.  But it is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  Date: Thu Sep 19 17:51:29 2013
  InstallationDate: Installed on 2010-09-24 (1091 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago)

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

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

[Desktop-packages] [Bug 1243474] [NEW] clicking and draging to move a folder make window scroll.

2013-10-22 Thread Shunsuke Akagi

Public bug reported:

When I click a folder and drag to one folder right above to move it into the 
folder, window scrolls up all the way and I cannnot move it.
First of all absense of tree view is pretty bad but that's a spec problem. But 
this jumping around issue would be a bug.
Another problem is when I move a file/folder, the window become blank and I 
cannot do anything while it is blank.
There are too many problem/complaints to report for 13.10 numbering 
upgrade/practical downgrade.

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

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

Title:
  clicking and draging to move a folder make window scroll.

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When I click a folder and drag to one folder right above to move it into the 
folder, window scrolls up all the way and I cannnot move it.
  First of all absense of tree view is pretty bad but that's a spec problem. 
But this jumping around issue would be a bug.
  Another problem is when I move a file/folder, the window become blank and I 
cannot do anything while it is blank.
  There are too many problem/complaints to report for 13.10 numbering 
upgrade/practical downgrade.

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

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

[Desktop-packages] [Bug 1014897] Re: [ASRock A75M-ITX, Realtek ALC892, Grey SPDIF Out, Rear] Surround output not working

[sound-nua] does not provide ac3 passthrough spdif in 5.1 speaker test
in sound preference

** Package changed: alsa-driver (Ubuntu) => gnome-control-center
(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/1014897

Title:
  [ASRock A75M-ITX, Realtek ALC892, Grey SPDIF Out, Rear] Surround
  output not working

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

Bug description:
  This sound card (Realtek ALC892) is 7.1 channel capable via the digital out 
(SPDIF).
  However, Ubuntu is not recognizing it as such and on the sound configuration 
we can only see the stereo parameters (right and left).
  As you can see in the attached picture, the rear and subwoofer parameters are 
grayed out, as if the card didn't support it.

  I have connected it to a 5.1 amplifier and played a DTS suround file.
  Unfortunately the sound coming out is simply stereo. No 5.1 surround.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jabss  1592 F pulseaudio
jabss  3738 F alsamixer
   /dev/snd/controlC0:  jabss  1592 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfef44000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfef4 irq 16'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,18498892,00100302'
 Controls  : 40
 Simple ctrls  : 19
  Date: Tue Jun 19 00:29:21 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: Only some of outputs are working
  Title: [To Be Filled By O.E.M., Realtek ALC892, Grey SPDIF Out, Rear] 
Playback problem
  UpgradeStatus: Upgraded to precise on 2012-04-27 (52 days ago)
  dmi.bios.date: 02/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: A75M-ITX
  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.50:bd02/09/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75M-ITX: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.

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

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

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

[sound-nua] does not provide 5.1 ac3 passthrough in speaker test in
sound preference

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1037357] Re: at-spi2-registryd crashed with SIGSEGV in register_client()

** Changed in: at-spi
   Status: Unknown => New

** Changed in: at-spi
   Importance: Unknown => Medium

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

Title:
  at-spi2-registryd crashed with SIGSEGV in register_client()

Status in Assistive Technology Service Provider Interface:
  New
Status in “at-spi2-core” package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: at-spi2-core 2.5.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Wed Aug 15 20:21:02 2012
  ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1)
  ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb77305bf : mov0x8(%eax),%eax
   PC (0xb77305bf) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: at-spi2-core
  Stacktrace:
   #0  0xb77305bf in main ()
   No symbol table info available.
  StacktraceTop: main ()
  Title: at-spi2-registryd crashed with SIGSEGV in main()
  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/at-spi/+bug/1037357/+subscriptions

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

[Desktop-packages] [Bug 1127855] Re: [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost option, mic's very quiet.

you have to open new report if your notebook does not have same hda
codec , same init_pin_config, same number of speakers , jacks and mics

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

Title:
  [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost
  option, mic's very quiet.

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

Bug description:
  I tried options model=dell-3stack, model=laptop, model=dell-bios... no
  changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crazyden   4281 F mixer_applet2
crazyden   4318 F pulseaudio
   /dev/snd/pcmC0D0p:   crazyden   4318 F...m pulseaudio
  Date: Sun Feb 17 10:52:11 2013
  InstallationDate: Installed on 2012-07-20 (211 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Mic, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [MXG071, SigmaTel STAC9228, Mic, Internal] volume slider problem
  UpgradeStatus: Upgraded to quantal on 2013-02-12 (4 days ago)
  dmi.bios.date: 04/23/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0KX412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/23/2010:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn0KX412:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXG071
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-02-16T18:38:21.761644

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

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

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

2013-10-22 Thread Craig Setera

I've just validated that

sudo nmcli nm sleep false

works for me after suspend

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

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

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

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

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

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

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

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

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

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

2013-10-22 Thread Avi Schwartz

The latest PPA version fixed the problem for me. I can now use Alt-Space
and Alt-Shift-Space to switch to next and previous keyboards.

1:3.6.3-0ubuntu45ppa1   amd64
3.8.5-0ubuntu10ppa1 amd64

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

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

>  the ESI U46DJ is now recognized as a Surround device, which it isn't.

U46DJ is a 4-in 6-out multi-channel audio interface. The mix output and
the 2 phono inputs make the unit a perfect portable solution for digital
DJs, compatible with all major DJ software applications.

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

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

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

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10

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

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

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

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

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

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

  Regards.

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

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

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

[Desktop-packages] [Bug 1037357] Re: at-spi2-registryd crashed with SIGSEGV in register_client()

2013-10-22 Thread Luke Yelavich

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

** Also affects: at-spi via
   https://bugzilla.gnome.org/show_bug.cgi?id=710689
   Importance: Unknown
   Status: Unknown

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

Title:
  at-spi2-registryd crashed with SIGSEGV in register_client()

Status in Assistive Technology Service Provider Interface:
  Unknown
Status in “at-spi2-core” package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: at-spi2-core 2.5.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Wed Aug 15 20:21:02 2012
  ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1)
  ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb77305bf : mov0x8(%eax),%eax
   PC (0xb77305bf) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: at-spi2-core
  Stacktrace:
   #0  0xb77305bf in main ()
   No symbol table info available.
  StacktraceTop: main ()
  Title: at-spi2-registryd crashed with SIGSEGV in main()
  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/at-spi/+bug/1037357/+subscriptions

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

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

2013-10-22 Thread Pablo180

Ian, just checked and no I didn't! I'll try it again next resume.

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 885542]

2013-10-22 Thread Jim

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

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

Title:
  thunderbird email search should begin with the most recent email then
  progress to the oldest (what the user is searching for is more likely
  to be in recent rather than older emails)

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

Bug description:
  This becomes more problematic the more email a user has to search.
  With a large account, this can result in very long search times, which
  users are more likely to understand if the email is old. If it is a
  recent email, users expect to see the search result more quickly.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0.1+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1977 F pulseaudio
  BuildID: 20110929183320
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f1506e,17aa21da,0010 
HDA:80862805,80860101,0010'
 Controls  : 20
 Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
 Mixer name : 'ThinkPad EC (unknown)'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: release
  Date: Wed Nov  2 20:02:56 2011
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.102  
metric 2
  Prefs:
   places.database.lastMaintenance - 1320169182
   extensions.lastAppVersion - 7.0.1
   network.cookie.prefsMigrated - true
   gfx.blacklist.suggested-driver-version - Mesa 7.10.3
   places.history.expiration.transient_current_max_pages - 121141
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929183320 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (17 days ago)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET42WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  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:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1210852] Re: gvfsd-http assert failure in g_error_free()

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

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

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

Title:
  gvfsd-http assert failure in g_error_free()

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

Bug description:
  n/a

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu6
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/gvfs/gvfsd-http': munmap_chunk(): 
invalid pointer: 0x7f6a20ffea90 ***
  CrashCounter: 1
  Date: Sat Aug 10 21:54:49 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-http
  InstallationDate: Installed on 2013-07-28 (12 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spaw/2
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f6a205d26a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (action=3, str=0x7f6a205d2a18 "munmap_chunk(): invalid 
pointer", ptr=) at malloc.c:4902
   g_error_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-http assert failure: *** Error in `/usr/lib/gvfs/gvfsd-http': 
munmap_chunk(): invalid pointer: 0x7f6a20ffea90 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1243460] Re: package nvidia-prime 0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2013-10-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-prime 0.4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

Bug description:
  trying to fix a lack of graphics - after login I get a black screen covered 
with white dots.
  So i tried to remove bumblebee and install nvidia-prime

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-prime 0.4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Tue Oct 22 19:25:55 2013
  DuplicateSignature: package:nvidia-prime:0.4:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-10-21 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

2013-10-22 Thread Ian Nicholson

On 10/22/2013 05:50 PM, Pablo180 wrote:
> I'd just like to add that I have this problem, not on suspend (which I
> haven't tried since upgrading) but each and every time I resume from
> hibernate. I have to 'killall NetworkManager' to get networking back -
> every time.
>
> nmcli nm sleep false - didn't work for me.
>
Did you run it with sudo?

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:

  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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

[Desktop-packages] [Bug 1243460] [NEW] package nvidia-prime 0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2013-10-22 Thread Rabin Guha

Public bug reported:

trying to fix a lack of graphics - after login I get a black screen covered 
with white dots.
So i tried to remove bumblebee and install nvidia-prime

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: nvidia-prime 0.4
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Tue Oct 22 19:25:55 2013
DuplicateSignature: package:nvidia-prime:0.4:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-10-21 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: nvidia-prime
Title: package nvidia-prime 0.4 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 saucy

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

Title:
  package nvidia-prime 0.4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

Bug description:
  trying to fix a lack of graphics - after login I get a black screen covered 
with white dots.
  So i tried to remove bumblebee and install nvidia-prime

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-prime 0.4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Tue Oct 22 19:25:55 2013
  DuplicateSignature: package:nvidia-prime:0.4:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-10-21 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

did the switch at your u46DJ as Mic/line/phono ?

did the output of lsusb - change when you switch those switch from
Mic to line ?

the name of some controls should be mic capture volume and speaker playback 
volume 
instead of u46dj

the other controls should be named in the u46DJ functional block diagram
of the user manual

bTerminalID 4
wTerminalType  0x0201 Microphone
bAssocTerminal  6
bNrChannels 4
wChannelConfig 0x
iChannelNames   0 
iTerminal   2 


bLength 9
bDescriptorType36
bDescriptorSubtype  3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType  0x0301 Speaker
bAssocTerminal  1
bSourceID   2
iTerminal   2

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

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

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

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10

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

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

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

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

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

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

  Regards.

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

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

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

[Desktop-packages] [Bug 1243459] [NEW] al identificar el segundo monitor me pone 46" y es de 24"

2013-10-22 Thread Jose

Public bug reported:

el monitor que tengo parelelo es un NEVIR de 24"

I am using two monitors, one on the left es a Samsung 22", but second
monitor on the right is a Nevir 24", and the sistem identificated a 46"
monitor.

Thank you for all, I think your work is fantastic,. and I congratulate
you for it

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct 23 01:13:25 2013
DistUpgraded: 2013-10-21 02:47:21,487 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2013-09-30 (22 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=0e4b1ed0-8d26-4021-961e-4ffef85a62de ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
dmi.bios.date: 02/27/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75M-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF13:bd02/27/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.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: Tue Oct 22 21:55:33 2013
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1064 
 vendor SAM
xserver.version: 2:1.14.3-3ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 saucy 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/1243459

Title:
  al identificar el segundo monitor me pone 46" y es de 24"

Status in “xorg” package in Ubuntu:
  New

Bug description:
  el monitor que tengo parelelo es un NEVIR de 24"

  I am using two monitors, one on the left es a Samsung 22", but second
  monitor on the right is a Nevir 24", and the sistem identificated a
  46" monitor.

  Thank you for all, I think your work is fantastic,. and I congratulate
  you for it

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 01:13:25 2013
  DistUpgraded: 2013-10-21 02:47:21,487 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu

[Desktop-packages] [Bug 1127855] Re: [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost option, mic's very quiet.

2013-10-22 Thread Henning Bostelmann

Re hda-jack-retask: It doesn't show any internal mic 0xc for me, just
internal mic 0x13 .

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

Title:
  [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost
  option, mic's very quiet.

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

Bug description:
  I tried options model=dell-3stack, model=laptop, model=dell-bios... no
  changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crazyden   4281 F mixer_applet2
crazyden   4318 F pulseaudio
   /dev/snd/pcmC0D0p:   crazyden   4318 F...m pulseaudio
  Date: Sun Feb 17 10:52:11 2013
  InstallationDate: Installed on 2012-07-20 (211 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Mic, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [MXG071, SigmaTel STAC9228, Mic, Internal] volume slider problem
  UpgradeStatus: Upgraded to quantal on 2013-02-12 (4 days ago)
  dmi.bios.date: 04/23/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0KX412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/23/2010:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn0KX412:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXG071
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-02-16T18:38:21.761644

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

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

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

2013-10-22 Thread Kirill Jakovlev

(add proposed)
Try "caps lock" - it type "next group".
Noway to set combination for tty. I still have working "caps lock" in tty.

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

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

2013-10-22 Thread Romano Giannetti

Adding a screenshot...


** Attachment added: "The options for the keyboard special keys has disappeared 
after the last update"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1218322/+attachment/3887909/+files/keyboardoptions.png

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

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

2013-10-22 Thread Romano Giannetti

I received the (normal) update now. The problem is that the "options"
for changing the keyboard preferences has disappeared from the
"keyboard" settings...  using gnome (not unity), could be for this?

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

[Desktop-packages] [Bug 1127855] Re: [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost option, mic's very quiet.

2013-10-22 Thread Henning Bostelmann

Same problem here on:
Dell XPS M1330
Ubuntu 12.04
Kernel 3.2.0-54-generic-pae #82-Ubuntu SMP

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

Title:
  [MXG071, SigmaTel STAC9228, Mic, Internal] doen't have Mic Boost
  option, mic's very quiet.

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

Bug description:
  I tried options model=dell-3stack, model=laptop, model=dell-bios... no
  changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crazyden   4281 F mixer_applet2
crazyden   4318 F pulseaudio
   /dev/snd/pcmC0D0p:   crazyden   4318 F...m pulseaudio
  Date: Sun Feb 17 10:52:11 2013
  InstallationDate: Installed on 2012-07-20 (211 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Mic, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [MXG071, SigmaTel STAC9228, Mic, Internal] volume slider problem
  UpgradeStatus: Upgraded to quantal on 2013-02-12 (4 days ago)
  dmi.bios.date: 04/23/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0KX412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/23/2010:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn0KX412:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXG071
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-02-16T18:38:21.761644

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

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

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

2013-10-22 Thread Pablo180

I'd just like to add that I have this problem, not on suspend (which I
haven't tried since upgrading) but each and every time I resume from
hibernate. I have to 'killall NetworkManager' to get networking back -
every time.

nmcli nm sleep false - didn't work for me.

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

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

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

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

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

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

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

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

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

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

2013-10-22 Thread Jarno Suni

Actually, xscreensaver does not need to start at startup; the daemon can
be started within lxlock, if needed. But xscreensaver needs to be
installed, of course. I wrote a replacement script for lxlock that tries
to lock by xscreensaver; see the attachement for more details.

Still, there is a problem with how lxlock is used by e.g. the suspend
function of the Logout Lubuntu dialog: It runs lxlock in background and
does not check, if it ran successfully before entering the suspend mode,
see Bug #1054299

** Attachment added: "lxlock script that uses xscreensaver instead of dm-tool"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1205384/+attachment/3887901/+files/lxlock

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

Title:
  Lock can be circumvented by switching to console

Status in LXDE - Lightweight X11 Desktop Environment:
  New
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “lxsession” package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1)lock your screen using "dm-tool switch-to-greeter" or "dm-tool lock"
  2)switch to console via ctrl+alt+F1
  3)switch back to X via ctrl+alt+F7
  Result: session is unlocked without entering a password

  Expected behaviour:
  session should still be locked when switching back to X

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.7-0ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Fri Jul 26 17:30:23 2013
  InstallationDate: Installed on 2013-07-26 (0 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130723.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 729348] Re: wpa_supplicant crashed with SIGSEGV in __libc_start_main()

2013-10-22 Thread Antonio Roberts

Still happening on Dell XPS 13 Developer edition with Ubuntu 13.10
64-bit and Atheros AR9462 Wireless Network Adapter

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

Title:
  wpa_supplicant crashed with SIGSEGV in __libc_start_main()

Status in “wpasupplicant” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: wpasupplicant

  wpa_supplicant crashed with SIGSEGV in __libc_start_main()

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: wpasupplicant 0.7.3-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Mar  4 16:23:33 2011
  ExecutablePath: /sbin/wpa_supplicant
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202)
  ProcCmdline: /sbin/wpa_supplicant -u -s
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x47d516:  mov0x40(%rax),%rax
   PC (0x0047d516) ok
   source "0x40(%rax)" (0x0607e04d) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: wpasupplicant
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main () from /lib/libc.so.6
  Title: wpa_supplicant crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to natty on 2011-03-03 (1 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1237545] Re: check_gl_texture_size crashed with SIGSEGV in scalarEqual()

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

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

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

Title:
  check_gl_texture_size crashed with SIGSEGV in scalarEqual()

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  Just happened after starting Ubuntu 13.10 on 09.10.2013 in VirtualBox.
  (All packages up-to-date).

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libgnome-desktop-3-7 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  9 19:17:38 2013
  Disassembly: => 0x7ff19d6c6b20:   Cannot access memory at address 
0x7ff19d6c6b20
  ExecutablePath: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  InstallationDate: Installed on 2013-10-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7ff19d6c6b20:Cannot access memory at address 
0x7ff19d6c6b20
   PC (0x7ff19d6c6b20) in non-executable VMA region: 
0x7ff19d69a000-0x7ff19d89a000 ---p /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  SegvReason: executing non-writable VMA 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Signal: 11
  SourcePackage: gnome-desktop3
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   glXChooseVisual () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: check_gl_texture_size crashed with SIGSEGV in glXChooseVisual()
  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/mesa/+bug/1237545/+subscriptions

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

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

2013-10-22 Thread vladk

next group issue fixed for me with last ppa update

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

2013-10-22 Thread ex-oficio

** Patch added: "alsa-info.diff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1242891/+attachment/3887839/+files/alsa-info.diff

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

2013-10-22 Thread ex-oficio

** Attachment added: "alsa-info.txt.old"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1242891/+attachment/3887838/+files/alsa-info.txt.old

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1242891] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

2013-10-22 Thread ex-oficio

Hi, I booted into the instal DVD, and issued "sudo modprobe snd-hda-
intel" to get the alsa-info for the old situation, because I couldn't
figure out how to get back there on my current installation.

I hope this helps.

alsa-info.txt is current setup.
alsa-info.old is livecd setup.
alsa-info.diff is the difference file as requested (obviously).


** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1242891/+attachment/3887837/+files/alsa-info.txt

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem & LED problem

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

Bug description:
  Possibly important:

  using raring 13.04.

  issue seen on hp DV6 7000 series laptop which had beats audio (4
  channels i think. it has a subwoofer. info from hp is very unclear).

  I am using the alsa daily package: oem-audio-hda-daily-dkms which
  builds a new snd-hda-intel kernel module every so often.

  

  with the snd-hda-intel  kernel module provided by the normal raring
  ubuntu repo, the mute/sound led works correctly, but the channels that
  the hardware has are not correctly detected, and headphones do not
  work/mute speakers. My laptop has multiple speaker channels, and
  sub/LFE. With the normal raring kernel module, there is no way to use
  all channels even with hda-jack-retask, and sadly sound only comes
  from the weakest of the 4 channels so is very disappointing.

  I have the alsa daily package ppa of oem-audio-hda-daily-dkms set in
  my software sources, so I whenever they release a new build I install
  it automatically. With the package from this PPA there are more
  channels seen in alsamixer, although i still need to use hda-jack-
  retask to get sound from them all. Crucially, the headphones jack
  works with the module built from this PPA, and automutes the speakers
  when headphones are plugged in.

  I raise this bug because non-technical users would not have been able
  to get acceptable sound from this laptop using ubuntu, which is an
  undesirable situation.

  however, the led now always indicates red for "muted" when it should
  be white for "unmuted". pressing the mute button toggles the mute
  function correctly in pulse/gnome, but the LED always indicates muted.

  Essentially, the snd-hda-intel module from this PPA is usable with a
  technical modification, but the led indicator does not function
  correctly, although it did before.

  please let me know if more information is needed, or if you need my to
  perform any tests.

  kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2367 F pulseaudio
  Date: Mon Oct 21 21:31:28 2013
  InstallationDate: Installed on 2013-10-01 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd04/22/2013:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY dv6 Notebook PC
  dmi.product.version: 088A1230591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

2013-10-22 Thread Alberto Salvia Novella

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: ubuntu-gnome
   Status: Confirmed => Fix Committed

** Changed in: indicator-keyboard (Ubuntu)
 Assignee: William Hua (attente) => (unassigned)

** Changed in: gnome-settings-daemon (Ubuntu)
 Assignee: William Hua (attente) => (unassigned)

** Changed in: gnome-control-center (Ubuntu)
 Assignee: William Hua (attente) => (unassigned)

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

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

Status in One Hundred Paper Cuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Fix Committed
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Invalid

Bug description:
  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

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

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

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

[Desktop-packages] [Bug 885989] Re: white screen on second monitor when using two xsessions

2013-10-22 Thread James M. Leddy

Hi Alberts,

Thanks for that note. Apparently this does not work with hybrid
graphics, so I'm going to have to get another machine to test.

https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1174278

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

Title:
  white screen on second monitor when using two xsessions

Status in Nautilus:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “nautilus” source package in Precise:
  Triaged

Bug description:
  If enable dual head mode (two X screens), the second monitor went
  white after login with unity or unity-2d. After tracking the gnome-
  session, it is caused by running "nautilus -n" for this configuration.
  And if kill the nautilus process, the desktop showed up normally on
  second screen.

  lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  apt-cache policy nautilus
  nautilus:
Installed: 1:3.2.1-0ubuntu2
Candidate: 1:3.2.1-0ubuntu2
Version table:
   *** 1:3.2.1-0ubuntu2 0
  500 http://cn.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.2.0-0ubuntu5 0
  500 http://cn.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

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

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

[Desktop-packages] [Bug 1243430] [NEW] After 13.10 installation, SAMBA did not work but...

2013-10-22 Thread Shunsuke Akagi

Public bug reported:

After 13.10 installation, SAMBA did not work but now it works OK though it 
still have problem.
1. Installed SAMBA.
2.It asked password to start but no response.
3.I installed GADMIN-SAMBA
4.SAMBA opened up but network share did not work at all.
5. I uninstalled SAMBA and deleted /etc/samba
6. After reinstallation, no response. same as 2.
7. I made s/etc/samba/smb.cof even though it was hard to make a "new document" 
due to down graded nautilus.
8. SAMBA opened and network share works great as usual.
9. preference>server setting won't open. yet functionally everything is working 
great!

Anyway somethings are wrong and I wasted so much time to figure out.

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

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

Title:
  After 13.10 installation, SAMBA did not work but...

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  After 13.10 installation, SAMBA did not work but now it works OK though it 
still have problem.
  1. Installed SAMBA.
  2.It asked password to start but no response.
  3.I installed GADMIN-SAMBA
  4.SAMBA opened up but network share did not work at all.
  5. I uninstalled SAMBA and deleted /etc/samba
  6. After reinstallation, no response. same as 2.
  7. I made s/etc/samba/smb.cof even though it was hard to make a "new 
document" due to down graded nautilus.
  8. SAMBA opened and network share works great as usual.
  9. preference>server setting won't open. yet functionally everything is 
working great!

  Anyway somethings are wrong and I wasted so much time to figure out.

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

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

[Desktop-packages] [Bug 1242723] Re: diagnostic settings

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

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

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

Title:
  diagnostic settings

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  ubuntustudio 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 21 16:04:19 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.88, 3.11.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:82fd]
  InstallationDate: Installed on 2013-10-19 (2 days ago)
  InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  LightdmGreeterLog:
   (lightdm-gtk-greeter:340): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
   
   ** (lightdm-gtk-greeter:340): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/sessions': No such file or directory
   
   ** (lightdm-gtk-greeter:340): WARNING **: Failed to load user image: Failed 
to open file '/home/jl/.face': No such file or directory
  LightdmGreeterLogOld:
   (lightdm-gtk-greeter:1478): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
   
   ** (lightdm-gtk-greeter:1478): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/sessions': No such file 
or directory
   
   ** (lightdm-gtk-greeter:1478): WARNING **: Failed to load user image: Failed 
to open file '/home/jl/.face': No such file or directory
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=6105f1d0-3e35-47ba-b317-25b0af037a15 ro quiet splash
  SourcePackage: xorg
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: Xlib:  extension "GLX" missing on display ":0.0".
   Error: GLX is not available on the system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M EVO
  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.:bvr1801:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-MEVO: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 21 14:56:07 2013
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1243425] Re: When renaming the background is transparent

2013-10-22 Thread Sebastien Bacher

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

** This bug has been marked a duplicate of bug 1236601
   wrong background color when editing icons on desktop

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

Title:
  When renaming the background is transparent

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Watch this video. It is impossible to read what is being written while 
renames a file.
  http://youtu.be/1LuL1VPMdLQ

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 18:28:26 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'805x997+65+24'"
  InstallationDate: Installed on 2013-10-06 (16 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  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/1243425/+subscriptions

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

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

2013-10-22 Thread Jamie Strandboge

I think the approach here is correct for now, especially for this
security update-- get the guest account confined with apparmor without
dbus mediation (and remember the system bus will have policykit in
effect too). This is what we did for other applications in Ubuntu in
13.10; we can examine more strict confinement going forward.

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

Title:
  lightdm no longer runs guest session through wrapper

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 19:51:27 2013
  InstallationDate: Installed on 2011-10-27 (726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (3 days ago)

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

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

[Desktop-packages] [Bug 1067301] Re: ssh-add: Error reading response length from authentication socket.