date:20131108

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

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

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

Title:
  Default soundcard

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  There is no way to set soundcard as default, it's very annoying. In
  Windows is simple functionality like when I set my USB soundcard as
  default and hook it up it automatically switches all sound source to
  it, including sound control.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: pulseaudio 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1
  ProcVersionSignature: Ubuntu 2.6.38-13.52-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mastier2198 F pulseaudio
   /dev/snd/controlC1:  mastier2198 F pulseaudio
   /dev/snd/pcmC1D0p:   mastier2198 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 47'
 Mixer name : 'Conexant CX20561 (Hermosa)'
 Components : 'HDA:14f15051,17aa211b,0010'
 Controls  : 16
 Simple ctrls  : 8
  Card1.Amixer.info:
   Card hw:1 'S51'/'Creative Technology SB X-Fi Surround 5.1 at 
usb-:00:1a.7-5.2, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:3042'
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Power LED',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7WHT19WW-1.06'
 Mixer name : 'ThinkPad EC 7WHT19WW-1.06'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [off]
  Date: Fri Dec 23 01:15:37 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   LANGUAGE=pl_PL:pl:en
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET69WW (3.19 )
  dmi.board.name: 7449C4G
  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:bvr7WET69WW(3.19):bd05/16/2011:svnLENOVO:pn7449C4G:pvrThinkPadX200Tablet:rvnLENOVO:rn7449C4G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7449C4G
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 599846]

2013-11-08 Thread Nelson Benitez

Created attachment 829607
0001-Bug-417952-Open-Containing-Folder-doesn-t-highlight-.patch

(In reply to Karl Tomlinson (:karlt) from comment #20)
> Comment on attachment 826479
> 0001-Bug-417952-Open-Containing-Folder-doesn-t-highlight-.patch
> 
> Thanks.  This is good.  Just some minor things:

Updated patch with those things corrected. :-)

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

Title:
  firefox right click open containing folder should highlight file

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

Bug description:
  Binary package hint: firefox

  The only reason I am assuming this is a bug is because the
  functionality is in Windows. Basically, if the user right clicks on a
  file in the Downloads of Firefox and selects "Open Containing Folder",
  Nautilus should open with the file highlighted to make the file easier
  to find.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu.
  Description:  Ubuntu 10.04 LTS
  Release:  10.04

  2) The version of the package you are using, via 'apt-cache policy 
packagename' or by checking in Synaptic.
Installed: 3.6.3+nobinonly-0ubuntu4
Candidate: 3.6.3+nobinonly-0ubuntu4
Version table:
   *** 3.6.3+nobinonly-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected my file to be highlighted.

  4) What happened instead
  Nautilus opened, but the file was not highlighted.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Tue Jun 29 11:15:58 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up

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

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia prime causes freeze at start up

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

Bug description:
  I believe nvidia-prime modified my xorg.conf to use intel during boot.
  I had to remove xorg.conf to enable my system to boot to unity again.
  I've attached the file that caused the problem.

  My system has onboard intel graphics on the motherboard, and a
  beefcake nvidia card to which my monitors are connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-prime 0.4.2~hybrid0.0.1
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Nov  8 06:07:51 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 891962] Re: Unity dash launcher very slow when running system monitor in background

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

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

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

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

Title:
  Unity dash launcher very slow when running system monitor in
  background

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

Bug description:
  when running gnome system monitor, click on the dash and move mouse over 
icons. icons light up very slowly and respond slowly when clicked.
  when running several programs ( excluding system monitor ) dash works fine 
and responds very quickly,
  open system monitor dash slows down and responds poorly.

  ubuntu 11.10 on aspire 5315 & satellite L350

  my first ever bug report.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Package: gnome-system-monitor 3.2.1-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1074599] Re: Hud menu for "Desktop" does not work

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

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

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

Title:
  Hud menu for "Desktop" does not work

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  On clean session meaning no desktop applications running. Click on
  desktop then press Alt key to display Hud menu. Apparently this is hud
  menu of Nautilus since it has Go menu. Anyway it seems not functional
  to some extent (have not tried every possible manu entry), but at
  least Go menu entires don't seem to be working.

  Scenario:
  1. Login to your desktop session. No applications running. Click on Desktop 
to "activate" it.
  2. Press Alt key to start Hud menu.
  3. Enter "Home". Hud displays Go->Home. Press enter to "open Home" folder.
  4. Nothing happens. Expected behaviour: Home folder is displayed in Nautilus.

  Other option would be to disable Hud menu for nautilus instance
  resposible for drawing Desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Sat Nov  3 11:44:59 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '775x611+57+24'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 219
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  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/1074599/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-11-08 Thread ==BJ==

I had used "Grave Accent" as dead key for switching layout in Ubuntu by 
manually changing X11 config. I did it for several versions of Ubuntu.
Now that "Alt+Shift"has been fixed. I wonder if it's possible to manually 
config it in Ubuntu 13.10?.

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

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

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged

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

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

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

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

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

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
     * Can't set keyboard layout change to Ctrl+Shift (bug 1245991)
     * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V 
are not working in gnome-terminal (bug 1246656)

  Shift+Shift:
     * Can't set keyboard layout change to Shift+Shift (bug 1245272)
     * lock screen - gnome-screensaver (bug 1245278)
     * Unity greeter (bug 1245280)

  Bugs which belong to keyboard layout switching:
     * Hotkeys not functional in non-latin keyboard layout in 13.10 (bug 
1226962)
     * Keyboard Layout Options window is missed in gnome-control-center 
keyboard (bug 1245064)
     * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy (bug 1245188)
     * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy (bug 1245199)
     * Keyboard shortcut for changing keyboard layout does not work on lock 
screen (bug 1244548)
     * [FFe] indicator-keyboard not working under greeter (bug 1228207)
     * Lost ability to remap Caps Lock to Ctrl (bug 1215826)
     * gnome-control-center keyboard no longer has way to modify caps lock key 
behavior (bug 1224575)
     * Pressing Caps Lock toggles LED even when mapped to another key (bug 
1221403)
 * Switching layout turns off NumLock (bug 1247668)

  --

  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.1

[Desktop-packages] [Bug 491572] Re: [lucid][rv350] radeon drm error (AGP)

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

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

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

Title:
  [lucid][rv350] radeon drm error (AGP)

Status in “linux” package in Ubuntu:
  Expired
Status in “mesa” package in Ubuntu:
  Invalid

Bug description:
  Seeing lots of these messages in the kernel log were not present in
  ubuntu Jaunty

  Dec  2 19:02:08 Robins-Laptop kernel: [21323.577223] [TTM] Failed moving 
buffer. Proposed placement 0x00060004
  Dec  2 19:02:08 Robins-Laptop kernel: [21323.577237] 
[drm:radeon_object_list_validate] *ERROR* radeon: failed to validate.
  Dec  2 19:02:08 Robins-Laptop kernel: [21323.577240] [drm:radeon_cs_ioctl] 
*ERROR* Failed to parse relocation !

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin0800   7871 F pulseaudio
   /dev/snd/pcmC0D0p:   robin0800   7871 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 33
 Simple ctrls  : 22
  Date: Wed Dec  2 20:41:07 2009
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=0768eca1-b0a8-4171-a2ec-bd62d0c2256d
  MachineType: Hewlett-Packard HP Compaq nc6000 (PQ491ES#ABU)
  Package: linux-image-2.6.32-6-generic 2.6.32-6.8
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-6-generic 
root=UUID=75592929-a2d6-45af-8d77-3ae360b1d026 ro quiet splash
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-6.8-generic
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.27
  Reproducible: Yes
  RfKill:
   
  SourcePackage: linux
  Tags: lucid needs-upstream-testing regression-potential
  TestedUpstream: No
  Uname: Linux 2.6.32-6-generic i686
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68BDD Ver. F.15
  dmi.board.name: 0890
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 8051 Version 1A.19
  dmi.chassis.asset.tag: CNU447FNCY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BDDVer.F.15:bd08/30/2006:svnHewlett-Packard:pnHPCompaqnc6000(PQ491ES#ABU):pvrF.15:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6000 (PQ491ES#ABU)
  dmi.product.version: F.15
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 733809] Re: chromium/chrome starts in incomplete fullscreen

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  chromium/chrome starts in incomplete fullscreen

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

Bug description:
  Binary package hint: chromium-browser

  I recently did a dist-upgrade from a stable 10.10 to the development
  version of 10.04.

  what i expect so see:
  I start chrome/chromium and it goes to fullscreen immediately.

  what happens:
  after start it goes into an incomplete fullscreen with part of the desktop 
still visible on the top between former title bar and former upper gnome-panel. 
this happens on both google-chome and chromium see attached screenshot for 
better description.

  workaround:
  click the visible desktop area or the panel and the window goes to complete 
fullscreen as supposed to.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: chromium-browser 10.0.648.127~r76697-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-6.34-generic-pae 2.6.38-rc7
  Uname: Linux 2.6.38-6-generic-pae i686
  Architecture: i386
  Date: Sat Mar 12 12:58:30 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to natty on 2011-03-12 (0 days ago)
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1222708] Re: libreoffice-kde packaging: cannot be installed - wrong dependencies

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

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

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

Title:
  libreoffice-kde packaging:  cannot be installed - wrong dependencies

Status in “libreoffice” package in Ubuntu:
  Expired

Bug description:
  ubuntu saucy, libreoffice packages are  1:4.1.1-0ubuntu1 ,
  but  libreoffice-kde  is set to depend on   = 1:4.0.2-0ubuntu5
  so installing is not possible

  steffen@mlk-serv:~$ sudo apt-get install -f libreoffice-kde
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
  Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
  Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
  nicht erstellt wurden oder Incoming noch nicht verlassen haben.
  Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

  shell output (german localisation)
  ---
  steffen@mlk-serv:~$ sudo apt-get install -f libreoffice-kde
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
  Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
  Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
  nicht erstellt wurden oder Incoming noch nicht verlassen haben.
  Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

  Die folgenden Pakete haben unerfüllte Abhängigkeiten:
   libreoffice-kde : Hängt ab von: libreoffice-core (= 1:4.0.2-0ubuntu5) soll 
aber nicht installiert werden
 Empfiehlt: libreoffice-style-oxygen soll aber nicht 
installiert werden
  E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte 
Pakete.
  ---
  and:
  ---
  steffen@mlk-serv:~$ dpkg -l|grep libreoffice
  ii  libreoffice-base-core 1:4.1.1-0ubuntu1
amd64office productivity suite -- shared library
  ii  libreoffice-calc  1:4.1.1-0ubuntu1
amd64office productivity suite -- spreadsheet
  ii  libreoffice-common1:4.1.1-0ubuntu1
all  office productivity suite -- arch-independent files
  ii  libreoffice-core  1:4.1.1-0ubuntu1
amd64office productivity suite -- arch-dependent files
  ii  libreoffice-draw  1:4.1.1-0ubuntu1
amd64office productivity suite -- drawing
  ii  libreoffice-emailmerge1:4.0.2-0ubuntu5
all  transitional package for LibreOffices email mail 
merge
  ii  libreoffice-help-de   1:4.1.1-0ubuntu1
all  office productivity suite -- German help
  ii  libreoffice-help-en-gb1:4.1.1-0ubuntu1
all  office productivity suite -- English_british help
  ii  libreoffice-help-en-us1:4.1.1-0ubuntu1
all  office productivity suite -- English_american help
  ii  libreoffice-impress   1:4.1.1-0ubuntu1
amd64office productivity suite -- presentation
  ii  libreoffice-l10n-de   1:4.1.1-0ubuntu1
all  office productivity suite -- German language 
package
  ii  libreoffice-l10n-en-gb1:4.1.1-0ubuntu1
all  office productivity suite -- English_british 
language package
  ii  libreoffice-l10n-en-za1:4.1.1-0ubuntu1
all  office productivity suite -- English_southafrican 
language package
  ii  libreoffice-math  1:4.1.1-0ubuntu1
amd64office productivity suite -- equation editor
  ii  libreoffice-pdfimport 1:4.1.1-0ubuntu1
amd64PDF Import component for LibreOffice
  ii  libreoffice-style-human   1:4.1.1-0ubuntu1
all  office productivity suite -- Human symbol style
  ii  libreoffice-writer1:4.1.1-0ubuntu1
amd64office productivity suite -- word processor
  --

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

[Desktop-packages] [Bug 1222845] Re: I dont know

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

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

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

Title:
  I dont know

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  i dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Sep  9 19:27:50 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
  InstallationDate: Installed on 2013-09-03 (6 days ago)
  InstallationMedia: Edubuntu 13.04 "Raring Ringtail" - Release i386 
(20130424.1)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=0deafa82-5a36-4eb3-a1c8-ddf19d3e128f ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0414
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM/PS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 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.:bvr0414:bd08/26/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.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.9~daily13.06.19~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Mon Sep  9 18:01:31 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputsonixj   KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1203024] Re: 'Install 3rd party software' does not install proper drivers for Nvidia Geforce GTX 580

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

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

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

Title:
  'Install 3rd party software' does not install proper drivers for
  Nvidia Geforce GTX 580

Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “ubiquity” package in Ubuntu:
  Expired

Bug description:
  To run the installer on a machine with an Nvidia Geforce GTX 580
  graphics card it is necessary to use the 'nomodeset'-option. After
  installation, Unity runs slowly and in a very low resolution. This can
  be fixed by installing the nvidia-current package.

  I asked on the ubiquity irc chat about this, and the response was that
  this is a bug, hence this bug report.

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

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

[Desktop-packages] [Bug 1025839] Re: Printing multiple copies submits multiple separate jobs (should submit one job)

2013-11-08 Thread jimav

Why does LibreOffice need to know if the printer hardware supports Collate?
Isn't it the job of the print server (i.e. CUPS) to know this and decide how to 
do multiple copies when requested?

( For example, single-page jobs can always be multi-copied in Postscript
printers by simply repeating the 'showpage'  operator, even if the
printer can't print multiple collated copies of multi-page jobs)

 If LibreOffice just invokes "lpr -# ..." or equivalent, then
the spooler should do the right thing.

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

Title:
  Printing multiple copies submits multiple separate jobs (should submit
  one job)

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

Bug description:
  In the print dialog, if "Number of Copies" is set to 50 then 50
  separate, independent print jobs are spooled.  It should submit a
  single print job, specifying 50 copies.   This will allow the printer
  to do the replication if it can (all Postscript printers can).

  This is important because:
   
1) Submitting a separate jobs for each copy causes the page(s) to be 
rendered again and again,
with a drastic reduction in through-put.   

   This is CRUCIAL if the pages contain complex graphics or images which 
take a long time to render
   or transmit to the printer:   A one-minute delay for the first of 50 
copies is okay, but 1 minute for 
   *each* of 50 copies is intolerable.

2) If the print job was a mistake, it is virtually impossible to stop the 
printer.  Pressing the cancel
button on the printer cancels just one copy, but after a little while 
the next one starts printing...

3) It is very inconvenient to cancel the job in CUPS, with 50 separate 
jobs, without affecting other
unrelated jobs in the queue (you can cancel all jobs in the queue at 
once, or one at a time).

  Note that CUPS has always supported a "number of copies" option at the 
command-line level.
  For example
 lpr '-#50'  file.pdf
  prints 50 copies of the file, rendering it once only.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33
  Uname: Linux 3.0.0-22-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 17 11:49:58 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1095498] Re: Printing PDFs with images is hideously slow

2013-11-08 Thread jimav

The %!PS-Adobe-3.0 is probably correct. It refers to the *Document
Structuring Convention* version, not the Postscript languageLevel
assumed by the script within.

DSC 3.0 was introduced in Sept. 1992, whereas Postscript language level
3 appeared in 1997.

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

Title:
Printing PDFs with images is hideously slow

Status in “cups” package in Ubuntu:
Incomplete

Bug description:
Printing anything with graphics from Firefix (such as a Google Maps
page), or a PDF file containing graphics, takes a ridiculously long
time to print, often several minutes per page. This is with a
directly-attached USB postscript printer (an HP 3030 mfp).

The exact same content prints in only 2 seconds when printed from
Windows 7 running in a VM, to the same printer via an independent
print server (avoiding CUPS in the Ubuntu host).

NOTE: If the page in Firefox is first printed "to file" and PDF is
selected, the very long delay happens when printing the resulting PDF
using the "lpr" command. If, instead, "print to file" is done from
Firefox and Postscript is selected, the resulting .ps file prints much
faster (still 10x slower than printing from Windows 7, but much faster
than printing the equivalent PDF).

