date:20140514

Public bug reported:

hello,

clean install Ubuntu 14.04 (whit internet cable on, update downloading
selected on install), at first start I don't have audio on internal
Audio card (ABit AA8XE). Before on 12.04 audio work fine.

http://www.alsa-
project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05


After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
Same identical problem. 

Tried to update the OS on 14 May 2014 but NOT solve my problem.

IF i select Sound settings i retrive dummy Output

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

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

Title:
  Ubuntu 14.04 NO audio (internal audio device not recognized Dummy
  Output)

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

Bug description:
  hello,

  clean install Ubuntu 14.04 (whit internet cable on, update downloading
  selected on install), at first start I don't have audio on internal
  Audio card (ABit AA8XE). Before on 12.04 audio work fine.

  http://www.alsa-
  project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05

  
  After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
  Same identical problem. 

  Tried to update the OS on 14 May 2014 but NOT solve my problem.

  IF i select Sound settings i retrive dummy Output

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

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

[Desktop-packages] [Bug 1306897] Re: xbmc with vdpau crashes on stop

** Tags added: trusty

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

Title:
  xbmc with vdpau crashes on stop

Status in “mesa” package in Ubuntu:
  Confirmed
Status in “mesa” source package in Trusty:
  Confirmed

Bug description:
  When freeing surfaces in application that use shared contexts, mesa
  will segfault. This was fixed with the following upstream patch, which
  was also marked for stable 10.1

  Please pick: 92e543c45da4581b1940178a94e6f2d66c749367

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

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

[Desktop-packages] [Bug 1318541] Re: Keyboard key not working in Chromium

2014-05-14 Thread Marius B. Kotsbak

** Description changed:

  The key 'ø' using Norwegian Dvorak keyboard layout has stopped working
  in Chromium. When I type it, nothing happens. I don't see this problem
  in other browser or other applications. Also using qwerty layout, I
  could not find any non working keys.
+ 
+ The key works fine in dialogs in Chromium and also in Chrome.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 12 10:26:02 2014
  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/
+  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/
  DetectedPlugins:
-  
+ 
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-precise-amd64-20130203-1
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  Env:
-  MOZ_PLUGIN_PATH = None
-  LD_LIBRARY_PATH = None
+  MOZ_PLUGIN_PATH = None
+  LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-03-12 (60 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (19 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

Title:
  Keyboard key not working in Chromium

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

Bug description:
  The key 'ø' using Norwegian Dvorak keyboard layout has stopped working
  in Chromium. When I type it, nothing happens. I don't see this problem
  in other browser or other applications. Also using qwerty layout, I
  could not find any non working keys.

  The key works fine in dialogs in Chromium and also in Chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 12 10:26:02 2014
  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/
  DetectedPlugins:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-03-12 (60 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (19 days ago)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

[Desktop-packages] [Bug 1319291] Re: Ubuntu 14.04 NO audio (internal audio device not recognized Dummy Output)

apport information

** Tags added: apport-collected trusty

** Description changed:

  hello,
  
  clean install Ubuntu 14.04 (whit internet cable on, update downloading
  selected on install), at first start I don't have audio on internal
  Audio card (ABit AA8XE). Before on 12.04 audio work fine.
  
  http://www.alsa-
  project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05
  
  
  After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
  Same identical problem. 
  
  Tried to update the OS on 14 May 2014 but NOT solve my problem.
  
  IF i select Sound settings i retrive dummy Output
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3
+ Architecture: i386
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2014-05-14 (0 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
+ Package: alsa-driver (not installed)
+ ProcEnviron:
+  LANGUAGE=it
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ Tags:  trusty
+ Uname: Linux 3.13.0-24-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 06/08/2006
+ dmi.bios.vendor: Phoenix Technologies, LTD
+ dmi.bios.version: 6.00 PG
+ dmi.board.name: AA8XE (Intel 925XE-ICH6R)
+ dmi.board.vendor: http://www.abit.com.tw/
+ dmi.board.version: 1.x
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/08/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAA8XE(Intel925XE-ICH6R):rvr1.x:cvn:ct3:cvr:

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1319291/+attachment/4112078/+files/AlsaInfo.txt

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

Title:
  Ubuntu 14.04 NO audio (internal audio device not recognized Dummy
  Output)

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

Bug description:
  hello,

  clean install Ubuntu 14.04 (whit internet cable on, update downloading
  selected on install), at first start I don't have audio on internal
  Audio card (ABit AA8XE). Before on 12.04 audio work fine.

  http://www.alsa-
  project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05

  
  After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
  Same identical problem. 

  Tried to update the OS on 14 May 2014 but NOT solve my problem.

  IF i select Sound settings i retrive dummy Output
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: AA8XE (Intel 925XE-ICH6R)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/08/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAA8XE(Intel925XE-ICH6R):rvr1.x:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1319291] CurrentDmesg.txt

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1319291/+attachment/4112080/+files/CurrentDmesg.txt

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

Title:
  Ubuntu 14.04 NO audio (internal audio device not recognized Dummy
  Output)

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

Bug description:
  hello,

  clean install Ubuntu 14.04 (whit internet cable on, update downloading
  selected on install), at first start I don't have audio on internal
  Audio card (ABit AA8XE). Before on 12.04 audio work fine.

  http://www.alsa-
  project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05

  
  After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
  Same identical problem. 

  Tried to update the OS on 14 May 2014 but NOT solve my problem.

  IF i select Sound settings i retrive dummy Output
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: AA8XE (Intel 925XE-ICH6R)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/08/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAA8XE(Intel925XE-ICH6R):rvr1.x:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1319291] BootDmesg.txt

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1319291/+attachment/4112079/+files/BootDmesg.txt

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

Title:
  Ubuntu 14.04 NO audio (internal audio device not recognized Dummy
  Output)

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

Bug description:
  hello,

  clean install Ubuntu 14.04 (whit internet cable on, update downloading
  selected on install), at first start I don't have audio on internal
  Audio card (ABit AA8XE). Before on 12.04 audio work fine.

  http://www.alsa-
  project.org/db/?f=376c0804cbdde90bcd2cb94799407cb1cacf5d05

  
  After this i tried to reinstall (clean install) 14.04 whitout the internet 
cable.
  Same identical problem. 

  Tried to update the OS on 14 May 2014 but NOT solve my problem.

  IF i select Sound settings i retrive dummy Output
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: AA8XE (Intel 925XE-ICH6R)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/08/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAA8XE(Intel925XE-ICH6R):rvr1.x:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1316095] Re: [Nvidia GF117M] 10de:1140 3D Controller disapear after reboot

2014-05-14 Thread Alberto Milone

I think this is a system specific issue (it depends on the BIOS).
Quoting Bbswitch's documentation:

On some machines, turning off the card is permanent and the card does
not reappear on subsequents reboots, which can result into the screen
staying black all the time, including the BIOS screen. If it occurs,
first try to shutdown, unplug power cord, remove battery, wait 30s, then
put everything back in and boot. If it's not solved, then the solution
is to reset the BIOS to factory settings. Before executing bbswitch for
the first time, it is therefore recommended to take note of the full key
sequence in the BIOS to do a reset.

source: https://github.com/Bumblebee-Project/bbswitch


On shutdown bbswitch is unloaded and should switch the discrete card back on, 
but apparently this doesn't work on this specific system.

** Changed in: linux (Ubuntu)
   Status: In Progress = Won't Fix

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

Title:
  [Nvidia GF117M] 10de:1140 3D Controller disapear after reboot

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “nvidia-prime” package in Ubuntu:
  Invalid

Bug description:
  Unable to switch back to nvidia graphic chip after reboot. Switching
  graphics does not requires reboot, but it does cause issue when user
  had to reboot for some reason, and will not able to use nvidia graphic
  until reboot.

  Step to reproduce: Switch to intel integrated graphic driver first if you 
were not,
  open nvidia settings from dash or use following command:
  sudo prime-select intel  sudo reboot now

  Expected result: Able to switch back to nvidia graphic chip using
  nvidia settings.

  Actuall result: unable to swich back to nvidia driver, the 3D controller 
disapeared in pci list. nvidia-settings will give you empty warning prompt, 
checking from console gives you unkown result:
  sudo prime-select query
  unknown

  WORKAROUND: Shutdown the system then turn on, the 3D controller will
  be back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1750 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Mon May  5 07:02:04 2014
  HibernationDevice: RESUME=UUID=c19bacd6-a604-4c9b-9a21-5d0a2d9cef5c
  InstallationDate: Installed on 2014-04-29 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 5460
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=15cbb6aa-65e8-4596-be71-2ff7431000be ro rootdelay=60 quiet splash 
initcall_debug
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: TIE3C2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/04/2013:svnDellInc.:pnVostro5460:pvr:rvnDellInc.:rnTIE3C2:rvrX00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Vostro 5460
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1315020]

2014-05-14 Thread Paul-silaghi

Verified fixed 32.0a1 (2014-05-12), Win 7 x64

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

Title:
  PDF.js prints blank pages

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

Bug description:
  The recent upgrade to 29.0+build1-0ubuntu0.12.04.2 (on Ubuntu 12.04.4
  LTS) cause printing from PDF.js to emit essentially blank output (the
  spooled files are very small, and contain showpage directives with no
  page content, i.e., blank pages come out of the printer).  Users can
  download the file from the down-arrow menu and print using a
  standalone viewer with no issue.

  This is probably https://bugzilla.mozilla.org/show_bug.cgi?id=1003707

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

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

[Desktop-packages] [Bug 1315020]

2014-05-14 Thread Ryanvm

https://hg.mozilla.org/releases/mozilla-beta/rev/956578072396

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

Title:
  PDF.js prints blank pages

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

Bug description:
  The recent upgrade to 29.0+build1-0ubuntu0.12.04.2 (on Ubuntu 12.04.4
  LTS) cause printing from PDF.js to emit essentially blank output (the
  spooled files are very small, and contain showpage directives with no
  page content, i.e., blank pages come out of the printer).  Users can
  download the file from the down-arrow menu and print using a
  standalone viewer with no issue.

  This is probably https://bugzilla.mozilla.org/show_bug.cgi?id=1003707

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

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

[Desktop-packages] [Bug 1283459] Re: Please merge xscreensaver (5.26-1) from Debian unstable

2014-05-14 Thread Martin Pitt

Thanks! I'll rearrange the changelog a bit to split between dropped
Ubuntu changes and remaining Ubuntu changes, as putting the former
into the latter section is confusing. But this looks so much cleaner
now.

** Changed in: xscreensaver (Ubuntu)
   Status: Incomplete = In Progress

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

Title:
  Please merge xscreensaver (5.26-1) from Debian unstable

Status in “xscreensaver” package in Ubuntu:
  In Progress