So there must be something bogus in how CUPS handles PDF files
containging images.

STEPS TO REPRODUCE:

1. Visit https://maps.google.com/ in Firefox on Ubuntu
2. Search for "San Francisco" and click the print icon (in the left bar near
the top).
3. A printable map is displayed; hit ^P to print it to a postscript printer
(1-2 minute delay before the page prints)

Do exactly the same on a Windows 7 system and printing starts in about
2 seconds.

Alternatively, try printing the attached PDF and PS files. The PDF is
hideously slow (minutes), but the PS is only slow (about 10 seconds
to print on my system).Compared to 2 seconds when printed from
Windows. All the same content.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cups 1.5.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
Date: Wed Jan 2 17:14:16 2013
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lpstat:
device for hp-LaserJet-3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM066305
device for hp-LaserJet-3030-Fax:
hpfax:/usb/hp_LaserJet_3030?serial=00CNBM066305
device for PDF: cups-pdf:/
MachineType: System manufacturer System Product Name
MarkForUpload: True
Papersize: letter
PpdFiles:
hp-LaserJet-3030: HP LaserJet 3020 3030 Postscript (recommended)
PDF: Generic CUPS-PDF Printer
hp-LaserJet-3030-Fax: HP Fax hpcups
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=UUID=8aaca318-f079-4a4f-95c0-735aa54bed2d ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to precise on 2012-08-10 (145 days ago)
dmi.bios.date: 09/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1408
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1247160] Re: Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound at all

2013-11-08 Thread Raymond

if the graphic driver knew monitor is connnected, just need to notify
audio driver whether eld is valid and pass it to audio drivet

HDMI1 connected

audio: auto
  supported: force-dvioffautoon

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

Title:
  Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out,
  HDMI] No sound at all

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

Bug description:
  The problem I reported regarding no audio/sound over HDMI in Ubuntu 11
  series as bug #793592, which was fixed in 12.04 and 12.10, has
  unfortunately reappeared in Ubuntu 13.10 following a fresh
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Date: Fri Nov  1 17:49:50 2013
  InstallationDate: Installed on 2013-11-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Symptom_Jack: Black Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 0P096C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: '01'
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd11/09/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA00:cvnDellInc.:ct3:cvr'01':
  dmi.product.name: Studio Hybrid 140g
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1229022] Re: Gnome control center crashes when opening network settings

2013-11-08 Thread Stéphane Guillou

Here is my list of error reports:


2a09b0ac-45f9-11e3-9183-2c768aafd08c
2e47eb70-448c-11e3-a9d3-e4115b0f8a4a
31173fc6-3295-11e3-bdac-2c768aafd08c
3964f75e-2fed-11e3-9052-e4115b0f8a4a
41c2d2ae-2fed-11e3-bf02-e4115b0f8a4a
6af778a8-447b-11e3-8345-e4115b0f8a4a
c831ad78-41eb-11e3-9b3e-e4115b0f8a4a
d04c27b4-4668-11e3-ab8e-2c768aafd08c
dcaea13e-453d-11e3-a182-2c768aafd08c
e080cb0a-41ca-11e3-8a92-e4115b0f8a4a
e2fe5b04-41ca-11e3-a675-e4115b0f8a4a


I am not sure which one is the right one, sorry.
Cheers

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

Title:
  Gnome control center crashes when opening network settings

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

Bug description:
  Gnome control center ("System settings") crashes systematically
  shortly after opening the Network settings, making it impossible to
  configure anything network-related, at least through the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu24.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: amd64
  Date: Mon Sep 23 14:22:53 2013
  InstallationDate: Installed on 2013-05-13 (133 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.2
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1
   gnome-control-center-unity  1.3daily13.06.19~13.04-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

[Desktop-packages] [Bug 1199933] Re: apparmor parser in precise does not support block_suspend capability (needed for backported kernels)

2013-11-08 Thread Ubuntu Foundations Team Bug Bot

The attachment "absolute minimum patch to support block_suspend in this
version of the parser" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  apparmor parser in precise does not support block_suspend capability
  (needed for backported kernels)

Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “cups” package in Ubuntu:
  New
Status in “apparmor” source package in Precise:
  Triaged
Status in “apparmor” source package in Saucy:
  Fix Released

Bug description:
  When running an up-to-date precise system with a 
linux-image-generic-lts-raring HWE kernel (linux 3.8), 
  the precise verion of apparmor will deny all attempts of apparmored apps to 
call the block_suspend system call:

  For example: 
  type=AVC msg=audit(XX.XXX:X): apparmor="DENIED" 
operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1040 comm="cupsd" 
pid=1040 comm="cupsd" capability=36  capname="block_suspend"

  But it is also impossible to add block_suspend to the apparmor profiles, 
because the AppArmor parser does not know about it:
Setting /usr/sbin/cupsd to enforce mode.
Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update 
cache, disable, or force-complain via stdin
AppArmor parser error, in stdin line 24: Invalid capability block_suspend.

  This seems to make it impossible to have apparmor  not deny block
  suspend when using an LTS HWE kernel.

  This seems to be related to bug #1052098.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apparmor 2.7.102-0ubuntu3.7
  ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Wed Jul 10 12:48:24 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  KernLog: Jul 10 12:34:08 gumdrop kernel: [580960.424225] SGI XFS with ACLs, 
security attributes, realtime, large block/inode numbers, no debug enabled
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.8.0-25-generic 
root=UUID=981723af-1da9-455d-b776-3a1e8885efde ro rootflags=subvol=@
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  audit.log: Error: [Errno 13] Permission denied: '/var/log/audit/audit.log'

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

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

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

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in GVFS:
  New
Status in Ubuntu GNOME:
  New
Status in “gvfs” package in Ubuntu:
  New
Status in “nautilus-udisks” package in Ubuntu:
  Invalid

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

  Inserting the USB I have in the log:

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

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

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

  ...and it works ok.

  Add: using from command line udisks works, too:

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

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

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

[Desktop-packages] [Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa

2013-11-08 Thread Raymond

** Summary changed:

- alsa bug in KVM virtual machines
+ no audio in KVM virtual machines : cannot select alsa or pa

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

Title:
  no audio in KVM virtual machines : cannot select alsa or pa

Status in “libvirt” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New
Status in “virt-manager” package in Ubuntu:
  Incomplete

Bug description:
  I am on Ubuntu 13.10 desktop
  16GB ram
  asus sabertooth 990fx r2.0 motherboard
  amd 8346 cpu
  nvidia gtx650 video card

  Since upgrading to Ubuntu 13.10 audio no longer works in KVM.
  Checking SYSLOG I found this error being logged:

  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: ALSA woke us up to read new data from the device, but 
there was actually nothing to read!
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent 
snd_pcm_avail() returned 0 or another value < min_avail.

  brian

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 19:45:53 2013
  InstallationDate: Installed on 2013-10-31 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003)
  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: 04/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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/libvirt/+bug/1246929/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: Incorrect handling of orientation when printing PDF files

2013-11-08 Thread Stephane Peter

Any progress for a resolution of this orientation bug?

-- 
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 1095498] Re: Printing PDFs with images is hideously slow

2013-11-08 Thread jimav

Now printing the googlemap.pdf test file causes an "out of memory" error
on the printer after 20-30 seconds.   That's an improvement over just
silently doing nothing at all, I guess.

This is after doing:
  lpadmin -p HP3030_Postscript -o pdftops-renderer-default=pdftops   # the real 
printer queue
  restart cups

I also tried 
   pdf2ps -dLanguageLevel=2 googlemap.pdf test.ps
The resulting file begins with  %!PS-Adobe-3.0 despite the -dLanguageLevel=2 
option

I then tried
   lpr -oraw test.ps

and the the printer stalled for a looong time (at least 3 minutes)
with the light blinking, then printed a completely blank page.

Again, this same googlemap.pdf prints in 2-3 seconds using gutenprint or
pcl3 drivers.

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

Title:
  Printing PDFs with images is hideously slow

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  Printing anything with graphics from Firefix (such as a Google Maps
  page), or a PDF file containing graphics, takes a ridiculously long
  time to print, often several minutes per page. This is with a
  directly-attached USB postscript printer (an HP 3030 mfp).

  The exact same content prints in only 2 seconds when printed from
  Windows 7 running in a VM, to the same printer via an independent
  print server (avoiding CUPS in the Ubuntu host).

  NOTE: If the page in Firefox is first printed "to file" and PDF is
  selected, the very long delay happens when printing the resulting PDF
  using the "lpr" command.   If, instead, "print to file" is done from
  Firefox and Postscript is selected, the resulting .ps file prints much
  faster (still 10x slower than printing from Windows 7, but much faster
  than printing the equivalent PDF).

  So there must be something bogus in how CUPS handles PDF files
  containging images.

  STEPS TO REPRODUCE:

  1. Visit https://maps.google.com/ in Firefox on Ubuntu
  2. Search for "San Francisco" and click the print icon (in the left bar near 
the top).
  3. A printable map is displayed; hit ^P to print it to a postscript printer
  (1-2 minute delay before the page prints)

  Do exactly the same on a Windows 7 system and printing starts in about
  2 seconds.

  Alternatively, try printing the attached PDF and PS files.  The PDF is
  hideously slow (minutes),  but the PS is only slow (about 10 seconds
  to print on my system).Compared to 2 seconds when printed from
  Windows.   All the same content.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Jan  2 17:14:16 2013
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lpstat:
   device for hp-LaserJet-3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM066305
   device for hp-LaserJet-3030-Fax: 
hpfax:/usb/hp_LaserJet_3030?serial=00CNBM066305
   device for PDF: cups-pdf:/
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  PpdFiles:
   hp-LaserJet-3030: HP LaserJet 3020 3030 Postscript (recommended)
   PDF: Generic CUPS-PDF Printer
   hp-LaserJet-3030-Fax: HP Fax hpcups
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=UUID=8aaca318-f079-4a4f-95c0-735aa54bed2d ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to precise on 2012-08-10 (145 days ago)
  dmi.bios.date: 09/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1408
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1249515] [NEW] regression with session-cleanup-script triggering without actual logins

2013-11-08 Thread Jason Unovitch

Public bug reported:

Description:
In Ubuntu 13.10, session-cleanup scripts trigger before a session has started.  
Simply clicking between users at the login menu triggers the session cleanup 
script.   In my particular configuration this triggers a logout script that 
runs rsync with the --delete flag.  Clicking between users runs the risk of 
deleting good files rather than doing backups as in prior releases so I can't 
update all my computers until fixed. The example below replicates and visually 
shows the effect.  While running, the user cannot login until it has completed 
and depending on what the logout script does it can cause problems.

Configuration to Replicate:
/etc/lightdm/lightdm.conf
session-setup-script = /usr/bin/gnome-terminal --command "/bin/sleep 10"
session-cleanup-script = /usr/bin/gnome-terminal --command "/bin/sleep 10"

Version Information:
`lsb_release -rd`
Description:Ubuntu 13.10
Release:13.10

`apt-cache policy lightdm`
lightdm:
  Installed: 1.8.4-0ubuntu1
  Candidate: 1.8.4-0ubuntu1
  Version table:
 *** 1.8.4-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.8.2-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

Log information (while clicking between users at login screen):
`cat /var/log/lightdm/lightdm.log`
[+825.63s] DEBUG: Session pid=8564: Greeter start authentication for nixadm
[+825.63s] DEBUG: Session pid=12697: Sending SIGTERM
[+825.63s] DEBUG: Seat: Setting XDG_SEAT=seat0
[+825.63s] DEBUG: Session: Setting XDG_VTNR=7
[+825.63s] DEBUG: Session pid=29773: Started with service 'lightdm', username 
'nixadm'
[+825.63s] DEBUG: Session pid=12697: Terminated with signal 15
[+825.63s] DEBUG: Session: Failed during authentication
[+825.63s] DEBUG: Seat: Session stopped
[+825.64s] DEBUG: Launching process 29780: /usr/bin/gnome-terminal --command 
"/bin/sleep 10"
[+835.82s] DEBUG: Process 29780 exited with return value 0
[+835.82s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command 
"/bin/sleep 10": 0
[+835.82s] DEBUG: Session pid=29773: Got 1 message(s) from PAM
[+835.82s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s)
[+836.30s] DEBUG: Session pid=8564: Greeter start authentication for jason
[+836.30s] DEBUG: Session pid=29773: Sending SIGTERM
[+836.30s] DEBUG: Seat: Setting XDG_SEAT=seat0
[+836.30s] DEBUG: Session: Setting XDG_VTNR=7
[+836.31s] DEBUG: Session pid=29790: Started with service 'lightdm', username 
'jason'
[+836.31s] DEBUG: Session pid=29773: Terminated with signal 15
[+836.31s] DEBUG: Session: Failed during authentication
[+836.31s] DEBUG: Seat: Session stopped
[+836.32s] DEBUG: Launching process 29797: /usr/bin/gnome-terminal --command 
"/bin/sleep 10"
[+846.47s] DEBUG: Process 29797 exited with return value 0
[+846.47s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command 
"/bin/sleep 10": 0
[+846.47s] DEBUG: Session pid=29790: Got 1 message(s) from PAM
[+846.47s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s)
[+846.92s] DEBUG: Session pid=8564: Greeter start authentication for nixadm
[+846.92s] DEBUG: Session pid=29790: Sending SIGTERM
[+846.92s] DEBUG: Seat: Setting XDG_SEAT=seat0
[+846.92s] DEBUG: Session: Setting XDG_VTNR=7
[+846.92s] DEBUG: Session pid=30421: Started with service 'lightdm', username 
'nixadm'
[+846.93s] DEBUG: Session pid=29790: Terminated with signal 15
[+846.93s] DEBUG: Session: Failed during authentication
[+846.93s] DEBUG: Seat: Session stopped
[+846.94s] DEBUG: Launching process 30428: /usr/bin/gnome-terminal --command 
"/bin/sleep 10"
[+857.08s] DEBUG: Process 30428 exited with return value 0
[+857.08s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command 
"/bin/sleep 10": 0
[+857.08s] DEBUG: Session pid=30421: Got 1 message(s) from PAM
[+857.08s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s)
[+857.60s] DEBUG: Session pid=8564: Greeter start authentication for jason
[+857.60s] DEBUG: Session pid=30421: Sending SIGTERM
[+857.61s] DEBUG: Seat: Setting XDG_SEAT=seat0
[+857.61s] DEBUG: Session: Setting XDG_VTNR=7
[+857.61s] DEBUG: Session pid=30437: Started with service 'lightdm', username 
'jason'
[+857.61s] DEBUG: Session pid=30421: Terminated with signal 15
[+857.61s] DEBUG: Session: Failed during authentication
[+857.61s] DEBUG: Seat: Session stopped
[+857.63s] DEBUG: Launching process 30444: /usr/bin/gnome-terminal --command 
"/bin/sleep 10"
[+867.77s] DEBUG: Process 30444 exited with return value 0
[+867.77s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command 
"/bin/sleep 10": 0
[+867.77s] DEBUG: Session pid=30437: Got 1 message(s) from PAM
[+867.77s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s)

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

-- 
You received this bug notification because you are a m

[Desktop-packages] [Bug 1025839] Re: Printing multiple copies submits multiple separate jobs (should submit one job)

** Changed in: df-libreoffice
   Importance: Medium => Wishlist

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

Title:
  Printing multiple copies submits multiple separate jobs (should submit
  one job)

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

Bug description:
  In the print dialog, if "Number of Copies" is set to 50 then 50
  separate, independent print jobs are spooled.  It should submit a
  single print job, specifying 50 copies.   This will allow the printer
  to do the replication if it can (all Postscript printers can).

  This is important because:
   
1) Submitting a separate jobs for each copy causes the page(s) to be 
rendered again and again,
with a drastic reduction in through-put.   

   This is CRUCIAL if the pages contain complex graphics or images which 
take a long time to render
   or transmit to the printer:   A one-minute delay for the first of 50 
copies is okay, but 1 minute for 
   *each* of 50 copies is intolerable.

2) If the print job was a mistake, it is virtually impossible to stop the 
printer.  Pressing the cancel
button on the printer cancels just one copy, but after a little while 
the next one starts printing...

3) It is very inconvenient to cancel the job in CUPS, with 50 separate 
jobs, without affecting other
unrelated jobs in the queue (you can cancel all jobs in the queue at 
once, or one at a time).

  Note that CUPS has always supported a "number of copies" option at the 
command-line level.
  For example
 lpr '-#50'  file.pdf
  prints 50 copies of the file, rendering it once only.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33
  Uname: Linux 3.0.0-22-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 17 11:49:58 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1208535] Re: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup_node()

2013-11-08 Thread zob

Sorry. I kept getting timeouts from launchpad. Here's the crash-log.

** Attachment added: "_usr_lib_gvfs_gvfsd-mtp.1000.crash.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1208535/+attachment/3903568/+files/_usr_lib_gvfs_gvfsd-mtp.1000.crash.tar.gz

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

Title:
  gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup_node()

Status in “gvfs” package in Ubuntu:
  Fix Released

Bug description:
  Occured when unmounting the Nexus 7 (running Android 4.3) by clicking
  the eject symbol in the Nautilus window.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu5
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Aug  5 18:23:23 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2013-06-05 (61 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/2
  Signal: 8
  SourcePackage: gvfs
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup()
  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/gvfs/+bug/1208535/+subscriptions

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

[Desktop-packages] [Bug 1208535] Re: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup_node()

2013-11-08 Thread zob

I get this in 13.10

kernel-version:
Linux desktopssd1310 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux

gvfs version:
gvfs:
  Installed: 1.18.2-0ubuntu1
  Candidate: 1.18.2-0ubuntu1
  Version table:
 *** 1.18.2-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status

Crash-log attached (tar.gz)

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

Title:
  gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup_node()

Status in “gvfs” package in Ubuntu:
  Fix Released

Bug description:
  Occured when unmounting the Nexus 7 (running Android 4.3) by clicking
  the eject symbol in the Nautilus window.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu5
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Aug  5 18:23:23 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2013-06-05 (61 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/2
  Signal: 8
  SourcePackage: gvfs
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup()
  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/gvfs/+bug/1208535/+subscriptions

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

[Desktop-packages] [Bug 1025839]

2013-11-08 Thread Cno

To me this means that I need to give multiple print command when doing more 
copies. Depending on selection/direction or such.
Luckily I do not print much :)

@david: still interested to take a look?

This is set as enhancement. But since 3.3 worked fine, this is a simple
bug?

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

Title:
  Printing multiple copies submits multiple separate jobs (should submit
  one job)

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

Bug description:
  In the print dialog, if "Number of Copies" is set to 50 then 50
  separate, independent print jobs are spooled.  It should submit a
  single print job, specifying 50 copies.   This will allow the printer
  to do the replication if it can (all Postscript printers can).

  This is important because:
   
1) Submitting a separate jobs for each copy causes the page(s) to be 
rendered again and again,
with a drastic reduction in through-put.   

   This is CRUCIAL if the pages contain complex graphics or images which 
take a long time to render
   or transmit to the printer:   A one-minute delay for the first of 50 
copies is okay, but 1 minute for 
   *each* of 50 copies is intolerable.

2) If the print job was a mistake, it is virtually impossible to stop the 
printer.  Pressing the cancel
button on the printer cancels just one copy, but after a little while 
the next one starts printing...

3) It is very inconvenient to cancel the job in CUPS, with 50 separate 
jobs, without affecting other
unrelated jobs in the queue (you can cancel all jobs in the queue at 
once, or one at a time).

  Note that CUPS has always supported a "number of copies" option at the 
command-line level.
  For example
 lpr '-#50'  file.pdf
  prints 50 copies of the file, rendering it once only.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33
  Uname: Linux 3.0.0-22-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 17 11:49:58 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1248260] Re: ibus-daemon hogging resources

2013-11-08 Thread Pablo Capeluto

Happens to me when I leave the netbook (msi-u100) single battery for a
few minutes, or when I change the brightness

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

Title:
  ibus-daemon hogging resources

Status in “ibus” package in Ubuntu:
  New

Bug description:
  At times, typing becomes very sluggish and I can see ibus-daemon
  becomes the process consuming most CPU and most memory in the system.

  Everything else is responsive, i.e. mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 17:08:06 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-07-07 (1217 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: Upgraded to saucy on 2013-10-25 (11 days ago)

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

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

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

2013-11-08 Thread Romano Giannetti

Reported upstream --- I hope it helps.


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

** Also affects: gvfs via
   https://bugzilla.gnome.org/show_bug.cgi?id=711711
   Importance: Unknown
   Status: Unknown

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in GVFS:
  Unknown
Status in Ubuntu GNOME:
  New
Status in “gvfs” package in Ubuntu:
  New
Status in “nautilus-udisks” package in Ubuntu:
  Invalid

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

  Inserting the USB I have in the log:

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

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

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

  ...and it works ok.

  Add: using from command line udisks works, too:

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

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

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

[Desktop-packages] [Bug 1131220] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in gvc_mixer_control_lookup_device_from_stream()

2013-11-08 Thread DancemasterGlenn

I am still using 13.04 currently, yes. I certainly wouldn't mind a ppa,
but I'm able to use the command line and all if I were given the proper
steps to take. The above steps don't look too daunting, but I think I
would need a bit more direction if I'm to go the non-ppa route. Would a
ppa be much trouble?

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

Title:
  [soundnua]: gnome-control-center crashed with SIGSEGV in
  gvc_mixer_control_lookup_device_from_stream()

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

Bug description:
  This only happens when I have my audio interface (my sound card)
  plugged in through usb. I get sound when it is plugged in, I simply
  cannot access the sound menu anymore. Began happening all of a sudden
  a week or two ago, only just diagnosed the problem after I tried a
  fresh install from quantal to the nightly builds of raring. Any help
  would be very, very much appreciated. Thank you!

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Thu Feb 21 09:08:45 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-02-18 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130217)
  MarkForUpload: True
  ProcCmdline: gnome-control-center sound-nua
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb6ba2a1a:call   0xb6c585e3
   PC (0xb6ba2a1a) ok
   source "0xb6c585e3" (0xb6c585e3) ok
   destination "(%esp)" (0xbf66afb0) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
   ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
   ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
   ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
   g_cclosure_marshal_VOID__VOIDv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [soundnua]: gnome-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID__VOIDv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1248143] Re: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases

This bug was fixed in the package friends -
0.2.0+14.04.20131108.1-0ubuntu1

---
friends (0.2.0+14.04.20131108.1-0ubuntu1) trusty; urgency=low

  [ Ken VanDine ]
  * Undo revert for the default polling frequency and ensure interval is
set before using it in the timeout. (LP: #1238083, #1248143)

  [ Colin Watson ]
  * Declare all binary packages Multi-Arch: foreign, since they expose
no architecture-dependent interfaces.

  [ Robert Bruce Park ]
  * More robust handling of Facebook msgids. (LP: #1248302). (LP:
#1248302)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 242
 -- Ubuntu daily releaseFri, 08 Nov 2013 
17:13:24 +

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

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

Title:
  the fix for Bug #1238083 seems to cause the systemsettle tests on mako
  to fail, blocking image releases

Status in “friends” package in Ubuntu:
  Fix Released

Bug description:
  with image 11 the fix for the above bug landed.
  it causes the systemsettle test to fail on mako for any test where 
friends-service is involved.

  
http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/
  
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/

  this currently causes a regression in the overall pass rate of the
  image builds which blocks us from releasing new touch images. please
  revert the change or fix it in a non-regressive way.

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

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

[Desktop-packages] [Bug 1238083] Re: friends-dispatcher is a little busy doing data updates on idle systems

This bug was fixed in the package friends -
0.2.0+14.04.20131108.1-0ubuntu1

---
friends (0.2.0+14.04.20131108.1-0ubuntu1) trusty; urgency=low

  [ Ken VanDine ]
  * Undo revert for the default polling frequency and ensure interval is
set before using it in the timeout. (LP: #1238083, #1248143)

  [ Colin Watson ]
  * Declare all binary packages Multi-Arch: foreign, since they expose
no architecture-dependent interfaces.

  [ Robert Bruce Park ]
  * More robust handling of Facebook msgids. (LP: #1248302). (LP:
#1248302)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 242
 -- Ubuntu daily releaseFri, 08 Nov 2013 
17:13:24 +

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

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

Title:
  friends-dispatcher is a little busy doing data updates on idle systems

Status in “friends” package in Ubuntu:
  Fix Released

Bug description:
  I've noticed that on an idle system friends-dispatcher is doing writes
  to a bunch of files and logs periodically.

  install fatrace, cd to / and run it and you will see the activity.

  This is what I observed over a 30 minute interval on the ubuntu-touch
  phone:

  14:21:52.912959 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.BQ9W4W
  14:21:52.931757 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:26:52.913722 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.V39W4W
  14:26:53.072627 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:31:52.912653 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:52.913020 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:52.933649 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:54.668513 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:31:54.781733 friends-dispatc(2517): W /tmp/oe77uw
  14:31:54.781855 friends-dispatc(2517): CW /tmp/oe77uw
  14:31:54.946894 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:31:54.952448 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:31:54.953394 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:32:24.846278 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:32:24.847956 friends-dispatc(2517): CW 
/home/phablet/.cache/friends/friends.log
  14:32:24.907710 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-shm
  14:32:24.907710 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-wal
  14:32:24.908015 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:36:52.913844 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.HAAX4W
  14:36:52.936030 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:41:52.913325 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:41:52.913660 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:41:52.932856 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:46:52.920893 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:52.921259 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:52.937769 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:54.778651 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:46:54.890253 friends-dispatc(2555): W /tmp/vg79r1
  14:46:54.890376 friends-dispatc(2555): CW /tmp/vg79r1
  14:46:55.082148 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:46:55.090266 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:46:55.091456 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:47:25.854884 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:47:25.856074 friends-dispatc(2555): CW 
/home/phablet/.cache/friends/friends.log
  14:47:25.927485 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-shm
  14:47:25.927485 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-wal
  14:47:25.927790 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db

  Periodic database updates and

[Desktop-packages] [Bug 1248302] Re: facebook msgid parsing fails

This bug was fixed in the package friends -
0.2.0+14.04.20131108.1-0ubuntu1

---
friends (0.2.0+14.04.20131108.1-0ubuntu1) trusty; urgency=low

  [ Ken VanDine ]
  * Undo revert for the default polling frequency and ensure interval is
set before using it in the timeout. (LP: #1238083, #1248143)

  [ Colin Watson ]
  * Declare all binary packages Multi-Arch: foreign, since they expose
no architecture-dependent interfaces.

  [ Robert Bruce Park ]
  * More robust handling of Facebook msgids. (LP: #1248302). (LP:
#1248302)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 242
 -- Ubuntu daily releaseFri, 08 Nov 2013 
17:13:24 +

** Changed in: friends (Ubuntu)
   Status: New => Fix Released

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

Title:
  facebook msgid parsing fails

Status in Friends:
  Confirmed
Status in “friends” package in Ubuntu:
  Fix Released

Bug description:
  ERROR  Thread-22013-10-30 00:33:35,425  friends.utils.base  list index 
out of range
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 159, in 
run
  super().run()
File "/usr/lib/python3.3/threading.py", line 594, in run
  self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 153, in 
_retval_catcher
  self._success_callback(str(func(*args, **kwargs)))
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
197, in receive
  self.home()
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
185, in home
  self._get(ME_URL + '/home', 'messages')
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
180, in _get
  self._publish_entry(entry, stream=stream)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
124, in _publish_entry
  entry=comment)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
92, in _publish_entry
  post_id = message_id.split('_')[1]
  IndexError: list index out of range

  This is clearly caused by the fix from
  https://bugs.launchpad.net/friends/+bug/1185684 so we need a more
  robust way of parsing that string.

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

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

[Desktop-packages] [Bug 1231799]

2013-11-08 Thread Z-jbf-faure

(In reply to comment #8)
> Thank you Björn :-)
> 
> Could this patch be backported to 4.1 ? 

Perhaps not so good idea because this would imply to add translatable
strings.

Best regards. JBF

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

Title:
  Libreoffice quicklist doesn't work says "label empty"

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “libreoffice” source package in Saucy:
  Fix Committed
Status in “unity” source package in Saucy:
  Confirmed

Bug description:
  Unity quick list for libreoffice apps in ubuntu 13.10 beta 2 just says
  "label empty" this is because in the .desktop files it incorrectly
  says "Unityquicklist= New Document" instead of "Name=New Document". If
  I edit the .desktop files to say "Name=New Document" the unity quick
  list works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 27 00:48:13 2013
  InstallationDate: Installed on 2013-09-27 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1231799]

2013-11-08 Thread Z-jbf-faure

Thank you Björn :-)

Could this patch be backported to 4.1 ? If I am not wrong, before this
change desktop files were identical in 4.1 and the master.

Best regards. JBF

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

Title:
  Libreoffice quicklist doesn't work says "label empty"

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “libreoffice” source package in Saucy:
  Fix Committed
Status in “unity” source package in Saucy:
  Confirmed

Bug description:
  Unity quick list for libreoffice apps in ubuntu 13.10 beta 2 just says
  "label empty" this is because in the .desktop files it incorrectly
  says "Unityquicklist= New Document" instead of "Name=New Document". If
  I edit the .desktop files to say "Name=New Document" the unity quick
  list works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 27 00:48:13 2013
  InstallationDate: Installed on 2013-09-27 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1249493] [NEW] onboard keyboard crashes when started in node.js running custom layout

2013-11-08 Thread Brian Newberry

Public bug reported:

lsb_release -rd:
Description:Ubuntu 12.04.1 LTS
Release:12.04

apt-cache policy onboard:
onboard:
  Installed: 0.99.0-0ppa~precise1
  Candidate: 0.99.0-0ppa~precise1
  Version table:
 *** 0.99.0-0ppa~precise1 0
500 http://ppa.launchpad.net/onboard/stable/ubuntu/ precise/main amd64 
Packages
100 /var/lib/dpkg/status
 0.97.0-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
 0.97.0-0ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

apt-cache policy python:
python:
  Installed: 2.7.3-0ubuntu2.2
  Candidate: 2.7.3-0ubuntu2.2
  Version table:
 *** 2.7.3-0ubuntu2.2 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.7.3-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages


I thought I had everything setup just the way I wanted it, but all the sudden, 
it started having problems on one of my three deployments.  Don't really know 
what happened as everyone swears they didn't do anything.  I have installed 
onboard 0.99 from the stable ppa onto Ubuntu 12.04.  I have python 2.7.3.

Here is my situation:
1)  When I try to open onboard with a custom layout from the console, it works 
fine
2)  When I try to open onboard with a non-custom layout (like Compact 
specifically is what I tested) programmatically from within a node.js program 
it works fine
3)  When I try to open onboard with a custom layout (made from Compact, not 
even modified yet) programmatically from within a node.js program, it crashes 
with the following error messages put out to stderr:

 Traceback (most recent call last):
  File "/usr/bin/onboard", line 16, in 
ob = Onboard()
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 111, in 
__init__
self.init()
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 180, in init
self.reload_layout()
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 560, in 
reload_layout
self.load_layout(layout_filename, color_scheme_filename)
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 581, in 
load_layout
layout = LayoutLoaderSVG().load(vk, layout_filename, color_scheme)
  File "/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py", line 84, in 
load
os.path.dirname(layout_filename))
  File "/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py", line 103, 
in _load
return self._load_layout(layout_filename, parent_item)
  File "/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py", line 111, 
in _load_layout
dom = minidom.parse(f).documentElement
  File "/usr/lib/python3.2/xml/dom/minidom.py", line 1945, in parse
return expatbuilder.parse(file)
  File "/usr/lib/python3.2/xml/dom/expatbuilder.py", line 928, in parse
result = builder.parseFile(file)
  File "/usr/lib/python3.2/xml/dom/expatbuilder.py", line 207, in parseFile
parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: syntax error: line 2, column 0

Here is the xml file named NextGen.onboard that it's crashing from:

[Desktop-packages] [Bug 1238083] Re: friends-dispatcher is a little busy doing data updates on idle systems

** Branch linked: lp:ubuntu/trusty-proposed/friends

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

Title:
  friends-dispatcher is a little busy doing data updates on idle systems

Status in “friends” package in Ubuntu:
  Fix Committed

Bug description:
  I've noticed that on an idle system friends-dispatcher is doing writes
  to a bunch of files and logs periodically.

  install fatrace, cd to / and run it and you will see the activity.

  This is what I observed over a 30 minute interval on the ubuntu-touch
  phone:

  14:21:52.912959 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.BQ9W4W
  14:21:52.931757 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:26:52.913722 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.V39W4W
  14:26:53.072627 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:31:52.912653 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:52.913020 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:52.933649 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.LD9W4W
  14:31:54.668513 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:31:54.781733 friends-dispatc(2517): W /tmp/oe77uw
  14:31:54.781855 friends-dispatc(2517): CW /tmp/oe77uw
  14:31:54.946894 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:31:54.952448 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:31:54.953394 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:32:24.846278 friends-dispatc(2517): W 