Bug description:
  Changes since the last upload:

  xscreensaver (5.26-1) unstable; urgency=low

    * New upstream release 5.26, changes since 5.23:
  - Updated feed-loading for recent Flickr changes.
  - Updated `webcollage' for recent Google changes.
  - Added Instagram and Bing as `webcollage' image sources.
  - Updated to latest autoconf.
  - Bug fixes.
    * Drop patch applied upstream:
  - debian/patches/12_upstream_use_cppflags.patch
    * Bump Standards-Version to 3.9.5 (no changes needed)

   -- Tormod Volden debian.tor...@gmail.com  Mon, 17 Feb 2014 20:34:28
  +0100

  xscreensaver (5.23-1) unstable; urgency=low

    * New upstream release 5.23 (Closes: #729311)
  - New hack, geodesic
  - More heuristics for using RSS feeds as image sources
  - Improved Wikipedia parser
  - Updated webcollage for recent Flickr changes
  - Added Android to bsod
  - Made quasicrystal work on weak graphics cards
  - Better compression on icons, plists and XML files
  - Reverted that DEACTIVATE change. Bad idea.
  - Phosphor now supports amber as well as green
    * Dropped patches applied upstream:
  - 12_upstream_quasicrystal_texture_width.patch
  - 14_upstream_hexadrop_keyboard_exit.patch
  - 15_upstream_activate_faster_nontty.patch
    * debian/patches/12_upstream_use_cppflags.patch:
  Make sure CPPFLAGS are used (fixes hardening warnings)
    * debian/control: Update VCS fields (fixes Lintian warning)

   -- Tormod Volden debian.tor...@gmail.com  Sat, 23 Nov 2013 20:47:28
  +0100

  xscreensaver (5.22-1) unstable; urgency=low

    * New upstream release 5.22 (Closes: #699833), changes since 5.15:
  - XInput devices now also ignore small mouse motions
  - Loading images via RSS feeds is much improved
  - Enlarged the texture image for lament
  - Made pipes be ridiculously less efficient, but spin
  - Added better mouse control to rubik, cube21, crackberg, and julia
  - Cosmetic improvements to queens and endgame
  - sonar can now ping local subnet on DHCP
  - Most savers now resize/rotate properly
  - New version of `fireworkx'
  - Minor fixes to `distort', `fontglide', `xmatrix'
  - New MacOS crash in `bsod'
  - New mode in `lcdscrub'
  - Gnome/KDE instructions updated in man page (Closes: #640640)
  - New --enable-pam-check-account-type option (Closes: #656766)
  - Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
  - Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
    image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
  - New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
  - Performance improvements for `interference'.
  - Fixed possible crashes in apple2, maze, pacman, polyominoes,
    fireworkx, engine (LP: #1196251)
  - Fix for `bumps' in 64 bit.
  - Fixed Shake to Randomize; display name of saver.
  - Fixed rotation problems with `pacman', `decayscreen'.
  - Better dragging in `fluidballs'.
  - Ignore rotation in hacks that don't benefit from it.
  - Ignore DEACTIVATE messages when locked, instead of popping up the
    password dialog box.
  - Fix format string glitch in xscreensaver-text (LP: #781948)
    (thanks Emanuel Bronshtein)
    * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
  logically separated and better named patches
    * debian/patches/57_grabDesktopImages_default_off.patch:
  Do not reveal desktop content by default (Closes: #679974)
    * debian/patches/12_upstream_quasicrystal_texture_width.patch:
  Adjust texture width to graphics card/driver capability
    * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
  Allow keyboard exit when run standalone (from upstream)
    * debian/patches/15_upstream_activate_faster_nontty.patch:
  Activate faster when not from tty session (LP: #1229486)
    * Bump Standards-Version to 3.9.4 (no changes needed)
    * debian/rules: Drop unnecessary dh_testroot from clean target
  (thanks Julien Cristau)
    * debian/rules: Include buildflags.mk for hardening options
    * Stop xscreensaver in prerm instead of postrm (Closes: 681613)
  (thanks Filipus Klutiero)
    * New xscreensaver daemon wrapper used by the example .desktop file
  to determine correct New login

[Desktop-packages] [Bug 1315020]

2014-05-14 Thread Ryanvm

https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/956578072396

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

Title:
  PDF.js prints blank pages

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

Bug description:
  The recent upgrade to 29.0+build1-0ubuntu0.12.04.2 (on Ubuntu 12.04.4
  LTS) cause printing from PDF.js to emit essentially blank output (the
  spooled files are very small, and contain showpage directives with no
  page content, i.e., blank pages come out of the printer).  Users can
  download the file from the down-arrow menu and print using a
  standalone viewer with no issue.

  This is probably https://bugzilla.mozilla.org/show_bug.cgi?id=1003707

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

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

[Desktop-packages] [Bug 1317151] Re: lightdm segfaults when trying to log in with NIS user

2014-05-14 Thread Owen Dunn

** Package changed: unity-greeter (Ubuntu) = lightdm (Ubuntu)

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

Title:
  lightdm segfaults when trying to log in with NIS user

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Running ubuntu 14.04 LTS with lightdm 1.10.0-0ubuntu3

  The system is configured to use NIS so has:

  passwd: files nis
  group: files nis
  shadow: files nis

  in /etc/nsswitch.conf.

  A NIS user can log in on a virtual console (tty1 etc.) but trying
  to log in under lightdm fails, with the following in dmesg:

  [ 1452.065454] lightdm[2957]: segfault at 0 ip 7fd8935b9be0 sp
  7fffaeafd270 error 4 in libc-2.19.so[7fd89354a000+1bc000]

  and the following in /var/log/lightdm/lightdm.log:

  [+0.32s] DEBUG: Session pid=3281: Greeter connected version=1.10.0
  [+0.55s] DEBUG: Session pid=3281: Greeter start authentication
  [+0.55s] DEBUG: Session pid=3402: Started with service 'lightdm', username 
'(null)'
  [+0.56s] DEBUG: Session pid=3402: Got 1 message(s) from PAM
  [+0.56s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)
  [+13.86s] DEBUG: Session pid=3281: Greeter start authentication for osd1000
  [+13.86s] DEBUG: Session pid=3402: Sending SIGTERM
  [+13.87s] DEBUG: Session pid=3432: Started with service 'lightdm', username 
'osd1000'
  [+13.87s] DEBUG: Session pid=3402: Terminated with signal 15
  [+13.87s] DEBUG: Session: Failed during authentication
  [+13.87s] DEBUG: Seat: Session stopped
  [+13.87s] DEBUG: Session pid=3432: Got 1 message(s) from PAM
  [+13.87s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)
  [+20.55s] DEBUG: Session pid=3281: Continue authentication
  [+20.66s] DEBUG: Session pid=3432: Terminated with signal 11
  [+20.66s] DEBUG: Session: Failed during authentication
  [+20.66s] DEBUG: Session pid=3281: Authenticate result for user osd1000: 
Authentication stopped before completion
  [+20.66s] DEBUG: Seat: Session stopped
  [+20.71s] DEBUG: Session pid=3281: Greeter start authentication for osd1000
  [+20.71s] DEBUG: Session pid=3434: Started with service 'lightdm', username 
'osd1000'
  [+20.71s] DEBUG: Session pid=3434: Got 1 message(s) from PAM
  [+20.71s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)

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

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

[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep

2014-05-14 Thread Xubnu

This bug seems to be a duplicate of this
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-
manager/+bug/1303736 there is a solution that seems to work
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-
manager/+bug/1303736/comments/56

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

Title:
  Ubuntu 14.04 blank screen after wakeup from sleep

Status in “linux-lts-trusty” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware 
profile).
  OS: Ubuntu 14.04 (updated today).

  After wakeup the notebook from the sleep mode, the screen goes blank while 
the OS and the hardware is awake.
  (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system).

  This problem is not happening with the AMD property drivers (but they
  have another bug, i can't set up the brighness of the monitor).

  The problem in my opinion is related to this package:  xserver-xorg-
  video-ati.

  Changing quiet splash with nomodeset into /etc/default/grub makes
  the wakeup working, but the pc is really slow (can't be used), also
  after the normal start up.

  
  Best regards and have a good work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  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
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1318249] Re: Failure to resume from hybrid suspend

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

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

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

Title:
  Failure to resume from hybrid suspend

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I followed http://askubuntu.com/questions/145443/how-do-i-use-pm-
  suspend-hybrid-by-default-instead-of-pm-suspend/145676#145676 to set
  up hybrid suspend, creating the file /etc/pm/config.d/00-use-suspend-
  hybrid with the following contents:

  -- snip ---
  HIBERNATE_MODE=platform

  # Always use hibernate instead of suspend, but with suspend to both
  if [ $METHOD = suspend ]; then
METHOD=hibernate
HIBERNATE_MODE=suspend
  fi

  # Make sure to use the kernel's method, in case uswsusp is installed etc.
  SLEEP_MODULE=kernel
  -- snip --

  On suspend, the system writes an image to disk (according to
  /var/log/syslog) and goes to sleep on RAM as expected. However, on
  resume things first seem to proceed normally, but the screen is never
  lit up. I couldn't find any obvious errors in /var/log/syslog.

  The behaviour is similar with the Indirect hybrid sleep approach,
  which used to work successfully before upgrading from 13.10 to 14.04.

  Both suspend-to-RAM and suspend-to-disk (hibernate) work and resume
  sucessfully, i.e. when removing the file /etc/pm/config.d/00-use-
  suspend-hybrid.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 10 22:34:48 2014
  InstallationDate: Installed on 2012-06-20 (689 days ago)
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (17 days ago)

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

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

[Desktop-packages] [Bug 923450] Re: Printing scaled pages over 100% keeps upper and left margins intact.

2014-05-14 Thread Bug Watch Updater

** Changed in: evince
   Status: New = Fix Released

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

Title:
  Printing scaled pages over 100% keeps upper and left margins intact.

Status in Evince document viewer:
  Fix Released
Status in “evince” package in Ubuntu:
  Triaged

Bug description:
  I tried to print a page with the scaling option at 120%, in order to
  take advantage of the large marginal area.Left and upper margins were
  left as they were, while the page overflowed to the right and lower
  sides.I tried different options and different files but it had no
  effect.Version of evince is GNOME Document Viewer 2.32.0 .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Sun Jan 29 20:43:14 2012
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  KernLog:
   Jan 29 19:53:41 asmodeus kernel: [ 2046.850347] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
   Jan 29 19:53:41 asmodeus kernel: [ 2046.855097] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
  ProcCmdline_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-13-generic 
root=UUID=13528e62-281f-4128-9d2a-466ab9b40bb0 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-13.53-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1317151] Re: lightdm segfaults when trying to log in with NIS user

2014-05-14 Thread Owen Dunn

I think this is actually an instance of 1308043, and removing pam-
kwallet fixes the problem.

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

Title:
  lightdm segfaults when trying to log in with NIS user

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Running ubuntu 14.04 LTS with lightdm 1.10.0-0ubuntu3

  The system is configured to use NIS so has:

  passwd: files nis
  group: files nis
  shadow: files nis

  in /etc/nsswitch.conf.

  A NIS user can log in on a virtual console (tty1 etc.) but trying
  to log in under lightdm fails, with the following in dmesg:

  [ 1452.065454] lightdm[2957]: segfault at 0 ip 7fd8935b9be0 sp
  7fffaeafd270 error 4 in libc-2.19.so[7fd89354a000+1bc000]

  and the following in /var/log/lightdm/lightdm.log:

  [+0.32s] DEBUG: Session pid=3281: Greeter connected version=1.10.0
  [+0.55s] DEBUG: Session pid=3281: Greeter start authentication
  [+0.55s] DEBUG: Session pid=3402: Started with service 'lightdm', username 
'(null)'
  [+0.56s] DEBUG: Session pid=3402: Got 1 message(s) from PAM
  [+0.56s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)
  [+13.86s] DEBUG: Session pid=3281: Greeter start authentication for osd1000
  [+13.86s] DEBUG: Session pid=3402: Sending SIGTERM
  [+13.87s] DEBUG: Session pid=3432: Started with service 'lightdm', username 
'osd1000'
  [+13.87s] DEBUG: Session pid=3402: Terminated with signal 15
  [+13.87s] DEBUG: Session: Failed during authentication
  [+13.87s] DEBUG: Seat: Session stopped
  [+13.87s] DEBUG: Session pid=3432: Got 1 message(s) from PAM
  [+13.87s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)
  [+20.55s] DEBUG: Session pid=3281: Continue authentication
  [+20.66s] DEBUG: Session pid=3432: Terminated with signal 11
  [+20.66s] DEBUG: Session: Failed during authentication
  [+20.66s] DEBUG: Session pid=3281: Authenticate result for user osd1000: 
Authentication stopped before completion
  [+20.66s] DEBUG: Seat: Session stopped
  [+20.71s] DEBUG: Session pid=3281: Greeter start authentication for osd1000
  [+20.71s] DEBUG: Session pid=3434: Started with service 'lightdm', username 
'osd1000'
  [+20.71s] DEBUG: Session pid=3434: Got 1 message(s) from PAM
  [+20.71s] DEBUG: Session pid=3281: Prompt greeter with 1 message(s)

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

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

[Desktop-packages] [Bug 1283459] Re: Please merge xscreensaver (5.26-1) from Debian unstable

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 1196251] Re: pacman crashed with SIGSEGV in is_bonus_dot()

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 103975] Re: [amd64] bumps crashed with SIGSEGV in __libc_start_main() [PutPixel32()]

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 1229486] Re: xscreensaver-command is slow at locking

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 609451] Re: xscreensaver-getimage can't find image on samba share

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 781948] Re: Format string bug in xscreensaver-text

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 1116006] Re: xscreensaver-settings breaks imageDirectory line if it is a URL

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
- Ubuntu delta to the screensavers sets.
- Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
  repository: the Desktop team does not have interest any more.
- The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
- debian/control:
  + Breaks/Replaces: the old changes are not needed anymore, but the
new changes the screensavers sets needs it.
- debian/rules:
  + Use /usr/share/backgrounds as image directory.
  + Add translation domain to .desktop files.
- debian/source_xscreensaver.py:
  + Add apport hook.
- debian/xscreensaver.dirs:
  + Install /usr/share/backgrounds. By default, settings search in
/usr/share/backgrounds and without it, it displays an error.
- debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
- debian/patches/60_sequential_glslideshow.patch:
  + Allow going through images sequentially rather than just at random in
the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
- Updated feed-loading for recent Flickr changes.
- Updated `webcollage' for recent Google changes.
- Added Instagram and Bing as `webcollage' image sources.
- Updated to latest autoconf.
- Bug fixes.
  * Drop patch applied upstream:
- debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
- New hack, geodesic
- More heuristics for using RSS feeds as image sources
- Improved Wikipedia parser
- Updated webcollage for recent Flickr changes
- Added Android to bsod
- Made quasicrystal work on weak graphics cards
- Better compression on icons, plists and XML files
- Reverted that DEACTIVATE change. Bad idea.
- Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
- 12_upstream_quasicrystal_texture_width.patch
- 14_upstream_hexadrop_keyboard_exit.patch
- 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
- XInput devices now also ignore small mouse motions
- Loading images via RSS feeds is much improved
- Enlarged the texture image for lament
- Made pipes be ridiculously less efficient, but spin
- Added better mouse control to rubik, cube21, crackberg, and julia
- Cosmetic improvements to queens and endgame
- sonar can now ping local subnet on DHCP
- Most savers now resize/rotate properly
- New version of `fireworkx'
- Minor fixes to `distort', `fontglide', `xmatrix'
- New MacOS crash in `bsod'
- New mode in `lcdscrub'
- Gnome/KDE instructions updated in man page (Closes: #640640)
- New --enable-pam-check-account-type option (Closes: #656766)
- Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
- Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
  image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
- New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
- Performance improvements for `interference'.
- Fixed possible crashes in apple2, maze, pacman, polyominoes,
  fireworkx, engine (LP: #1196251)
- Fix for `bumps' in 64 bit (LP: #103975)
- Fixed Shake to Randomize; display name of saver.
- Fixed rotation problems with `pacman', `decayscreen'.
- Better dragging in `fluidballs'.
- Ignore rotation in hacks that don't benefit from it.
- Ignore DEACTIVATE messages when locked, instead of popping up the
  password dialog box.
- Fix format string glitch in xscreensaver-text (LP: #781948)
  (thanks Emanuel Bronshtein)
  * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
logically separated and better named patches
  * debian/patches/57_grabDesktopImages_default_off.patch:
Do not reveal desktop content by default (Closes: #679974)
  * debian/patches/12_upstream_quasicrystal_texture_width.patch:
Adjust texture width to graphics card/driver capability
  * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
Allow keyboard exit when run standalone (from upstream)
  * debian/patches/15_upstream_activate_faster_nontty.patch:
Activate faster when not from tty session (LP: #1229486)
  * Bump Standards-Version to 3.9.4 (no changes needed)
  * debian/rules: Drop unnecessary dh_testroot from clean target
(thanks Julien Cristau)
  * debian/rules:

[Desktop-packages] [Bug 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume

2014-05-14 Thread Gabriele

@Raymond
I will try to send the patch to the alsa devel mailing list when I've time. 
Surely they'll know better than me what to do.

Anyway, I'm not using Ubuntu, so I can't hel you with your last
question.

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

Title:
  [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background
  noise or low volume

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

Bug description:
  When listening to sound on my laptop through headphones, there's a
  constant background hiss (which disappears only when all sound has
  been stopped for a few seconds. power saving I guess).

  I also need to turn the volume *way* down to 10% for the sound volume
  to be reasonable (it's way too loud otherwise).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martijn2130 F pulseaudio
   /dev/snd/pcmC1D0p:   martijn2130 F...m pulseaudio
   /dev/snd/controlC0:  martijn2130 F pulseaudio
  Date: Tue Nov 19 14:26:46 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Intern geluid - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1319324] [NEW] Problem report keeps the user in the dark

2014-05-14 Thread DonQuichote

Public bug reported:

When a crash report exists, I am greeted at system start-up with a
windows that says: There is a system problem. Do you want to report it
now? It does not give any clue about what that problem is.

I expect that window to show what problem it is referring to.

For example, I had an updating issue with a package from an external
repository (MariaDB in my case), which was easily solved by following
the suggestions made by apt-get. So there was no issue. However, at the
next system start I was confronted with this problem that was not a
problem. Only by looking in /var/crash/, I could see that it had to be
this issue.

Also, this window leaves me the choice between filing a report (bad
option in this case) or cancel, which means postponing the report (also
a bad option).

I would like the opportunity to see that the problem presented at start-
up is one I already solved, and NOT report it. Preferably in or from
that same start-up window. I managed to delete the problem report by
deleting the file in /var/crash/, but that is not exactly newbie-
friendly.

$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10

$ apt-cache policy apport
apport:
  Installed: 2.12.5-0ubuntu2.2
  Candidate: 2.12.5-0ubuntu2.2
  Version table:
 *** 2.12.5-0ubuntu2.2 0
500 http://nl.archive.ubuntu.com/ubuntu/ saucy-updates/main i386 
Packages
100 /var/lib/dpkg/status
 2.12.5-0ubuntu2.1 0
500 http://security.ubuntu.com/ubuntu/ saucy-security/main i386 Packages
 2.12.5-0ubuntu2 0
500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages

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

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

Title:
  Problem report keeps the user in the dark

Status in “apport” package in Ubuntu:
  New

Bug description:
  When a crash report exists, I am greeted at system start-up with a
  windows that says: There is a system problem. Do you want to report
  it now? It does not give any clue about what that problem is.

  I expect that window to show what problem it is referring to.

  For example, I had an updating issue with a package from an external
  repository (MariaDB in my case), which was easily solved by following
  the suggestions made by apt-get. So there was no issue. However, at
  the next system start I was confronted with this problem that was
  not a problem. Only by looking in /var/crash/, I could see that it had
  to be this issue.

  Also, this window leaves me the choice between filing a report (bad
  option in this case) or cancel, which means postponing the report
  (also a bad option).

  I would like the opportunity to see that the problem presented at
  start-up is one I already solved, and NOT report it. Preferably in or
  from that same start-up window. I managed to delete the problem report
  by deleting the file in /var/crash/, but that is not exactly newbie-
  friendly.

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy apport
  apport:
Installed: 2.12.5-0ubuntu2.2
Candidate: 2.12.5-0ubuntu2.2
Version table:
   *** 2.12.5-0ubuntu2.2 0
  500 http://nl.archive.ubuntu.com/ubuntu/ saucy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.12.5-0ubuntu2.1 0
  500 http://security.ubuntu.com/ubuntu/ saucy-security/main i386 
Packages
   2.12.5-0ubuntu2 0
  500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages

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

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

[Desktop-packages] [Bug 1309505] Re: 10de:0a3c [HP EliteBook 8540w] system freeze

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

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

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

Title:
  10de:0a3c [HP EliteBook 8540w] system freeze

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Syetem freezes after 3 minutes with nouveau.

  WORKAROUND: Nvidia works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 18 14:37:24 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1521]
  InstallationDate: Installed on 2014-04-14 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=941accfe-1eb6-4d0f-a38c-56626980c09b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.08
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.08:bd04/28/2010:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Apr 18 14:23:12 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1319326] [NEW] fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build

2014-05-14 Thread gbagape

Public bug reported:

 fglrx kernel module failed to build

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:8.970-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
.tmp.unity.support.test.0:
 
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSBuildLog:
 DKMS make.log for fglrx-8.970 for kernel 3.13.0-24-generic (i686)
 miercuri 14 mai 2014, 12:33:46 +0300
 AMD kernel module generator version 2.1
 kernel includes at /lib/modules/3.13.0-24-generic/build/include not found or 
incomplete
 file: /lib/modules/3.13.0-24-generic/build/include/linux/version.h
DKMSKernelVersion: 3.13.0-24-generic
Date: Wed May 14 12:33:51 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.970: added
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7641]
InstallationDate: Installed on 2014-05-14 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: MSI MS-7641
PackageVersion: 2:8.970-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=34ff2ca6-6a7a-4a45-892b-9155278f87b1 ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer
Title: fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V17.15
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 760GM-P23(FX) (MS-7641)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 3.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV17.15:bd04/28/2013:svnMSI:pnMS-7641:pvr3.0:rvnMSI:rn760GM-P23(FX)(MS-7641):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: MS-7641
dmi.product.version: 3.0
dmi.sys.vendor: MSI
make.log:
 DKMS make.log for fglrx-8.970 for kernel 3.13.0-24-generic (i686)
 miercuri 14 mai 2014, 12:33:46 +0300
 AMD kernel module generator version 2.1
 kernel includes at /lib/modules/3.13.0-24-generic/build/include not found or 
incomplete
 file: /lib/modules/3.13.0-24-generic/build/include/linux/version.h
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed May 14 09:06:38 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 Error loading keymap 
/var/lib/xkb/server-C3DB0219DAD0989E87CAAD72AD54F5E06B41CB57.xkm
 XKB: Failed to load keymap. Loading default keymap instead.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0   VGA-0
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 third-party-packages trusty ubuntu

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

Title:
  fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
   fglrx kernel module failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:8.970-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSBuildLog:
   DKMS make.log for fglrx-8.970 for kernel 3.13.0-24-generic (i686)
   miercuri 14 mai 2014, 12:33:46 +0300
   AMD kernel module generator version 2.1
   kernel includes at /lib/modules/3.13.0-24-generic/build/include not found or 
incomplete
   file: /lib/modules/3.13.0-24-generic/build/include/linux/version.h
  DKMSKernelVersion: 3.13.0-24-generic
  Date: Wed May 14 12:33:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

2014-05-14 Thread Alberto Milone

@krelx0: I'm not sure what you mean by adding rules with prime

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

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

Bug description:
  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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/1310023/+subscriptions

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

[Desktop-packages] [Bug 1319164] Re: Amarok won't work on Lubuntu 14.04 AMD64

2014-05-14 Thread Myriam Schweingruber

This is most likely a problem with the Spectrum Analyzer and OpenGL, you
can workaround this for the moment and disable the analyzer by editing
the ~/.kde/share/config/amarokrc file and set this value:

[Context View]
firstTimeWithAnalyzer=false

Restarting Amarok after that should show if I am right.

FWIW: if you want a sensible output from the konsole, always start
amarok with

amarok -d --nofork

** Bug watch added: KDE Bug Tracking System #323635
   https://bugs.kde.org/show_bug.cgi?id=323635

** Also affects: amarok via
   https://bugs.kde.org/show_bug.cgi?id=323635
   Importance: Unknown
   Status: Unknown

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

Title:
  Amarok won't work on Lubuntu 14.04 AMD64

Status in The Amarok Music Player:
  Unknown
Status in “amarok” package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Amilo Pa 1538 (AMD Turion 64, X2 Mobile technology TL-50)
  1 GB RAM
  Graphic card: Nvidia G72M (Geforce Go 7400)
  System: Lubuntu 14.04 Desktop AMD64
  BIOS up to date

  Fresh install + install of new upgrades (official repositories)
  Install amarok 2.8 (including automatic selected necessary packages) out of 
the official repositories.

  On starting amarok, amarok window appears but freezes almost instantly 
(before the usual animation on first start after installation). There is no 
reaction by clicking anywhere inside the window.
  The window may be maximized, but only the frame maximizes, the content of the 
window doesn't get maximized.
  The computer can still be used or shut down the usual way when amarok is 
hanging that way.
  The amarok process doesn't use CPU then. It must be killed to stop.

  On a previous install of the same OS (exactly same version) on the
  same computer, Amarok started after some trials (I did nothing
  special. I had just played an MP3 with Gnome MPlayer before, but I
  don't think it was the reason. I shall also say that it first worked
  on the day after installation of the OS). Afterwards, amarok always
  worked fine.

  With Lubuntu 14.04 i386 on this machine, amarok works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: amarok 2:2.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue May 13 21:39:53 2014
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: amarok
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1317436] Re: onboard memory usage/cpu increase and lockup

2014-05-14 Thread Zen25000

Not sure if this is useful - short run, opened and closed TB which
downloaded 25 emails then stopped onboard:

==11274== 1,890,176 bytes in 118,136 blocks are definitely lost in loss record 
17,326 of 17,338
==11274==at 0x4C2863A: realloc (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11274==by 0x1070577E: set_length (dbus-string.c:352)
==11274==by 0x10706054: _dbus_string_append_len (dbus-string.c:903)
==11274==by 0x106F6153: dbus_message_iter_get_signature 
(dbus-message.c:2157)
==11274==by 0x104C620C: _atspi_dbus_set_interfaces (atspi-misc.c:1364)
==11274==by 0x104C6FC3: add_accessible_from_iter (atspi-misc.c:460)
==11274==by 0x104C7622: process_deferred_messages.part.14 (atspi-misc.c:681)
==11274==by 0x104C7798: process_deferred_messages_callback 
(atspi-misc.c:748)
==11274==by 0x953CABC: g_main_context_dispatch (gmain.c:3064)
==11274==by 0x953CE27: g_main_context_iterate.isra.24 (gmain.c:3734)
==11274==by 0x953D0E9: g_main_loop_run (gmain.c:3928)
==11274==by 0xB7D77F4: gtk_main (in /usr/lib64/libgtk-3.so.0.1200.1)

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

Title:
  onboard memory usage/cpu increase and lockup

Status in Onboard on-screen keyboard:
  Invalid
Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  I am running onboard in Mageia 5 (Cauldron) and recently I'm seeing a
  total lock-up of onboard after the machine has been running for over
  24 hours.

  The tray icon is there but does nothing. At this point onboard is
  using 25% cpu and 880MB ram..

  I am attaching the memory usage analysis  for onboard (after the
  lockup)  in the hope that it will be of use.

  In the meantime I will try to monitor  memory usage  over a day to see
  if this increase is gradual or happens suddenly.

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

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

[Desktop-packages] [Bug 434476]

2014-05-14 Thread Edwin-d

(In reply to Karl Tomlinson (needinfo?:karlt) from comment #41)
 +WakeLockTopic::UninhibitScreensaver()
 +{
 +  if (!mShouldInhibit) {
 +// Screensaver isn't inhibited. Nothing to do here.
 +return NS_OK;
 
 Could this instead assert that this path is not reached, as in
 InhibitScreensaver()?

No. There are two states unlocked and locked-background that we map
to Uninhibit, that can both be reached directly from locked-
foreground.

Addressing other comments, new patch coming.

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

Title:
  screensaver starts while playing HTML5 videos

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

Bug description:
  Binary package hint: firefox-3.5

  karmic alpha6 + updates

  - click on a .ogv video link
  - after watching some time, screensaver starts.

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Sep 22 08:45:53 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: firefox 3.5.3+build1+nobinonly-0ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: firefox-3.5
  Uname: Linux 2.6.31-10-generic x86_64

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

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

[Desktop-packages] [Bug 1319338] [NEW] Default boost v1.54 has broken asio while available 1.55 is fixed

2014-05-14 Thread Tobias Föhst

Public bug reported:

Release: 14.04 LTS
Version: 1.54.0.1ubuntu1
Expected: Depend on working version of boost
Happened: Depends on boost 1.54

Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
Due to that, working with boost/asio seems impossible.

The bug is still present in boost1.54 but fixed in boost1.55. Therefore
I consider it a bug to use version 1.54 as default, as other libraries'
dev-packages depend on boost-default and hence cannot be installed
together with libboost1.55-dev without being rebuild.

Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

** Affects: boost-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Default boost v1.54 has broken asio while available 1.55 is fixed

Status in “boost-defaults” package in Ubuntu:
  New

Bug description:
  Release: 14.04 LTS
  Version: 1.54.0.1ubuntu1
  Expected: Depend on working version of boost
  Happened: Depends on boost 1.54

  Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
  Due to that, working with boost/asio seems impossible.

  The bug is still present in boost1.54 but fixed in boost1.55.
  Therefore I consider it a bug to use version 1.54 as default, as other
  libraries' dev-packages depend on boost-default and hence cannot be
  installed together with libboost1.55-dev without being rebuild.

  Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
  But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1319338/+subscriptions

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

[Desktop-packages] [Bug 1319339] [NEW] Unity lock screen - please fix password input delay.

2014-05-14 Thread AndreK

Public bug reported:

Before 14.04:
I could type password and press enter to log on even when displays were still 
sleeping.

in 14.04:
The first keypresses are never registered, tping PW directly+enter gives wrong 
password (and too few dots appear in the PW field)
now I furst need to wake the computer, by pressing other kays like arrows, then 
enter PW.

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

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

Title:
  Unity lock screen - please fix password input delay.

Status in “unity” package in Ubuntu:
  New

Bug description:
  Before 14.04:
  I could type password and press enter to log on even when displays were still 
sleeping.

  in 14.04:
  The first keypresses are never registered, tping PW directly+enter gives 
wrong password (and too few dots appear in the PW field)
  now I furst need to wake the computer, by pressing other kays like arrows, 
then enter PW.

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

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

[Desktop-packages] [Bug 867753] Re: Accept-Language header contains incorrect value

2014-05-14 Thread Sven Jörns

It was possible for me to fix this problem with this addOn
https://addons.mozilla.org/de/firefox/addon/quick-accept-language-switc/?src=api
Changing Accept-Language to any value, restart and set to default in 
about:config.

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

Title:
  Accept-Language header contains incorrect value

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

Bug description:
  Both my OS and Firefox preferences has en-GB and en as the language,
  however, it's sending en-US, en in the accept-language request
  header. This was verified using Bugzilla after finding the problem.
  Dates on some sites are a particular problem given that for many dates
  there is no way to tell the difference between en-GB and en-US, you
  just read the date wrong.

  Steps to reproduce:
  1) Start Firefox
  2) In Edit - Preferences - check the lanugage settings are en-gb and en.
  3) Start Firebug.
  4) Access www.google.co.uk
  5) Check the Net tab in firebug.
  6) Expand the first (or any line).
  7) Scroll to the Request Headers.
  8) Observe Accept-language contains en-us,en;q=0.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phill  1675 F pulseaudio
  BuildID: 20110928224508
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf680 irq 43'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:10ec0662,14621033,00100101 
HDA:80862804,14621033,0010'
     Controls  : 20
     Simple ctrls  : 11
  Channel: release
  Date: Tue Oct  4 19:03:40 2011
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  IpRoute:
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.2  metric 2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   default via 192.168.0.1 dev wlan0  proto static
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110928224508 (Running)
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1681IG6 VER.109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: Micro-Star International
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Micro-Star International
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1681IG6VER.109:bd07/21/2010:svnMicro-StarInternational:pnCalpellaplatform:pvrVer.001:rvnMicro-StarInternational:rnTobefilledbyO.E.M.:rvrVer.001:cvnMicro-StarInternational:ct9:cvrVer.001:
  dmi.product.name: Calpella platform
  dmi.product.version: Ver.001
  dmi.sys.vendor: Micro-Star International

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

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

[Desktop-packages] [Bug 1188774] Re: 8086:0126 [Lenovo ThinkPad Edge E430] [snb] 13.04 goes into hard lock mode randomly.

JaSauders, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1188774/comments/16 regarding this being fixed with an
update. For future reference you can manage the status of your own bugs
by clicking on the current status in the yellow line and then choosing a
new status in the revealed drop down box. You can learn more about bug
statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for
taking the time to report this bug and helping to make Ubuntu better.
Please submit any future bugs you may find.

sohel, thank you for your comment. So your hardware and problem may be tracked,
could you please file a new report with Ubuntu by executing the following in a
terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Invalid

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

Title:
8086:0126 [Lenovo ThinkPad Edge E430] [snb] 13.04 goes into hard lock
mode randomly.

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

Bug description:
Ubuntu 13.04 64 bit.
Lenovo E430 laptop.

My laptop will lock up at random times. When it locks up, there is no
mouse movement, no time change with the clock, just... nothing. The
only option is to hold the power button to force it off and restart.
This happens at any given time, it doesn't matter what I'm doing.
There are times it happens while web browsing. The other night I fell
asleep and woke up 1.5 hours later to my laptop still looking at me. I
thought, it should have suspended by now. Nope, it was hard locked.
The time on the clock confirmed it: 8:18 PM on the Lenovo when it was
about 10:00 PM. When I've experienced it, I've never been pushing the
system hard. It's always been under more light duty tasks. When this
has happened I have not had a 2nd monitor plugged in.

While I don't have a recent syslog (unless ubuntu-bug picked it up
when I filed), I did notice one entry in my syslog that was similar
each time I powered the system back up. It was the only thing that
looked somewhat off. It's this line here:

May 24 21:45:28 JS-UbuE430 signond[2949]:
../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root.
Secure storage will not be available.

For what it's worth, I spoke to another user who said they were having
100% identical issues. I do believe they are on a Dell system, not a
Lenovo system like I am, however our graphics card came up identical
when we both ran lspci:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09)

Thank you for your time.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jun 7 15:04:43 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:5000]
InstallationDate: Installed on 2013-05-15 (23 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: LENOVO 3254CTO
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic
root=UUID=0d29548d-e336-4c01-a0f2-dbf78a194e17 ro acpi_osi=!Windows 2012
quiet splash vt.handoff=7
SourcePackage:

[Desktop-packages] [Bug 1315881] Re: Chromium changes its name to 'Facebook' after using Tools Create Application Shortcuts... Application Menu on www.facebook.com

2014-05-14 Thread Ads20000

How can I make this complete please?

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

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

Title:
  Chromium changes its name to 'Facebook' after using Tools  Create
  Application Shortcuts...  Application Menu on www.facebook.com

Status in BAMF Application Matching Framework:
  Incomplete
Status in “chromium-browser” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  On a brand new install of Ubuntu 14.04 LTS Trusty Tahr 64-bit with 
chromium-browser 34.0.1847.116-0ubuntu2 and Unity 
7.2.0+14.04.20140423-0ubuntu1.2 (all fully updated when the bug was found):

  1. Install Chromium
  2. Click the Settings icon on the right
  3. Click on Tools  Create Application Shortcuts...
  4. [Deselect Desktop] Select Application Menu
  5. Click Create
  6. An icon will come up with the Chromium logo with the 'Facebook' name
  7. Close all Chromium windowschromium-browser
  8. Unlock the normal 'Chromium' one from the Launcher
  9a. When clicking on the 'Facebook' launcher - launches a New Tab in Chromium.
  9b. When searching for 'Chromium' in the Dash, it can't find it - Chromium is 
now known as Facebook

  For some reason, I can now add a second Facebook launcher with the
  correct icon and everything but the Chromium one which calls itself
  'Facebook' in the Dash and Launcher just acts like normal Chromium.
  Because of this, I'm not sure if the bug can be reproduced. Really
  annoying though: if anyone has a fix for this (so - how do I correct
  'Chromium' to call itself 'Chromium' not 'Facebook' in the Dash) then
  I would be very grateful :)

  If you need any files, please ask. Running 'ubuntu-bug chromium-
  browser' only opened a New Tab (in a new window) in Chromium after
  reporting so I couldn't do that. I will report that as a separate bug
  when I get the chance. (Update: Seems like this happens for every link
  I try to open from the desktop)

  I don't know if this is a bug in Unity or Chromium so I've filed it as
  under both. Feel free to Invalidate one once you know which project
  this isn't a problem in.

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

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

Re: [Desktop-packages] [Bug 1283459] Re: Please merge xscreensaver (5.26-1) from Debian unstable

2014-05-14 Thread Mattia Rizzolo

On May 14, 2014 10:31 AM, Martin Pitt martin.p...@ubuntu.com wrote:

 Thanks!

Thank you for sponsoring the upload!

 I'll rearrange the changelog a bit to split between dropped
 Ubuntu changes and remaining Ubuntu changes, as putting the former
 into the latter section is confusing.

Yeah, better now :)

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

Title:
  Please merge xscreensaver (5.26-1) from Debian unstable

Status in “xscreensaver” package in Ubuntu:
  Fix Released

Bug description:
  Changes since the last upload:

  xscreensaver (5.26-1) unstable; urgency=low

    * New upstream release 5.26, changes since 5.23:
  - Updated feed-loading for recent Flickr changes.
  - Updated `webcollage' for recent Google changes.
  - Added Instagram and Bing as `webcollage' image sources.
  - Updated to latest autoconf.
  - Bug fixes.
    * Drop patch applied upstream:
  - debian/patches/12_upstream_use_cppflags.patch
    * Bump Standards-Version to 3.9.5 (no changes needed)

   -- Tormod Volden debian.tor...@gmail.com  Mon, 17 Feb 2014 20:34:28
  +0100

  xscreensaver (5.23-1) unstable; urgency=low

    * New upstream release 5.23 (Closes: #729311)
  - New hack, geodesic
  - More heuristics for using RSS feeds as image sources
  - Improved Wikipedia parser
  - Updated webcollage for recent Flickr changes
  - Added Android to bsod
  - Made quasicrystal work on weak graphics cards
  - Better compression on icons, plists and XML files
  - Reverted that DEACTIVATE change. Bad idea.
  - Phosphor now supports amber as well as green
    * Dropped patches applied upstream:
  - 12_upstream_quasicrystal_texture_width.patch
  - 14_upstream_hexadrop_keyboard_exit.patch
  - 15_upstream_activate_faster_nontty.patch
    * debian/patches/12_upstream_use_cppflags.patch:
  Make sure CPPFLAGS are used (fixes hardening warnings)
    * debian/control: Update VCS fields (fixes Lintian warning)

   -- Tormod Volden debian.tor...@gmail.com  Sat, 23 Nov 2013 20:47:28
  +0100

  xscreensaver (5.22-1) unstable; urgency=low

    * New upstream release 5.22 (Closes: #699833), changes since 5.15:
  - XInput devices now also ignore small mouse motions
  - Loading images via RSS feeds is much improved
  - Enlarged the texture image for lament
  - Made pipes be ridiculously less efficient, but spin
  - Added better mouse control to rubik, cube21, crackberg, and julia
  - Cosmetic improvements to queens and endgame
  - sonar can now ping local subnet on DHCP
  - Most savers now resize/rotate properly
  - New version of `fireworkx'
  - Minor fixes to `distort', `fontglide', `xmatrix'
  - New MacOS crash in `bsod'
  - New mode in `lcdscrub'
  - Gnome/KDE instructions updated in man page (Closes: #640640)
  - New --enable-pam-check-account-type option (Closes: #656766)
  - Fixed imageDirectory URL parsing. Closes: #714582 (LP: #1116006)
  - Use of AC_SYS_LARGEFILE fixes inode number overflow when accessing
    image files on cifs file systems (LP: #609451) Thanks Mamoru Tasaka!
  - New hacks: kaleidocycle, quasicrystal, unknownpleasures, hexadrop
  - Performance improvements for `interference'.
  - Fixed possible crashes in apple2, maze, pacman, polyominoes,
    fireworkx, engine (LP: #1196251)
  - Fix for `bumps' in 64 bit.
  - Fixed Shake to Randomize; display name of saver.
  - Fixed rotation problems with `pacman', `decayscreen'.
  - Better dragging in `fluidballs'.
  - Ignore rotation in hacks that don't benefit from it.
  - Ignore DEACTIVATE messages when locked, instead of popping up the
    password dialog box.
  - Fix format string glitch in xscreensaver-text (LP: #781948)
    (thanks Emanuel Bronshtein)
    * debian/patches: Split up 53_XScreenSaver.ad.in.patch into
  logically separated and better named patches
    * debian/patches/57_grabDesktopImages_default_off.patch:
  Do not reveal desktop content by default (Closes: #679974)
    * debian/patches/12_upstream_quasicrystal_texture_width.patch:
  Adjust texture width to graphics card/driver capability
    * debian/patches/14_upstream_hexadrop_keyboard_exit.patch:
  Allow keyboard exit when run standalone (from upstream)
    * debian/patches/15_upstream_activate_faster_nontty.patch:
  Activate faster when not from tty session (LP: #1229486)
    * Bump Standards-Version to 3.9.4 (no changes needed)
    * debian/rules: Drop unnecessary dh_testroot from clean target
  (thanks Julien Cristau)
    * debian/rules: Include buildflags.mk for hardening options
    * Stop xscreensaver in prerm instead of postrm (Closes: 681613)
  (thanks Filipus Klutiero)
    * New xscreensaver daemon wrapper used by the example .desktop file
  to determine

[Desktop-packages] [Bug 923450] Re: Printing scaled pages over 100% keeps upper and left margins intact.

2014-05-14 Thread Sebastien Bacher

The issue has been fixed upstream with
https://git.gnome.org/browse/evince/commit/?id=4df4afe90c902652a84d16e1735105960a649145

** Changed in: evince (Ubuntu)
   Status: Triaged = Fix Committed

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

Title:
  Printing scaled pages over 100% keeps upper and left margins intact.

Status in Evince document viewer:
  Fix Released
Status in “evince” package in Ubuntu:
  Fix Committed

Bug description:
  I tried to print a page with the scaling option at 120%, in order to
  take advantage of the large marginal area.Left and upper margins were
  left as they were, while the page overflowed to the right and lower
  sides.I tried different options and different files but it had no
  effect.Version of evince is GNOME Document Viewer 2.32.0 .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Sun Jan 29 20:43:14 2012
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  KernLog:
   Jan 29 19:53:41 asmodeus kernel: [ 2046.850347] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
   Jan 29 19:53:41 asmodeus kernel: [ 2046.855097] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
  ProcCmdline_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-13-generic 
root=UUID=13528e62-281f-4128-9d2a-466ab9b40bb0 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-13.53-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts

2014-05-14 Thread Arthur

iBus is working by switching layouts manually, from keyboard indicator
icon on the panel, but cannot handle keyboard shortcuts, such as
Alt+Shift or Ctrl+Shift, when I try to configure it.
Controlspace, which is by default - also not work.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1319149] Re: HP Pavillion x360 boots very unreliably

2014-05-14 Thread Maarten Lankhorst

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

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

Title:
  HP Pavillion x360 boots very unreliably

Status in “linux” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  New

Bug description:
  and the touch screen doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick   1911 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 13 14:47:04 2014
  HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
   Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097512405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1071277] Re: Banshee doesn't remember volume setting

2014-05-14 Thread Chow Loong Jin

I got the fix from upstream.

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

Title:
  Banshee doesn't remember volume setting

Status in Banshee Music Player:
  Fix Released
Status in “banshee” package in Ubuntu:
  Fix Released

Bug description:
  If I set the music volume using the volume control in the top right of
  Banshee, then quit and restart the program, the volume is reset to
  100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: banshee 2.6.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Oct 25 12:25:15 2012
  InstallationDate: Installed on 2012-04-24 (183 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  MarkForUpload: True
  SourcePackage: banshee
  UpgradeStatus: Upgraded to quantal on 2012-09-17 (37 days ago)

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

** Attachment added: gpu-manager.log
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+attachment/4112199/+files/gpu-manager.log

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

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

Bug description:
  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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/1310023/+subscriptions

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

[Desktop-packages] [Bug 1312159] Re: (gksu:xxxx): CRITICAL : fcntl error

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

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

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Hi, I'm seeing the same thing on a fresh install of xubuntu 14.04. Once
it was installed I did the search for restricted drivers thing and
picked the top nvidia choice on the list: 331.38-0ubuntu7

In nvidia-settings if I try to switch away from Intel I get an empty pop
up with just a no-entry road sign graphic and [Ok] button.

from the command line is:

** Message: PRIME: Requires offloading
** Message: PRIME: is it supported? yes


when nvidia-settings starts, and

ERROR: 


when I try to click on NVIDIA (Performance Mode) when it asks which GPU
I'd like to use.

Interestingly, `nvidia-detector` returns none.

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] 
(rev a1)

my setup is 3 monitors, two being driven by the Intel on chip-HD, and
the third being driven by the GeForce. I never did get the third monitor
working with 12.04, but it is dual-boot with Windows7 and in Windows it
all three work fine.

A month or two back I booted the same system with a either a 14.04 beta1
or Mint live USB stick and all three monitors came to life in linux for
the first time, so I'm quite hopeful that the new linux kernel is
capable of good things.

I never installed bumblebee, and 'dpkg -l' shows it listed as ^un.
Would reminants of it have been pulled in during install so it would
need a --purge anyway?

`lsmod` shows that the 'nvidia' kernel module is loaded.

some of dmesg:
   11.293526] nvidia: module license 'NVIDIA' taints kernel.
[   11.293528] Disabling lock debugging due to kernel taint
[   11.293601] mei_me :00:16.0: irq 47 for MSI/MSI-X
[   11.296345] nvidia: module verification failed: signature and/or  required 
key missing - tainting kernel
[   11.299871] nvidia :01:00.0: enabling device ( - 0003)
[   11.299944] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=none
[   11.300129] [drm] Initialized nvidia-drm 0.0.0 20130102 for :01:00.0 on 
minor 0
[   11.300135] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  
8 19:32:30 PST 2014
[   11.300823] [drm] Memory usable by graphics device = 2048M
[   11.306653] WARNING! power/level is deprecated; use power/control instead
[   11.350366] i915 :00:02.0: irq 48 for MSI/MSI-X
[   11.350373] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.350374] [drm] Driver supports precise vblank timestamp query.
[   11.374521] [drm] Wrong MCH_SSKPD value: 0x20100406
[   11.374521] [drm] This can cause pipe underruns and display issues.
[   11.374521] [drm] Please upgrade your BIOS to fix this.
[   11.495669] fbcon: inteldrmfb (fb0) is primary device
...
[   11.825261] Console: switching to colour frame buffer device 210x65
[   11.827757] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   11.827758] i915 :00:02.0: registered panic notifier
[   11.830828] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   11.831006] acpi device:58: registered as cooling_device14
[   11.831047] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7
[   11.831198] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 1
[   11.831327] ACPI Warning: 0x0428-0x042f SystemIO 
conflicts with Region \PMIO 1 (20131115/utaddress-251)
[   11.831332] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   11.831335] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \GPIO 1 (20131115/utaddress-251)
[   11.831338] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   11.831339] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \LED_ 1 (20131115/utaddress-251)
[   11.831340] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \GPIO 2 (20131115/utaddress-251)
[   11.831342] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   11.831343] lpc_ich: Resource conflict(s) found affecting gpio_ich
...
[   15.322637] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
[   15.322642] bbswitch: cannot find ACPI handle for VGA device :01:00.0
[   15.322652] bbswitch: No discrete VGA device found
...
[   25.329742] init: Failed to spawn nvidia-persistenced main process: unable 
to execute: No such file or directory
...
[  726.739568] bbswitch: version 0.7
[  726.739575] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
[  726.739578] bbswitch: cannot find ACPI handle for VGA device :01:00.0
[  726.739580] bbswitch: No discrete VGA device found
[  736.749874] init: Failed to spawn nvidia-persistenced main process: unable 
to execute: No such file or directory


hmmm,

$ dpkg -l |

[Desktop-packages] [Bug 1312159] Re: (gksu:xxxx): CRITICAL : fcntl error

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DistroRelease: Ubuntu 12.04
MarkForUpload: True
Package: gksu 2.0.2-6ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 SHELL=/bin/bash
Tags:  precise
Uname: Linux 3.15.0-997-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo


** Tags added: precise

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1312159] Re: (gksu:xxxx): CRITICAL : fcntl error

I have attached a report from 3.14.0-997-lowlatency where gksu works,
and from 3.15.0-997-lowlatency where gksu doesn work.

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1312159] Dependencies.txt

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1312159/+attachment/4112207/+files/Dependencies.txt

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

** Attachment added: Xorg.0.log
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+attachment/4112211/+files/Xorg.0.log

** Changed in: nvidia-prime (Ubuntu)
   Status: Incomplete = 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/1310023

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

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

Bug description:
  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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/1310023/+subscriptions

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

[Desktop-packages] [Bug 1312159] apport information

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DistroRelease: Ubuntu 12.04
MarkForUpload: True
Package: gksu 2.0.2-6ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 SHELL=/bin/bash
Tags:  precise
Uname: Linux 3.14.0-997-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1312159] Dependencies.txt

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1312159/+attachment/4112210/+files/Dependencies.txt

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Confirmed

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1300283]

2014-05-14 Thread Momonasmon

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

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

Title:
  LibreOffice does not start in a KDE 4 session

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  It seems that the latest RC of LO is completely broken on KDE 4.

  Launching the LO center causes nothing to come up ( I can see a window
  title, but nothing inside the window itself ), launching writer causes
  a window to come up, which immediately hangs.

  Multiple users have brought this up on the Kubuntu Devel mailing list
  too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar 31 17:22:08 2014
  InstallationDate: Installed on 2014-03-18 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318)
  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/1300283/+subscriptions

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

[Desktop-packages] [Bug 1319348] [NEW] PCI/internal sound card not detected

2014-05-14 Thread AboAlfadl

Public bug reported:

sund card not detected

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
Uname: Linux 3.13.0-26-generic x86_64
NonfreeKernelModules: hid_generic psmouse usbhid hid r8169 mii
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 14 12:44:27 2014
InstallationDate: Installed on 2014-05-14 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
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: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FH
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S2P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFH:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

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

Bug description:
  sund card not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  NonfreeKernelModules: hid_generic psmouse usbhid hid r8169 mii
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 14 12:44:27 2014
  InstallationDate: Installed on 2014-05-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFH:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1319351] [NEW] Home Care Program - Sensitive Skin

2014-05-14 Thread Beatrice Bee

Public bug reported:

With Susceptible cutis, the skins obstruction is ofttimes broken, allowing 
essential moisture to negligence and irritants to understand the pare feat 
painful, symptom and irritation. All rind types can be stirred, but is many 
commonly initiate in those with dry peel.
Examples of sensitised pare permit - Sun Defect, Interlace Consume, Chemical 
Exhaust and strip that may possess had a response.
Morning  Evening Performance 
Groom. We neaten the strip to effectively disappear piss up, opencut grime and 
trash. This enables for a exceed onrush of products to ensue. Hold cleanser to 
deaden rind, transform into the tegument using flyer motions and disappear with 
facility  sponges.
* Ultra Soothing Cleanser 
Cover. (Period and/or Daylight)Unremarkably masking is misused to barf 
impurities from the wound and increase hydration levels, still, for sensitised 
tegument our end is to throttle rubor, irritation and inflammation so in this 
circumstance we relate the mask after the neaten. Deal to the tackling, cervix 
and decollette for 10 - 20 minutes and disappear using warm food.
* Ultra Soothing Meliorate Mask 
Interval. We delivery the tegument to disappear opencut oils and dust, leaving 
the wound cleansed, flaccid and advisable prepared for the usage and perception 
of handling products.Pertain by dispersion the skin lightly all over and stain 
dry.
* Ultra Soothing Toner
Management. Apply any recommended speciality humour. Our discourse products are 
designed to direct your specialized rind attention concerns / conditions. 
Dispense 1-2 shoe to the present, neck and decollette. These products are rapt 
quick in to the skin facultative the moisturiser to originate immediately.
* Qualifier Aid Serum for sensitised strip requiring straightaway embossment 
and shelter against boost sentience.
* Vitamin K Better Humor for capillaries, Acne, redness or bruising  after 
laser or surgery.
* Simple Firming Humour for pare requiring much of an anti old benefit.
* Environmental Cutis Restore for injure that has been unprotected to sun and 
curve.
MOISTURISE. Hold the advisable moisturiser. Moisturising locks wetness and any 
handling products in to the skin exploding hydration levels and protecting the 
skins barrier. Distribute to the confronting, pet and decollette and gently 
massage in to the strip.
* Maximum Roadblock Improve Toiletries for real dry and dry peel.
* Soothing Barrier Mend Ointment for normal/combination rind
http://trynaturalphytoceramides.com/
* Oil People Obstacle Improve Withdraw for oleaginous and really soiled wound
PROTECT. (Morning Exclusive) It is mode that you use a white sunblock every day 
to protect the skin from the uncomfortable and senescent personalty of UV rays. 
Use a tiny assets of cream to the play, pet and decollette on top of the 
moisturiser. FACT -50% of the UVA rays (Senescent rays) can fathom through 
darken, furnish and aggregation. This is why ointment is significant all 
assemblage say.
* SPF 30 Nociceptive Strip Cream

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

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

Title:
  Home Care Program - Sensitive Skin

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

Bug description:
  With Susceptible cutis, the skins obstruction is ofttimes broken, allowing 
essential moisture to negligence and irritants to understand the pare feat 
painful, symptom and irritation. All rind types can be stirred, but is many 
commonly initiate in those with dry peel.
  Examples of sensitised pare permit - Sun Defect, Interlace Consume, Chemical 
Exhaust and strip that may possess had a response.
  Morning  Evening Performance 
  Groom. We neaten the strip to effectively disappear piss up, opencut grime 
and trash. This enables for a exceed onrush of products to ensue. Hold cleanser 
to deaden rind, transform into the tegument using flyer motions and disappear 
with facility  sponges.
  * Ultra Soothing Cleanser 
  Cover. (Period and/or Daylight)Unremarkably masking is misused to barf 
impurities from the wound and increase hydration levels, still, for sensitised 
tegument our end is to throttle rubor, irritation and inflammation so in this 
circumstance we relate the mask after the neaten. Deal to the tackling, cervix 
and decollette for 10 - 20 minutes and disappear using warm food.
  * Ultra Soothing Meliorate Mask 
  Interval. We delivery the tegument to disappear opencut oils and dust, 
leaving the wound cleansed, flaccid and advisable prepared for the usage and 
perception of handling products.Pertain by dispersion the skin lightly all over 
and stain dry.
  * Ultra Soothing Toner
  Management. Apply any recommended speciality humour. Our discourse products 
are designed to direct your specialized rind attention concerns / conditions. 
Dispense 1-2 shoe to the

[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

2014-05-14 Thread Matthias Niess

This also happens when there is only one keyboard layout installed. It
still randomly switches to en_us. This shouldn't be classified as low
importance since it is a major problem, especially in corporate
environments. I have this happening on dozens of machines and have lots
of annoyed users who have to use the workaround of switching layouts
forth and back on a daily basis.

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

Title:
  Keyboard layout changing randomly

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

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  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
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

another hmmm from the X.org log:


[   726.531] (II) LoadModule: nvidia
[   726.532] (WW) Warning, couldn't open module nvidia
[   726.532] (II) UnloadModule: nvidia
[   726.532] (II) Unloading nvidia
[   726.532] (EE) Failed to load module nvidia (module does not exist, 0)
[   726.532] (II) LoadModule: nouveau
[   726.532] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[   726.532] (II) Module nouveau: vendor=X.Org Foundation
[   726.532]compiled for 1.15.0, module version = 1.0.10
[   726.532]Module class: X.Org Video Driver
[   726.532]ABI class: X.Org Video Driver, version 15.0



Hamish

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

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

Bug description:
  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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/1310023/+subscriptions

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

[sorry for the flurry of speparate posts]

$ dpkg -l | grep nvidia
ii  nvidia-304 304.116-0ubuntu0.0.1 
   NVIDIA binary Xorg driver, kernel module and VDPAU library
ii  nvidia-common  1:0.2.44.2   
   Find obsolete NVIDIA drivers
ii  nvidia-current 304.116-0ubuntu0.0.1 
   Transitional package for nvidia-current
ii  nvidia-settings331.20-0ubuntu0.0.1  
   Tool for configuring the NVIDIA graphics driver
ii  nvidia-settings-304331.20-0ubuntu0.0.1  
   Transitional package for nvidia-settings

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

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

Bug description:
  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  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/1310023/+subscriptions

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

[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

2014-05-14 Thread JockeTF

As a programmer, this is a very frustrating issue for me as well.
Punctuation, brackets and other such characters are located in very
different positions on sv_SE compared to en_US.

My keyboard layout always changes to en_US when GNOME Shell is
restarted. Never on the initial startup though. The following command
solves the issue temporarily for me:

gsettings set org.gnome.desktop.input-sources current 0

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

Title:
  Keyboard layout changing randomly

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

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  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
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1312159] Re: (gksu:xxxx): CRITICAL : fcntl error

György Szokolai, did this problem not occur in a release prior to
Trusty?

** Changed in: gksu (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Incomplete

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1312159] Re: (gksu:xxxx): CRITICAL : fcntl error

Mathias Burén, please do not apport-collect to another person's report. 
Instead, so your hardware and problem may be tracked, could you please file a 
new report with Ubuntu by executing the following in a terminal while booted 
into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags removed: apport-collected precise

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1312159/+attachment/4112210/+files/Dependencies.txt

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1312159/+attachment/4112207/+files/Dependencies.txt

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

Title:
  ** (gksu:): CRITICAL **: fcntl error

Status in “gksu” package in Ubuntu:
  Incomplete

Bug description:
  I chaneged my system from 13.10 to 14.04 by clean install. I got
  kerneloops on 14.04 beta 2 so I went back to 13.10.

  To try to new kernel on 14.04 I installed it yesterday. After the
  clean install and run updates my first task was to modify the grub and
  fstab. I'm using for it the gksu gedit command. Now I got error
  message and gedit not opened. For example:

  barricade@Barricade:~$ gksu gedit /etc/fstab

  (gksu:4983): Gtk-WARNING **: Failed to set text from markup due to
  error parsing markup: Error on line 1 char 86: Element 'b' was closed,
  but the currently open element is 'big'

  ** (gksu:4983): CRITICAL **: fcntl error

  ** (gksu:4983): WARNING **: Lock taken by pid: -1. Exiting.

  We talked about it on hungarian ubuntu forum and got same message from
  gksu other user too. I tryed to purge and reinstall the gksu but it
  not solved the problem. The sudo nano /etc/fstab and sudo gedit
  /etc/fstab commands working well.

  I tryed reinstall all system but the gksu problem is occured again.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1319149] Re: [HP Pavilion 11-n038ca x360 PC] HP Pavillion x360 boots very unreliably

Rick Spencer, thank you for reporting this and helping make Ubuntu better. As 
per 
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4158lc=encc=usdlc=ensw_lang=product=6846607#N1394
 an update to your BIOS is available (F.06). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Thank you for your understanding.

** Summary changed:

- HP Pavillion x360 boots very unreliably
+ [HP Pavilion 11-n038ca x360 PC] HP Pavillion x360 boots very unreliably

** Summary changed:

- [HP Pavilion 11-n038ca x360 PC] HP Pavillion x360 boots very unreliably
+ [HP Pavilion 11-n038ca x360 PC] Boots very unreliably

** Description changed:

- and the touch screen doesn't work
+ Boots very unreliably.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rick   1911 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rick   1911 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 13 14:47:04 2014
  HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
-  Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
+  Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-24-generic N/A
-  linux-backports-modules-3.13.0-24-generic  N/A
-  linux-firmware 1.127.2
+  linux-restricted-modules-3.13.0-24-generic N/A
+  linux-backports-modules-3.13.0-24-generic  N/A
+  linux-firmware 1.127.2
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097512405F00010420180
  dmi.sys.vendor: Hewlett-Packard

** Tags added: bios-outdated-f.06

** No longer affects: xorg (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

** Tags added: needs-boot-debug

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

Title:
  [HP Pavilion 11-n038ca x360 PC] Boots very unreliably

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Boots very unreliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick   1911 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 13 14:47:04 2014
  HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08
  InstallationDate: Installed

[Desktop-packages] [Bug 1302393] Re: gvfsd-metadata freez and load IO

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

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

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

Title:
  gvfsd-metadata freez and load IO

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes in a week I see blinking IO-indicator on my PC. Look iotop
  and see that gvfsd-metadata write something on disk while jbd2 load IO
  up to 100%

  Earlier I wait for some minutes than use killall gvfsd-metada. And now
  use killall immediately after see that my PC start work slowly and
  check iotop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.19.90-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 17:33:39 2014
  InstallationDate: Installed on 2014-01-20 (74 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1319351] Re: Home Care Program - Sensitive Skin

2014-05-14 Thread Raymond

** Changed in: alsa-driver (Ubuntu)
   Status: New = Invalid

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

Title:
  Home Care Program - Sensitive Skin

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

Bug description:
  With Susceptible cutis, the skins obstruction is ofttimes broken, allowing 
essential moisture to negligence and irritants to understand the pare feat 
painful, symptom and irritation. All rind types can be stirred, but is many 
commonly initiate in those with dry peel.
  Examples of sensitised pare permit - Sun Defect, Interlace Consume, Chemical 
Exhaust and strip that may possess had a response.
  Morning  Evening Performance 
  Groom. We neaten the strip to effectively disappear piss up, opencut grime 
and trash. This enables for a exceed onrush of products to ensue. Hold cleanser 
to deaden rind, transform into the tegument using flyer motions and disappear 
with facility  sponges.
  * Ultra Soothing Cleanser 
  Cover. (Period and/or Daylight)Unremarkably masking is misused to barf 
impurities from the wound and increase hydration levels, still, for sensitised 
tegument our end is to throttle rubor, irritation and inflammation so in this 
circumstance we relate the mask after the neaten. Deal to the tackling, cervix 
and decollette for 10 - 20 minutes and disappear using warm food.
  * Ultra Soothing Meliorate Mask 
  Interval. We delivery the tegument to disappear opencut oils and dust, 
leaving the wound cleansed, flaccid and advisable prepared for the usage and 
perception of handling products.Pertain by dispersion the skin lightly all over 
and stain dry.
  * Ultra Soothing Toner
  Management. Apply any recommended speciality humour. Our discourse products 
are designed to direct your specialized rind attention concerns / conditions. 
Dispense 1-2 shoe to the present, neck and decollette. These products are rapt 
quick in to the skin facultative the moisturiser to originate immediately.
  * Qualifier Aid Serum for sensitised strip requiring straightaway embossment 
and shelter against boost sentience.
  * Vitamin K Better Humor for capillaries, Acne, redness or bruising  after 
laser or surgery.
  * Simple Firming Humour for pare requiring much of an anti old benefit.
  * Environmental Cutis Restore for injure that has been unprotected to sun and 
curve.
  MOISTURISE. Hold the advisable moisturiser. Moisturising locks wetness and 
any handling products in to the skin exploding hydration levels and protecting 
the skins barrier. Distribute to the confronting, pet and decollette and gently 
massage in to the strip.
  * Maximum Roadblock Improve Toiletries for real dry and dry peel.
  * Soothing Barrier Mend Ointment for normal/combination rind
  http://trynaturalphytoceramides.com/
  * Oil People Obstacle Improve Withdraw for oleaginous and really soiled wound
  PROTECT. (Morning Exclusive) It is mode that you use a white sunblock every 
day to protect the skin from the uncomfortable and senescent personalty of UV 
rays. Use a tiny assets of cream to the play, pet and decollette on top of the 
moisturiser. FACT -50% of the UVA rays (Senescent rays) can fathom through 
darken, furnish and aggregation. This is why ointment is significant all 
assemblage say.
  * SPF 30 Nociceptive Strip Cream

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

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

[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories

2014-05-14 Thread Uqbar

Temporary fix:

sudo apt-get purge nautilus

Be warned, the above command will purge (thus remove completely) the nautilus 
file browser from your system.
If you, like me, are running KDE, then dolphin will do.

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

Title:
  Under KDE firefox uses nautilus instead of dolphin to handle
  directories

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  1. Run firefox under kde
  2. Download a file with it
  3. Click the download icon
  4. Right click on the download object
  5. Ask to open the containing folder

  I would expect the KDE file browser dolphin to open.

  What instead happens the GNOME file browser nautilus is opened
  without the needed icons. (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
   /dev/snd/controlC0:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu Apr 24 13:43:20 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-04-23 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  IpRoute:
   default via 192.168.254.254 dev eth0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.254.0/24 dev eth0  proto kernel  scope link  src 192.168.254.42  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.01
  dmi.board.asset.tag: CZC3523T17
  dmi.board.name: 18EB
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3523T17
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 490 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1293481] Re: asp.net 4.0 with apache does not seem to work on trusty

2014-05-14 Thread Peder Chr . Nørgaard

Zachary, shahid, thanks for your help.

The bug is truly easy to fix in the distribution:   Just change line 83
in the source file debian/mono-server4-update to use 4.5 instead of 4.0.
So now

Zachary, the problem you mention with the module installs - I have had
them, too (and also in ealier Ubuntu distros) but as the problem belongs
to a different source package (mod_mono), we should not discuss them
here.  I may write a report on that problem myself one day.

I attach a patch - almost an overkill - but maybe that will prompt
someone to verify the problem and solution and actually work the fix
into the distribution.

** Attachment added: xsp_patch
   
https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481/+attachment/4112221/+files/xsp_patch

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

Title:
  asp.net 4.0 with apache does not seem to work on trusty

Status in “xsp” package in Ubuntu:
  Confirmed

Bug description:
  This is a sister-bug to #1292567 which reports a similar problem with
  asp.net 2.0.  I have created two different reports, because the faults
  manifests themselves very differently, depending on the asp.net
  version.

  I have created an extremely small ASP.NET application (attached as a
  tar file).

  When I run that against the apache server on saucy salamander, using
  mono-server4, it runs just fine.

  When I run it against the apache server on the current beta of trusty
  tahr, using mono-server4, the mono-server4 dies with a SIGABRT.  The
  client gets a 500 error and the mono process running
  /usr/lib/mono/4.5/mod-mono-server4.exe disappears from the system.

  Luckily there is a good description in the apache error log:

  Stacktrace:

at unknown 0x
at Mono.WebServer.VPathToHost.CreateHost 
(Mono.WebServer.ApplicationServer,Mono.WebServer.WebSource) 0x0007b
at Mono.WebServer.ApplicationServer.GetApplicationForPath 
(string,int,string,bool) 0x0013f
at (wrapper remoting-invoke-with-check) 
Mono.WebServer.ApplicationServer.GetApplicationForPath (string,int,string,bool) 
0x
at Mono.WebServer.ModMonoWorker.InnerRun (object) 0x0024f
at Mono.WebServer.ModMonoWorker.Run (object) 0x0001b
at (wrapper runtime-invoke) Module.runtime_invoke_void__this___object 
(object,intptr,intptr,intptr) 0x

  Native stacktrace:

  /usr/bin/mono() [0x8105b4a]
  [0xb77bb40c]
  [0xb77bb424]
  /lib/i386-linux-gnu/libc.so.6(gsignal+0x46) [0xb75ba7e6]
  /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb75bdc33]
  /usr/bin/mono() [0x8288b23]
  /usr/bin/mono() [0x8288bb3]
  /usr/bin/mono() [0x816b4d1]
  /usr/bin/mono(mono_class_get_full+0xff) [0x816bdff]
  /usr/bin/mono(mono_class_from_name+0x107) [0x816c237]
  /usr/bin/mono(mono_class_from_typeref+0x190) [0x816b9a0]
  /usr/bin/mono(mono_class_get_full+0x164) [0x816be64]
  /usr/bin/mono(mono_class_get+0x1f) [0x816bf4f]
  /usr/bin/mono(mono_metadata_parse_mh_full+0x45c) [0x81b29fc]
  /usr/bin/mono(mono_method_get_header+0xbf) [0x819130f]
  /usr/bin/mono() [0x807ff7c]
  /usr/bin/mono() [0x8066ccc]
  /usr/bin/mono() [0x8068de4]
  /usr/bin/mono() [0x8069aee]
  /usr/bin/mono() [0x8106d17]
  [0xb757903e]
  [0xb5816970]
  [0xb58167fc]
  [0xb5812aa8]
  [0xb58126c4]
  [0xb7466c9d]
  /usr/bin/mono() [0x8069bf0]

  Debug info from gdb:

  
  =
  Got a SIGABRT while executing native code. This usually indicates
  a fatal error in the mono runtime or one of the native libraries 
  used by your application.
  =

  So, as you see, the SIGABRT occurs in a basic mono runtime routine called 
from the mod-mono-server4.exe
  module.  Of course, I cannot know whether the bug that causes the abortion is 
in xsp or in basic mono.  But 
  any search after the bug would start in mod-mono-server4, so I chose to file 
the bug against that package.

  I have the same bug on my company's larger ASP.NET application.

  This report is not made from the trusty installation, that one is a
  test installation without access to the net, so you don't get all the
  stuff that apport would collect to you. Honestly, you don't need it to
  reproduce, just grab a pristine trusty installation and try it!

  However, a few important package versions:

  libapache2-mod-mono: 2.11+git20130708.6b73e85-4ubuntu1
  mono-complete: 3.2.8+dfsg-4ubuntu1
  mono-apache-server2: 3.0.11-1

  I am willing to offer any possible kind of assistance in fixing this
  problem - my company had looked forward to upgrade to trusty. But,
  to be honest, I don't think you really need my help - the problem is
  so trivial

[Desktop-packages] [Bug 1319364] [NEW] Replace ADTRESULTSDIR by ADT_ARTIFACTS in autopkgtest testsuite in Utopic

2014-05-14 Thread Jean-Baptiste Lallement

Public bug reported:

The new version of autopkgtest in Utopic now officially uses the
variable ADT_ARTIFACTS as the location to collect test artifacts from
the testbed.

Firefox testsuite (next and security PPAs) in Utopic must be updated to
push xml test result files to $ADT_ARTIFACTS in order to publish test
results to Jenkins.

The following files must be updated:
firefox-30.0~b2+build1⟫ grep -r ADTRESULT debian/tests/
debian/tests/mochitest-2:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-5:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/xpcshell-package-tests:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/reftest:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/post-process:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-ipcplugins:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-1:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-a11y:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/xpcshell-tests:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/crashtest:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-browser:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-chrome:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-4:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/mochitest-3:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}
debian/tests/jstestbrowser:TESTRESULTS_DIR=${ADTRESULTSDIR:-/tmp/testresults}

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 29.0+build1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  j-lallement   2588 F pulseaudio
 /dev/snd/controlC0:  j-lallement   2588 F pulseaudio
BuildID: 20140428193813
Channel: Unavailable
CurrentDesktop: Unity
Date: Wed May 14 13:55:26 2014
DefaultProfileBrokenPermissions:
 
extensions/{9A2DA8C0-A778-4438-A892-D5CCEFC7BB85}/chrome/searchpluginshacks.jar 
(0o400)
 extensions/{9A2DA8C0-A778-4438-A892-D5CCEFC7BB85}/install.rdf (0o400)
DefaultProfileIncompatibleExtensions:
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Français Language Pack - langpack...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefSources:
 prefs.js
 user.js
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-09-03 (252 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902)
MostRecentCrashID: bp-6543633a-0798-4778-b0d1-c45702140422
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 (Default) - LastVersion=29.0/20140428193813 (In use)
 Profile1 - LastVersion=9.0/20111209134226 (Out of date)
RelatedPackageVersions:
 rhythmbox-mozilla 3.0.2-0ubuntu2
 totem-mozilla 3.10.1-1ubuntu5
 google-talkplugin 5.3.1.0-1
 garmin-plugin 0.3.20-1ubuntu1
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
 bp-6543633a-0798-4778-b0d1-c45702140422
 bp-dac087a0-fc10-4155-a024-e41542130405
 bp-3653253b-69dd-4200-86c9-51cef2130108
 bp-0676fc98-8f9c-4668-9bd7-005582121003
 bp-3ea89d3c-bac2-44e3-995f-01eca2120814
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug utopic

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

Title:
  Replace ADTRESULTSDIR by ADT_ARTIFACTS in autopkgtest testsuite in
  Utopic

Status in “firefox” package in Ubuntu:
  New

Bug description:
  The new version of autopkgtest

[Desktop-packages] [Bug 1261060] Re: sometime empathy chat dialogs open empty/with a negative unread count

2014-05-14 Thread Bug Watch Updater

** Changed in: empathy
   Status: Confirmed = Fix Released

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

Title:
  sometime empathy chat dialogs open empty/with a negative unread count

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “empathy” source package in Trusty:
  Fix Released

Bug description:
  * Impact:
  sometime messages are not displayed when opening the chat view after 
receiving one

  * Test Case:
  - open the empathy contact list
  - select the contact that is going to send you a message
  - clear the history
  - send the message
  - open it by clicking the buddy list entry

  - the message should be listed in the chat view

  * Regression potential:
  check that messages are correctly listed in chat view, in correct order and 
the scrolling is done correct when adding new ones

  

  Whenever i get a message in empathy (google talk account) and i open
  the message via the blue indicator symbol, only an empty window opens,
  swallowing the message, with title (-X unread)

  See screenshot:
  https://dl.dropboxusercontent.com/u/27087995/ubuntubugs/unread.png

  desired behaviour:
  have the message appear in the window

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-messages 13.10.1+13.10.20131011-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Dec 15 02:02:26 2013
  InstallationDate: Installed on 2013-12-13 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1293481] Re: asp.net 4.0 with apache does not seem to work on trusty

2014-05-14 Thread Ubuntu Foundations Team Bug Bot

The attachment xsp_patch 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 xsp in Ubuntu.
https://bugs.launchpad.net/bugs/1293481

Title:
  asp.net 4.0 with apache does not seem to work on trusty

Status in “xsp” package in Ubuntu:
  Confirmed

Bug description:
  This is a sister-bug to #1292567 which reports a similar problem with
  asp.net 2.0.  I have created two different reports, because the faults
  manifests themselves very differently, depending on the asp.net
  version.

  I have created an extremely small ASP.NET application (attached as a
  tar file).

  When I run that against the apache server on saucy salamander, using
  mono-server4, it runs just fine.

  When I run it against the apache server on the current beta of trusty
  tahr, using mono-server4, the mono-server4 dies with a SIGABRT.  The
  client gets a 500 error and the mono process running
  /usr/lib/mono/4.5/mod-mono-server4.exe disappears from the system.

  Luckily there is a good description in the apache error log:

  Stacktrace:

at unknown 0x
at Mono.WebServer.VPathToHost.CreateHost 
(Mono.WebServer.ApplicationServer,Mono.WebServer.WebSource) 0x0007b
at Mono.WebServer.ApplicationServer.GetApplicationForPath 
(string,int,string,bool) 0x0013f
at (wrapper remoting-invoke-with-check) 
Mono.WebServer.ApplicationServer.GetApplicationForPath (string,int,string,bool) 
0x
at Mono.WebServer.ModMonoWorker.InnerRun (object) 0x0024f
at Mono.WebServer.ModMonoWorker.Run (object) 0x0001b
at (wrapper runtime-invoke) Module.runtime_invoke_void__this___object 
(object,intptr,intptr,intptr) 0x

  Native stacktrace:

  /usr/bin/mono() [0x8105b4a]
  [0xb77bb40c]
  [0xb77bb424]
  /lib/i386-linux-gnu/libc.so.6(gsignal+0x46) [0xb75ba7e6]
  /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb75bdc33]
  /usr/bin/mono() [0x8288b23]
  /usr/bin/mono() [0x8288bb3]
  /usr/bin/mono() [0x816b4d1]
  /usr/bin/mono(mono_class_get_full+0xff) [0x816bdff]
  /usr/bin/mono(mono_class_from_name+0x107) [0x816c237]
  /usr/bin/mono(mono_class_from_typeref+0x190) [0x816b9a0]
  /usr/bin/mono(mono_class_get_full+0x164) [0x816be64]
  /usr/bin/mono(mono_class_get+0x1f) [0x816bf4f]
  /usr/bin/mono(mono_metadata_parse_mh_full+0x45c) [0x81b29fc]
  /usr/bin/mono(mono_method_get_header+0xbf) [0x819130f]
  /usr/bin/mono() [0x807ff7c]
  /usr/bin/mono() [0x8066ccc]
  /usr/bin/mono() [0x8068de4]
  /usr/bin/mono() [0x8069aee]
  /usr/bin/mono() [0x8106d17]
  [0xb757903e]
  [0xb5816970]
  [0xb58167fc]
  [0xb5812aa8]
  [0xb58126c4]
  [0xb7466c9d]
  /usr/bin/mono() [0x8069bf0]

  Debug info from gdb:

  
  =
  Got a SIGABRT while executing native code. This usually indicates
  a fatal error in the mono runtime or one of the native libraries 
  used by your application.
  =

  So, as you see, the SIGABRT occurs in a basic mono runtime routine called 
from the mod-mono-server4.exe
  module.  Of course, I cannot know whether the bug that causes the abortion is 
in xsp or in basic mono.  But 
  any search after the bug would start in mod-mono-server4, so I chose to file 
the bug against that package.

  I have the same bug on my company's larger ASP.NET application.

  This report is not made from the trusty installation, that one is a
  test installation without access to the net, so you don't get all the
  stuff that apport would collect to you. Honestly, you don't need it to
  reproduce, just grab a pristine trusty installation and try it!

  However, a few important package versions:

  libapache2-mod-mono: 2.11+git20130708.6b73e85-4ubuntu1
  mono-complete: 3.2.8+dfsg-4ubuntu1
  mono-apache-server2: 3.0.11-1

  I am willing to offer any possible kind of assistance in fixing this
  problem - my company had looked forward to upgrade to trusty. But,
  to be honest, I don't think you really need my help - the problem is
  so trivial to reproduce, it ought to be pretty trivial to fix if you
  know the ropes.

  best regards

  Peder Chr. Nørgaard

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

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

[Desktop-packages] [Bug 1303079] Re: refresh rate value is not saved

2014-05-14 Thread Dylan

I have a very similar problem.  I change the update interval of the
system monitor, but when I closes the preferences dialog and then reopen
the update interval has been reset to 0.00.

gnome-system-monitor 3.8.2.1-2ubuntu1

Ubuntu 14.04

$ uname -a
Linux maxwelld-linux 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  refresh rate value is not saved

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

Bug description:
  
  When I change the values, closes the monitor and open again and the values 
returns to defaults.

  gnome-system-monitor version: 3.8.2.1-2ubuntu1

  Ubuntu 14.04 (Trusty)

  $ uname -a
  Linux alan-pc 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 07:01:54 UTC 2014 
i686 i686 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 1303079] Re: refresh rate value is not saved

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

Title:
  refresh rate value is not saved

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

Bug description:
  
  When I change the values, closes the monitor and open again and the values 
returns to defaults.

  gnome-system-monitor version: 3.8.2.1-2ubuntu1

  Ubuntu 14.04 (Trusty)

  $ uname -a
  Linux alan-pc 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 07:01:54 UTC 2014 
i686 i686 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 1319375] [NEW] BEAUTIFUL SKIN

2014-05-14 Thread Beatrice Bee

Public bug reported:

Skin is one of the introductory parts of the body to conduct problems
from toxins. The embody essentially sees the cutis as not as intrinsical
as another key organs similar the hunch and lungs. The body, unluckily,
diverts nutrients from the rind to the key organs to cell them as
sensible as realistic. This fact is problematical for the face and
texture of our peel because the rind relies totally on nutrients for its
eudaemonia --- which is a mirror for how our wound appears. Toxins blast
matter stores and when comfortable quantities are not addressable for
the entire embody, the rind suffers.

Outstanding causes of toxins which should be reduced or eliminated to
keep reasonable, rude force of nutrients are the following:

1. Ventilation
Probably the last toxin for levelheaded pare is breathing, because it seriously 
constricts murder vessels that venture smokers to screw a stained appearance. 
The nutrients can exclusive be delivered to the pare with a intelligent feat 
scheme, which is compromised by vaporization because it constricts circulation, 
stabbing off an decent furnish of the nutrients and gas needed. It's been 
conclusively shown that smokers in their 40's screw the duplicate amount of 
wrinkles as non-smokers who are 20 years senior. The Nagoya Metropolis Lincoln 
Examination School in Archipelago has demonstrated respiration increases levels 
in the embody of an enzyme that book to occurrence trailing collagen - which is 
the fabric that keeps the strip Beverage
Other toxin that causes student problems with rubicund peel is intoxicant in 
that it actually alters the form of red slaying cells that trammel the total of 
oxygen movement through the system. It, suchlike vapor, increases an enzyme 
that attacks collagen and, peculiarly, the snap of our injure. 

3. Accentuate
Single hormones are nonvoluntary by overflowing difficulty levels that wipe-out 
the B vitamins travel systems pauperism to create flourishing red murder cells. 
Say drives arid looking cutis because of the demand of competent vitamin B. 

4. Sun
The factual cyanogenic foe when it comes to our skin is the sun. Dermatologists 
bonk presented a orientation that if we didn't endanger our injure to the sun, 
wrinkles would not materialize course until the 60's. The problem with sun is 
it allows tall levels of discharge radicals to be molded in the wound that 
assault the collagen and live fibers. Too some sunlight over moment thickens 
the stimulant layers of the skin, which make a soft, alter feigning. 

Detoxing your peel (and tomentum) against the quartet above issues is a thing 
of significantly reaction or actually eliminating these toxins. If it is 
ticklish or unconvincing that they can be significantly reduced, steps can be 
condemned to augment nutritional stores and use all-natural reward peel charge 
products to overcome the affect of toxins. A ample multi-vitamin paper, such as 
Utter Essentials for Women, can be obtained from IH System LLC and should be 
augmented with Assemblage Stuff Antioxidant. If unclean strip is verbalise, an 
oil-free cleaner, much as
Bio-Matte, is valuable. Balm candy, ivy, lavender, and mallow render soothing 
anti-inflammatory production and actually condition the cutis on lense. If 
toxins are constantly interpret, a set specified as Rejuvenating Elite, also 
usable from IH Arrangement LLC, testament make a better, younger quality with a 
patented mix of vitamin E and naturally occurring paraffin acids. The 
incomparable compounding of botanicals softens the see of lines and repairs and 
returns the wound to a median, moisture-rich refer. A opportune party, much as 
the uncomparable 
Thermal Correction Enzyme Mask, improves cutis texture, clarity, and strength. 
It's a spontaneous, unhazardous non-abrasive alternative to a harsh chemical 
pare. It gets beneath the articulator of the tegument to weightlifting and 
exfoliate without harming growing cells. 
http://trynaturalphytoceramides.com/

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

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

Title:
  BEAUTIFUL SKIN

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

Bug description:
  Skin is one of the introductory parts of the body to conduct problems
  from toxins. The embody essentially sees the cutis as not as
  intrinsical as another key organs similar the hunch and lungs. The
  body, unluckily, diverts nutrients from the rind to the key organs to
  cell them as sensible as realistic. This fact is problematical for the
  face and texture of our peel because the rind relies totally on
  nutrients for its eudaemonia --- which is a mirror for how our wound
  appears. Toxins blast matter stores and when comfortable quantities
  are not addressable for the entire embody, the rind suffers.

  Outstanding causes of

[Desktop-packages] [Bug 1269818] Re: impossible to turn off the bluetooth

2014-05-14 Thread Alex Barattini

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New = Invalid

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

Title:
  impossible to turn off the bluetooth

Status in “gnome-bluetooth” package in Ubuntu:
  Invalid

Bug description:
  Turning OFF the bluetooth in the control panel has no effect and if i
  return to the control panel after setting it OFF, I find it
  automatically set to ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-bluetooth 3.8.1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan 16 15:12:04 2014
  InstallationDate: Installed on 2013-12-14 (32 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1281588] Re: Disk standby timer is broken

2014-05-14 Thread Rocko

I confirm John Reid's patch to udisks2 allows my WDC WD40EZRX-00SPEB0 to
spindown into standby after 10 minutes (Ubuntu 14.04, udisks-
udisks2-2.1.3. The patch actually failed so I applied it manually).

But exactly at the 30 minute mark it spins back up into idle mode, even
though gnome-disks says that the last check was 30 minutes ago. So it
appears that polling _is_ in this case waking up the drive and I need to
do more than just assign a sane polling interval to udisks. Any idea why
this would be?

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

Title:
  Disk standby timer is broken

Status in “udisks2” package in Ubuntu:
  Triaged

Bug description:
  gnome-disk-utility's support for the drive standby timer is broken.
  Instead of issuing the STANDBY command to the drive, it issues the
  IDLE command.

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

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

[Desktop-packages] [Bug 1319149] Re: [HP Pavilion 11-n038ca x360 PC] Boots very unreliably

2014-05-14 Thread Joseph Salisbury

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

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

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

Title:
  [HP Pavilion 11-n038ca x360 PC] Boots very unreliably

Status in “linux” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  New

Bug description:
  Boots very unreliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick   1911 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 13 14:47:04 2014
  HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
   Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097512405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2014-05-14 Thread Thomas Lutz

After upgrading LTS from 12.04 to 14.04 I have the same issue.

I have a 4 monitor setup with 2 graphic cards. I tried a lot of
configruations / drivers,  but the only thing that worked was
completly uninstalling fglrx and connecting 3 monitors to 1 graphic
card.

Setup:
--
1x Radeon HD 6450
  -- 2x DVI  BenQ  GW2750
  -- 1x HDMI BenQ  GW2750

1x Radeon HD 6450
  -- 1x DVI  BenQ  GW2750


Result
-
Mouse Flicker on the 3 monitor system. No flicker on the 1 Monitor system.


Funny thing
---
When changing to gnome 3 or Xfce the flickering disapears - Unity Bug?


cat /etc/issue
--
Ubuntu 14.04 LTS

lspci | grep -i vga
---
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  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)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I Restore
  previous settings, after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1303874] Re: No GLX Rendering on old intel graphics

you can't install old packages on a newer distro, that's never supported

** Changed in: mesa (Ubuntu)
   Status: New = Invalid

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

Title:
  No GLX Rendering on old intel graphics

Status in “mesa” package in Ubuntu:
  Invalid

Bug description:
  Problem:
  glxinfo errors:
  Error: couldn't find RGB GLX visual or fbconfig
  Error: couldn't find RGB GLX visual or fbconfig

  inxi -Gx reports:
  Graphics:  Card: Intel 82865G Integrated Graphics Controller bus-ID: 00:02.0
     X.Org: 1.14.5 drivers: intel (unloaded: fbdev) FAILED: vesa 
Resolution: 1360x768@60.0hz
     GLX Renderer: N/A GLX Version: N/A Direct Rendering: N/A

  Workout:
  Due dependencies problems, you will first need to install the following 
packages:
  libllvm3.0 and  libdrm-nouveau1a (= 2.4.23), I did it this way:

  sudo apt-get install libllvm3.0
  wget 
http://launchpadlibrarian.net/160002667/libdrm-nouveau1a_2.4.46-1ubuntu0.0.1_i386.deb
  sudo dpkg -i libdrm-nouveau1a_2.4.46-1ubuntu0.0.1_i386.deb

  And then followed what rkmugen explains on
  url=http://forums.linuxmint.com/viewtopic.php?f=59t=120296#p665422,
  Linux Mint Forums:

  libgl1-mesa-dri_8.0.4-1ubuntu1_i386.deb
  libgl1-mesa-glx_8.0.4-1ubuntu1_i386.deb
  libglapi-mesa_8.0.4-1ubuntu1_i386.deb
  libglu1-mesa

  Opened up a terminal in the directory containing the 4 downloaded
  files then installed all of them using:

  sudo dpkg -i *.deb

  And now,
  inxi -Gx reports:
  Graphics:  Card: Intel 82865G Integrated Graphics Controller bus-ID: 00:02.0
     X.Org: 1.14.5 drivers: intel (unloaded: fbdev) FAILED: vesa 
Resolution: 1360x768@60.0hz
     GLX Renderer: Mesa DRI Intel 865G x86/MMX/SSE2 GLX Version: 1.3 
Mesa 8.0.4 Direct Rendering: Yes
  You should also install the same version of the libgles2-mesa package from 
https://launchpadlibrarian.net/111797533/libgles2-mesa_8.0.4-1ubuntu1_i386.deb

  Thanks all.
  The problem persist on Lubuntu 14.04 (20140406), the updated mesa packages 
somehow aren't working on this graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-dri 8.0.4-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Sun Apr  6 23:59:15 2014
  InstallationDate: Installed on 2014-04-05 (2 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 
(20131016.1)
  MarkForUpload: True
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1246013] Re: Whould be nice for libgl1-mesa-dev to be multiarched

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

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

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

Title:
  Would be nice for libgl1-mesa-dev to be multiarched

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  As per title.

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

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

[Desktop-packages] [Bug 949606] Re: 64 bit dev packages should include 32 bit .so library file

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

** This bug has been marked a duplicate of bug 1246013
   Whould be nice for libgl1-mesa-dev to be multiarched

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

Title:
  64 bit dev packages should include 32 bit .so library file

Status in “mesa” package in Ubuntu:
  Triaged

Bug description:
  64 bit dev packages contain a 64 bit version of the library file(s)
  that they provide for linking but not a 32 bit version of the library
  file(s). In previous versions of Ubuntu, however, it was possible to
  compile 32 bit applications using the 64 bit dev packages in by
  installing ia32-libs, which contained the required 32 bit library
  files.

  In the move to multiarch, 32 bit library files are being removed from
  ia32-libs. Multiarch (I assume) aims to keep the architectures
  separate, so the generally intended solution is to install the i386
  version of the dev package when compiling 32 bit applications, ie
  side-by-side with the 64 bit dev package.

  However, some 64 bit development packages conflict with their 32 bit
  equivalent. This creates a regressive situation where it is impossible
  to install them side-by-side - you are forced to either install the 32
  bit package, which breaks 64 bit compilations, or the 64 bit package,
  which breaks 32 bit compilations.

  An example is libglu1-mesa-dev, which conflicts with libglu1-mesa-
  dev:i386. The libglu1-mesa-dev file contains all the necessary
  development files for 32 bit *except* for the 32 bit library file. It
  does contain the 64 bit library file. Since the library file is part
  of the development files, libglu1-mesa-dev does not contain all the
  necessary development files for 32 bit, ie it does not contain all the
  necessary development files for multiarch. I think that it *should*
  contain all the necessary files for building multarch applications.

  The two workarounds are:

  1. Manually re-install the required i386 dev packages before compiling
  32 bit apps, and then manually re-install the required amd64 dev
  packages before compiling 64 bit apps. This is a real pain.

  2. Install the i386 binary package (eg libglu1-mesa:i386) and the
  amd64 dev package (eg libglu1-mesa-dev), and manually create symlinks
  for the i386 libXYZ.so package (eg sudo ln -s /usr/lib/i386-linux-
  gnu/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so). This is a more
  permanent solution but is a real pain to set up, as you have to find
  each missing library manually, and some library files, like
  mesa/libGL.so.1, are in subfolders.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libglu1-mesa-dev 8.0.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,resize,compiztoolbox,vpswitch,place,gnomecompat,move,regex,animation,imgpng,snap,mousepoll,session,expo,workarounds,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Mar  8 10:20:54 2012
  DistUpgraded: Log time: 2012-02-26 08:25:08.500725
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 4.1.8, 3.2.0-12-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-14-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-17-generic, x86_64: installed
   virtualbox-guest, 4.1.8, 3.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120201.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=630a9f76-6f8f-43be-bb99-6be721c9deaf ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: mesa
  UpgradeStatus: Upgraded to precise on 2012-02-26 (11 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2

[Desktop-packages] [Bug 1246013] Re: Would be nice for libgl1-mesa-dev to be multiarched

** Summary changed:

- Whould be nice for libgl1-mesa-dev to be multiarched
+ Would be nice for libgl1-mesa-dev to be multiarched

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

Title:
  Would be nice for libgl1-mesa-dev to be multiarched

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  As per title.

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

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

[Desktop-packages] [Bug 1214352] Re: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2014-05-14 Thread Andreas Heinlein

I can finally confirm that the patch from gnome bug 695925 above
actually fixes the problem with Ubuntu 12.04.4 and LO 4.2.4 from the
PPA. I have applied the patch to the glib source package and rebuilt and
installed it, and then rebuilt libreoffice, gtk+3.0, dbus-glib and gvfs
against the patched glib.

This now finally seems to work.

Unfortunately, this whole rebuilding is a PITA and takes a long time,
especially for libreoffice. I'm not sure if everything is needed, but
anyway I have a bad feeling with this. Now there are still lots of
packages on my system which were built against the unpatched glib, so I
really think this needs to be fixed in Ubuntu 12.04 with *ALL* packages
which depend on glib being rebuilt against a patched version.

How can we achieve this?

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

Title:
  GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The G Library - GLib:
  Fix Released
Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

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

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

[Desktop-packages] [Bug 1253620] Re: Can't open a LibreOffice native file via CIFS share

2014-05-14 Thread Andreas Heinlein

I finally found a solution by patching glib-2.0 and rebuilding
libreoffice, gvfs, dbus-glib and gtk-3.0 against it. This works. Now
this really needs to be fixed in Ubuntu by rebuilding *all* packages
depending on glib, I think. I added a comment to bug 1214352 and wrote
to canonical using the contact form from the URL you provided.

I really hope this gets fixed soon...

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

Title:
  Can't open a LibreOffice native file via CIFS share

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

Bug description:
  Problem description: 
  Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 
12.04 and LibreOffice 4.1.3.2 (from ppa).

  System informations:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04
  Codename: precise

  LibreOffice package from ppa:libreoffice/ppa: 
  1:4.1.3~rc2-0ubuntu1~precise1~ppa1

  Steps to reproduce:
  1. Open LibreOffice
  2. Select Open File from file menu
  3. Select the remote share folder
  4. Click to open the file

  Current behavior:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior:
  LibreOffice opens the remote file correctly.

  Alternatives steps:
  1. Open the remote path via Nautilus
  2. Double click on remote LibreOffice native files

  Current behavior2:
  LibreOffice trys to recover the remote file and fails.

  Expected behavior2:
  LibreOffice opens the remote file correctly.

  Notes: 
  * Remote and local MS files are opened correctly.
  * The problems with LibreOffice native files disappear if copying the remote 
files in a local path

  Here a workaround:
  sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' 
/usr/share/applications/libreoffice-*

  No problem present on:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  with LibreOffice:
  1:4.1.3~rc2-0ubuntu1~saucy1~ppa3

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

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

[Desktop-packages] [Bug 1319411] [NEW] Best Anti Aging Skin Care Products

2014-05-14 Thread Beatrice Bee

Public bug reported:

Wouldn't you equivalent to examine junior than you do alter now. I know you 
would bang to appear the way you undergo, teenage and vibrant. Get rid of the 
sagging pet, the dry splotched cutis, those age symptom, those wrinkles around 
your eyes and rima. You person probably been disagreeable vindicatory nearly 
every strip fixture creation that has been advertised on the activity, yet, 
these never springy up to their promises. It's instant to advantage living your 
lifetime with a bonnie, growing superficial injure.
Most of the injure help products on the market contains collagen and elastin, 
You see collagen and elastin are substances that testament better ameliorate 
your peel and alter it position to that young face and look. Collagen and 
elastin testament service rectify your skin to puddle it author lucent and 
steady toned. The difficulty is, applied topically, collagen does not output. 
The molecules in collagen are too ample, they cannot enter the injure. Yet 
there are substances which present naturally provide your embody to expose its 
own collagen and elastin. Can you individual create your embody to create its 
own fresh ply of collagen. I hump through a lot of research and possess 
recovered an anti ageing tegument charge reserves which uses Cynergy TK in its 
connecter products. Hence, you cognize with this method in a thing of months 
you can individual that youthful strip you bonk been dreaming around all these 
eld. If you don't believe me, do your own search, call any honourable 
technological website and do a seek and you testament be hip on how this nub 
activity.
I make finished my research and that is why I present not use any new opposed 
ageing tegument work fluid, because I realize that the exclusive way to a 
beauteous, rubicund, scrunch people skin is to gain a cutis mend fluid that 
uses Cynergy TK which will allot your injure to expose its own collagen and 
elastin.
Some your reasons for wanting a junior, more youthful perception pare, I urge 
you to consonant wasting your money on products that conscionable does not 
affect. They present never be competent to communicate on their promises. 
Transform a author informed consumer and purchase products that leave employ 
you the results you are salaried for.
http://trynaturalphytoceramides.com/

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

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

Title:
  Best Anti Aging Skin Care Products

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

Bug description:
  Wouldn't you equivalent to examine junior than you do alter now. I know you 
would bang to appear the way you undergo, teenage and vibrant. Get rid of the 
sagging pet, the dry splotched cutis, those age symptom, those wrinkles around 
your eyes and rima. You person probably been disagreeable vindicatory nearly 
every strip fixture creation that has been advertised on the activity, yet, 
these never springy up to their promises. It's instant to advantage living your 
lifetime with a bonnie, growing superficial injure.
  Most of the injure help products on the market contains collagen and elastin, 
You see collagen and elastin are substances that testament better ameliorate 
your peel and alter it position to that young face and look. Collagen and 
elastin testament service rectify your skin to puddle it author lucent and 
steady toned. The difficulty is, applied topically, collagen does not output. 
The molecules in collagen are too ample, they cannot enter the injure. Yet 
there are substances which present naturally provide your embody to expose its 
own collagen and elastin. Can you individual create your embody to create its 
own fresh ply of collagen. I hump through a lot of research and possess 
recovered an anti ageing tegument charge reserves which uses Cynergy TK in its 
connecter products. Hence, you cognize with this method in a thing of months 
you can individual that youthful strip you bonk been dreaming around all these 
eld. If you don't believe me, do your own search, call any honourable 
technological website and do a seek and you testament be hip on how this nub 
activity.
  I make finished my research and that is why I present not use any new opposed 
ageing tegument work fluid, because I realize that the exclusive way to a 
beauteous, rubicund, scrunch people skin is to gain a cutis mend fluid that 
uses Cynergy TK which will allot your injure to expose its own collagen and 
elastin.
  Some your reasons for wanting a junior, more youthful perception pare, I urge 
you to consonant wasting your money on products that conscionable does not 
affect. They present never be competent to communicate on their promises. 
Transform a author informed consumer and purchase products that leave employ 
you the results you are salaried for.

[Desktop-packages] [Bug 1319418] [NEW] Locking the screen over lxpanel results in an error

2014-05-14 Thread Sworddragon

Public bug reported:

I'm using lxde-common 0.5.0-4ubuntu4 and xscreensaver 5.26-1ubuntu1 and
after upgrading xscreensaver from version 5.15 to 5.26 I'm noticing that
locking over lxpanel does make some problems. Here is my panel entry:

Plugin {
type = launchbar
Config {
Button {
id=lxde-screenlock.desktop
}
Button {
id=lxde-logout.desktop
}
}
}


If I'm now clicking the id=lxde-screenlock.desktop button nothing happens for 
several seconds and then xscreensaver locks the screen but shows the error 
message couldn't grab pointer (AlreadyGrabbed) and mouse movements doesn't 
popup the input fields anymore (but the keyboard is still recognized). Using 
xscreensaver-command -lock manually works fine.

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

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

Title:
  Locking the screen over lxpanel results in an error

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  I'm using lxde-common 0.5.0-4ubuntu4 and xscreensaver 5.26-1ubuntu1
  and after upgrading xscreensaver from version 5.15 to 5.26 I'm
  noticing that locking over lxpanel does make some problems. Here is my
  panel entry:

  Plugin {
  type = launchbar
  Config {
  Button {
  id=lxde-screenlock.desktop
  }
  Button {
  id=lxde-logout.desktop
  }
  }
  }

  
  If I'm now clicking the id=lxde-screenlock.desktop button nothing happens 
for several seconds and then xscreensaver locks the screen but shows the error 
message couldn't grab pointer (AlreadyGrabbed) and mouse movements doesn't 
popup the input fields anymore (but the keyboard is still recognized). Using 
xscreensaver-command -lock manually works fine.

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

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

[Desktop-packages] [Bug 1319420] [NEW] Entering the wrong password causes some annoying behavior

2014-05-14 Thread Sworddragon

Public bug reported:

I'm using Ubuntu 14.10 dev with xscreensaver 5.26-1ubuntu1 and on
locking the screen and entering the wrong password xscreensaver shows in
the panel the message Authentication failed! while showing the buttons
New Login and OK. But these 2 buttons are useless as a mouseclick on
any position wil close the panel. Also if an empty password is entered
xscreensaver shows an error message out of the panel. Maybe this should
be kept more consistent with showing both error types outside or inside
the panel instead of mixing this.

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

** Description changed:

- I'm using xscreensaver 5.26-1ubuntu1 and on locking the screen and
- entering the wrong password xscreensaver shows in the panel the message
- Authentication failed! while showing the buttons New Login and OK.
- But these 2 buttons are useless as a mouseclick on any position wil
- close the panel. Also if an empty password is entered xscreensaver shows
- an error message out of the panel. Maybe this should be kept more
- consistent with showing both error types outside or inside the panel
- instead of mixing this.
+ I'm using Ubuntu 14.10 dev with xscreensaver 5.26-1ubuntu1 and on
+ locking the screen and entering the wrong password xscreensaver shows in
+ the panel the message Authentication failed! while showing the buttons
+ New Login and OK. But these 2 buttons are useless as a mouseclick on
+ any position wil close the panel. Also if an empty password is entered
+ xscreensaver shows an error message out of the panel. Maybe this should
+ be kept more consistent with showing both error types outside or inside
+ the panel instead of mixing this.

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

Title:
  Entering the wrong password causes some annoying behavior

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with xscreensaver 5.26-1ubuntu1 and on
  locking the screen and entering the wrong password xscreensaver shows
  in the panel the message Authentication failed! while showing the
  buttons New Login and OK. But these 2 buttons are useless as a
  mouseclick on any position wil close the panel. Also if an empty
  password is entered xscreensaver shows an error message out of the
  panel. Maybe this should be kept more consistent with showing both
  error types outside or inside the panel instead of mixing this.

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

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

[Desktop-packages] [Bug 1319418] Re: Locking the screen over lxpanel results in an error

2014-05-14 Thread Sworddragon

** Description changed:

- I'm using lxde-common 0.5.0-4ubuntu4 and xscreensaver 5.26-1ubuntu1 and
- after upgrading xscreensaver from version 5.15 to 5.26 I'm noticing that
- locking over lxpanel does make some problems. Here is my panel entry:
+ I'm using Ubuntu 14.10 dev with lxde-common 0.5.0-4ubuntu4 and
+ xscreensaver 5.26-1ubuntu1 and after upgrading xscreensaver from version
+ 5.15 to 5.26 I'm noticing that locking over lxpanel does make some
+ problems. Here is my panel entry:
  
  Plugin {
- type = launchbar
- Config {
- Button {
- id=lxde-screenlock.desktop
- }
- Button {
- id=lxde-logout.desktop
- }
- }
+ type = launchbar
+ Config {
+ Button {
+ id=lxde-screenlock.desktop
+ }
+ Button {
+ id=lxde-logout.desktop
+ }
+ }
  }
  
- 
- If I'm now clicking the id=lxde-screenlock.desktop button nothing happens 
for several seconds and then xscreensaver locks the screen but shows the error 
message couldn't grab pointer (AlreadyGrabbed) and mouse movements doesn't 
popup the input fields anymore (but the keyboard is still recognized). Using 
xscreensaver-command -lock manually works fine.
+ If I'm now clicking the id=lxde-screenlock.desktop button nothing
+ happens for several seconds and then xscreensaver locks the screen but
+ shows the error message couldn't grab pointer (AlreadyGrabbed) and
+ mouse movements doesn't popup the input fields anymore (but the keyboard
+ is still recognized). Using xscreensaver-command -lock manually works
+ fine.

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

Title:
  Locking the screen over lxpanel results in an error

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with lxde-common 0.5.0-4ubuntu4 and
  xscreensaver 5.26-1ubuntu1 and after upgrading xscreensaver from
  version 5.15 to 5.26 I'm noticing that locking over lxpanel does make
  some problems. Here is my panel entry:

  Plugin {
  type = launchbar
  Config {
  Button {
  id=lxde-screenlock.desktop
  }
  Button {
  id=lxde-logout.desktop
  }
  }
  }

  If I'm now clicking the id=lxde-screenlock.desktop button nothing
  happens for several seconds and then xscreensaver locks the screen but
  shows the error message couldn't grab pointer (AlreadyGrabbed) and
  mouse movements doesn't popup the input fields anymore (but the
  keyboard is still recognized). Using xscreensaver-command -lock
  manually works fine.

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

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

[Desktop-packages] [Bug 1310849] Re: Chromium not remembering all tabs and running slow

2014-05-14 Thread ggomez

I noticed that new version 34.0.1847.116 Ubuntu 14.04 aura (260972) updated 
today in my Ubuntu also lost some tabs on startup.
I have 23 open tabs.

Thanks
Gabriel

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

Title:
  Chromium not remembering all tabs and running slow

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

Bug description:
  I've installed Ubuntu 14.04 64 bit and Chromium 34.0.1847.116 Ubuntu
  14.04 aura (260972). I've noticed a few problems...

  1) Despite having the setting Continue where you left off checked,
  only some of the tabs are reopened when I start up Chromium. I
  typically have about 10 tabs open when I close Chromium so I can't see
  that being some limit - hasn't been a problem in the past.

  2) If I right click a link and open in a new window, that window can
  take up to a minute to load the page and once loaded, runs sluggishly
  (scrolling is slow or if a YouTube video, runs as though I've got poor
  bandwidth).

  I've removed Chromium (apt-get purge) and then also removed the
  directories ~/.cache/chromium and ~/.config/chromium and then did a
  reinstall of Chromium but to no avail. Interestingly after running
  what should be a clean Chromium, I hit CTRL + H and all my browser
  history was there...

  FWIW, I also tried changing video drivers - switching from Nouveau to
  Nvidia (all three versions which available to me) and the problem
  persists.

  I finally decided to reinstall 14.04 and the problem returns.

  I've got the pepper flash plugin installed so I don't know if that has
  something to do with this, although this is the first time I've
  (knowingly) installed this plugin. I've never had this problem on
  13.10 with Chromium and have had no problems with Firefox. I also have
  the webmail ad blocker plugin installed but that's never given me
  trouble in the past either.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 22 09:29:55 2014
  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/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-21T09:10:03.078925

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

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

[Desktop-packages] [Bug 1242678] Re: evince cannot render some EPS files

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

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

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

Title:
  evince cannot render some EPS files

Status in Evince document viewer:
  New
Status in GS-GPL  -  GPL Ghostscript:
  Unknown
Status in libspectre:
  Confirmed
Status in “evince” package in Ubuntu:
  Confirmed
Status in “ghostscript” package in Ubuntu:
  Invalid
Status in “gnuplot” package in Ubuntu:
  Invalid
Status in “libspectre” package in Ubuntu:
  Triaged
Status in “evince” source package in Trusty:
  Confirmed
Status in “ghostscript” source package in Trusty:
  Invalid
Status in “gnuplot” source package in Trusty:
  Invalid
Status in “libspectre” source package in Trusty:
  Triaged

Bug description:
  I upgraded to Ubuntu Saucy,
  evince cannot render EPS files generated by gnuplot.
  (Just show an empty page.)

  
  [how to reproduce]

  1. Generate an EPS file using gnuplot by executing the following command.
  $ gnuplot -e set terminal postscript; set output 'test.eps'; plot x;

  2. Open the file test.eps just created.
  $ evince test.eps

  The following are what evince writes to the terminal.

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

  (evince:24176): Gtk-WARNING **: drawing failure for widget `EvView':
  invalid matrix (not invertible)

  (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface:
  assertion 'width  0  height  0' failed

  (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface:
  assertion 'width  0  height  0' failed

  3. Then evince just shows an empty (white) page.

  ===

  If i rotate 90 or -90 degree by pressing Ctrl+Left or Ctrl+Right key,
  evince can show this file correctly.

  ===

  Okular, GIMP, inkscape and gs can show this EPS file.
  (may be rotated 90 degree, however)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 21:23:15 2013
  InstallationDate: Installed on 2013-09-07 (44 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to saucy on 2013-10-04 (16 days ago)

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

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

[Desktop-packages] [Bug 1242678] Re: evince cannot render some EPS files

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

** Changed in: evince (Ubuntu Trusty)
   Status: New = Confirmed

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

Title:
  evince cannot render some EPS files

Status in Evince document viewer:
  New
Status in GS-GPL  -  GPL Ghostscript:
  Unknown
Status in libspectre:
  Confirmed
Status in “evince” package in Ubuntu:
  Confirmed
Status in “ghostscript” package in Ubuntu:
  Invalid
Status in “gnuplot” package in Ubuntu:
  Invalid
Status in “libspectre” package in Ubuntu:
  Triaged
Status in “evince” source package in Trusty:
  Confirmed
Status in “ghostscript” source package in Trusty:
  Invalid
Status in “gnuplot” source package in Trusty:
  Invalid
Status in “libspectre” source package in Trusty:
  Triaged

Bug description:
  I upgraded to Ubuntu Saucy,
  evince cannot render EPS files generated by gnuplot.
  (Just show an empty page.)

  
  [how to reproduce]

  1. Generate an EPS file using gnuplot by executing the following command.
  $ gnuplot -e set terminal postscript; set output 'test.eps'; plot x;

  2. Open the file test.eps just created.
  $ evince test.eps

  The following are what evince writes to the terminal.

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

  (evince:24176): Gtk-WARNING **: drawing failure for widget `EvView':
  invalid matrix (not invertible)

  (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface:
  assertion 'width  0  height  0' failed

  (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface:
  assertion 'width  0  height  0' failed

  3. Then evince just shows an empty (white) page.

  ===

  If i rotate 90 or -90 degree by pressing Ctrl+Left or Ctrl+Right key,
  evince can show this file correctly.

  ===

  Okular, GIMP, inkscape and gs can show this EPS file.
  (may be rotated 90 degree, however)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 21:23:15 2013
  InstallationDate: Installed on 2013-09-07 (44 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to saucy on 2013-10-04 (16 days ago)

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

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

[Desktop-packages] [Bug 1317425] Re: compiz crash and window decorator disappear

2014-05-14 Thread Marc-Andre Heroux

After running the system with mostly: OpenGL (Fast), Desktop Cube,
Rotate Cube, Cube Reflection and Deformation, Woobly Windows and most of
the other standard options, I got another crash. This time, the Window
refreshed and I the decoration remain correct. Firefox became running
fullscreen. It crash when pressing Leafpad from the Unity bar, nothing
special.

Video card: i915

Here is the debugging information: http://pastebin.com/L1bEmNAK

Have a good one!

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

Title:
  compiz crash and window decorator disappear

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Many times everyday, compiz crashes and some applications become
  fullscreen (e.g.: leafpad, vmplayer, thunderbird especially). I cannot
  close those applications so I change desktop and kill the process of
  each. After, I go in .config and change config for thuderbird and
  remove for leafpad, because else, application start fullscreen the
  next time?

  Please find the debug.out information here:

  http://pastebin.com/L5bnVHzv
  http://pastebin.com/Q3Vri4ug
  http://pastebin.com/ppiJZdqq

  Regards,
  Marc-Andre!

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

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

[Desktop-packages] [Bug 1318589] Re: [BDW] fix various GPU hang issues