/home/phablet/.cache/friends/friends.log
  14:32:24.847956 friends-dispatc(2517): CW 
/home/phablet/.cache/friends/friends.log
  14:32:24.907710 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-shm
  14:32:24.907710 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-wal
  14:32:24.908015 friends-dispatc(2517): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:36:52.913844 friends-service(2226): WO 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.HAAX4W
  14:36:52.936030 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams
  14:41:52.913325 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:41:52.913660 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:41:52.932856 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.6E9W4W
  14:46:52.920893 friends-service(2226): O 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:52.921259 friends-service(2226): W 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:52.937769 friends-service(2226): CW 
/home/phablet/.local/share/resources/com.canonical.Friends.Streams.NQLT4W
  14:46:54.778651 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db
  14:46:54.890253 friends-dispatc(2555): W /tmp/vg79r1
  14:46:54.890376 friends-dispatc(2555): CW /tmp/vg79r1
  14:46:55.082148 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:46:55.090266 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:46:55.091456 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:47:25.854884 friends-dispatc(2555): W 
/home/phablet/.cache/friends/friends.log
  14:47:25.856074 friends-dispatc(2555): CW 
/home/phablet/.cache/friends/friends.log
  14:47:25.927485 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-shm
  14:47:25.927485 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db-wal
  14:47:25.927790 friends-dispatc(2555): CW 
/home/phablet/.config/libaccounts-glib/accounts.db

  Periodic database updates and writes to the log are fine, but if we
  see lots of data and metadata writes spaced out over time with a few
  minute intervals between them then spinning media such as hard disks
  don't really get the opportunity to go into idle and spin down, hence
  consuming more power on laptops etc.   Perhaps somebody can look into
  seeing of the number of writes can be reduced or batched better.

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

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

[Desktop-packages] [Bug 1249488] [NEW] package libsane 1.0.23-0ubuntu3 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/rules.

2013-11-08 Thread albgdy

Public bug reported:

At the start of the system

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: libsane 1.0.23-0ubuntu3 [modified: lib/udev/rules.d/40-libsane.rules]
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Thu Nov  7 21:15:35 2013
DuplicateSignature: package:libsane:1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules]:intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
InstallationDate: Installed on 2013-10-20 (19 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: sane-backends
Title: package libsane 1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: intentando 
sobreescribir el compartido `/lib/udev/rules.d/40-libsane.rules', que es 
distinto de otras instancias del paquetes libsane:i386
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sane.d.dll.conf: [modified]
mtime.conffile..etc.sane.d.dll.conf: 2013-10-28T19:54:37.856534

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package saucy

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

Title:
  package libsane 1.0.23-0ubuntu3 [modified:
  lib/udev/rules.d/40-libsane.rules] failed to install/upgrade:
  intentando sobreescribir el compartido
  `/lib/udev/rules.d/40-libsane.rules', que es distinto de otras
  instancias del paquetes libsane:i386

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

Bug description:
  At the start of the system

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: libsane 1.0.23-0ubuntu3 [modified: lib/udev/rules.d/40-libsane.rules]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov  7 21:15:35 2013
  DuplicateSignature: package:libsane:1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules]:intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
  InstallationDate: Installed on 2013-10-20 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: sane-backends
  Title: package libsane 1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: intentando 
sobreescribir el compartido `/lib/udev/rules.d/40-libsane.rules', que es 
distinto de otras instancias del paquetes libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sane.d.dll.conf: [modified]
  mtime.conffile..etc.sane.d.dll.conf: 2013-10-28T19:54:37.856534

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

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

[Desktop-packages] [Bug 1248143] Re: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases

** Branch linked: lp:ubuntu/trusty-proposed/friends

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

Title:
  the fix for Bug #1238083 seems to cause the systemsettle tests on mako
  to fail, blocking image releases

Status in “friends” package in Ubuntu:
  Fix Committed

Bug description:
  with image 11 the fix for the above bug landed.
  it causes the systemsettle test to fail on mako for any test where 
friends-service is involved.

  
http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/
  
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/

  this currently causes a regression in the overall pass rate of the
  image builds which blocks us from releasing new touch images. please
  revert the change or fix it in a non-regressive way.

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

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

[Desktop-packages] [Bug 1248302] Re: facebook msgid parsing fails

** Branch linked: lp:ubuntu/trusty-proposed/friends

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

Title:
  facebook msgid parsing fails

Status in Friends:
  Confirmed
Status in “friends” package in Ubuntu:
  New

Bug description:
  ERROR  Thread-22013-10-30 00:33:35,425  friends.utils.base  list index 
out of range
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 159, in 
run
  super().run()
File "/usr/lib/python3.3/threading.py", line 594, in run
  self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 153, in 
_retval_catcher
  self._success_callback(str(func(*args, **kwargs)))
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
197, in receive
  self.home()
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
185, in home
  self._get(ME_URL + '/home', 'messages')
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
180, in _get
  self._publish_entry(entry, stream=stream)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
124, in _publish_entry
  entry=comment)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line 
92, in _publish_entry
  post_id = message_id.split('_')[1]
  IndexError: list index out of range

  This is clearly caused by the fix from
  https://bugs.launchpad.net/friends/+bug/1185684 so we need a more
  robust way of parsing that string.

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

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

[Desktop-packages] [Bug 1249488] Re: package libsane 1.0.23-0ubuntu3 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/rules.d/

2013-11-08 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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1249488

Title:
  package libsane 1.0.23-0ubuntu3 [modified:
  lib/udev/rules.d/40-libsane.rules] failed to install/upgrade:
  intentando sobreescribir el compartido
  `/lib/udev/rules.d/40-libsane.rules', que es distinto de otras
  instancias del paquetes libsane:i386

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

Bug description:
  At the start of the system

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: libsane 1.0.23-0ubuntu3 [modified: lib/udev/rules.d/40-libsane.rules]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov  7 21:15:35 2013
  DuplicateSignature: package:libsane:1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules]:intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/rules.d/40-libsane.rules', que es distinto de otras instancias del 
paquetes libsane:i386
  InstallationDate: Installed on 2013-10-20 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: sane-backends
  Title: package libsane 1.0.23-0ubuntu3 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: intentando 
sobreescribir el compartido `/lib/udev/rules.d/40-libsane.rules', que es 
distinto de otras instancias del paquetes libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sane.d.dll.conf: [modified]
  mtime.conffile..etc.sane.d.dll.conf: 2013-10-28T19:54:37.856534

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

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

[Desktop-packages] [Bug 1245915] Re: Can't change auto login status to "no" in Ubuntu or Ubuntu GNOME Saucy after "yes" is selected

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

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

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

Title:
  Can't change auto login status to "no" in Ubuntu or Ubuntu GNOME Saucy
  after "yes" is selected

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

Bug description:
  I've been testing alternative DE's in both Ubuntu and Ubuntu GNOME
  Saucy and I've been selecting "auto-login" during installation of the
  OS.

  I now notice that going to System Settings > User Accounts and
  changing the automatic login status from on to off has no effect.
  Since it effects both Ubuntu and Ubuntu GNOME it's also fair to say it
  effects both lightdm and gdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Tue Oct 29 09:52:09 2013
  InstallationDate: Installed on 2013-10-17 (11 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1197395] Re: /run/user/$ID/pulse owned by root and not by the user

2013-11-08 Thread jnns

Problem occurs on a Lenovo Thinkpad X230 as well.

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

Title:
  /run/user/$ID/pulse owned by root and not by the user

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a 
media player (I use Musique), it freezes, as it finds that it cannot write into 
/run/user/$ID/pulse.
  If I change the owner of that directory to me, the media player starts as 
usual and is able to play music.
  I've never had this problem with previous versions of Ubuntu.
  Someone says that running PulseAudio with the -D argument changes the owner 
of that directory, but I didn't try.

  This is before manually changing the owner of that directory:
  $ musique
  Failed to create secure directory (/run/user/1000/pulse): Permission denied+

  ... # it doesn't crash, it keeps waiting

  If needed:
  (dmesg attached)
  lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
  00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
  00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 
port SATA Controller [AHCI mode] (rev 03)
  02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter 
(PCI-Express) (rev 01)
  85:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8072 PCI-E 
Gigabit Ethernet Controller (rev 10)

  From /var/log/syslog:
  Jul  3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] core-util.c: 
Failed to create secure directory (/run/user/1000/pulse): Permission denied
  Jul  3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] main.c: 
User-configured server at 
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to 
start/autospawn.
  Jul  3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] core-util.c: 
Failed to create secure directory (/run/user/1000/pulse): Permission denied
  Jul  3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] main.c: 
User-configured server at 
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to 
start/autospawn.

  This is a fresh installation, I haven't updated it from a previous version. 
I'm using Ubuntu with Unity, not a derivative.
  These are my PPAs:
  canonical-qt5-edgers-qt5-proper-saucy.list
  dropbox.list
  dukto.list
  google-earth.list
  jd-team-jdownloader-saucy.list
  kivy-team-kivy-saucy.list
  mitya57-ppa-saucy.list
  numix-icon-theme-dev-utouch-saucy.list
  otto-kesselgulasch-gimp-saucy.list
  phablet-team-desktop-deps-saucy.list
  satyajit-happy-themes-saucy.list
  steam.list
  ubuntu-sdk-team-ppa-saucy.list
  ubuntutrucchi.list
  ubuntutrucchi-testing.list
  ubuntu-wine-ppa-saucy.list
  webupd8team-y-ppa-manager-saucy.list

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

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

[Desktop-packages] [Bug 1249487] [NEW] freeze with display system message regarding a display problem on log in

2013-11-08 Thread Mosh Aharoni

Public bug reported:

After login with my username and password, the display became black, mouse 
curser was stuck and changed into a "target" shape, and a display message 
appeard saying that there is some kind of display problem, and gave me 
different options to choose from (I didn't write them down). After choosing any 
one of the options, the screen became black and the system frooze - needed a 
hard reboot. 
First time it ever happend on this system. +  system updated about two days ago 
using uodate manager.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Fri Nov  8 23:04:31 2013
InstallationDate: Installed on 2012-12-17 (326 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
SourcePackage: unity-greeter
UpgradeStatus: Upgraded to saucy on 2013-10-26 (13 days ago)

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


** Tags: apport-bug i386 saucy

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

Title:
  freeze with display system message regarding a display problem on log
  in

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

Bug description:
  After login with my username and password, the display became black, mouse 
curser was stuck and changed into a "target" shape, and a display message 
appeard saying that there is some kind of display problem, and gave me 
different options to choose from (I didn't write them down). After choosing any 
one of the options, the screen became black and the system frooze - needed a 
hard reboot. 
  First time it ever happend on this system. +  system updated about two days 
ago using uodate manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-greeter 13.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Fri Nov  8 23:04:31 2013
  InstallationDate: Installed on 2012-12-17 (326 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  SourcePackage: unity-greeter
  UpgradeStatus: Upgraded to saucy on 2013-10-26 (13 days ago)

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

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

[Desktop-packages] [Bug 1249358] Re: PS3 Eye showing with lsusb, but not mounted or available now to Cheese, Skype, etc., .

2013-11-08 Thread Michael Hurt

** Package changed: libgphoto2 (Ubuntu) => gspca (Ubuntu)

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

Title:
  PS3 Eye showing with lsusb, but not mounted or available now to
  Cheese, Skype, etc.,.

Status in “gspca” package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 13.10
  PS3 Eye driver or underlying USB auto mount library
  PS3 Eye about 5 days ago was working properly as it should. Mounted and 
available when Ubuntu booted.
  PS3 Eye isn't being mounted as /dev/video and /dev/audio.

  The PS3 Eye has 2 leds, 1 shows camera in use, while the other shows
  power (from the usb port). During a normal bootup into linux, before
  the operating system gui is fully loaded, the red "in use" light will
  light then go off, then the system comes up for use. One logged in, I
  can use the camera as a built in mic using Skype, Cheese, StopMotion,
  etc.,.

  Earlier this week we'd completed some simple animation using
  StopMotion, and everything seems to work as expected with the camera.
  The only hitch being a parameter that was omitted in the StopMotion
  installation script that once manually entered, worked as normal. That
  was a StopMotion problem, not a PS3 Eye problem.

  After 2 quick minor updates (didn't notice which, but I did notice it
  was small) the PS3 Eye is no longer usable as a camera or microphone.

  Here's what i've noticed so far:

  When I do a "lsusb" here's what i get...

  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 1415:4000 Nam Tai E&E Products Ltd. or OmniVision 
Technologies, Inc.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 009 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ... the "Nam Tai" entry above, I believe is the PS3 Eye. This is where
  the PS3 Eye is not recognized. Now yesterday when it was working,
  there was a 2nd "Nam Tai" entry which looked the same except at the
  end of the text description is had something like "Sony Playstation".
  So when 2 entries were present when using "lsusb" the camera worked,
  with just 1 entry like the above showing, it doesn't.

  I'm guessing either the library assigned to the camera isn't seeing it
  as a valid camera, or something isn't fully mounting the camera
  properly. Is there a command I can use to manally "mount" that
  particular usb device and see if that's the problem (not being
  properly mounted)?

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

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

[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2013-11-08 Thread Chad Miller

Hrm.  I know of no change that would affect this bug. Keeping as
Incomplete because Steven may still see it.

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1199933] Re: apparmor parser in precise does not support block_suspend capability (needed for backported kernels)

2013-11-08 Thread Marc Deslauriers

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

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: apparmor (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  apparmor parser in precise does not support block_suspend capability
  (needed for backported kernels)

Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “cups” package in Ubuntu:
  New
Status in “apparmor” source package in Precise:
  Triaged
Status in “apparmor” source package in Saucy:
  Fix Released

Bug description:
  When running an up-to-date precise system with a 
linux-image-generic-lts-raring HWE kernel (linux 3.8), 
  the precise verion of apparmor will deny all attempts of apparmored apps to 
call the block_suspend system call:

  For example: 
  type=AVC msg=audit(XX.XXX:X): apparmor="DENIED" 
operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1040 comm="cupsd" 
pid=1040 comm="cupsd" capability=36  capname="block_suspend"

  But it is also impossible to add block_suspend to the apparmor profiles, 
because the AppArmor parser does not know about it:
Setting /usr/sbin/cupsd to enforce mode.
Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update 
cache, disable, or force-complain via stdin
AppArmor parser error, in stdin line 24: Invalid capability block_suspend.

  This seems to make it impossible to have apparmor  not deny block
  suspend when using an LTS HWE kernel.

  This seems to be related to bug #1052098.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apparmor 2.7.102-0ubuntu3.7
  ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Wed Jul 10 12:48:24 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  KernLog: Jul 10 12:34:08 gumdrop kernel: [580960.424225] SGI XFS with ACLs, 
security attributes, realtime, large block/inode numbers, no debug enabled
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.8.0-25-generic 
root=UUID=981723af-1da9-455d-b776-3a1e8885efde ro rootflags=subvol=@
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  audit.log: Error: [Errno 13] Permission denied: '/var/log/audit/audit.log'

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

-- 
Mailing list: https://launchpad.net/~desktop-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-11-08 Thread Nazar Mokrynskyi

Can't use Right Ctrl key.
What is interesting, if hold ctrl and press some letter key - layout changes! 
If just click - returns to English, regardless which layout was before. The 
same for Caps Lock key, but, weirdly, Right Shift key works perfectly!!!
WTF guys?
This is not high priority bug, this is EXTREMELY HIGH PRIORITY ANNOYING BUG FOR 
ALMOST EVERY GNOME SHELL USER!

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

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

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged

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

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

  === gnome-control-center ===

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

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

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

  === gnome-settings-daemon ===

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

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

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

  --

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

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

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

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

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
     * Can't set keyboard layout change to Ctrl+Shift (bug 1245991)
     * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V 
are not working in gnome-terminal (bug 1246656)

  Shift+Shift:
     * Can't set keyboard layout change to Shift+Shift (bug 1245272)
     * lock screen - gnome-screensaver (bug 1245278)
     * Unity greeter (bug 1245280)

  Bugs which belong to keyboard layout switching:
     * Hotkeys not functional in non-latin keyboard layout in 13.10 (bug 
1226962)
     * Keyboard Layout Options window is missed in gnome-control-center 
keyboard (bug 1245064)
     * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy (bug 1245188)
     * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy (bug 1245199)
     * Keyboard shortcut for changing keyboard layout does not work on lock 
screen (bug 1244548)
     * [FFe] indicator-keyboard not working under greeter (bug 1228207)
     * Lost ability to remap Caps Lock to Ctrl (bug 1215826)
     * gnome-control-center keyboard no longer has way to modify caps lock key 
behavior (bug 1224575)
     * Pressing Caps Lock toggles LED even when mapped to another key (bug 
1221403)
 * Switching layout turns off NumLock (bug 1247668)

  --

  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
  ProcVersionSignatur

[Desktop-packages] [Bug 973552] Re: telepathy-logger crashed with SIGSEGV in _IO_vfprintf_internal()

2013-11-08 Thread Ryan Daly

I'm seeing this bug, as well.  Here's the stack trace...  If any more
information is needed I can try to provide it.

: linux13 123#; apport-retrace --stdout 
/var/crash/_usr_lib_telepathy_telepathy-logger.1245.crash
--- stack trace ---
#0  0x7f38ab01e3b1 in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7f38ab0dd911 in __vasprintf_chk () from 
/lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7f38aba3edcb in g_vasprintf () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7f38aba1e46d in g_strdup_vprintf () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f38abf0ef0e in _tpl_debug (flag=TPL_DEBUG_CHANNEL, format=) at debug.c:97
message = 
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7fff508844b0, reg_save_area = 0x7fff508843e0}}
#5  0x7f38aa25ca14 in ffi_call_unix64 () from 
/usr/lib/x86_64-linux-gnu/libffi.so.6
No symbol table info available.
#6  0x7f38aa25c435 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
No symbol table info available.
#7  0x7f38abcc1b16 in g_cclosure_marshal_generic_va () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#8  0x7f38abcc0eca in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#9  0x7f38abcd9711 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#10 0x7f38abcda724 in g_signal_emit_by_name () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#11 0x7f38ab6682b6 in ?? () from /usr/lib/libtelepathy-glib.so.0
No symbol table info available.
#12 0x7f38ab668651 in ?? () from /usr/lib/libtelepathy-glib.so.0
No symbol table info available.
#13 0x7f38ab640051 in ?? () from /usr/lib/libtelepathy-glib.so.0
No symbol table info available.
#14 0x7f38ab6f74ec in ?? () from /usr/lib/libtelepathy-glib.so.0
No symbol table info available.
#15 0x7f38aba03d13 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#16 0x7f38aba04060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#17 0x7f38aba0445a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#18 0x0040164e in main (argc=, argv=) at 
telepathy-logger.c:194
dbus_srv = 
observer = 0x1315000
error = 0x0
__PRETTY_FUNCTION__ = "main"

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

Title:
  telepathy-logger crashed with SIGSEGV in _IO_vfprintf_internal()

Status in Telepathy Logger:
  Unknown
Status in “telepathy-logger” package in Ubuntu:
  Confirmed

Bug description:
  telepathy-logger crashed with SIGSEGV in vfprintf()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: telepathy-logger 0.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Thu Apr  5 00:28:50 2012
  ExecutablePath: /usr/lib/telepathy/telepathy-logger
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120309)
  ProcCmdline: /usr/lib/telepathy/telepathy-logger
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-logger
  Title: telepathy-logger crashed with SIGSEGV in vfprintf()
  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/telepathy-logger/+bug/973552/+subscriptions

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

[Desktop-packages] [Bug 1249358] Re: PS3 Eye showing with lsusb, but not mounted or available now to Cheese, Skype, etc., .

2013-11-08 Thread Michael Hurt

Just starting digging around and noticed this entry in the "syslog":

gspca_ov534: unknown parameter 'videomode' ignored

Checking the contents of "dmesg" shows this when plugging in the PS3
Eye:

Nov  8 15:35:43 mthpc kernel: [  295.511533] usb 2-2: Manufacturer:
SONY

Checking "modinfo gspca-ov534" shows this:

filename:   
/lib/modules/3.11.0-13-generic/kernel/drivers/media/usb/gspca/gspca_ov534.ko
license:GPL 
description:GSPCA/OV534 USB Camera Driver
author: Antonio Ospite 
srcversion: C333FFCB2949885F148658C
alias:  usb:v06F8p3002d*dc*dsc*dp*ic*isc*ip*in*
alias:  usb:v1415p2000d*dc*dsc*dp*ic*isc*ip*in*
depends:gspca_main,videodev
intree: Y
vermagic:   3.11.0-13-generic SMP mod_unload modversions 

I'm wondering if the problem with the camera is the GSPCA driver isn't
initializing it properly and updating the system tables.

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

Title:
  PS3 Eye showing with lsusb, but not mounted or available now to
  Cheese, Skype, etc.,.

Status in “libgphoto2” package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 13.10
  PS3 Eye driver or underlying USB auto mount library
  PS3 Eye about 5 days ago was working properly as it should. Mounted and 
available when Ubuntu booted.
  PS3 Eye isn't being mounted as /dev/video and /dev/audio.

  The PS3 Eye has 2 leds, 1 shows camera in use, while the other shows
  power (from the usb port). During a normal bootup into linux, before
  the operating system gui is fully loaded, the red "in use" light will
  light then go off, then the system comes up for use. One logged in, I
  can use the camera as a built in mic using Skype, Cheese, StopMotion,
  etc.,.

  Earlier this week we'd completed some simple animation using
  StopMotion, and everything seems to work as expected with the camera.
  The only hitch being a parameter that was omitted in the StopMotion
  installation script that once manually entered, worked as normal. That
  was a StopMotion problem, not a PS3 Eye problem.

  After 2 quick minor updates (didn't notice which, but I did notice it
  was small) the PS3 Eye is no longer usable as a camera or microphone.

  Here's what i've noticed so far:

  When I do a "lsusb" here's what i get...

  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 1415:4000 Nam Tai E&E Products Ltd. or OmniVision 
Technologies, Inc.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 009 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ... the "Nam Tai" entry above, I believe is the PS3 Eye. This is where
  the PS3 Eye is not recognized. Now yesterday when it was working,
  there was a 2nd "Nam Tai" entry which looked the same except at the
  end of the text description is had something like "Sony Playstation".
  So when 2 entries were present when using "lsusb" the camera worked,
  with just 1 entry like the above showing, it doesn't.

  I'm guessing either the library assigned to the camera isn't seeing it
  as a valid camera, or something isn't fully mounting the camera
  properly. Is there a command I can use to manally "mount" that
  particular usb device and see if that's the problem (not being
  properly mounted)?

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

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

[Desktop-packages] [Bug 958007] Re: First switching of the keyboard layout doesn't update the layout indicator

2013-11-08 Thread Nazar Mokrynskyi

How long you are planning to save this bug?

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

Title:
  First switching of the keyboard layout doesn't update the layout
  indicator

Status in Indicator keyboard:
  New
Status in Ubuntu network, Bluetooth, keyboard menus:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Good day!

  I am reporting this bug after this one has been fixed: 
https://bugs.launchpad.net/ubuntu/oneiric/+source/gnome-settings-daemon/+bug/885730
  This is because an issue remained with incorrect keyboard layout displaying 
by the indicator.

  The problem is in the first keyboard layout switching right after
  start of an application. The first switching leads to actual change of
  the layout but it is not followed by the indicator change.

  To reproduce:
  1) Start any application (say, gedit). The layout is "en" and the indicator 
shows also "en".
  2) Switch the layout to the other. The layout will actually be changed but 
the indicator will still show "en" which is incorrect.

  And one more observation. If you do something (press Alt to reveal HUD, 
switch to another window and then return back) before the first layout change, 
the indicator will react correctly after that.
  Also, I can reproduce this within both settings "Use the same layout for all 
windows" and "Allow different layouts for individual windows".

  Thank you!

  P.S. This is my first bug report, so if something is wrong, I give my
  sincere apology. Please correct me then.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.3.91-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CasperVersion: 1.311
  Date: Sat Mar 17 20:43:56 2012
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120317)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 964620] Re: bogus selection after undoing and redoing a cut operation

** Changed in: gedit
   Status: New => Confirmed

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

Title:
  bogus selection after undoing and redoing a cut operation

Status in Light-Weight Text Editor for Gnome:
  Confirmed
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  - open gedit
  - write the text: abcdefghijklmnopqrstuvwxyz
  - select the portion from "e" to "i" included (5 characters)
  - cut it e.g. by using ctrl+x  => no text is selected now (ok)
  - undo with ctrl+z  => the un-cutted text is selected now (ok)
  - redo with ctrl+shift+z

  Expected: after re-doing, no character should be selected

  Observed: => after redoing, the characters "jklmn" are selected, which
  are the one that occupy the positions previously occupied by the
  selected text.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gedit 3.2.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Mar 25 17:50:05 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (108 days ago)

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

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

[Desktop-packages] [Bug 514930] Re: URLs not clickable

** Changed in: evince
   Status: New => Confirmed

** Changed in: evince
   Importance: Medium => Wishlist

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

Title:
  URLs not clickable

Status in Evince document viewer:
  Confirmed
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: evince

  The URL contained in the pdf are not clickable

  Ubuntu Lucid 10.04 (Netbook Edition)

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

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

[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2013-11-08 Thread shantanu saha

bug fixed in Version 30.0.1599.114 Ubuntu 13.10
(30.0.1599.114-0ubuntu0.13.10.2).

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1246656] Re: If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal

2013-11-08 Thread Norbert

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

** This bug has been marked a duplicate of bug 1245473
   Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes 
shortcuts with ctrl+shift, etc not working in any program

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

Title:
  If keyboard layout switching hotkey is set to Ctrl+Shift,
  Ctrl+Shift+C/V are not working in gnome-terminal

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

Bug description:
  I have installed recent updates:
  gnome-control-center – 1:3.6.3-0ubuntu45
  gnome-settings-daemon – 3.8.5-0ubuntu11.1

  In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and 
pasting text in gnome-terminal even if my keyboard layout change hotkey is set 
to Ctrl+Shift. 
  In Saucy I can't use these shortcuts in gnome-terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Thu Oct 31 13:59:44 2013
  InstallationDate: Installed on 2013-10-20 (10 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2013-11-08 Thread Norbert

Merged bug 1246656 here. It's description was:
"In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and 
pasting text in gnome-terminal even if my keyboard layout change hotkey is set 
to Ctrl+Shift.
In Saucy I can't use these shortcuts in gnome-terminal."

Bug exists with the latest versions of packages (gnome-control-center
1:3.6.3-0ubuntu45.1, gnome-settings-daemon 3.8.5-0ubuntu11.1).

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

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

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  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/1245473/+subscriptions

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

This bug was fixed in the package apparmor - 2.8.0-0ubuntu34

---
apparmor (2.8.0-0ubuntu34) trusty; urgency=low

  [ Tyler Hicks ]
  * 0078-parser-check-for-dbus-kernel-support.patch: The parser should not
include D-Bus rules in the binary policy that it loads into the kernel if
the kernel does not support D-Bus rules (LP: #1231778)
  * 0079-utils-ignore-unsupported-log-events.patch: aa-logprof should ignore
audit events that it does not yet support instead of treating them as
errors (LP: #1243932)
  * 0080-tests-use-ldconfig-for-library-detection.patch: Fix libapparmor
detection in regression tests after the multiarch changes

  [ Jamie Strandboge ]
  * 0081-python-abstraction-updates.patch: Add rules in support of Python 3.3

  [ Chad Miller ]
  * debian/patches/0001-add-chromium-browser.patch: Follow new chromium-browser
sandbox name.  Keep old name for now to allow transition. LP: #1247269
 -- Tyler HicksMon, 04 Nov 2013 15:57:30 -0800

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

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “apparmor” source package in Saucy:
  In Progress
Status in “network-manager” source package in Saucy:
  Invalid
Status in “apparmor” source package in Trusty:
  Fix Released
Status in “network-manager” source package in Trusty:
  Invalid

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Automated Test Case]

  * test_lp1231778 has been added to QRT's test-apparmor.py script
  * Run the test under the latest Saucy, Raring, and Lucid kernels to excercise 
all possible test load scenarios

  [Manual Test Case]

  * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Install and reboot into newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Reboot into Ubuntu 3.11.0-12-generic kernel

  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
  $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
  method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
     array [
    string "org.freedesktop.DBus"
  ...
  $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message

[Desktop-packages] [Bug 1203349] Re: nautilus crashed with SIGSEGV in _gdk_pixbuf_new_from_uri_at_scale()

2013-11-08 Thread Shaharil Ahmad

Frequently happen on my Download folder, Desktop, when encoding file and
also on external hdd when the process are interupted or incomplete. The
0 byte file making folder and hdd inaccessable and also my desktop files
on saucy gone.

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

Title:
  nautilus crashed with SIGSEGV in _gdk_pixbuf_new_from_uri_at_scale()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Occurs when opening a folder that contains a  video or audio file that is 
invalid or a 0 byte file. Nautilus crashes  on the invalid or o byte file when 
attempting to thumbnail instead of just moving past
  Generally there would be no reason to have such file but it can be created 
when an encoder errors out
  nautilus should be able to deal with gracefully without crashing

  Test case:
  run in terminal -
  touch Videos/1.mp4
  Now try to open Videos in nautilus

  nautilus Videos
  sys:1: Warning: g_object_set: assertion 'G_IS_OBJECT (object)' failed

  ** (nautilus:4334): CRITICAL **:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

  ** (nautilus:4334): CRITICAL **: nautilus_menu_provider_get_background_items: 
assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
  totem-video-thumbnailer couldn't open file 'file:///home/doug/Videos/1.mp4'

  (nautilus:4334): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close:
  assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed

  (nautilus:4334): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_get_pixbuf: 
assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed
  sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Segmentation fault (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 20 13:53:27 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1018x500+57+24'"
  InstallationDate: Installed on 2013-07-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2535c621e0 : mov(%rdi),%eax
   PC (0x7f2535c621e0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
   clone () from /lib/x86_64-linux-gnu/libc.so.6
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   brasero 3.8.0-1ubuntu2
   file-roller 3.8.3-0ubuntu1
   python-nautilus 1.1-3ubuntu3
   totem   3.8.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1240088] Re: add network (nm-applet) to login screen

2013-11-08 Thread Marc Deslauriers

NACK. This needs the unity-greeter policykit file so the network settings can't 
get modified at the login screen.
I believe network-manager also needs some modifications so the policykit 
permissions are properly enforced.

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

Title:
  add network (nm-applet) to login screen

Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “unity-greeter” source package in Precise:
  Triaged

Bug description:
  [Impact] 
   * User has a hard time to login via network, (krb5) if nm-applet is not 
accessible via login screen. 

  [Test Case]
  1) make sure the system is configure to authenticate via krb5
  2) login with user "A" and disconnect from the network via nm-applet, logout
  3) Try to login with user B

   a. Actual Results:
  User B is not able to authenticate because the system is not connected to the 
network so we are not able to talk to the krb servers

   b. Expected Results:
  Users should be able to use network manager from within unity greater and 
reconnect to the network before attempting to login.

  
  [Regression Potential] 
   * n/a . The patch is a backport from upstream

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

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

[Desktop-packages] [Bug 1246656] Re: If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal

2013-11-08 Thread Andrey

Actually, Ctrl+Shift+[any key combination] hotkeys doesn't work in any
program after that, see bug #1245473

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

Title:
  If keyboard layout switching hotkey is set to Ctrl+Shift,
  Ctrl+Shift+C/V are not working in gnome-terminal

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

Bug description:
  I have installed recent updates:
  gnome-control-center – 1:3.6.3-0ubuntu45
  gnome-settings-daemon – 3.8.5-0ubuntu11.1

  In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and 
pasting text in gnome-terminal even if my keyboard layout change hotkey is set 
to Ctrl+Shift. 
  In Saucy I can't use these shortcuts in gnome-terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Thu Oct 31 13:59:44 2013
  InstallationDate: Installed on 2013-10-20 (10 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248391] Re: Can't mirror more than 640x480

2013-11-08 Thread Chris Weiss

I'll get the log later, laptop is not with me.

to clarify, the external is a full HD projector, and JustWorks with
windows on this laptop.  The 640x480 option is the only option that
shows as soon as I check the "mirror" box.

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

Title:
  Can't mirror more than 640x480

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

Bug description:
  i3 cpu, lspci lists as vga "Intel Corporation 2nd Generation Core
  Processor Family Integrated Graphics Controller (rev 09)"

  trying to mirror lcd and HDMI.  only option is 640x480.  tried
  increasing video ram in BIOS, 512MB won't boot, all smaller values do
  not change the options.

  I cam mirror at 720P in windows, so the hardware should be capable.

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

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

[Desktop-packages] [Bug 1248303] Re: Regression: cannot install driver for Canon MP160

** Also affects: system-config-printer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Regression: cannot install driver for Canon MP160

Status in “gnome-control-center” package in Ubuntu:
  Incomplete
Status in “system-config-printer” package in Ubuntu:
  New

Bug description:
  Installing driver for Canon MP160 has worked perfectly from 12.04 to
  13.04, but not anymore in 13.10. The USB printer get detected
  correctly, but when installing the driver via "New Printer" dialog,
  only gutenprint can be selected and the "Installing driver gutenprint"
  dialog just gets stuck and nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 22:10:02 2013
  InstallationDate: Installed on 2013-10-20 (16 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1228961] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Nothing more

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 23 00:47:09 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'840x550+58+71'"
  InstallationDate: Installed on 2013-09-14 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MarkForUpload: True
  ProcCmdline: nautilus /home/username/Documentos/Aficiones/4WD\ Truck/Motor
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9950fcedd5:mov0x10(%rax),%rdi
   PC (0x7f9950fcedd5) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7f996b54a700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy fuse games 
lpadmin plugdev sambashare saned scanner src sudo tape tty users video voice

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

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

[Desktop-packages] [Bug 1217085] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  It happened when, from shotwell, opening the corresponding folder of a
  picture.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Aug 26 21:05:20 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'262'
  InstallationDate: Installed on 2013-08-16 (10 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130815)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f3cff5bd1c0 : mov(%rdi),%eax
   PC (0x7f3cff5bd1c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7f3cefdad700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  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/nautilus/+bug/1217085/+subscriptions

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

[Desktop-packages] [Bug 1228118] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Crash while opening ntfs partition on local disk.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  Uname: Linux 3.12.0-031200rc1-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Sep 20 20:17:58 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'648x715+716+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-07-12 (69 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb9b1cb1c0 : mov(%rdi),%eax
   PC (0x7feb9b1cb1c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7feb8bd9b700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: Upgraded to saucy on 2013-08-24 (26 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers video

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

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

[Desktop-packages] [Bug 1234356] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Random-seeming crash of nautilus while downloading files through
  firefox and conducting a GUI-update-manager upgrade.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct  2 14:19:53 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'840x550+49+24'"
  InstallationDate: Installed on 2013-09-29 (2 days ago)
  InstallationMedia: This
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f44ae45e1c0 : mov(%rdi),%eax
   PC (0x7f44ae45e1c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7f449feb2700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2013-09-30T09:32:45.690249

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

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

[Desktop-packages] [Bug 1234115] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Nautilus crashes when trying to open internal storage on Nexus 4 phone
  running cyanogenmod 10.2, and on Nexus 4 running stock Android 4.3

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  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-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct  2 12:41:01 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+326+110'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'161'
  InstallationDate: Installed on 2013-08-28 (34 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc4b50761c0 : mov(%rdi),%eax
   PC (0x7fc4b50761c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7fc47c197700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (4 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev powerdev sambashare scanner sudo tape video

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

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

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

2013-11-08 Thread Jean Marc

Hi,

Same issue here, randomly, with an azerty layout keyboard (French,
deprecated variant), but only once a week approximately.

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

Title:
  on bootup wrong keyboard layout is recognized

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

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

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

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

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

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

[Desktop-packages] [Bug 1234415] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  If a Nautilus window is open showing some video files which are
  downloaded by Firefox it crashes while trying to create a thumbnail
  image. After downloads have finished the thumbnails appear and
  Nautilus doesn't crash anymore.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct  2 22:26:33 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1080x1032+65+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'150'
  InstallationDate: Installed on 2012-03-18 (563 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f634dada1c0 : mov(%rdi),%eax
   PC (0x7f634dada1c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7f6342a1d700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: Upgraded to saucy on 2013-09-29 (2 days ago)
  UserGroups: adm admin cdrom dialout fuse libvirtd lp lpadmin plugdev 
sambashare vboxusers

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

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

[Desktop-packages] [Bug 1210809] Re: nautilus crashed with SIGSEGV in gnome_desktop_thumbnail_factory_generate_thumbnail()

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  gnome_desktop_thumbnail_factory_generate_thumbnail()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Happened while exporting a video with OpenShot to my desktop, while
  nautilus was open with the desktop folder.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1 [modified: usr/bin/nautilus 
usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server 
usr/lib/nautilus/nautilus-convert-metadata]
  Uname: Linux 3.10.1-pf x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Sat Aug 10 17:25:16 2013
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2010-05-06 (1192 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  ProcCmdline: /usr/bin/nautilus /home/username/Desktop
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x3c3bc0e1c0 :   mov(%rdi),%eax
   PC (0x3c3bc0e1c0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread (arg=0x7f89052a0700) at pthread_create.c:311
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: Upgraded to saucy on 2013-07-06 (35 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd 
lpadmin netdev plugdev sambashare saned tape users vboxusers video
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2012-04-26T22:17:41.801936

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

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

[Desktop-packages] [Bug 1203349] Re: nautilus crashed with SIGSEGV in _gdk_pixbuf_new_from_uri_at_scale()

2013-11-08 Thread Timo Palomaa

Also started having this in 13.10, nautilus 3.8.2. Too bad didn't check
when the 0-byte file was created (was a 0 byte .gif), but I'm fairly
sure it was there previously. Yesterday I did some system updates
though...

In my case I narrowed the problem down to nautilus-compare package.

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

Title:
  nautilus crashed with SIGSEGV in _gdk_pixbuf_new_from_uri_at_scale()

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Occurs when opening a folder that contains a  video or audio file that is 
invalid or a 0 byte file. Nautilus crashes  on the invalid or o byte file when 
attempting to thumbnail instead of just moving past
  Generally there would be no reason to have such file but it can be created 
when an encoder errors out
  nautilus should be able to deal with gracefully without crashing

  Test case:
  run in terminal -
  touch Videos/1.mp4
  Now try to open Videos in nautilus

  nautilus Videos
  sys:1: Warning: g_object_set: assertion 'G_IS_OBJECT (object)' failed

  ** (nautilus:4334): CRITICAL **:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

  ** (nautilus:4334): CRITICAL **: nautilus_menu_provider_get_background_items: 
assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
  totem-video-thumbnailer couldn't open file 'file:///home/doug/Videos/1.mp4'

  (nautilus:4334): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close:
  assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed

  (nautilus:4334): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_get_pixbuf: 
assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed
  sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Segmentation fault (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 20 13:53:27 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1018x500+57+24'"
  InstallationDate: Installed on 2013-07-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2535c621e0 : mov(%rdi),%eax
   PC (0x7f2535c621e0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.7
   gnome_desktop_thumbnail_factory_generate_thumbnail () from 
/usr/lib/libgnome-desktop-3.so.7
   ?? ()
   start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
   clone () from /lib/x86_64-linux-gnu/libc.so.6
  Title: nautilus crashed with SIGSEGV in 
gnome_desktop_thumbnail_factory_generate_thumbnail()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   brasero 3.8.0-1ubuntu2
   file-roller 3.8.3-0ubuntu1
   python-nautilus 1.1-3ubuntu3
   totem   3.8.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

** Branch linked: lp:ubuntu/trusty-proposed/apparmor

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Fix Committed
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “apparmor” source package in Saucy:
  In Progress
Status in “network-manager” source package in Saucy:
  Invalid
Status in “apparmor” source package in Trusty:
  Fix Committed
Status in “network-manager” source package in Trusty:
  Invalid

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Automated Test Case]

  * test_lp1231778 has been added to QRT's test-apparmor.py script
  * Run the test under the latest Saucy, Raring, and Lucid kernels to excercise 
all possible test load scenarios

  [Manual Test Case]

  * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Install and reboot into newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Reboot into Ubuntu 3.11.0-12-generic kernel

  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
  $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
  method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
     array [
    string "org.freedesktop.DBus"
  ...
  $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient, 0 matched 
rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)

  [Regression Potential]

  * The regression potential is minor because the fix is small and easy
  to test

  [Original Bug Report]

  Note that apparmor_parser warns that the dbus rule(s) will not be
  enforced and then loads the binary policy without any dbus rules.

  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

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

[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2013-11-08 Thread Chad Miller

In a terminal, run 
gnome-open http://launchpad.net/
.  What happens?

Once chromium is running, hold Alt and hit Home button on keyboard.
What happens?

Finally, when you reproduce the bug, please paste the result of this run
in a terminal:

ps xauw |grep chromium

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Chad Miller (cmiller)

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

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

Title:
  URL doesn't open from other application in chromium-browser

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

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1248391] Re: Can't mirror more than 640x480

2013-11-08 Thread Chris Wilson

First step is to attach your Xorg.0.log. For mirroring with HDMI you
will be limited to the intersection of modes supported by both the
monitor and the LCD. If the HDMI monitor does not list 720p as being
supported, you will need to override it and add that mode yourself.

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

Title:
  Can't mirror more than 640x480

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

Bug description:
  i3 cpu, lspci lists as vga "Intel Corporation 2nd Generation Core
  Processor Family Integrated Graphics Controller (rev 09)"

  trying to mirror lcd and HDMI.  only option is 640x480.  tried
  increasing video ram in BIOS, 512MB won't boot, all smaller values do
  not change the options.

  I cam mirror at 720P in windows, so the hardware should be capable.

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

2013-11-08 Thread Jamie Strandboge

apparmor 2.8.0-0ubuntu34 uploaded to trusty.

** Changed in: apparmor (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Fix Committed
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “apparmor” source package in Saucy:
  In Progress
Status in “network-manager” source package in Saucy:
  Invalid
Status in “apparmor” source package in Trusty:
  Fix Committed
Status in “network-manager” source package in Trusty:
  Invalid

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Automated Test Case]

  * test_lp1231778 has been added to QRT's test-apparmor.py script
  * Run the test under the latest Saucy, Raring, and Lucid kernels to excercise 
all possible test load scenarios

  [Manual Test Case]

  * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Install and reboot into newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Reboot into Ubuntu 3.11.0-12-generic kernel

  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
  $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
  method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
     array [
    string "org.freedesktop.DBus"
  ...
  $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient, 0 matched 
rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)

  [Regression Potential]

  * The regression potential is minor because the fix is small and easy
  to test

  [Original Bug Report]

  Note that apparmor_parser warns that the dbus rule(s) will not be
  enforced and then loads the binary policy without any dbus rules.

  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1249468] [NEW] Screen Flickering and display problems

2013-11-08 Thread Shashwat Sridhar

Public bug reported:

On doing a fresh install of Ubuntu 13.10 on a system which previously
had 12.04, using a USB stick, I booted my HP ProBook 445 laptop (AMD
A6-5350 chip with Radeon HD Graphics) to find that some launcher icons
were flashing on and off, and the screen generally seemed to be
flickering, with the icons in the system tray and the launcher blinking.
The system itself was working fast, but there seemed to be something
wrong with the display. A couple of minutes after it booted completely,
the Update Manager started up, but its windows were flickering, and it
was difficult to read text written inside the window. After it completed
updating, i rebooted the laptop, and things seemed to flickering less
than earlier. So i thought i'd open a simple application, like Files,
and see if the display was still awry. It still was. I could see
occassional streaks and dark lines across the screen, and the display
seemed to have some serious internal error. A long press of the Super
Key opens the Unity help window, as we know, and when i long-pressed the
Super Key, the screen starting behaving weird, with text and icons
disappearing and reappearing randomly across the screen. It definitely
wasn't fun to see, and it definitely didn't seem like everything was
fine. It was just not what one would expect off a fresh install of the
latest Ubuntu OS.

I cannot attach screenshots, because whenever i try to take screenshots
of a weird looking screen, the screenshot is either never taken, or if
taken, everything looks perfect in the picture.

The result for apt-cache policy xorg is

xorg:
  Installed: 1:7.7+1ubuntu6
  Candidate: 1:7.7+1ubuntu6
  Version table:
 *** 1:7.7+1ubuntu6 0
500 http://in.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Nov  9 00:05:34 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1950]
InstallationDate: Installed on 2013-11-08 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP ProBook 445 G1
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=731cac08-a53d-4405-9318-1681ff7bbda2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CPE Ver. F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1950
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 445 G1
dmi.product.version: A2018CD200
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.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: Sat Nov  9 00:01:39 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.3-3ubuntu2
xserver.video_driver: radeon

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


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

Title:
  Screen Flickering and display problems

Status in “xorg” package in Ubuntu:
  New

Bug des

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

2013-11-08 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1249464/+attachment/3903474/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1152281
   evolution-calendar-factory crashed with SIGABRT in __libc_message()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

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

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

Bug description:
  this bug appeared when I logged in

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evolution-data-server 3.6.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  Date: Fri Nov  8 19:47:43 2013
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2013-04-08 (213 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
  Title: evolution-calendar-factory crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-05-12 (180 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

2013-11-08 Thread Ted Gould

** Changed in: upstart-app-launch
   Status: Triaged => In Progress

** Changed in: upstart-app-launch
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock: Plug-ins:
  Fix Released
Status in Diodon - GTK+ Clipboard Manager:
  Triaged
Status in Scratch:
  Fix Committed
Status in Totem Movie Player:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity Applications Lens:
  In Progress
Status in Unity Files Lens:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in Upstart Application Launcher:
  In Progress
Status in “activity-log-manager” package in Ubuntu:
  Fix Released
Status in “bijiben” package in Ubuntu:
  New
Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Released
Status in “diodon” package in Ubuntu:
  Fix Released
Status in “folks” package in Ubuntu:
  New
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “synapse” package in Ubuntu:
  New
Status in “totem” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-lens-applications” package in Ubuntu:
  In Progress
Status in “unity-lens-files” package in Ubuntu:
  Fix Released
Status in “unity-lens-video” package in Ubuntu:
  In Progress
Status in “upstart-app-launch” package in Ubuntu:
  New

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

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

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

[Desktop-packages] [Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

** Branch linked: lp:~ted/upstart-app-launch/zg-reenable

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock: Plug-ins:
  Fix Released
Status in Diodon - GTK+ Clipboard Manager:
  Triaged
Status in Scratch:
  Fix Committed
Status in Totem Movie Player:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity Applications Lens:
  In Progress
Status in Unity Files Lens:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in Upstart Application Launcher:
  In Progress
Status in “activity-log-manager” package in Ubuntu:
  Fix Released
Status in “bijiben” package in Ubuntu:
  New
Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Released
Status in “diodon” package in Ubuntu:
  Fix Released
Status in “folks” package in Ubuntu:
  New
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “synapse” package in Ubuntu:
  New
Status in “totem” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-lens-applications” package in Ubuntu:
  In Progress
Status in “unity-lens-files” package in Ubuntu:
  Fix Released
Status in “unity-lens-video” package in Ubuntu:
  In Progress
Status in “upstart-app-launch” package in Ubuntu:
  New

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

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

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

[Desktop-packages] [Bug 1189639] Re: [dp] External Screen doesn't wake up from sleep

2013-11-08 Thread omriasta

Issue is definitely related to DPMS. Disabling DPMS altogether prevents the 
screen from turning off completely in turn preventing it from failing to turn 
back on. Screen still blanks when I lock the screen but backlight remains on 
and the screen doesn't go to "power saving" mode. 
I have updated to the latest kernel from drm-intel-next (found here: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/) and the issue 
still exists in 3.12.0-997.
It seems this issue has also been noted on the Pixel here: 
https://code.google.com/p/chromium/issues/detail?id=257457
On the new Kernel I installed the Error is slightly different. dmesg shows:
[ 1927.534343] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.558323] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.582264] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.606214] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.630118] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.654053] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.677958] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[ 1927.678207] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, 
aborting
and also:
[ 2288.677894] [ cut here ]
[ 2288.677931] WARNING: CPU: 0 PID: 1279 at 
/home/apw/COD/linux/drivers/gpu/drm/i915/intel_dp.c:2683 
intel_dp_link_down+0x1dc/0x210 [i915]()
[ 2288.677933] Modules linked in: hid_generic hidp hid nfnetlink_queue 
nfnetlink_log nfnetlink joydev parport_pc ppdev x86_pkg_temp_thermal 
intel_powerclamp rfcomm coretemp bnep kvm_intel kvm cdc_mbim arc4 nls_iso8859_1 
cdc_ncm usbnet cdc_wdm uvcvideo cdc_acm mii iwldvm videobuf2_vmalloc 
snd_hda_codec_hdmi videobuf2_memops videobuf2_core mac80211 ext2 
snd_hda_codec_realtek btusb bluetooth videodev snd_hda_intel snd_hda_codec 
snd_hwdep snd_pcm thinkpad_acpi iwlwifi nvram snd_page_alloc snd_seq_midi 
snd_seq_midi_event snd_rawmidi cfg80211 psmouse snd_seq microcode 
snd_seq_device serio_raw snd_timer lpc_ich snd mei_me soundcore mei tpm_tis 
intel_smartconnect lp mac_hid parport dm_crypt crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd i2c_algo_bit ahci sdhci_pci drm_kms_helper libahci sdhci drm 
wmi video
[ 2288.677989] CPU: 0 PID: 1279 Comm: Xorg Tainted: GW
3.12.0-997-generic #201311050452
[ 2288.677991] Hardware name: LENOVO 3443CTO/3443CTO, BIOS G6ET96WW (2.56 ) 
04/29/2013
[ 2288.677993]  0a7b 88020ffd3a58 81739f5f 
0007
[ 2288.677997]   88020ffd3a98 810675fc 
06080004
[ 2288.678001]  8800362b30c8 880035c7c000 8800362b1000 
88021244f000
[ 2288.678004] Call Trace:
[ 2288.678010]  [] dump_stack+0x46/0x58
[ 2288.678015]  [] warn_slowpath_common+0x8c/0xc0
[ 2288.678019]  [] warn_slowpath_null+0x1a/0x20
[ 2288.678034]  [] intel_dp_link_down+0x1dc/0x210 [i915]
[ 2288.678049]  [] intel_disable_dp+0x78/0x90 [i915]
[ 2288.678064]  [] ironlake_crtc_disable+0x195/0x2a0 [i915]
[ 2288.678077]  [] intel_crtc_disable+0x34/0x150 [i915]
[ 2288.678090]  [] __intel_set_mode+0x105/0x360 [i915]
[ 2288.678103]  [] intel_set_mode+0x16/0x30 [i915]
[ 2288.678115]  [] intel_crtc_set_config+0x29d/0x310 [i915]
[ 2288.678119]  [] ? __pollwait+0xf0/0xf0
[ 2288.678133]  [] drm_mode_set_config_internal+0x5c/0xe0 
[drm]
[ 2288.678144]  [] drm_mode_setcrtc+0x310/0x4c0 [drm]
[ 2288.678154]  [] drm_ioctl+0x4da/0x600 [drm]
[ 2288.678165]  [] ? drm_mode_setplane+0x3f0/0x3f0 [drm]
[ 2288.678169]  [] do_vfs_ioctl+0x7a/0x2e0
[ 2288.678172]  [] ? vfs_read+0x111/0x180
[ 2288.678175]  [] SyS_ioctl+0x91/0xb0
[ 2288.678179]  [] ? SyS_read+0x70/0xa0
[ 2288.678182]  [] system_call_fastpath+0x1a/0x1f
[ 2288.678185] ---[ end trace 17a901f12eb53208 ]---


** Bug watch added: code.google.com/p/chromium/issues #257457
   http://code.google.com/p/chromium/issues/detail?id=257457

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

Title:
  [dp] External Screen doesn't wake up from sleep

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

Bug description:
  I have a Lenovo X1 Carbon with an external screen connected to a Mini DP to 
VGA adapter. External screen works fine until the display goes to sleep for 
inactivity (just the display goes to sleep, not the laptop).
  When I return to the laptop, the built in screen wakes but the external 
screen does not. The screen is still detected, xrandr displays the resolution 
and I can move the cursor to the external display but the display remains off.
  I have tried cycling with Fn+F7 and also tried Ctrl+Alt+F1 then Ctrl+Alt+F7. 
The only way to get the exte

[Desktop-packages] [Bug 760344] Re: gvfsd-http not closing tcp connections

2013-11-08 Thread Filiprino

I upgraded to 13.10 and I still have this bug. Opened some images on
GIMP by giving to it the URL of the photos, and gvfs-http did not close
the tcp connections. They remained in CLOSE_WAIT (even after closing
GIMP) until I killed the process GVFS.

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

Title:
  gvfsd-http not closing tcp connections

Status in GVFS:
  Invalid
Status in “gvfs” package in Ubuntu:
  Fix Committed
Status in “gvfs” source package in Precise:
  Triaged
Status in “gvfs” source package in Quantal:
  Triaged

Bug description:
  Binary package hint: gvfs

  How to recreate the bug...

  Run Rhythmbox, and enable the context pane + album art, and lyrics for
  good measure as well. Close the plugins windows that pops up, click on
  the new icon next to the Ubuntu One Music store and your new window
  should show up. The context pane is great for me, as I love to know
  what I can about the music I listen to. Rhythmbox, through gvfsd-http
  has now fetched all your cool text from last.fm about your artist, but
  it does not close the connection. These connections stay in close_wait
  till you kill the gvfsd-http process.

  this happens any time gvfsd-http is used. 
  netstat -a |grep tcp 

  tcp1  0 farva:47729 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:35961 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:36086 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:42357 10x.terra.com.br:www
CLOSE_WAIT 
  tcp0  0 farva:47836 64.208.5.34:www 
ESTABLISHED
  tcp1  0 farva:42219 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:46945 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:36126 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:59815 64.208.5.24:www 
CLOSE_WAIT 
  tcp0  0 farva:24800 wabothlp0282996.gs:6776 
ESTABLISHED
  tcp1  0 farva:36021 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp0  0 farva:37285 64.208.5.26:www 
ESTABLISHED
  tcp1  0 farva:33204 64.208.5.34:www 
CLOSE_WAIT 
  tcp1  0 farva:36007 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:53431 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:35975 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:59027 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:47637 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:58324 207.114.197.87:www  
CLOSE_WAIT 
  tcp 5131  0 farva:42165 10x.terra.com.br:wwwCLOSE_WAIT

  gvfsd-htt 1795   josh   18r IPv4  30730  0t0
TCP farva:54963->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   19u IPv4  38478  0t0
TCP farva:39645->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   22u IPv4  23139  0t0
TCP farva:39074->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   24u IPv4  19766  0t0
TCP farva:42176->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   25u sock0,6  0t0  
19650 can't identify protocol
  gvfsd-htt 1795   josh   26u IPv4  19607  0t0
TCP farva:35892->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   27u IPv4  20164  0t0
TCP farva:42219->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   29u IPv4  38494  0t0
TCP farva:51584->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   30u sock0,6  0t0  
23195 can't identify protocol
  gvfsd-htt 1795   josh   31u sock0,6  0t0  
20157 can't identify protocol

  I posted a form message about this too 
  http://ubuntuforums.org/showthread.php?p=10646961#post10646961

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

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

[Desktop-packages] [Bug 1248578] Re: Adding printer from commandline does not work anymore after upgrade to 13.10

** Changed in: cups (Ubuntu Saucy)
   Status: In Progress => Fix Committed

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

Title:
  Adding printer from commandline does not work anymore after upgrade to
  13.10

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups” source package in Saucy:
  Fix Committed

Bug description:
  In Ubuntu 13.10 I can't add printers from the commandline. For example
  when I use the following command as root:

  lpadmin -p i44hpneu -m "drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd"
  -D "xxx" -L "xxx" -E -v socket://my-printer-url

  Then the printer i44hpneu is created but it does not work. Another
  symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The
  model/driver is listed in "lpinfo -m", so the printer-driver-hpcups
  package appears to have installed correctly. Adding printers from the
  GUI or the cups webpage is working. Ubuntu version 13.04 and earlier
  work too.

  (I'm mainting around 20 linux PCs so automating printer installation
  from the commandline is a very convenient tool as I can prepare
  scripts to do all the setup).

  [Impact]

  Very important feature for administrators of print servers, especially
  head-less servers are not working, causing major problems for the
  admin:

  1. Setting up print queues with "lpadmin", specifying the PPD/driver
  with the "-m" option does not work, leading to a raw queue.

  2. Setting up printers with the web interface of CUPS
  (http://localhost:631/) does not work.

  [Test Case]

  Run the command

  lpadmin -p test -E -v file:/dev/null -m drv:///sample.drv/laserjet.ppd

  This should create a print queue with the generic LaserJet PPD (PCL 5e
  printer). The PPD should be in /etc/cups/ppd/test.ppd.

  What you get is a raw queue without the PPD.

  The proposed package fixes this. The same command correctly creates a
  print queue with PPD.

  [Regression Potential]

  Very low, as only a few lines are modified in the code for lpadmin and
  for the appropriate part of the web interface. The CUPS daemon and the
  CUPS library are not modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 15:55:40 2013
  InstallationDate: Installed on 2013-02-13 (266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Lpstat:
   device for i44canon: socket://i44canon.info.uni-karlsruhe.de
   device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de
   device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de
   device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de
   device for PDF: cups-pdf:/
  MachineType: FUJITSU ESPRIMO P910
  MarkForUpload: True
  Papersize: a4
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=0de5b9f6-e317-48be-83f8-90ee01c66888 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (0 days ago)
  dmi.bios.date: 12/17/2012
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.3 R1.19.0 for D3162-A1x
  dmi.board.name: D3162-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3162-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$PXW6
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.19.0forD3162-A1x:bd12/17/2012:svnFUJITSU:pnESPRIMOP910:pvr:rvnFUJITSU:rnD3162-A1:rvrS26361-D3162-A1:cvnFUJITSU:ct6:cvrC$PXW6:
  dmi.product.name: ESPRIMO P910
  dmi.sys.vendor: FUJITSU

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

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

[Desktop-packages] [Bug 1249455] Re: at-spi2-registryd crashed with SIGABRT in raise()

2013-11-08 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1249455/+attachment/3903432/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  at-spi2-registryd crashed with SIGABRT in raise()

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

Bug description:
  In My Ubuntu 12.04.2 based installation Firefox few weeks ago upgraded with 
25.0 release.
  When I try using the 25.0 version and do some heading level navigation and 
arrow key scrolling, at-spi2-registrid crashed.
  After this problem I downgraded with Firefox 24.0 and hold the package to I 
possible use Firefox with Orca 3.4.2.

  Attila

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: at-spi2-core 2.4.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Wed Oct 30 06:03:14 2013
  ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
  ExecutableTimestamp: 137223
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130123.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  ProcCwd: /
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=hu:en
   LANG=hu_HU.UTF-8
  Signal: 6
  SourcePackage: at-spi2-core
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: at-spi2-registryd crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2013-02-06 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data

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

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

[Desktop-packages] [Bug 1249457] [NEW] upgrade to trusty gives scary warning with no way to act on...

2013-11-08 Thread Alexander Sack

Public bug reported:

dist-upgrading to trusty I get this:

"The PostgreSQL version 9.1 is obsolete, but the server or client
packages are still installed. Please install the latest packages
(postgresql-9.3 and postgresql-client-9.3) and upgrade the existing
clusters with pg_upgradecluster (see manpage).

Please be aware that the installation of postgresql-9.3 will
automatically create a default cluster 9.3/main. If you want to upgrade
the 9.1/main cluster, you need to remove the already existing 9.3
cluster (pg_dropcluster --stop 9.3 main, see manpage for details).

The old server and client packages are no longer supported. After the
existing clusters are upgraded, the postgresql-9.1 and postgresql-
client-9.1 packages should be removed.

Please see /usr/share/doc/postgresql-common/README.Debian.gz for
details."

I never touched configs etc...

The dialog is very scary and doesnt offer a way to stop/abort/fix the
problem it conveys to the end user.

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "postgresql.png"
   
https://bugs.launchpad.net/bugs/1249457/+attachment/3903442/+files/postgresql.png

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

Title:
  upgrade to trusty gives scary warning with no way to act on...

Status in “postgresql-common” package in Ubuntu:
  New

Bug description:
  dist-upgrading to trusty I get this:

  "The PostgreSQL version 9.1 is obsolete, but the server or client
  packages are still installed. Please install the latest packages
  (postgresql-9.3 and postgresql-client-9.3) and upgrade the existing
  clusters with pg_upgradecluster (see manpage).

  Please be aware that the installation of postgresql-9.3 will
  automatically create a default cluster 9.3/main. If you want to
  upgrade the 9.1/main cluster, you need to remove the already existing
  9.3 cluster (pg_dropcluster --stop 9.3 main, see manpage for details).

  The old server and client packages are no longer supported. After the
  existing clusters are upgraded, the postgresql-9.1 and postgresql-
  client-9.1 packages should be removed.

  Please see /usr/share/doc/postgresql-common/README.Debian.gz for
  details."

  I never touched configs etc...

  The dialog is very scary and doesnt offer a way to stop/abort/fix the
  problem it conveys to the end user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1249457/+subscriptions

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

[Desktop-packages] [Bug 551783] Re: Missing dependency on python-gconf

2013-11-08 Thread Sebastien Bacher

the new version stopped using gconf, closing the bug

** Changed in: gnome-sudoku (Ubuntu)
 Assignee: Lorenzo De Liso (blackz) => (unassigned)

** Changed in: gnome-sudoku (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Missing dependency on python-gconf

Status in “gnome-sudoku” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-sudoku

  Upgraded to Kububtu 9.10 (karmic) from 9.04. The gnome-sudoku program
  broke during the upgrade; after upgrading it refuses to run with this
  error:

  $ gnome-sudoku 
  Traceback (most recent call last):
File "/usr/games/gnome-sudoku", line 67, in 
  start_game()  
File "/usr/lib/pymodules/python2.6/gnome_sudoku/gnome_sudoku.py", line 21, 
in start_game
  import main   

File "/usr/lib/pymodules/python2.6/gnome_sudoku/main.py", line 19, in 
  
  import printing   

File "/usr/lib/pymodules/python2.6/gnome_sudoku/printing.py", line 5, in 
   
  from gtk_goodies import gconf_wrapper 

File 
"/usr/lib/pymodules/python2.6/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 
6, in 
  import gconf  
  
  ImportError: No module named gconf
  

  Installing the "python-gconf" package resolves the issue, so this
  should be a run-time dependency for gnome-sudoku.

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Mar 30 17:12:12 2010
  DistroRelease: Ubuntu 9.10
  Package: gnome-sudoku 1:2.28.0-0ubuntu1
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: gnome-games
  Uname: Linux 2.6.31-20-generic x86_64

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

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

[Desktop-packages] [Bug 1181897] Re: Mouse freezes randomly

2013-11-08 Thread n0PxN0p

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

** This bug has been marked a duplicate of bug 1103164
   062a:0201 [MSI Z77A-G43] hid-generic: can't reset device, status -71

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

Title:
  Mouse freezes randomly

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I encountered this problem in Ubuntu 11.04, 11.10, 12.04 and now
  13.04. I never encountered it with 12.10 so I'm
  frustrated/disappointed that it's reappeared in 13.04.

  The mouse will randomly freeze and the only solution is to reboot.
  Usually I can open a terminal window (Ctrl-Alt-T) to try and gather
  information but occassionally I will encounter a complete system
  freeze. My Xorg log records no events and dmesg only shows a single
  change from boot (usb 2-1: USB disconnect, device number 2).  I've
  attached:

  system and version details
  Xorg.o.log at boot and as there's no difference at error I haven't attached 
fiff files
  Dmesg at boot and after error and the diff output. The USB disconnect message 
appears after some seconds rather than immediately (perhaps some timeout event).
  lsusb output
  lspci output
  uname output

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 20 09:49:52 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed
   virtualbox, 4.2.10, 3.8.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350/4550] [1002:954f] 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. Device [1462:1613]
  InstallationDate: Installed on 2013-05-02 (17 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Compaq-Presario VT568AA-ABG CQ3260AN
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic 
root=UUID=b662ee11-a7f4-4f4a-a170-f616d8df083e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.15
  dmi.board.name: Narra6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 6.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.15:bd11/06/2009:svnCompaq-Presario:pnVT568AA-ABGCQ3260AN:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: VT568AA-ABG CQ3260AN
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Mon May 20 09:33:11 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1248578] Re: Adding printer from commandline does not work anymore after upgrade to 13.10

Uploaded fixed package to -proposed. Please test it as soon as it gets
approved. Instructions will get posted here then. Note that your testing
of the update is required for the update getting released for everyone.

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

Title:
  Adding printer from commandline does not work anymore after upgrade to
  13.10

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups” source package in Saucy:
  In Progress

Bug description:
  In Ubuntu 13.10 I can't add printers from the commandline. For example
  when I use the following command as root:

  lpadmin -p i44hpneu -m "drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd"
  -D "xxx" -L "xxx" -E -v socket://my-printer-url

  Then the printer i44hpneu is created but it does not work. Another
  symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The
  model/driver is listed in "lpinfo -m", so the printer-driver-hpcups
  package appears to have installed correctly. Adding printers from the
  GUI or the cups webpage is working. Ubuntu version 13.04 and earlier
  work too.

  (I'm mainting around 20 linux PCs so automating printer installation
  from the commandline is a very convenient tool as I can prepare
  scripts to do all the setup).

  [Impact]

  Very important feature for administrators of print servers, especially
  head-less servers are not working, causing major problems for the
  admin:

  1. Setting up print queues with "lpadmin", specifying the PPD/driver
  with the "-m" option does not work, leading to a raw queue.

  2. Setting up printers with the web interface of CUPS
  (http://localhost:631/) does not work.

  [Test Case]

  Run the command

  lpadmin -p test -E -v file:/dev/null -m drv:///sample.drv/laserjet.ppd

  This should create a print queue with the generic LaserJet PPD (PCL 5e
  printer). The PPD should be in /etc/cups/ppd/test.ppd.

  What you get is a raw queue without the PPD.

  The proposed package fixes this. The same command correctly creates a
  print queue with PPD.

  [Regression Potential]

  Very low, as only a few lines are modified in the code for lpadmin and
  for the appropriate part of the web interface. The CUPS daemon and the
  CUPS library are not modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 15:55:40 2013
  InstallationDate: Installed on 2013-02-13 (266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Lpstat:
   device for i44canon: socket://i44canon.info.uni-karlsruhe.de
   device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de
   device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de
   device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de
   device for PDF: cups-pdf:/
  MachineType: FUJITSU ESPRIMO P910
  MarkForUpload: True
  Papersize: a4
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=0de5b9f6-e317-48be-83f8-90ee01c66888 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (0 days ago)
  dmi.bios.date: 12/17/2012
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.3 R1.19.0 for D3162-A1x
  dmi.board.name: D3162-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3162-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$PXW6
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.19.0forD3162-A1x:bd12/17/2012:svnFUJITSU:pnESPRIMOP910:pvr:rvnFUJITSU:rnD3162-A1:rvrS26361-D3162-A1:cvnFUJITSU:ct6:cvrC$PXW6:
  dmi.product.name: ESPRIMO P910
  dmi.sys.vendor: FUJITSU

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

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

[Desktop-packages] [Bug 1242632] Re: Eclipse Ganymede Crashes after a minute's usage in Ubuntu 13.10, Problematic frame: C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18

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

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

** Changed in: java-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  Eclipse Ganymede Crashes after a minute's usage in Ubuntu 13.10,
  Problematic frame: C  [libgobject-2.0.so.0+0x19528]
  g_object_get_qdata+0x18

Status in “gtk+2.0” package in Ubuntu:
  Confirmed
Status in “java-common” package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 13.10
  Release:13.10

  I have a designer which is built over eclipse ganymede.
  It was working fine with version 13.04.
  I updated to 13.10 and my designer jvm crashes almost after a minutes usage

  tried with jdk 6u33 and 7u21

  Here's the log

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f7838e54528, pid=3556, tid=140154561955584
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libgobject-2.0.so.0+0x19528]  g_object_get_qdata+0x18
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  ---  T H R E A D  ---

  Current thread (0x7f7840007800):  JavaThread "main"
  [_thread_in_native, id=3557,
  stack(0x7f7846d1,0x7f7846e11000)]

  siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR),
  si_addr=0x3c00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1242632/+subscriptions

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

[Desktop-packages] [Bug 1242632] Re: Eclipse Ganymede Crashes after a minute's usage in Ubuntu 13.10, Problematic frame: C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18

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

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

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Eclipse Ganymede Crashes after a minute's usage in Ubuntu 13.10,
  Problematic frame: C  [libgobject-2.0.so.0+0x19528]
  g_object_get_qdata+0x18

Status in “gtk+2.0” package in Ubuntu:
  Confirmed
Status in “java-common” package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 13.10
  Release:13.10

  I have a designer which is built over eclipse ganymede.
  It was working fine with version 13.04.
  I updated to 13.10 and my designer jvm crashes almost after a minutes usage

  tried with jdk 6u33 and 7u21

  Here's the log

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f7838e54528, pid=3556, tid=140154561955584
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libgobject-2.0.so.0+0x19528]  g_object_get_qdata+0x18
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  ---  T H R E A D  ---

  Current thread (0x7f7840007800):  JavaThread "main"
  [_thread_in_native, id=3557,
  stack(0x7f7846d1,0x7f7846e11000)]

  siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR),
  si_addr=0x3c00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1242632/+subscriptions

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

[Desktop-packages] [Bug 1248578] Re: Adding printer from commandline does not work anymore after upgrade to 13.10

** Description changed:

  In Ubuntu 13.10 I can't add printers from the commandline. For example
  when I use the following command as root:
  
  lpadmin -p i44hpneu -m "drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd" -D
  "xxx" -L "xxx" -E -v socket://my-printer-url
  
  Then the printer i44hpneu is created but it does not work. Another
  symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The
  model/driver is listed in "lpinfo -m", so the printer-driver-hpcups
  package appears to have installed correctly. Adding printers from the
  GUI or the cups webpage is working. Ubuntu version 13.04 and earlier
  work too.
  
  (I'm mainting around 20 linux PCs so automating printer installation
  from the commandline is a very convenient tool as I can prepare scripts
  to do all the setup).
  
+ [Impact]
+ 
+ Very important feature for administrators of print servers, especially
+ head-less servers are not working, causing major problems for the admin:
+ 
+ 1. Setting up print queues with "lpadmin", specifying the PPD/driver
+ with the "-m" option does not work, leading to a raw queue.
+ 
+ 2. Setting up printers with the web interface of CUPS
+ (http://localhost:631/) does not work.
+ 
+ [Test Case]
+ 
+ Run the command
+ 
+ lpadmin -p test -E -v file:/dev/null -m drv:///sample.drv/laserjet.ppd
+ 
+ This should create a print queue with the generic LaserJet PPD (PCL 5e
+ printer). The PPD should be in /etc/cups/ppd/test.ppd.
+ 
+ What you get is a raw queue without the PPD.
+ 
+ The proposed package fixes this. The same command correctly creates a
+ print queue with PPD.
+ 
+ [Regression Potential]
+ 
+ Very low, as only a few lines are modified in the code for lpadmin and
+ for the appropriate part of the web interface. The CUPS daemon and the
+ CUPS library are not modified.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 15:55:40 2013
  InstallationDate: Installed on 2013-02-13 (266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Lpstat:
-  device for i44canon: socket://i44canon.info.uni-karlsruhe.de
-  device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de
-  device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de
-  device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de
-  device for PDF: cups-pdf:/
+  device for i44canon: socket://i44canon.info.uni-karlsruhe.de
+  device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de
+  device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de
+  device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de
+  device for PDF: cups-pdf:/
  MachineType: FUJITSU ESPRIMO P910
  MarkForUpload: True
  Papersize: a4
  ProcEnviron:
-  LANGUAGE=en_US
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=0de5b9f6-e317-48be-83f8-90ee01c66888 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (0 days ago)
  dmi.bios.date: 12/17/2012
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.3 R1.19.0 for D3162-A1x
  dmi.board.name: D3162-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3162-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$PXW6
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.19.0forD3162-A1x:bd12/17/2012:svnFUJITSU:pnESPRIMOP910:pvr:rvnFUJITSU:rnD3162-A1:rvrS26361-D3162-A1:cvnFUJITSU:ct6:cvrC$PXW6:
  dmi.product.name: ESPRIMO P910
  dmi.sys.vendor: FUJITSU

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

Title:
  Adding printer from commandline does not work anymore after upgrade to
  13.10

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups” source package in Saucy:
  In Progress

Bug description:
  In Ubuntu 13.10 I can't add printers from the commandline. For example
  when I use the following command as root:

  lpadmin -p i44hpneu -m "drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd"
  -D "xxx" -L "xxx" -E -v socket://my-printer-url

  Then the printer i44hpneu is created but it does not work. Another
  symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The
  model/driver is listed in "lpinfo -m", so the printer-driver-hpcups
  package appears to have installed correctly. Adding printers from the
  GUI or the cups webpage is working. Ubuntu version 13.04 and earlier
  work too.

  (I'm mainting around 20 linux PCs so automating printer installation
  from the commandline is a very c

[Desktop-packages] [Bug 1235912] Re: firefox build misses google api key, breaks geolocation

2013-11-08 Thread blaamann

Geolocation does not work in 13.10 either in Firefox 25. If I download
and use Firefox 25 from Mozilla it works as it should.

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

Title:
  firefox build misses google api key, breaks geolocation

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=13.04
  DISTRIB_CODENAME=raring
  DISTRIB_DESCRIPTION="Ubuntu 13.04"
  Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
  firefox:
Installed: 24.0+build1-0ubuntu0.13.04.1
Candidate: 24.0+build1-0ubuntu0.13.04.1

  
  Firefox package is broken, it is missing the google api key required for 
geolocation features.

  Test:
  https://developers.google.com/maps/documentation/javascript/examples
  /map-geolocation?csw=1

  Enable debug:  geo.wifi.logging.enabled, true
  Start from console, try geolocation

  *** WIFI GEO: startup called.  testing mode isfalse
  *** WIFI GEO: watch called
  *** WIFI GEO: onChange called
  [...]
  *** WIFI GEO: * Sending request:
  https://www.googleapis.com/geolocation/v1/geolocate?key=no-google-api-key

  Note that "no-google-api-key" is used as API key. Google answers with
  *** WIFI GEO: gls returned status: 400 --> 
{"error":{"errors":[{"domain":"usageLimits","reason":"keyInvalid","message":"Bad
 Request"}],"code":400,"message":"Bad Request"}}

  Which is more or less expected.

  PLEASE add an automatic test to prevent a regression.

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

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

[Desktop-packages] [Bug 1248578] Re: Adding printer from commandline does not work anymore after upgrade to 13.10

Matthias, thank you for testing.

Marking as fixed in Trusty as there we are using 1.7.0 final already.

Preparing SRU for Saucy, please stay tuned for testing the official
update package.

** Changed in: cups (Ubuntu)
   Status: New => Fix Released

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

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

** Changed in: cups (Ubuntu Saucy)
Milestone: None => saucy-updates

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

Title:
  Adding printer from commandline does not work anymore after upgrade to
  13.10

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups” source package in Saucy:
  In Progress

Bug description:
  In Ubuntu 13.10 I can't add printers from the commandline. For example
  when I use the following command as root:

  lpadmin -p i44hpneu -m "drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd"
  -D "xxx" -L "xxx" -E -v socket://my-printer-url

  Then the printer i44hpneu is created but it does not work. Another
  symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The
  model/driver is listed in "lpinfo -m", so the printer-driver-hpcups
  package appears to have installed correctly. Adding printers from the
  GUI or the cups webpage is working. Ubuntu version 13.04 and earlier
  work too.

  (I'm mainting around 20 linux PCs so automating printer installation
  from the commandline is a very convenient tool as I can prepare
  scripts to do all the setup).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 15:55:40 2013
  InstallationDate: Installed on 2013-02-13 (266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Lpstat:
   device for i44canon: socket://i44canon.info.uni-karlsruhe.de
   device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de
   device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de
   device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de
   device for PDF: cups-pdf:/
  MachineType: FUJITSU ESPRIMO P910
  MarkForUpload: True
  Papersize: a4
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=0de5b9f6-e317-48be-83f8-90ee01c66888 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (0 days ago)
  dmi.bios.date: 12/17/2012
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.3 R1.19.0 for D3162-A1x
  dmi.board.name: D3162-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3162-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$PXW6
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.19.0forD3162-A1x:bd12/17/2012:svnFUJITSU:pnESPRIMOP910:pvr:rvnFUJITSU:rnD3162-A1:rvrS26361-D3162-A1:cvnFUJITSU:ct6:cvrC$PXW6:
  dmi.product.name: ESPRIMO P910
  dmi.sys.vendor: FUJITSU

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

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

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

2013-11-08 Thread Goalie Fight

I could never go 10 minutes without having a lockup using nouveau. Maybe
it just happens less often with nvidia-current. Haven't seen any since I
changed the driver. Overall, I think this issue is related -- it just
happens more often in certain setups. Not sure what to say about the
people with Radeon though.

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

Title:
  Ubuntu 13.10 random screen freeze while Normal OS activites

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

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

  I,am not sure, whether it is bug ?

  thanks for the expertise support.

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

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

[Desktop-packages] [Bug 48371] Re: uncleared mine tiles same color as cleared tiles

** Changed in: gnome-games
   Status: In Progress => Confirmed

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

Title:
  uncleared mine tiles same color as cleared tiles

Status in GNOME Games:
  Confirmed
Status in “gnome-games” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-games

  All mine tiles appear white. In the previous release, the uncleared
  tiles appeared blue.

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

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

[Desktop-packages] [Bug 674594] Re: IBus preference dialog only opens after repeated attempts

2013-11-08 Thread Aron Xu

No enough information provided, and it's not in supported release, thus
mark as Incomplete in case further information is given.

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  IBus preference dialog only opens after repeated attempts

Status in “ibus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ibus

  I am using Ubuntu 10.10 Maverick and ibus-1.3.7-1ubuntu3.

  In order to begin inputting a language using ibus you are required to
  add that language in the preferences dialog. I clicked on the ibus
  indicator applet and selected preferences. I expected the preferences
  dialog to open, but it did not. I repeated this process three more
  times, and it finally opened. After this initial opening, the
  preferences dialog opens on the first selection. I am not sure if the
  initial opening is simply delayed, or must be repeated a number of
  times to work.

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

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

[Desktop-packages] [Bug 1249216] Re: bluetooth HSP mode broken in pulseaudio

2013-11-08 Thread shorted.neuron

attached detailed lsusb output for the bus of affected bluetooth device.
lsusb -vs 6:

** Attachment added: "lsusb-vs6.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1249216/+attachment/3903374/+files/lsusb-vs6.txt

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

Title:
  bluetooth HSP mode broken in pulseaudio

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  All involved hardware worked in Ubuntu 11.10.  HSP-only headsets (like
  Motorola H300, H700) do not output sound, often cause pulseaudio to
  hang, and eventually kick out this log message:

  #v+
  E: [pulseaudio] bluetooth-util.c: Failed to acquire transport fd: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
  E: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" 
(argument: "address="00:16:8F:D1:95:36" 
path="/org/bluez/31385/hci0/dev_00_16_8F_D1_95_36""): initialization failed.
  #v-

  After that, the audio sink shows up in pavucontrol, but when selected
  I cannot play sound through it.  Many apps like mplayer will hang,
  presumably because pulseaudio's input buffer is full.

  See also
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/972063

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

  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:1.1-0ubuntu15.4
Candidate: 1:1.1-0ubuntu15.4
Version table:
   *** 1:1.1-0ubuntu15.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:1.1-0ubuntu15 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  $ apt-cache policy bluez
  bluez:
Installed: 4.98-2ubuntu7
Candidate: 4.98-2ubuntu7
Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.4
  ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
  Uname: Linux 3.2.0-55-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bts1045 F pulseaudio
   /dev/snd/controlC1:  bts1045 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,1458a042,0011'
 Controls  : 45
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'CinemaTM'/'Microsoft Microsoft® LifeCam Cinema(TM) at 
usb-:00:12.2-5, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB045e:075d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 56
 Mono: Capture 53 [95%] [33.00dB] [on]
  Date: Fri Nov  8 00:34:24 2013
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2013-10-13 (26 days ago)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-770TA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/25/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-770TA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770TA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770TA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 516428] Re: IBUS kanji window selection

2013-11-08 Thread Aron Xu

9.10 is not supported anymore, mark as Incomplete in case anyone still
have the same problem in recent versions.

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

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

Title:
  IBUS kanji window selection

Status in “ibus” package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu.

  9.10 desktop x86

  2) The version of the package you are using, via 'apt-cache policy
  packagename' or by checking in Synaptic.

  IBus 1.2.0.20090927

  3) What you expected to happen

  Using anthy in openoffice writer, sometimes the window for kanji
  selection disappears. Need to close and open again the document.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Feb  3 08:10:50 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/yelp
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: yelp 2.28.0-0ubuntu2
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: yelp
  Uname: Linux 2.6.31-17-generic i686

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

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

[Desktop-packages] [Bug 676401] Re: PDF Links not working in evince