[Desktop-packages] [Bug 1284466] Re: [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all

2014-03-21 Thread Raymond
if node 0a  alway  plugged and node 0x0f (headphone at center) always
unplugged

you have to find out whether the mute is controlled by gpio

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

Title:
  [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all

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

Bug description:
  For a few years sound did not work on this laptop. Sometime during the
  13.10 release cycle the problem was fixed in the kernel. Now in the
  14.04 after a kernel update sound no longer works. I'm not 100% sure
  which kernel update broke sound. I will try to install some of the
  older kernels and track it down.

  Alsa and PulseAudio both show that the sound is turned all the way up,
  but no sound plays and the sound tests fail to make any noise too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  3312 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Feb 25 01:01:28 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1907 F pulseaudio
david  3312 F pulseaudio
   /dev/snd/seq:timidity   1585 F timidity
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (58 days ago)
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0DT492
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0DT492:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1294515] Re: FFE: new upstream version to support touchpads on newer Lenovo models

2014-03-21 Thread Timo Aaltonen
** Changed in: libevdev (Ubuntu)
   Status: New = Fix Released

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

Title:
  FFE: new upstream version to support touchpads on newer Lenovo models

Status in “libevdev” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  Upstream has released -synaptics 1.7.99.1:

  A snapshot of what will be synaptics 1.8. There are a couple of significant
  changes in here:

  libevdev support:
The evdev backend on Linux now uses libevdev. We recommend to use libevdev
1.1-rc1 or later as the synaptics driver is very likely to trigger
SYN_DROPPED and we've fixed a bunch of issues in libevdev 1.1.

  Support for T440, T540, X240, Helix, Yoga:
The bulk of the changes is to support this set of Lenovo touchpads. These
touchpads don't have separate physical buttons for the trackstick and need
to be emulated as software-button by the driver.

  TouchpadOff behaviour change:
Synaptics has a property Synaptics Off to disable events. Previously,
this disabled any event from the touchpad. Now, physical button clicks are
allowed even when the touchpad is disabled.

  mtdev was dropped:
There are no touchpad drivers in the kernel tree that use protocol A, so
using mtdev is just a computationally expensiv and memory-wasting noop.

  this needs a newer libevdev too.

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

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


[Desktop-packages] [Bug 1290611] Re: [Clevo W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] crackling sound and audio up a note

2014-03-21 Thread Raymond
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/hda_eld.c?id=acdda7915eb5dae20b6e43b8b772b712b1ed32c3


Allow users to fix quicks of ELD ROMs by writing new values to the ELD proc 
interface. The format is one or more lines of name hex_value. Users can 
add/remove/modify up to 32 SAD(Short Audio Descriptor) entries.

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

Title:
  [Clevo W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] crackling
  sound and audio up a note

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

Bug description:
  installed pavucontrol to get the sound from HDMI but the result is
  crackle sound and audio is up a note.

  This problem exists on 13.10 and 14.04 not on 13.04. I noticed the

  
  alsa info from 13.4 shows the soundcard: 
  00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)
  00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio 
Controller (rev 05)

  while from 14.04
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 10 23:55:20 2014
  InstallationDate: Installed on 2014-03-04 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140302)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RTO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RTO:bd12/05/2013:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1295526] [NEW] disable touchpad while typing doesn't work

2014-03-21 Thread Lex Ross
Public bug reported:

Disable touchpad while typing checkbox in System Settings does not
work on my Asus F5N laptop. The button to disable touchpad does not work
as well. As a workaround I use syndaemon -i 1 -K -d command as per
Ubuntu help page https://help.ubuntu.com/community/SynapticsTouchpad/
but it does not fix the issue with the said chechbox and hardware
button. I guess it still needs to access shared memory using SHMconfig
option in xorg.conf in which case it is the same bug that has been
around for 3 years starting from Ubuntu 11.10

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-input-synaptics 1.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 21 10:10:18 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
MachineType: ASUSTeK Computer Inc. F5N
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-6-generic 
root=UUID=f239c25a-4c5d-4e97-a6e7-befdcc142599 ro quiet splash 
enable_mtrr_cleanup elevator=noop
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F5N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd04/08/2008:svnASUSTeKComputerInc.:pnF5N:pvr1.0:rvnASUSTeKComputerInc.:rnF5N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F5N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.11+14.04.20140310-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~rc3-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
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-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: Tue Mar 18 22:35:44 2014
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.0-1ubuntu6

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  disable touchpad while typing doesn't work

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  Disable touchpad while typing checkbox in System Settings does not
  work on my Asus F5N laptop. The button to disable touchpad does not
  work as well. As a workaround I use syndaemon -i 1 -K -d command as
  per Ubuntu help page
  https://help.ubuntu.com/community/SynapticsTouchpad/ but it does not
  fix the issue with the said chechbox and hardware button. I guess it
  still needs to access shared memory using SHMconfig option in
  xorg.conf in which case it is the same bug that has been around for 3
  years starting from Ubuntu 11.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-input-synaptics 1.7.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 10:10:18 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  MachineType: ASUSTeK Computer Inc. F5N
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-6-generic 
root=UUID=f239c25a-4c5d-4e97-a6e7-befdcc142599 ro quiet splash 
enable_mtrr_cleanup elevator=noop
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F5N
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd04/08/2008:svnASUSTeKComputerInc.:pnF5N:pvr1.0:rvnASUSTeKComputerInc.:rnF5N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  

[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Chris
All I have no idea what was the update last two days now running the
gdk-pixbuf-query-loaders come back with segmentation fault.

All my gnome based WM can not be used any more. Vmware also failed to
start due to failed to support the png file type.

PLEASE HELP!!

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1292438] Re: BETA 14.04 cant connect to PulseAudio server

2014-03-21 Thread Paul Konecny
I tihink, I've got the same problem.

Was running Kubuntu 14.04 as of 19th March 2014 and everything worked perfectly.
I then installed audacity to record something but it would only show the Splash 
screen and hang there. 

After that every program trying to access the soundcard would hang. Even
after several reboots.  KDE then said Sound Device unavailable,
switching to Default.  And the taskmanager would show 4 processes of
pulseaudio 2 of which were always active on harddrive.

Tried it with Xubuntu as well. Same Problem even without audacity
installed.

I've got  a HP Elitebook 850 G1 with Intel / AMD hybrid graphics running with 
Dynamic dGPU poweroff by default. 
Could the dynamic switching be the problem?

Best regards!

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

Title:
  BETA 14.04 cant connect to PulseAudio server

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  
  1) Install  Ubuntustudio 64 bit  14.04  Beta 1 (Alpha)  Feb 24
  2) reboot etc

  result:  Sound system works properly

  3) Install all the latest updates as of Mar 14,  3.13.0-17-lowlatency kernel
  4) reboot etc

  result:  Sound System no longer works
  anything that tries to connect to the PulseAudio server, including the Volume 
Contol, hangs...

  Expected:  PulseAudio should still work after the update

  Note: JACK is still usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-17.37-lowlatency 3.13.6
  Uname: Linux 3.13.0-17-lowlatency x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  em 1829 F pulseaudio
   /dev/snd/controlC0:  em 1829 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 14 02:45:02 2014
  InstallationDate: Installed on 2014-03-14 (0 days ago)
  InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha amd64 (20140224)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1641
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd11/11/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058912242B2020100:rvnHewlett-Packard:rn1641:rvr67.32:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058912242B2020100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1008277] Re: [upstream] Recent menu botches file names

2014-03-21 Thread Adolfo Jayme
** Package changed: gtk+3.0 (Ubuntu) = ubuntu

** Package changed: ubuntu = unity-gtk-module (Ubuntu)

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

Title:
  [upstream] Recent menu botches file names

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “unity-gtk-module” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04 64-bit
  Libreoffice 
(not sure about what package to check for version, so I just checked core:
  - dpkg -s libreoffice-core | grep -i version
  Version: 1:3.5.3-0ubuntu1
)

  I have file names that have underscore characters.  On the recent
  menu, these are all removed, probably as the string gets sanitized for
  other special characters.  However, there's no real reason to remove
  underscores, that I know of anyway.

  Expected:
All file names to be displayed as they exist on the system

  Actual:
Underscores are removed...haven't checked other characters

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

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


[Desktop-packages] [Bug 1295526] Re: disable touchpad while typing doesn't work

2014-03-21 Thread Lex Ross
Actually, neither starting syndaemon via rc.local nor enabling SHMconfig
in xorg.conf helped. The only way to disable touchpad while typing was
to start syndaemon from a graphic session as a user. The button to
disable touchpad does not work and the disable touchpad while typing
checkbox in system control panel has no effect as per my original
report.

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

Title:
  disable touchpad while typing doesn't work

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  Disable touchpad while typing checkbox in System Settings does not
  work on my Asus F5N laptop. The button to disable touchpad does not
  work as well. As a workaround I use syndaemon -i 1 -K -d command as
  per Ubuntu help page
  https://help.ubuntu.com/community/SynapticsTouchpad/ but it does not
  fix the issue with the said chechbox and hardware button. I guess it
  still needs to access shared memory using SHMconfig option in
  xorg.conf in which case it is the same bug that has been around for 3
  years starting from Ubuntu 11.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-input-synaptics 1.7.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 10:10:18 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  MachineType: ASUSTeK Computer Inc. F5N
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-6-generic 
root=UUID=f239c25a-4c5d-4e97-a6e7-befdcc142599 ro quiet splash 
enable_mtrr_cleanup elevator=noop
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F5N
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd04/08/2008:svnASUSTeKComputerInc.:pnF5N:pvr1.0:rvnASUSTeKComputerInc.:rnF5N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: F5N
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140310-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~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  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-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: Tue Mar 18 22:35:44 2014
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1295526/+subscriptions

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Chris
I've going through the /var/log/apt/history.log

I believe this is where the error starts to crop out.

Start-Date: 2014-03-18  08:53:02
Commandline: aptdaemon role='role-commit-packages' sender=':1.113'
Upgrade: indicator-virtual-box:amd64 (1.0.30-1, 1.0.31-1), clamav:amd64 
(0.97.8+dfsg-1ubuntu1.12.04.1, 0.97.8+dfsg-1ubuntu1.12.04.2), clamav-base:amd64 
(0.97.8+dfsg-1ubuntu1.12.04.1, 0.97.8+dfsg-1ubuntu1.12.04.2), libclamav6:amd64 
(0.97.8+dfsg-1ubuntu1.12.04.1, 0.97.8+dfsg-1ubuntu1.12.04.2), 
gir1.2-gtk-3.0:amd64 (3.4.2-0ubuntu0.6, 3.4.2-0ubuntu0.7), 
librsvg2-common:amd64 (2.36.1-0ubuntu1, 2.36.1-0ubuntu1.1), 
librsvg2-common:i386 (2.36.1-0ubuntu1, 2.36.1-0ubuntu1.1), libgtk-3-bin:amd64 
(3.4.2-0ubuntu0.6, 3.4.2-0ubuntu0.7), libgtk-3-0:amd64 (3.4.2-0ubuntu0.6, 
3.4.2-0ubuntu0.7), tzdata-java:amd64 (2013g-0ubuntu0.12.04, 
2014a-0ubuntu0.12.04), libgail-3-0:amd64 (3.4.2-0ubuntu0.6, 3.4.2-0ubuntu0.7), 
google-chrome-stable:amd64 (33.0.1750.149-1, 33.0.1750.152-1), 
virtualbox-4.1:amd64 (4.1.30-91550~Ubuntu~precise, 
4.1.32-92798~Ubuntu~precise), clamav-freshclam:amd64 
(0.97.8+dfsg-1ubuntu1.12.04.1, 0.97.8+dfsg-1ubuntu1.12.04.2), tzdata:amd64 
(2013g-0ubuntu0.12.04, 2014a-0ubuntu0.12.04), librsvg2-2:amd64 
(2.36.1-0ubuntu1, 2.36.1-0ubuntu1.1), librsvg2-2:i386 (2.36.1-0ubuntu1, 
2.36.1-0ubuntu1.1), libgtk-3-common:amd64 (3.4.2-0ubuntu0.6, 3.4.2-0ubuntu0.7)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2014-03-18  08:54:19

There show the error during dpkg.

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1064461] Re: [EMU10K1 - SB Live! Value [CT4871], playback] When changing volume sound stutters in Rythmbox or other applications

2014-03-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [EMU10K1 - SB Live! Value [CT4871], playback]  When changing volume
  sound stutters in Rythmbox or other applications

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

Bug description:
  This is on a fresh install of Ubuntu 12.04.1 LTS 
  PulseAudio 1:1.1-0ubuntu15.1
  Generally if I change volume in the application or at the main volume 
control, volume does change by sound stutters badly.  Eventually it will stop 
stuttering and I can force it to stop by moving teh volume control slightly 
back from where I initially set it. (turn it down or up a little from where I 
stopped).  Also, when I close RythmBox or other applications playing sound, the 
sound will repeat itself until the volume control is moved or after a few 
seconds it may stop stuttering.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  todd   2894 F pulseaudio
   /dev/snd/controlC2:  todd   2894 F pulseaudio
   /dev/snd/controlC0:  todd   2894 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Live'/'SB Live! Value [CT4871] (rev.7, serial:0x80321102) at 
0xcc00, irq 18'
 Mixer name : 'Cirrus Logic CS4297A rev 3'
 Components : 'AC97a:43525913'
 Controls  : 222
 Simple ctrls  : 42
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf9f78000 irq 22'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,10ec,0011'
 Controls  : 45
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Bt878'/'Brooktree Bt878 at 0xcfffe000, irq 19'
 Mixer name : 'Bt87x'
 Components : ''
 Controls  : 3
 Simple ctrls  : 5
  Date: Tue Oct  9 10:05:05 2012
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Live failed
  Symptom_Card: Bt878 Audio Capture - Brooktree Bt878
  Symptom_PulseAudioLog:
   
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [EMU10K1 - SB Live! Value [CT4871], playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MI-A78S-8209
  dmi.board.vendor: XFX
  dmi.board.version: Ver1.1
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/06/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnXFX:rnMI-A78S-8209:rvrVer1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1207626] Re: Hybrid graphics doesn't work with pci classes other than 300

2014-03-21 Thread Alberto Milone
@Antonio: what Ubuntu release are you using?

Also, please attach the output of the following command:

lspci -Dn

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

Title:
  Hybrid graphics doesn't work with pci classes other than 300

Status in “fglrx-pxpress” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Fix Released

Bug description:
  Unable to log into unity corretly, where intel graphic chipset can
  work correctly when removing nvidia driver.

  Affected graphic card:
  01:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 610M/710M / 
GT 620M/625M/630M/720M] [10de:1140] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 319.32-0ubuntu5
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Fri Aug  2 01:38:26 2013
  InstallationDate: Installed on 2013-08-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130731)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-319
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1207626/+subscriptions

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


[Desktop-packages] [Bug 1295546] [NEW] There is a border around Unity launcher options

2014-03-21 Thread Archisman Panigrahi
Public bug reported:

When I right click on any application icon on Unity Launcher in Ubuntu 14.04 
LTS beta 1, there is a border around the options.
I have attached a picture.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140318-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar 21 13:28:56 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:303c]
InstallationDate: Installed on 2014-03-20 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
MachineType: LENOVO 222
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=2cc86464-eef3-493e-abcf-77188d0b1389 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 52KT43AUS
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvr52KT43AUS:bd07/04/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: 222
dmi.product.version: LENOVO 
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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 Mar 21 12:24:03 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputWebcam C170  KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   61500 
 vendor DEL
xserver.version: 2:1.15.0-1ubuntu7

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


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

** Attachment added: launcher.png
   
https://bugs.launchpad.net/bugs/1295546/+attachment/4035274/+files/launcher.png

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

Title:
  There is a border around Unity launcher options

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I right click on any application icon on Unity Launcher in Ubuntu 14.04 
LTS beta 1, there is a border around the options.
  I have attached a picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:28:56 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:303c]
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  MachineType: LENOVO 222
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=2cc86464-eef3-493e-abcf-77188d0b1389 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade 

[Desktop-packages] [Bug 223989] Re: Reconsider the Browse C:\ Drive launcher

2014-03-21 Thread Scott Ritchie
** Also affects: wine1.6 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: wine1.6 (Ubuntu)
   Status: New = Triaged

** Changed in: wine1.6 (Ubuntu)
   Importance: Undecided = Medium

** Changed in: wine1.4 (Ubuntu)
   Status: Triaged = Won't Fix

** Changed in: wine1.6 (Ubuntu)
 Assignee: (unassigned) = Scott Ritchie (scottritchie)

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

Title:
  Reconsider the Browse C:\ Drive launcher

Status in Nautilus:
  Won't Fix
Status in “nautilus” package in Ubuntu:
  Won't Fix
Status in “wine1.4” package in Ubuntu:
  Won't Fix
Status in “wine1.6” package in Ubuntu:
  Triaged

Bug description:
  Nautilus (and KDE/XFCE equivalent) needs a default bookmark to
  ~/.wine/dosdevices/c: so that browsing the Wine C:\ drive can be done
  from the Places menu rather than the Application menu.  This icon is
  hidden if this folder doesn't exist, so it should only affect users
  with Wine installed and configured.

  ---original report---
  An easy one :-)
  The launcher named Browse C:\ Drive executes the command
  xdg-open ~/.wine/drive_c
  The command should be
  xdg-open ~/.wine/dosdevices/c:
  (correctly displaying the c: directory wherever it is)
  Cheers, André.

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

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


[Desktop-packages] [Bug 1294006] Re: New upstream microreleases 9.3.4, 9.1.13, 8.4.21

2014-03-21 Thread Martin Pitt
Synced, propagated:

 postgresql-9.1 | 9.1.13-1 | trusty/universe | source


** Changed in: postgresql-9.1 (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  New upstream microreleases 9.3.4, 9.1.13, 8.4.21

Status in “postgresql-8.4” package in Ubuntu:
  Invalid
Status in “postgresql-9.1” package in Ubuntu:
  Fix Released
Status in “postgresql-9.3” package in Ubuntu:
  Fix Released
Status in “postgresql-8.4” source package in Lucid:
  In Progress
Status in “postgresql-8.4” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Quantal:
  In Progress
Status in “postgresql-9.1” source package in Saucy:
  In Progress
Status in “postgresql-9.1” source package in Trusty:
  Fix Released
Status in “postgresql-9.3” source package in Trusty:
  Fix Released

Bug description:
  PostgreSQL will publish new upstream microreleases this Thursday which
  fix several data loss bugs. No security issues.

  As per the standing MRE for PostgreSQL these should go into stable
  Ubuntu releases.

  Upstream announcement: http://www.postgresql.org/about/news/1511/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1294006/+subscriptions

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


[Desktop-packages] [Bug 1294006] Re: New upstream microreleases 9.3.4, 9.1.13, 8.4.21

2014-03-21 Thread Martin Pitt
Synced, propagated:
postgresql-9.3 | 9.3.4-1 | trusty | source, amd64, arm64, armhf, i386, powerpc, 
ppc64el

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  New upstream microreleases 9.3.4, 9.1.13, 8.4.21

Status in “postgresql-8.4” package in Ubuntu:
  Invalid
Status in “postgresql-9.1” package in Ubuntu:
  Fix Released
Status in “postgresql-9.3” package in Ubuntu:
  Fix Released
Status in “postgresql-8.4” source package in Lucid:
  In Progress
Status in “postgresql-8.4” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Precise:
  In Progress
Status in “postgresql-9.1” source package in Quantal:
  In Progress
Status in “postgresql-9.1” source package in Saucy:
  In Progress
Status in “postgresql-9.1” source package in Trusty:
  Fix Released
Status in “postgresql-9.3” source package in Trusty:
  Fix Released

Bug description:
  PostgreSQL will publish new upstream microreleases this Thursday which
  fix several data loss bugs. No security issues.

  As per the standing MRE for PostgreSQL these should go into stable
  Ubuntu releases.

  Upstream announcement: http://www.postgresql.org/about/news/1511/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1294006/+subscriptions

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


[Desktop-packages] [Bug 1247974] Re: network don't work after longtime suspend mode

2014-03-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  network don't work after longtime suspend mode

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

Bug description:
  when my system in suspend mode for long time (1 hour or more) -
  network connection is down. Only reboot saving.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Uname: Linux 3.12.0-1-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  Date: Mon Nov  4 23:22:26 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-26 (101 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130726)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.100  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-10-08T20:01:22.891003
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.4connected   enabled   enabled 
enabledenabled disabled

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Chris
Or possible this one?

Start-Date: 2014-03-07  09:13:12
Commandline: aptdaemon role='role-commit-packages' sender=':1.422'
Install: linux-image-3.2.0-60-generic:amd64 (3.2.0-60.91), 
linux-headers-3.2.0-60:amd64 (3.2.0-60.91), 
linux-headers-3.2.0-60-generic:amd64 (3.2.0-60.91)
Upgrade: libmagickcore4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
gnome-settings-daemon:amd64 (3.4.2-0ubuntu0.6.4, 3.4.2-0ubuntu0.6.5), 
icedtea-netx:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
libmagickwand4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
linux-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), libmagickcore4-extra:amd64 
(6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), libmagick++4:amd64 
(6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), icedtea-netx-common:amd64 
(1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), imagemagick-common:amd64 
(6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), linux-headers-generic:amd64 
(3.2.0.59.70, 3.2.0.60.71), linux-image-generic:amd64 (3.2.0.59.70, 
3.2.0.60.71), icedtea-7-plugin:amd64 (1.2.3-0ubuntu0.12.04.3, 
1.2.3-0ubuntu0.12.04.4), imagemagick:amd64 (6.6.9.7-5ubuntu3.2, 
6.6.9.7-5ubuntu3.3), linux-libc-dev:amd64 (3.2.0-59.90, 3.2.0-60.91), 
linux-libc-dev:i386 (3.2.0-59.90, 3.2.0-60.91), perlmagick:amd64 
(6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3)
End-Date: 2014-03-07  09:16:05

HELP!

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Hongbo Zhu
My system is ubuntu 12.04 on Linux 3.8.0-37-generic. I got some crash
report after a system update two days ago (seemly from librsvg2). After
I reboot the PC, I notice some of the icons are missing. In addition, I
cannot open .png files using eog. After some googling I tried to re-
install librsvg-related packages. But I constantly got Segmentation
fault

Unpacking librsvg2-common (from 
.../librsvg2-common_2.36.1-0ubuntu1.1_amd64.deb) ... 
Processing triggers for libgdk-pixbuf2.0-0 ... 
Segmentation fault (core dumped)
Setting up librsvg2-common (2.36.1-0ubuntu1.1) ... 
Processing triggers for libgdk-pixbuf2.0-0 ... 
Segmentation fault (core dumped)

I also tried to force reinstall libgdk-pixbuf2.0-0 but got segmentation
fault, too.

Do you want to continue [Y/n]? 
(Reading database ... 1106000 files and directories currently installed.)
Preparing to replace libgdk-pixbuf2.0-0 2.26.1-1 (using 
.../libgdk-pixbuf2.0-0_2.26.1-1_amd64.deb) ...
Unpacking replacement libgdk-pixbuf2.0-0 ...
Preparing to replace libgdk-pixbuf2.0-0:i386 2.26.1-1 (using 
.../libgdk-pixbuf2.0-0_2.26.1-1_i386.deb) ...
Unpacking replacement libgdk-pixbuf2.0-0:i386 ...
Setting up libgdk-pixbuf2.0-0 (2.26.1-1) ...
Segmentation fault (core dumped)
Setting up libgdk-pixbuf2.0-0:i386 (2.26.1-1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

I downloaded the .deb package and tried installing it but same segfault
msg.

running gdk-pixbuf-query-loaders brings up segfaults as well (but not
gdk-pixbuf-pixdata or gdk-pixbuf-csource):

gdk-pixbuf-query-loaders --update-cache
Segmentation fault (core dumped)

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295557] [NEW] Crashes if indicator-sound is not installed

2014-03-21 Thread David Henningsson
Public bug reported:

If indicator-sound is not installed, the command unity-control-center
sound will crash with  Settings schema 'com.canonical.indicator.sound'
is not installed and then a  SIGTRAP.

Either unity-control-center should hard depend on indicator-sound or
unity-control-center needs to handle the absense of this schema.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 21 09:31:26 2014
InstallationDate: Installed on 2013-11-04 (136 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center:
 activity-log-manager   0.9.7-0ubuntu10
 deja-dup   29.5-0ubuntu2
 gnome-control-center   1:3.6.3-0ubuntu53
 gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

** Affects: unity-control-center (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 unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1295557

Title:
  Crashes if indicator-sound is not installed

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

Bug description:
  If indicator-sound is not installed, the command unity-control-center
  sound will crash with  Settings schema
  'com.canonical.indicator.sound' is not installed and then a  SIGTRAP.

  Either unity-control-center should hard depend on indicator-sound or
  unity-control-center needs to handle the absense of this schema.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 09:31:26 2014
  InstallationDate: Installed on 2013-11-04 (136 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Desktop-packages] [Bug 1293058] Re: compiz: PAM unable to dlopen(pam_usb.so): /lib/security/pam_usb.so: cannot open shared object file: No such file or directory

2014-03-21 Thread Karma Dorje
after today updates  I can finally switch the input languages with a
mouse.

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

Title:
  compiz: PAM unable to dlopen(pam_usb.so): /lib/security/pam_usb.so:
  cannot open shared object file: No such file or directory

Status in Unity:
  New
Status in “lightdm” package in Ubuntu:
  New

Bug description:
  after resume from suspend/sleep mode i can't login via usb-stick and cannot 
login via password because my keyboard is unresponsive — not possible to change 
the input language.
  apt-cache policy compiz
  compiz:
    Installed: 1:0.9.11+14.04.20140310-0ubuntu1
    Candidate: 1:0.9.11+14.04.20140310-0ubuntu1
    Version table:
   *** 1:0.9.11+14.04.20140310-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libpam-usb
  libpam-usb:
    Installed: 0.5.0-4
    Candidate: 0.5.0-4
    Version table:
   *** 0.5.0-4 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
  100 /var/lib/dpkg/status

  dpkg --listfiles libpam-usb
  /.
  /usr
  /usr/share
  /usr/share/pam-configs
  /usr/share/pam-configs/usb
  /usr/share/doc
  /usr/share/doc/libpam-usb
  /usr/share/doc/libpam-usb/README.Debian
  /usr/share/doc/libpam-usb/copyright
  /usr/share/doc/libpam-usb/NEWS.Debian.gz
  /lib
  /lib/x86_64-linux-gnu
  /lib/x86_64-linux-gnu/security
  /lib/x86_64-linux-gnu/security/pam_usb.so
  /usr/share/doc/libpam-usb/changelog.Debian.gz

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

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


[Desktop-packages] [Bug 1294578] Re: [ffe/uife] Match the display settings checkbox

2014-03-21 Thread Treviño
** Branch linked: lp:~3v1n0/unity-control-center/applications-scaling-
selector

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

Title:
  [ffe/uife] Match the display settings checkbox

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

Bug description:
  Here are some notes on the
  
https://code.launchpad.net/~hikiko/unity-control-center/u-c-c.checkbox-for-app-scaling/+merge/211681
 MP:

  After we introduced the HiDPI changes and the per-monitor Unity
  scaling factor (ui-scale gsetting) there was the following problem,
  discussed at UDS:

  The Qt and Gnome applications would use the scaling-factor and text-
  scaling-factor for scaling and not our ui-scale, so their window
  contents would have a different size than their decorations, the menus
  and the launcher. Another problem was that the Gnome text-scaling-
  factor and scaling-factor are settings for the whole desktop whereas
  ui-scale is per monitor and there would be some inconsistency anyway
  when multiple monitors are plugged in.

  So, as a quick partial solution to the problem, we promised to add a
  checkbox in each monitor's settings that sets the scaling-factor and
  text-scaling factor values in accordance with the ui-scale for that
  monitor when it's checked.

  This way, the user will see the same size in Unity and the Gtk/Qt
  applications in  1 monitor if he checks the checkbox of a monitor.

  To allow this, we had to introduce a new gsetting that stores the
  selected monitor name here: https://code.launchpad.net/~hikiko
  /gsettings-ubuntu-touch-schemas/gsettings-ubuntu-touch-schemas
  .selected-monitor/+merge/211680.

  Of course this whole feature could be better designed so that the user
  receives more visual feedback. We discussed it with the designers team
  and they gave us a much better design that will be used in the future:
  https://wiki.ubuntu.com/BrightnessAndDisplays#Displays (credits
  Matthew Paul Thomas)

  For the moment we will just use the checkbox to meet the deadline
  which is in a few days, as we promised at UDS.

  -
  Some notes  in the logic:
  -

  First of all, here is the way we set the scaling-factor and text-
  scaling factor to be in accordance with the ui-scale. The idea is
  Marco Trevisan's and I paste his algorithm as it was in our Unity team
  document:

   Scaling the World…
   So, after scaling unity we should care also about the apps… There are still 
some troubles to get the best experience:
   Applications doesn’t care about the per-monitor scaling
   Gtk2 and Qt (using a gtk2 rendering style) apps only care about scaling 
factor, so there’s not much we can do with them
   Gtk3 apps support integer UI scaling only
   [...]
   When that option is true we set the gdk-interface-scaling factor to match 
the integer part of maximum scaling factor of the
   attached display, while we set the text-scaling-factor to a value that 
multiplied for the interface scaling factor will result our
   scaling factor (this will apply to both Gtk and Qt applications)
   [...]
   So, our monitor has the scaling factor of 2.25, we set:
- scaling-factor: 2
- text-scaling-factor: 2.25 / 2 = 1.125
  (In the above example 2.25 is the ui-scale, the Unity scaling factor that is 
per monitor)

  How the checkbox works:
  ---

  The first time the user runs the u-c-c (which is after a fresh
  installation) the checkbox appears to be checked in the primary
  monitor and we set the scaling-factor, text-scaling-factor (Gnome) to
  match the ui-scale (Unity), so that the user can have a good visual
  experience in his primary monitor. We also store the primary monitor
  as selected-display in our gsetting to remember this choice.

  Every other time:
  Unless if the scaling factors have been changed from a non u-c-c application 
(see below for this case), the checkbox appears unchecked for every monitor 
except of the selected that is checked. When the user selects a new monitor, 
u-c-c remembers his choice and the new selection appears checked whereas all 
the others are unchecked. The selected monitor is stored in the 
selected-display gsetting in gsettings-ubuntu-schemas.

  What if the scaling factors change from outside u-c-c?
  
-
  Every time we update the checkbox status (checked or unchecked) we not only 
check the selected-monitor's value but the consistency of the 3 scaling factors.

  In other words, if:

  scaling-factor * text-scaling-factor != ui-scale +- small_ERROR for
  the ui-scale of the selected monitor,

  and

  the selected-display setting matches the selected monitor,

  it means that either the text-scaling-factor or the scaling-factor
  

[Desktop-packages] [Bug 1295497] Re: Cannot enter password in lightdm on the first time

2014-03-21 Thread Sebastien Bacher
you can also open an indicator and then close it as a workaround, it's
easier than login in and out from guest

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

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

Title:
  Cannot enter password in lightdm on the first time

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

Bug description:
  I have only one administrator account and have guest account enabled.

  1. When I try to enter my password, no stars or dots are shown.
  2. I click on guest and go back to my account.
  3. Now I can enter my password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.8-0ubuntu1
  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: Unity
  Date: Fri Mar 21 10:07:51 2014
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=archisman
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1293790] Re: An application wants access to the keyring (*which* application is not specified)

2014-03-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 246185 ***
https://bugs.launchpad.net/bugs/246185

read https://bugzilla.gnome.org/show_bug.cgi?id=574315 for specifics
details on why having the label/app name wouldn't help much, if you are
interested

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

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

Title:
  An application wants access to the keyring (*which* application is
  not specified)

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

Bug description:
  I have Ubuntu 13.10 Desktop installed. I am being prompted with this
  message: Title: 'Unlock Keyring' - An application wants access to the
  keyring 'default', but it is locked. Password? [] Note that in
  this case there is no Details  expansion control, no reveal more,
  no button to view details etc.

  This is not an unfamiliar message, similar concepts exist for both
  Windows and Mac, and the behavior derives from earlier forms of Linux.
  The idea of a keyring specifically is something I used on the Mac.

  I have some beef with this message in Ubuntu's form, however. What
  application is requesting this? Accessing a keyring with a password is
  asking for a Master password, one password to rule them all. One
  cannot, and should not, just hand out this master password to any
  application. So what application wants access to the keyring??

  IMO this failure to disclose who is asking for the master password is
  critically bad security.

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

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


[Desktop-packages] [Bug 1235457] Re: nautilus exits when opened using sudo user and properties of a file/folder is opened

2014-03-21 Thread Sebastien Bacher
running graphical softwares under sudo is neither recommended nor
supported, don't do that

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

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

Title:
  nautilus exits when opened using sudo user and properties of a
  file/folder is opened

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  I have a similar problem, when I type the command sudo nautilus
  happens the error below.

  Nautilus opens, closes however if I want to get into any folder
  properties.

  $ sudo nautilus

  (nautilus:7610): Nautilus-Python-WARNING **: g_module_open libpython failed: 
/usr/lib/libpython2.7.so.1.0: Não é possivel abrir arquivo de objetos 
compartilhado: Arquivo ou diretório não encontrado
  ImportError: could not import gobject (error was: 
'/usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: 
_Py_ZeroStruct')

  (nautilus:7610): Nautilus-Python-WARNING **: pygobject initialization
  failed

  (nautilus:7610): Nautilus-Python-WARNING **:
  nautilus_python_init_python failed

  I want to change the permissions of a folder and subfolders and files,
  however the terminal does not present any error but too does not
  change the permissions. And to change opening the Nautilus happens
  that I reported above.

  My system is Ubuntu 13.04  updated
  My computer is Notebook HP AMD A8 64 bits

  
-

  Confirmed that this bug exists on 14.04 release with nautilus version
  3.10.1 but the error message is as follows:

  (nautilus:13221): Gtk-WARNING **: Failed to register client: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  **
  ERROR:nautilus-properties-window.c:1839:schedule_owner_change_timeout: 
assertion failed: (NAUTILUS_IS_FILE (file))

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

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


[Desktop-packages] [Bug 1295565] Re: nautilus crashed with SIGABRT in g_assertion_message()

2014-03-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1274291 ***
https://bugs.launchpad.net/bugs/1274291

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035346/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035348/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035349/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035350/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035351/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035352/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1295565/+attachment/4035353/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1274291
   nautilus SIGABRT NAUTILUS_IS_FILE (file) (when using under sudo?)

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Nautilus crashes while using as root and right-click on file-
  properties.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Mar 21 09:37:15 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-03-12 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226)
  ProcCmdline: /usr/bin/nautilus --no-default-window
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 907381] Re: [Dell Vostro 3550] Display resolution keeps switching with external monitor connected

2014-03-21 Thread Lee Willis
Confirmed - no change in the problem after updating to the latest BIOS -
resolution switches still occur.

** Tags removed: bios-outdated-a12
** Tags added: latest-bios-a12

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

Title:
  [Dell Vostro 3550] Display resolution keeps switching with external
  monitor connected

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  A fresh install of Ubuntu 11.10 on a Dell Vostro 3550 with all updates (OSS 
only - no proprietary drivers). When connecting the laptop to an external 
monitor to extend my desktop the display settings are unstable. I choose to 
enable both the laptop panel, and the external monitor setting appropriate 
resolutions and apply settings. Sometimes the chosen settings do not take. If 
they do apply, and I confirm that I want to keep the settings, at random 
intervals the display settings are auto-changed by the system. This may include:
  - Resetting to mirrored displays at 1024x768
  - Resetting to a single display on the laptop panel
  - Resetting to a single display on the external monitor
  - Some other weird combination.

  E.g. When using my computer in a time range of 10 minutes i could get
  through 5 different dispositions and resolutions. It could be both
  display working fine, then only one but with wrong resolution, then
  the two again but with mirror, then just the second, and so on.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.7-0ubuntu6
  Architecture: i386
  CasperVersion: 1.336ubuntu1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cd]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (prog-if 00 [VGA controller])
     Subsystem: Dell Radeon HD 6630M [1028:04cd]
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140108)
  MachineType: Dell Inc. Vostro 3550
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.12.0-7-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0DJW0H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/18/2011:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0DJW0H:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3550
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Wed Jan  8 13:59:41 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 739
   vendor LGD
  xserver.version: 2:1.14.5-1ubuntu2

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

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


[Desktop-packages] [Bug 379008] Re: Active screen changes when suspending by lid close

2014-03-21 Thread Andreas Schildbach
I'd say its not an issue any more on 14.04.

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

Title:
  Active screen changes when suspending by lid close

Status in “pm-utils” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: acpi-support

  I have two screens, an internal Dell Latitude X1 and an external Dell
  2405FPW. Both screens are switched on, and the external monitor is
  connected to the VGA output of the X1.

  Using display preferences, I have switched off the external display,
  using just the internal display.

  When suspending by closing the lid, the external display is briefly
  activated and the internal display deactivated. The machine then goes
  to standby, which deactivates both displays. After resuming, the
  desktop appears on the external display, while the internal display is
  switched off. This behaviour is _not_ expected. I'd expect Ubuntu to
  respect my display configuration.

  This is _not_ an issue when suspending via pm-suspend. It is also not
  an issue when I change the lid action from suspend to e.g. blank
  screen and then close the lid.

  Environment: Jaunty, upgraded with recommended updates. xserver-xorg-
  video-intel driver on i915GMS.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: acpi-support 0.121
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  Uname: Linux 2.6.28-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/379008/+subscriptions

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Hongbo Zhu
** Information type changed from Public to Public Security

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1289515] [PATCH] sink/source: Initialize port before fixate hook (fixes volume/mute not restored)

2014-03-21 Thread David Henningsson
In case a port has not yet been saved, which is e g often the case
if a sink/source has only one port, reading volume/mute will be done
without port, whereas writing volume/mute will be done with port.

Work around this by setting a default port before the fixate hook,
so module-device-restore can read volume/mute for the correct port.

BugLink: https://bugs.launchpad.net/bugs/1289515
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 src/pulsecore/sink.c   |   11 +++
 src/pulsecore/source.c |   11 +++
 2 files changed, 22 insertions(+)

diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
index 08143e9..9c4b0c3 100644
--- a/src/pulsecore/sink.c
+++ b/src/pulsecore/sink.c
@@ -235,6 +235,17 @@ pa_sink* pa_sink_new(
 pa_device_init_icon(data-proplist, true);
 pa_device_init_intended_roles(data-proplist);
 
+if (!data-active_port  !data-save_port) {
+void *state;
+pa_device_port *p, *p2 = NULL;
+
+PA_HASHMAP_FOREACH(p, data-ports, state)
+if (!p2 || p-priority  p2-priority) {
+p2 = p;
+pa_sink_new_data_set_port(data, p2-name);
+}
+}
+
 if (pa_hook_fire(core-hooks[PA_CORE_HOOK_SINK_FIXATE], data)  0) {
 pa_xfree(s);
 pa_namereg_unregister(core, name);
diff --git a/src/pulsecore/source.c b/src/pulsecore/source.c
index 2a600e2..94533df 100644
--- a/src/pulsecore/source.c
+++ b/src/pulsecore/source.c
@@ -222,6 +222,17 @@ pa_source* pa_source_new(
 pa_device_init_icon(data-proplist, false);
 pa_device_init_intended_roles(data-proplist);
 
+if (!data-active_port  !data-save_port) {
+void *state;
+pa_device_port *p, *p2 = NULL;
+
+PA_HASHMAP_FOREACH(p, data-ports, state)
+if (!p2 || p-priority  p2-priority) {
+p2 = p;
+pa_source_new_data_set_port(data, p2-name);
+}
+}
+
 if (pa_hook_fire(core-hooks[PA_CORE_HOOK_SOURCE_FIXATE], data)  0) {
 pa_xfree(s);
 pa_namereg_unregister(core, name);
-- 
1.7.9.5

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

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1295584] [NEW] Belgian keyboard-layout is indicated as german-belgian

2014-03-21 Thread Bernard Decock
Public bug reported:

Live-session. Change keyboard-layout to Belgian.
Reset ibus-keyboard-indicator

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ibus 1.5.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CasperVersion: 1.339
CurrentDesktop: XFCE
Date: Fri Mar 21 10:22:22 2014
LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140320)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

** Attachment added: German_Belgian.png
   
https://bugs.launchpad.net/bugs/1295584/+attachment/4035419/+files/German_Belgian.png

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

Title:
  Belgian keyboard-layout is indicated as german-belgian

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Live-session. Change keyboard-layout to Belgian.
  Reset ibus-keyboard-indicator

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Fri Mar 21 10:22:22 2014
  LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140320)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1289515] Re: Sound volume resets after making a call

2014-03-21 Thread David Henningsson
I was able to see something similar on the desktop, and came up with a
patch to fix it. Can you test it and see if it resolves your problem as
well?

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

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1289515] Re: Sound volume resets after making a call

2014-03-21 Thread David Henningsson
** Patch added: 
0001-sink-source-Initialize-port-before-fixate-hook-fixes.patch
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1289515/+attachment/4035418/+files/0001-sink-source-Initialize-port-before-fixate-hook-fixes.patch

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

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1287753] Re: Please update to 331. 49 and/or provide Nvidia 334.21

2014-03-21 Thread Alberto Milone
Excellent. I'll work on it.

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Description changed:

- Provide Nvidia 334.21 drivers for ubuntu 14.04.
+ Provide Nvidia 334.21 drivers for ubuntu 14.04 in the xorg-edgers PPA.
  This driver provides alot of performance improvements and new GPUs support.
  
  Changlog:
  http://www.nvidia.com/download/driverResults.aspx/73666/en-us

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

Title:
  Please update to 331. 49 and/or provide Nvidia 334.21

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged

Bug description:
  Provide Nvidia 334.21 drivers for ubuntu 14.04 in the xorg-edgers PPA.
  This driver provides alot of performance improvements and new GPUs support.

  Changlog:
  http://www.nvidia.com/download/driverResults.aspx/73666/en-us

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

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


[Desktop-packages] [Bug 1295592] [NEW] Unable to make screenshot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session in Trusty

2014-03-21 Thread Norbert
Public bug reported:

In Trusty with all installed updates it is not possible to make
ScreenShot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen,
Ctrl+Shift+PrintScreen keyboard buttons.

Steps to reproduce:
1. Install Ubuntu 14.04.
2. Login to Unity session.
3a. Try to make screenshot of the whole desktop with Ctrl+PrintScreen
3b. Try to make screenshot of active window with Ctrl+Alt+PrintScreen
3c. Try to make screenshot of selected area with Ctrl+Shift+PrintScreen

Expected results:
* Corresponding screenshot is saved in clipboard and may be inserted to other 
applications with Ctrl+V.

Actual results:
* Screenshot is not saved to clipboard.


Notes:
1. This bug is complementary to bug 1282649 (Unable to make screenshot with 
PrintScreen key in Unity session in Trusty).
2. I use default shortcuts Super+Space and Shift+Super+Space for keyboard 
layout switching.
3. I did some tests (see my Google Docs table - 
https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHpGYVlMZ2JuYXdXdEtmUi1QbGxsYXcusp=sharing).
 In Ubuntu 12.04 (with no matter Unity or GNOME sessions) the full working list 
of shortcuts used for screenshoting is as follows: PrintScreen, 
Alt+PrintScreen, Ctrl+PrintScreen, Shift+PrintScreen, 
Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen. All these hotkeys work 
normally in 14.04 too on GNOME FlashBack session (Compiz and Metacity).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Fri Mar 21 13:29:53 2014
InstallationDate: Installed on 2014-03-17 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140316)
SourcePackage: unity-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.unity-settings-daemon.log: (gnome-terminal:2677): GLib-GIO-CRITICAL **: 
g_settings_get: the format string may not contain '' (key 
'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call 
will probably stop working with a future version of glib.

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


** Tags: apport-bug i386 trusty

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

Title:
  Unable to make screenshot to clipboard with Ctrl+PrintScreen,
  Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session
  in Trusty

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

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot to clipboard with Ctrl+PrintScreen,
  Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keyboard buttons.

  Steps to reproduce:
  1. Install Ubuntu 14.04.
  2. Login to Unity session.
  3a. Try to make screenshot of the whole desktop with Ctrl+PrintScreen
  3b. Try to make screenshot of active window with Ctrl+Alt+PrintScreen
  3c. Try to make screenshot of selected area with Ctrl+Shift+PrintScreen

  Expected results:
  * Corresponding screenshot is saved in clipboard and may be inserted to other 
applications with Ctrl+V.

  Actual results:
  * Screenshot is not saved to clipboard.

  
  Notes:
  1. This bug is complementary to bug 1282649 (Unable to make screenshot with 
PrintScreen key in Unity session in Trusty).
  2. I use default shortcuts Super+Space and Shift+Super+Space for keyboard 
layout switching.
  3. I did some tests (see my Google Docs table - 
https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHpGYVlMZ2JuYXdXdEtmUi1QbGxsYXcusp=sharing).
 In Ubuntu 12.04 (with no matter Unity or GNOME sessions) the full working list 
of shortcuts used for screenshoting is as follows: PrintScreen, 
Alt+PrintScreen, Ctrl+PrintScreen, Shift+PrintScreen, 
Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen. All these hotkeys work 
normally in 14.04 too on GNOME FlashBack session (Compiz and Metacity).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:29:53 2014
  InstallationDate: Installed on 2014-03-17 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140316)
  SourcePackage: unity-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity-settings-daemon.log: (gnome-terminal:2677): GLib-GIO-CRITICAL 
**: g_settings_get: the format string may not contain '' (key 
'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call 
will probably stop working with a future version of glib.

To manage notifications about this bug go 

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

2014-03-21 Thread Alberto Salvia Novella
** Changed in: hundredpapercuts
   Importance: Undecided = Low

** Changed in: hundredpapercuts
   Status: In Progress = Fix Released

** Changed in: hundredpapercuts
 Assignee: Vanderson M. do Rosario (vandersonmr) = (unassigned)

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

Title:
  Save screenshot dialog window has wrong focus

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

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

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty

2014-03-21 Thread Norbert
I reported separate bug about making screenshots to clipboard in Unity
session - this is bug 1295592.

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

Title:
  Unable to make screenshot with PrintScreen key in Unity session in
  Trusty

Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot with Print Screen keyboard button.

  The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and 
desired screenshot is not saved in ~/Pictures.
  Tested in guest and normal sessions.

  Please fix this bug. Do not forget about Alt+PrintScreen,
  Ctrl+PrintScreen and Ctrl+Shift+PrintScreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 20 19:40:24 2014
  DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Sony Corporation Device [104d:907a]
  InstallationDate: Installed on 2013-10-20 (123 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Sony Corporation VPCF13Z1R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF13Z1R
  dmi.product.version: C607OEHZ
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3
  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: Thu Feb 20 19:32:11 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.0-1ubuntu6
  xserver.video_driver: nouveau

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

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


[Desktop-packages] [Bug 1295584] Re: Belgian keyboard-layout is indicated as german-belgian

2014-03-21 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1295584

** Tags added: iso-testing

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

Title:
  Belgian keyboard-layout is indicated as german-belgian

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Live-session. Change keyboard-layout to Belgian.
  Reset ibus-keyboard-indicator

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Fri Mar 21 10:22:22 2014
  LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140320)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Hongbo Zhu
** Information type changed from Public Security to Public

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white

2014-03-21 Thread Matthias Niess
Can we please re-open this bug? There is no released fix that ever
worked for me. I'm on 14.04 development, fresh install and I still
experience this bug following the original steps to reproduce:

- minimize window
- show scale (super+w)
- hide scale (super+w)
- click on window in launcher

- black empty window.

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

Title:
  [nvidia] Windows appear blank white

Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: compiz

  When switching focus from one window to another, the target window may
  become blank. See the attached screenshot, where I opened two gnome-
  terminals and clicked on their titlebars alternately - the issue was
  triggered after about 5-10 clicks. I've had this happen on other
  appications too, e.g. software-centre, empathy, etc.

  HOW TO REPRODUCE:
  1. Minimize a window
  2. Initiate Scale and deactivate it again (press Super+W to show all windows 
and then press it again to go back to normal)
  3. Click the window icon on the launcher to maximize it again.
  4. The window contents will be white or black depending on the Ubuntu version

  WORKAROUND:
  Uncheck CCSM - Ubuntu Unity Plugin - Switcher - Show live previews of 
windows in the Switcher. Side-effect: scale doesn't show minimized windows.

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

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


[Desktop-packages] [Bug 1286395] Re: package thunderbird-locale-en-gb 1:24.3.0+build2-0ubuntu0.13.10.1 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it

2014-03-21 Thread Mark van Jaarsveld
Ubuntu 13.10

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

Title:
  package thunderbird-locale-en-gb 1:24.3.0+build2-0ubuntu0.13.10.1
  failed to install/upgrade: Package is in a very bad inconsistent state
  - you should  reinstall it before attempting configuration.

Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  Ubuntu 13:10

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: thunderbird-locale-en-gb 1:24.3.0+build2-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.5-0ubuntu2.2
  AptOrdering:
   python-setuptools: Install
   python-pip: Install
   thunderbird-locale-en-gb: Configure
   python-setuptools: Configure
   python-pip: Configure
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  markvanjaarsveld   1862 F pulseaudio
   /dev/snd/controlC1:  markvanjaarsveld   1862 F pulseaudio
   /dev/snd/controlC0:  markvanjaarsveld   1862 F pulseaudio
  BuildID: 20140210221129
  Channel: Unavailable
  Date: Sat Mar  1 00:52:19 2014
  DuplicateSignature: 
package:thunderbird-locale-en-gb:1:24.3.0+build2-0ubuntu0.13.10.1:Package is in 
a very bad inconsistent state - you should  reinstall it before attempting 
configuration.
  ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-25 (156 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  IpRoute:
   default via 192.168.1.1 dev wlan1  proto static 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.129  
metric 9
  MarkForUpload: True
  NoProfiles: True
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird-locale-en-gb 1:24.3.0+build2-0ubuntu0.13.10.1 
failed to install/upgrade: Package is in a very bad inconsistent state - you 
should  reinstall it before attempting configuration.
  UpgradeStatus: Upgraded to saucy on 2014-01-09 (50 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/03/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0WG261
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd02/03/2006:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0WG261:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM051
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Franz Koessler
My system is ubuntu 12.04.4 GNU/Linux 3.5.0-47-generic i686 .
Errors started after a system update...

Here's what happens when I try to install libgdk-pixbuf2.0-0:

sudo apt-get install --reinstall libgdk-pixbuf2.0-0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/194 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 1093567 files and directories currently installed.)
Preparing to replace libgdk-pixbuf2.0-0 2.26.1-1 (using 
.../libgdk-pixbuf2.0-0_2.26.1-1_i386.deb) ...
Unpacking replacement libgdk-pixbuf2.0-0 ...
Setting up libgdk-pixbuf2.0-0 (2.26.1-1) ...
Segmentation fault
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295605] [NEW] Left mouse button not working

2014-03-21 Thread Mark Abrahams
Public bug reported:

The left mouse button stopped working a few days ago - was working fine
before then.  Tried two different mice.  Left mouse button doesn't work
on either.  Changed mouse settings (Settings - Mouse and Touchpad) to
left-handed mouse.  Button functionality was swapped, but left button
still didn't work.  Tried Unity and Xfce, left button not working on
either.  Rebooting didn't fix the fault.  Using Ubuntu 13.10.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Mar 21 22:59:02 2014
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.2.16, 3.11.0-13-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-17-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2054]
InstallationDate: Installed on 2013-11-21 (119 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:5322): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/sessions': No such file or directory
 
 ** (lightdm-gtk-greeter:5322): WARNING **: Failed to load user image: Failed 
to open file '/home/mark/.face': No such file or directory
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:4476): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/sessions': No such file or directory
 
 ** (lightdm-gtk-greeter:4476): WARNING **: Failed to load user image: Failed 
to open file '/home/mark/.face': No such file or directory
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=9c16f807-f912-445c-8800-a8a2ce711f7c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: WYLPT10H.86A.0018.2013.0918.2135
dmi.board.name: D54250WYK
dmi.board.vendor: Intel Corporation
dmi.board.version: H13922-302
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0018.2013.0918.2135:bd09/18/2013:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-302:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Mar 21 22:43:33 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech Logitech BT Mini-Receiver KEYBOARD, id 9
 inputLogitech Logitech BT Mini-Receiver KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 877 
 vendor SAM
xserver.version: 2:1.14.5-1ubuntu2~saucy1

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


** Tags: amd64 apport-bug saucy ubuntu

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

Title:
  Left mouse button not working

Status in “xorg” package in Ubuntu:
  New

Bug description:
  The left mouse button stopped working a few days ago - was working
  fine before then.  Tried two different mice.  Left mouse button
  doesn't work on either.  Changed mouse settings (Settings - Mouse and
  Touchpad) to left-handed mouse.  Button functionality was swapped, but
  left button still didn't work.  Tried Unity and Xfce, left button not
  working on either.  Rebooting didn't fix the fault.  Using Ubuntu
  13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: 

[Desktop-packages] [Bug 1295557] Re: Crashes if indicator-sound is not installed

2014-03-21 Thread Sebastien Bacher
Right, confirmed, that's not the only indicator, I'm going to add those
to depends

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

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

** Summary changed:

- Crashes if indicator-sound is not installed
+ Needs to depends on the indicators it's controling

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

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

Title:
  Needs to depends on the indicators it's controling

Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  If indicator-sound is not installed, the command unity-control-center
  sound will crash with  Settings schema
  'com.canonical.indicator.sound' is not installed and then a  SIGTRAP.

  Either unity-control-center should hard depend on indicator-sound or
  unity-control-center needs to handle the absense of this schema.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 09:31:26 2014
  InstallationDate: Installed on 2013-11-04 (136 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Desktop-packages] [Bug 1295335] Re: Online Accounts: icons are absent for some of the items of the Google account

2014-03-21 Thread Sebastien Bacher
** Package changed: unity-control-center (Ubuntu) = gnome-control-
center-signon (Ubuntu)

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

Title:
  Online Accounts: icons are absent for some of the items of the Google
  account

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

Bug description:
  This is a small visual defect. In System Settings - Online Accounts,
  in the list of applications to integrate with Google account, there
  are icons for Empathy, Shotwell, Photos and Google Drive. But there
  are no icons for the list items which appeared here recently in 14.04:
  GMail, Google Contacts, Google Calendar.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 23:23:33 2014
  InstallationDate: Installed on 2014-01-27 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Desktop-packages] [Bug 1295557] Re: Needs to depends on the indicators it's controling

2014-03-21 Thread Launchpad Bug Tracker
** Branch linked: lp:~seb128/unity-control-center/depends-on-indicators

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

Title:
  Needs to depends on the indicators it's controling

Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  If indicator-sound is not installed, the command unity-control-center
  sound will crash with  Settings schema
  'com.canonical.indicator.sound' is not installed and then a  SIGTRAP.

  Either unity-control-center should hard depend on indicator-sound or
  unity-control-center needs to handle the absense of this schema.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 09:31:26 2014
  InstallationDate: Installed on 2013-11-04 (136 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Desktop-packages] [Bug 1294578] Re: [ffe/uife] Match the display settings checkbox

2014-03-21 Thread Sebastien Bacher
** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = High

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

Title:
  [ffe/uife] Match the display settings checkbox

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

Bug description:
  Here are some notes on the
  
https://code.launchpad.net/~hikiko/unity-control-center/u-c-c.checkbox-for-app-scaling/+merge/211681
 MP:

  After we introduced the HiDPI changes and the per-monitor Unity
  scaling factor (ui-scale gsetting) there was the following problem,
  discussed at UDS:

  The Qt and Gnome applications would use the scaling-factor and text-
  scaling-factor for scaling and not our ui-scale, so their window
  contents would have a different size than their decorations, the menus
  and the launcher. Another problem was that the Gnome text-scaling-
  factor and scaling-factor are settings for the whole desktop whereas
  ui-scale is per monitor and there would be some inconsistency anyway
  when multiple monitors are plugged in.

  So, as a quick partial solution to the problem, we promised to add a
  checkbox in each monitor's settings that sets the scaling-factor and
  text-scaling factor values in accordance with the ui-scale for that
  monitor when it's checked.

  This way, the user will see the same size in Unity and the Gtk/Qt
  applications in  1 monitor if he checks the checkbox of a monitor.

  To allow this, we had to introduce a new gsetting that stores the
  selected monitor name here: https://code.launchpad.net/~hikiko
  /gsettings-ubuntu-touch-schemas/gsettings-ubuntu-touch-schemas
  .selected-monitor/+merge/211680.

  Of course this whole feature could be better designed so that the user
  receives more visual feedback. We discussed it with the designers team
  and they gave us a much better design that will be used in the future:
  https://wiki.ubuntu.com/BrightnessAndDisplays#Displays (credits
  Matthew Paul Thomas)

  For the moment we will just use the checkbox to meet the deadline
  which is in a few days, as we promised at UDS.

  -
  Some notes  in the logic:
  -

  First of all, here is the way we set the scaling-factor and text-
  scaling factor to be in accordance with the ui-scale. The idea is
  Marco Trevisan's and I paste his algorithm as it was in our Unity team
  document:

   Scaling the World…
   So, after scaling unity we should care also about the apps… There are still 
some troubles to get the best experience:
   Applications doesn’t care about the per-monitor scaling
   Gtk2 and Qt (using a gtk2 rendering style) apps only care about scaling 
factor, so there’s not much we can do with them
   Gtk3 apps support integer UI scaling only
   [...]
   When that option is true we set the gdk-interface-scaling factor to match 
the integer part of maximum scaling factor of the
   attached display, while we set the text-scaling-factor to a value that 
multiplied for the interface scaling factor will result our
   scaling factor (this will apply to both Gtk and Qt applications)
   [...]
   So, our monitor has the scaling factor of 2.25, we set:
- scaling-factor: 2
- text-scaling-factor: 2.25 / 2 = 1.125
  (In the above example 2.25 is the ui-scale, the Unity scaling factor that is 
per monitor)

  How the checkbox works:
  ---

  The first time the user runs the u-c-c (which is after a fresh
  installation) the checkbox appears to be checked in the primary
  monitor and we set the scaling-factor, text-scaling-factor (Gnome) to
  match the ui-scale (Unity), so that the user can have a good visual
  experience in his primary monitor. We also store the primary monitor
  as selected-display in our gsetting to remember this choice.

  Every other time:
  Unless if the scaling factors have been changed from a non u-c-c application 
(see below for this case), the checkbox appears unchecked for every monitor 
except of the selected that is checked. When the user selects a new monitor, 
u-c-c remembers his choice and the new selection appears checked whereas all 
the others are unchecked. The selected monitor is stored in the 
selected-display gsetting in gsettings-ubuntu-schemas.

  What if the scaling factors change from outside u-c-c?
  
-
  Every time we update the checkbox status (checked or unchecked) we not only 
check the selected-monitor's value but the consistency of the 3 scaling factors.

  In other words, if:

  scaling-factor * text-scaling-factor != ui-scale +- small_ERROR for
  the ui-scale of the selected monitor,

  and

  the selected-display setting matches the selected monitor,

  it means that either the text-scaling-factor or the scaling-factor
  have 

[Desktop-packages] [Bug 1295592] Re: Unable to make screenshot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session in Trusty

2014-03-21 Thread Sebastien Bacher
Thank you for your bug report. I can't confirm that, using ctrl-
printscreen does the screenshot animation and I can paste the image in
e.g inkscape

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

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

Title:
  Unable to make screenshot to clipboard with Ctrl+PrintScreen,
  Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session
  in Trusty

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

Bug description:
  In Trusty with all installed updates it is not possible to make
  ScreenShot to clipboard with Ctrl+PrintScreen,
  Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keyboard buttons.

  Steps to reproduce:
  1. Install Ubuntu 14.04.
  2. Login to Unity session.
  3a. Try to make screenshot of the whole desktop with Ctrl+PrintScreen
  3b. Try to make screenshot of active window with Ctrl+Alt+PrintScreen
  3c. Try to make screenshot of selected area with Ctrl+Shift+PrintScreen

  Expected results:
  * Corresponding screenshot is saved in clipboard and may be inserted to other 
applications with Ctrl+V.

  Actual results:
  * Screenshot is not saved to clipboard.

  
  Notes:
  1. This bug is complementary to bug 1282649 (Unable to make screenshot with 
PrintScreen key in Unity session in Trusty).
  2. I use default shortcuts Super+Space and Shift+Super+Space for keyboard 
layout switching.
  3. I did some tests (see my Google Docs table - 
https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHpGYVlMZ2JuYXdXdEtmUi1QbGxsYXcusp=sharing).
 In Ubuntu 12.04 (with no matter Unity or GNOME sessions) the full working list 
of shortcuts used for screenshoting is as follows: PrintScreen, 
Alt+PrintScreen, Ctrl+PrintScreen, Shift+PrintScreen, 
Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen. All these hotkeys work 
normally in 14.04 too on GNOME FlashBack session (Compiz and Metacity).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:29:53 2014
  InstallationDate: Installed on 2014-03-17 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140316)
  SourcePackage: unity-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity-settings-daemon.log: (gnome-terminal:2677): GLib-GIO-CRITICAL 
**: g_settings_get: the format string may not contain '' (key 
'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call 
will probably stop working with a future version of glib.

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

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


[Desktop-packages] [Bug 1175601] Re: Two Chromium background instances and a browser window open on boot without my permission

2014-03-21 Thread Thaddäus Tintenfisch
Please clear the session cache (Settings Manager  Session and Startup 
Session) and make sure that the startup launcher for Chromium is
deactivated. Does Chromium still launch automatically after clearing the
cache and restarting the session?

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

Title:
  Two Chromium background instances and a browser window open on boot
  without my permission

Status in “chromium-browser” package in Ubuntu:
  Invalid
Status in “xfce4-session” package in Ubuntu:
  New

Bug description:
  When I log into my user session (type in my password on the login
  prompt after boot), Chromium auto-starts, and two instances of its
  background process automatically open: per the attached image, two
  Chromium icons appear in the top bar. Also, an instance of the browser
  appears in the middle of the screen.

  When this happens, I get an inconsistent browsing experince in
  Chromium, where it is randomly unable to connect to web sites or
  download components referenced by web pages (e.g., CSS files, JS
  files, etc.).

  I can fix by closing the browser and also both the background
  sessions, then restarting Chromium.

  I have never configured Chromium to start up when I log into my
  session. This has happened without my explicit permission or consent.

  If I go to Session and Startup's Application Autostart tab, Chromium
  appears in the list and is checked. I did not configure this.

  Expected behavior: No part of Chromium opens at all, not even a
  background process, until I launch the browser for the first time.

  I am using a copy of Xubuntu 13.04 that was upgraded from Xubuntu
  12.10. This problem was happening for several weeks back with Xubuntu
  12.10, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: chromium-browser 25.0.1364.160-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May  2 08:18:13 2013
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-01-02 (119 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to raring on 2013-04-30 (1 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'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n'

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

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


[Desktop-packages] [Bug 1293634] Re: Unable to mount Disco CD-R empty

2014-03-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks! 

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

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New = Incomplete

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

Title:
  Unable to mount Disco CD-R empty

Status in “unity-settings-daemon” package in Ubuntu:
  Incomplete

Bug description:
  i have problems with the empty cd - dvd when open the maximum capacity
  is 22 Kb for empty cd or dvd so when i open the disks creator it does
  not give me the chance to wright on them i am using 14.04 the message
  come out spontaneously when CD- R is inserted I try to use image
  creator the cd is virgin and the same story is for DVD-R

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 17 20:53:54 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-fallback-mount-helper
  InstallationDate: Installed on 2014-03-12 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301)
  SourcePackage: unity-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging

2014-03-21 Thread Digulla-hepe
Related bug in Eclipse's Bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073

** Bug watch added: Eclipse bugs #421073
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073

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

Title:
  After upgrading to saucy, eclipse crashes in
  gtk_tree_view_get_background_area+0x8a while debugging

Status in “gtk+2.0” package in Ubuntu:
  Confirmed

Bug description:
  to reproduce, I open the Variables view in eclipse and step through
  the application. the eclipse jvm crashes with:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912
  #
  # JRE version: 7.0_21-b11
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libgtk-x11-2.0.so.0+0x2202aa]  gtk_tree_view_get_background_area+0x8a
  #
  # Core dump written. Default location: /home/juergen/core or core.11567
  #
  # An error report file with more information is saved as:
  # /home/juergen/hs_err_pid11567.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  This did not happen in ubuntu 13.04.

  using KDE as a desktop (installed ubuntu, installed kde packages)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Tue Sep 10 07:25:17 2013
  InstallationDate: Installed on 2010-11-24 (1020 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/+subscriptions

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


[Desktop-packages] [Bug 1295622] Re: compiz crashed with SIGSEGV in frame_device_get_property()

2014-03-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1200270 ***
https://bugs.launchpad.net/bugs/1200270

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035544/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035547/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035556/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035558/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035559/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035560/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1295622/+attachment/4035561/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1200270

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in frame_device_get_property()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Compiz crashed under high load when upgrading packages.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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: Fri Mar 21 11:56:30 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-18-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-18-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-18-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0493]
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Device [1028:1493]
  MachineType: Dell Inc. Latitude E6420
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-18-generic 
root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f112d3a5570:cmpl   $0x9,(%rdi)
   PC (0x7f112d3a5570) ok
   source $0x9 ok
   destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libframe.so.6
   frame_device_get_property () from /usr/lib/x86_64-linux-gnu/libframe.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
  Title: compiz crashed with SIGSEGV in frame_device_get_property()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo 
vboxusers
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140310-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Desktop-packages] [Bug 1291608] Re: No user icons provided / user icons not used

2014-03-21 Thread Sebastien Bacher
** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  No user icons provided / user icons not used

Status in Ayatana Design:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  GNOME Control Centre provided a default set of user icons so users
  could pick an icon for themself. Since we've migrated to Unity Control
  Centre we no longer have any default icons.

  The options seem to be:
  1. Split the icons out of gnome-control-center and ship them with both GNOME 
Control Centre and Unity Control Centre.
  2. Provide a set of Ubuntu themed icons, e.g. the Ubuntu pictograms [1].
  3. Remove support from Unity Control Centre for user icons since they're not 
actually used anywhere.

  What does design think about option 3? I note the design [2] shows
  icons but it doesn't indicate if they're used anywhere. If not option
  3, can we get a good set of pictograms to use?

  [1] 
http://design.canonical.com/2011/06/whats-round-and-sticky-and-how-you-can-make-some/
  [2] https://wiki.ubuntu.com/UserAccounts

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

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

2014-03-21 Thread Venco
Same problem on Ubuntu 12.04/64 with LibreOffice 4.2.1.1 (download from
LO site)

-- 
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:
  Confirmed

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 1253620]

2014-03-21 Thread sophie
*** Bug 75055 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/1253620

Title:
  Can't open a LibreOffice native file via CIFS share

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

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 1291608] Re: No user icons provided / user icons not used

2014-03-21 Thread Launchpad Bug Tracker
** Branch linked: lp:~seb128/unity-control-center/recommends-shared-data

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

Title:
  No user icons provided / user icons not used

Status in Ayatana Design:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  GNOME Control Centre provided a default set of user icons so users
  could pick an icon for themself. Since we've migrated to Unity Control
  Centre we no longer have any default icons.

  The options seem to be:
  1. Split the icons out of gnome-control-center and ship them with both GNOME 
Control Centre and Unity Control Centre.
  2. Provide a set of Ubuntu themed icons, e.g. the Ubuntu pictograms [1].
  3. Remove support from Unity Control Centre for user icons since they're not 
actually used anywhere.

  What does design think about option 3? I note the design [2] shows
  icons but it doesn't indicate if they're used anywhere. If not option
  3, can we get a good set of pictograms to use?

  [1] 
http://design.canonical.com/2011/06/whats-round-and-sticky-and-how-you-can-make-some/
  [2] https://wiki.ubuntu.com/UserAccounts

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

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


[Desktop-packages] [Bug 1294767] Re: Need upgrading for nv110 (maxwell gtx 750)

2014-03-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New = Confirmed

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

Title:
  Need upgrading for nv110 (maxwell gtx 750)

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  Testcase:

  i was succesfully using that driver with an old 8500gt nvidia card plugged 
within vga.
  Upgrading to a new gtx 750 card plugged within hdmi 1.3, nouveau cant be used 
because the bios process is stopped at:

   fb: conflicting fb hw usage nouveaufb ... 

  So to support that gtx750 card, i've installed nvidia 334.21 from joe-
  yasi/xorg-related ppa, and blacklisted vga16fb, nvidiafb, rivafb and
  rivatv inside /etc/modprobe.d/blacklist.conf file. Note that the
  actual Trusty archive only propose the 331 driver, so adding the 334
  asap should be a good move too.

  Results about these tweaks:
  - the display is usable, but, the displayed font quality is worst than before 
(it was superb) ; (mesa was also update to 10.2, so maybe related ?)
  - the lcd display is a 22 1920x1080, but it is found as a 42 1920x1080 by 
both the  kernel and nvidia (nouveau was working fine with the 8500 gt). So i 
need to downsized now to 1680 to get the menu/topbar/buttons; otherwise they 
are not seen.

  To resume:
  - need nouveau working with nv110 family
  - need 334.21 driver added to archive

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  334.21  Thu Feb 27 15:04:33 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Mar 19 18:03:50 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-18-generic, i686: installed
   nvidia-334, 334.21, 3.13.0-18-generic, i686: installed
   nvidia-334-uvm, 334.21, 3.13.0-18-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:362e]
  InstallationDate: Installed on 2013-10-25 (145 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20131021.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=83f51130-24a6-4486-9284-f8d6700df293 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140319-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140319-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Mar 19 17:50:35 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB RECEIVER MOUSE, id 8
   input 

[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Valentin Clavreul
I am affected too, but didn't run a system upgrade (current : 12.04)

@chrisliaw : my gnome totally broke too, but you can partially restore
some functionalities  by switching to another theme than defaut (I am
now mainly with Radiance). But PNG are still missing, and some apps
can't even run (like meld).

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1293659] Re: Unity locks screen after unlocking

2014-03-21 Thread Stephen M. Webb
** Tags added: lockscreen

** Also affects: unity
   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/1293659

Title:
  Unity locks screen after unlocking

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  After locking the computer I wanted to unlock the computer again. Once
  entering the desktop the screen gets locked without doing anything
  after several seconds. Unlocking for the second time gives no problem.
  However, when locking the screen again, the same problem occurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140313-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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 Mar 17 17:26:30 2014
  DistUpgraded: 2014-03-14 17:04:08,335 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed
   virtualbox, 4.3.6, 3.11.0-18-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-06-15 (275 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  JockeyStatus:
   kmod:nvidia_304_updates - NVIDIA legacy binary driver - version 304.117 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_331 - NVIDIA binary driver - version 331.38 (Proprietary, 
Disabled, Not in use)
   kmod:nvidia_331_updates - nvidia_331_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA legacy binary driver - version 304.117 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=4e34beb2-745f-4a18-8d61-eff5a31a069d ro quiet splash pcie_aspm=force
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-14 (3 days ago)
  dmi.bios.date: 07/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.03
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.03:bd07/25/2011:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140310-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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: Mon Mar 17 12:44:06 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Francisco Augusto
Ubuntu 12.04.4 x86_64, same problem after last upgrade.

Downgrade of librsvg2 to 2.36.1-0ubuntu1 didn't work

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1200270] Re: compiz crashed with SIGSEGV in oif::frame::Value::GetValue()

2014-03-21 Thread Sebastien Bacher
** Information type changed from Private to Public

** Package changed: compiz (Ubuntu) = unity (Ubuntu)

** Changed in: unity (Ubuntu)
   Importance: Medium = High

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

** Changed in: unity
   Importance: Undecided = High

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

Title:
  compiz crashed with SIGSEGV in oif::frame::Value::GetValue()

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I havent found out every bug correspondig to this crash notification
  yet, but e.g. the software center is also crashing after starting
  it/is not working properly.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: compiz-core 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 11 16:58:52 2013
  DistUpgraded: 2013-07-10 10:00:16,415 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3690/3850] 
[1002:9505] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2003]
  InstallationDate: Installed on 2013-04-02 (99 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic 
root=UUID=0208EF1508EF068F loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f6ed62a4570:cmpl   $0x9,(%rdi)
   PC (0x7f6ed62a4570) ok
   source $0x9 ok
   destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libframe.so.6
   frame_device_get_property () from /usr/lib/x86_64-linux-gnu/libframe.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
  Title: compiz crashed with SIGSEGV in frame_device_get_property()
  UpgradeStatus: Upgraded to saucy on 2013-07-10 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.45-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu1.1
  xserver.bootTime: Thu Jul 11 16:58:29 2013
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.1-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1295635] [NEW] when I start gnome-disk-utility, the top part part of its window is under the top bar of unity

2014-03-21 Thread SteliosSk
Public bug reported:

As described, in ubuntu trusty, when I start gnome-disk-utlity, the top
part of its window is under the top bar of unity. Please see picture at
https://dl.dropboxusercontent.com/u/19393967/gnome-disk-utility.png

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-disk-utility 3.10.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 21 13:24:38 2014
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2014-03-07 (13 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
ProcEnviron:
 LANGUAGE=el
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=el_GR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-disk-utility (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: gnome-disk-utility.png
   
https://bugs.launchpad.net/bugs/1295635/+attachment/4035605/+files/gnome-disk-utility.png

** Description changed:

- As described, in ubuntu trusty, when I start nome-disk-utlity, the top
- par tof its window is under the top bar of unity. Please see picture at
+ As described, in ubuntu trusty, when I start gnome-disk-utlity, the top
+ part of its window is under the top bar of unity. Please see picture at
  https://dl.dropboxusercontent.com/u/19393967/gnome-disk-utility.png
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:24:38 2014
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-03-07 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  ProcEnviron:
-  LANGUAGE=el
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=el_GR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=el
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=el_GR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  when  I start gnome-disk-utility, the top part part of its window is
  under the top bar of unity

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  As described, in ubuntu trusty, when I start gnome-disk-utlity, the
  top part of its window is under the top bar of unity. Please see
  picture at https://dl.dropboxusercontent.com/u/19393967/gnome-disk-
  utility.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:24:38 2014
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-03-07 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  ProcEnviron:
   LANGUAGE=el
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1171342] Re: mouse scroll wheel not working in gedit System Monitor

2014-03-21 Thread Sandro Rettinger
I see the same issue after upgrading (yes, just recently, I'm a slacker)
to 13.10 from 13.04, on evince and nautilus.  I too am running XFCE.
(Specifically 4.10)

Hovering over those applications and using the scroll wheel still raises
them, just as if I'd clicked on them, but does not scroll them.

click scrolling (as described above by Willy) does cause the
applications in question to scroll.  The click functionality of my
scrollwheel is normal unix middle button behaviour.

I will try the PPA listed above and report back.

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

Title:
  mouse scroll wheel not working in gedit  System Monitor

Status in GTK+ GUI Toolkit:
  Fix Released
Status in X.Org X server:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Open System Monitor

  Using mouse wheel button - scroll up or down - list does not move. If
  Press the wheel button and then scroll up or down the list will move.

  This also occurs in Gedit. Firefox and Terminal work as expected. IE
  do not need to press the wheel and then scroll

  Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
  Description:  Ubuntu 13.04
  Release:  13.04

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

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


[Desktop-packages] [Bug 1284134] Re: Xorg crash

2014-03-21 Thread Jakob Bornecrantz
Did you fully upgrade the VM?

Tho I no longer need to press enter to close emacs,
could this have something to do with it?

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

Title:
  Xorg crash

Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  I use the Nouveau theme of Gnome-Do, and I bind its invocation to Alt-
  Ctrl-Space.  Invoking Gnome-Do crashes X and leaves me back at the
  login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-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
  CurrentDmesg:
   [   13.651845] init: plymouth-stop pre-start process (1605) terminated with 
status 1
   [   13.678625] dm-0: WRITE SAME failed. Manually zeroing.
  Date: Mon Feb 24 09:11:37 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-12-06 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  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-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: Mon Feb 24 09:10:52 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: vmware

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

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


[Desktop-packages] [Bug 1295639] [NEW] move to workspace loses track of window entirely

2014-03-21 Thread James Hunt
Public bug reported:

Moving a window to another workspace using the context menu options
Move to Workspace right or Move to Another Workspace causes unity to
lose track of the window entirely - it disappears never to return.

Note: the processes associated with the windows *are* still running as
shown by xlsclients.

Moving the windows manually to another workspace (by shifting the window
almost off the screen to the right or bottom, then changing to the
appropriate workspace and pulling the half-obscured window into that
workspace) works.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140318-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Mar 21 11:36:12 2014
InstallationDate: Installed on 2010-10-21 (1247 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago)

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


** Tags: apport-bug i386 trusty

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

Title:
  move to workspace loses track of window entirely

Status in “unity” package in Ubuntu:
  New

Bug description:
  Moving a window to another workspace using the context menu options
  Move to Workspace right or Move to Another Workspace causes unity
  to lose track of the window entirely - it disappears never to return.

  Note: the processes associated with the windows *are* still running as
  shown by xlsclients.

  Moving the windows manually to another workspace (by shifting the
  window almost off the screen to the right or bottom, then changing to
  the appropriate workspace and pulling the half-obscured window into
  that workspace) works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Mar 21 11:36:12 2014
  InstallationDate: Installed on 2010-10-21 (1247 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago)

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

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


[Desktop-packages] [Bug 1291170] Re: too many Tomboy Notes open in the panel and can't create a new note

2014-03-21 Thread David Callé
*** This bug is a duplicate of bug 1277802 ***
https://bugs.launchpad.net/bugs/1277802

** This bug has been marked a duplicate of bug 1277802
   When the key input to dash, tomboy is started more than once.

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

Title:
  too many Tomboy Notes open in the panel and can't create a new note

Status in “tomboy” package in Ubuntu:
  New

Bug description:
  after i update to ubuntu 14.04 LTS when i start my system and open
  dashboard, too many tomboy notes open in the panel and i cant even
  create a new note in it but can edit the previous notes.

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

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


[Desktop-packages] [Bug 1291608] Re: No user icons provided / user icons not used

2014-03-21 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/trusty-proposed/gnome-control-center

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

Title:
  No user icons provided / user icons not used

Status in Ayatana Design:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  GNOME Control Centre provided a default set of user icons so users
  could pick an icon for themself. Since we've migrated to Unity Control
  Centre we no longer have any default icons.

  The options seem to be:
  1. Split the icons out of gnome-control-center and ship them with both GNOME 
Control Centre and Unity Control Centre.
  2. Provide a set of Ubuntu themed icons, e.g. the Ubuntu pictograms [1].
  3. Remove support from Unity Control Centre for user icons since they're not 
actually used anywhere.

  What does design think about option 3? I note the design [2] shows
  icons but it doesn't indicate if they're used anywhere. If not option
  3, can we get a good set of pictograms to use?

  [1] 
http://design.canonical.com/2011/06/whats-round-and-sticky-and-how-you-can-make-some/
  [2] https://wiki.ubuntu.com/UserAccounts

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

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


[Desktop-packages] [Bug 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpos

2014-03-21 Thread Reinhard Tartler
I believe this is effectively a duplicate of #1277552

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

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libpostproc” package in Ubuntu:
  New

Bug description:
   -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 00:57:47 2014
  Dependencies:
   gcc-4.9-base 4.9-20140222-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140222-0ubuntu1
   multiarch-support 2.19-0ubuntu2
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-12-12 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to 
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Marc Deslauriers
Is someone able to get a backtrace of the segfault?

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Francisco Augusto
(gdb) run
Starting program: /usr/bin/gdk-pixbuf-query-loaders 
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Program received signal SIGSEGV, Segmentation fault.
0x77385616 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x77385616 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x77914189 in g_str_equal () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x779138af in g_hash_table_lookup () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7793198f in g_quark_from_static_string () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x75b428bf in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x77de9306 in ?? () from /lib64/ld-linux-x86-64.so.2
#6  0x77de93df in ?? () from /lib64/ld-linux-x86-64.so.2
#7  0x77dedada in ?? () from /lib64/ld-linux-x86-64.so.2
#8  0x77de9176 in ?? () from /lib64/ld-linux-x86-64.so.2
#9  0x77ded31a in ?? () from /lib64/ld-linux-x86-64.so.2
#10 0x770faf26 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#11 0x77de9176 in ?? () from /lib64/ld-linux-x86-64.so.2
#12 0x770fb52f in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#13 0x770fafc1 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2
#14 0x77bd76fc in g_module_open () from 
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
#15 0x004010a0 in ?? ()
#16 0x00400e7a in ?? ()
#17 0x7731f76d in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#18 0x00400f39 in ?? ()
#19 0x7fffe378 in ?? ()
#20 0x001c in ?? ()
#21 0x0001 in ?? ()
#22 0x7fffe628 in ?? ()
#23 0x in ?? ()

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295335] Re: Online Accounts: icons are absent for some of the items of the Google account

2014-03-21 Thread Alberto Mardegan
Adding design team: we need icons for these services.

** Also affects: gnome-control-center-signon
   Importance: Undecided
   Status: New

** Also affects: ayatana-design
   Importance: Undecided
   Status: New

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

Title:
  Online Accounts: icons are absent for some of the items of the Google
  account

Status in Ayatana Design:
  New
Status in Online Accounts: GNOME Control Center:
  New
Status in “gnome-control-center-signon” package in Ubuntu:
  New

Bug description:
  This is a small visual defect. In System Settings - Online Accounts,
  in the list of applications to integrate with Google account, there
  are icons for Empathy, Shotwell, Photos and Google Drive. But there
  are no icons for the list items which appeared here recently in 14.04:
  GMail, Google Contacts, Google Calendar.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 23:23:33 2014
  InstallationDate: Installed on 2014-01-27 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Desktop-packages] [Bug 1064461] Re: [EMU10K1 - SB Live! Value [CT4871], playback] When changing volume sound stutters in Rythmbox or other applications

2014-03-21 Thread Raymond
** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  [EMU10K1 - SB Live! Value [CT4871], playback]  When changing volume
  sound stutters in Rythmbox or other applications

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

Bug description:
  This is on a fresh install of Ubuntu 12.04.1 LTS 
  PulseAudio 1:1.1-0ubuntu15.1
  Generally if I change volume in the application or at the main volume 
control, volume does change by sound stutters badly.  Eventually it will stop 
stuttering and I can force it to stop by moving teh volume control slightly 
back from where I initially set it. (turn it down or up a little from where I 
stopped).  Also, when I close RythmBox or other applications playing sound, the 
sound will repeat itself until the volume control is moved or after a few 
seconds it may stop stuttering.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  todd   2894 F pulseaudio
   /dev/snd/controlC2:  todd   2894 F pulseaudio
   /dev/snd/controlC0:  todd   2894 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Live'/'SB Live! Value [CT4871] (rev.7, serial:0x80321102) at 
0xcc00, irq 18'
 Mixer name : 'Cirrus Logic CS4297A rev 3'
 Components : 'AC97a:43525913'
 Controls  : 222
 Simple ctrls  : 42
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf9f78000 irq 22'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,10ec,0011'
 Controls  : 45
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Bt878'/'Brooktree Bt878 at 0xcfffe000, irq 19'
 Mixer name : 'Bt87x'
 Components : ''
 Controls  : 3
 Simple ctrls  : 5
  Date: Tue Oct  9 10:05:05 2012
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Live failed
  Symptom_Card: Bt878 Audio Capture - Brooktree Bt878
  Symptom_PulseAudioLog:
   
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [EMU10K1 - SB Live! Value [CT4871], playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MI-A78S-8209
  dmi.board.vendor: XFX
  dmi.board.version: Ver1.1
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/06/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnXFX:rnMI-A78S-8209:rvrVer1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Bill Bennert
Unable to get backtrace from apt-get process.

Backtrace of gdk-pixbuf-query-loaders:

$ gdb /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
(gdb) run
Starting program: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Program received signal SIGSEGV, Segmentation fault.
0x77385616 in ?? () from /lib/x86_64-linux-gnu/libc.so.6

(gdb) backtrace
#0  0x77385616 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x77914189 in g_str_equal () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x779138af in g_hash_table_lookup () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7793198f in g_quark_from_static_string () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x764148bf in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x77de9306 in ?? () from /lib64/ld-linux-x86-64.so.2
#6  0x77de93df in ?? () from /lib64/ld-linux-x86-64.so.2
#7  0x77dedada in ?? () from /lib64/ld-linux-x86-64.so.2
#8  0x77de9176 in ?? () from /lib64/ld-linux-x86-64.so.2
#9  0x77ded31a in ?? () from /lib64/ld-linux-x86-64.so.2
#10 0x770faf26 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#11 0x77de9176 in ?? () from /lib64/ld-linux-x86-64.so.2
#12 0x770fb52f in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
#13 0x770fafc1 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2
#14 0x77bd76fc in g_module_open () from 
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
#15 0x004010a0 in ?? ()
#16 0x00400e7a in ?? ()
#17 0x7731f76d in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#18 0x00400f39 in ?? ()
#19 0x7fffe618 in ?? ()
#20 0x001c in ?? ()
#21 0x0001 in ?? ()
#22 0x7fffe832 in ?? ()
#23 0x in ?? ()
(gdb)

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295064] Re: Release print job does nothing

2014-03-21 Thread Till Kamppeter
Please follow the instructions in the section CUPS error_log on
https://wiki.ubuntu.com/DebuggingPrintingProblems. Activate debug
logging as described and then do all steps for reproducing the bug as
you mentioned in the description. After that attach the resulting
error_log. Do not compress the file.

** Changed in: cups (Ubuntu)
   Status: New = Incomplete

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

Title:
  Release print job does nothing

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  When I right-click on a print job that is in the Held status and
  choose Release nothing happens. I would expect it to start printing
  almost immediately. I get the same result using the toolbar Play
  button. The job eventually releases itself after 5 minutes.

  The job goes into the held status usually because the printer isn't
  ready when I printed it (I rarely use my printer so it's normally
  turned off). However even after the printer is connected and shows as
  Idle in Settings-Printers and even prints new jobs while the old
  one is stuck in the held status, the release function does not work.

  It seems that the only option is to wait 5 minutes, or cancel the job
  and re-print. I'm sure that the release function used to work in older
  versions as I've had this configuration for years.

  I found the following steps reproduce the problem easily (turn
  networking on/off instead of the printer as it's a quicker and cleaner
  than waiting for printer to get its act together):

  1) Set up a network printer
  2) Make sure everything is working and you are able to print a page
  3) Turn off networking
  4) Attempt to print a page
  5) View it's status in the queue showing held (from the status icon)
  6) Turn on networking
  7) Try to release the job from (from the queue from the status icon)
  8) Observe nothing happens
  9) Print a differnt page
  10) Observe the new page prints immediately
  11) Wait for the original page to print after 5 minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5.2
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Mar 20 10:04:16 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-05-03 (320 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  Lpstat: device for HP-Officejet-6500-E709n: 
hp:/net/Officejet_6500_E709n?zc=dhcppc30
  MachineType: System manufacturer V-P5G45
  MarkForUpload: True
  Papersize: a4
  PpdFiles: HP-Officejet-6500-E709n: HP Officejet 6500 e709n, hpcups 3.13.9
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=1fb8697a-7ed6-41e1-9a44-8c3728862ad7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2014-02-10 (37 days ago)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Marc Deslauriers
Could you please run the following command, and paste the results:

$ dpkg -l | grep libglib

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295648] [NEW] Ubuntu detects a non-existing screen

2014-03-21 Thread Dominik Wiernicki
Public bug reported:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1244827

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
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: Fri Mar 21 13:20:06 2014
DistUpgraded: 2014-03-13 18:10:39,713 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.6, 3.11.0-18-generic, x86_64: installed
 virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0563]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:0563]
InstallationDate: Installed on 2014-02-02 (46 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: Dell Inc. Dell System Vostro 3460
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=310955f0-4f98-45bf-adaa-bca9bbeb73ee ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-03-13 (7 days ago)
dmi.bios.date: 05/17/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0WCY8Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/17/2013:svnDellInc.:pnDellSystemVostro3460:pvr:rvnDellInc.:rn0WCY8Y:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System Vostro 3460
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140310-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-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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 Mar 21 10:49:48 2014
xserver.configfile: default
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5233 
 vendor CMN
xserver.version: 2:1.15.0-1ubuntu7

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


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

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

Title:
  Ubuntu detects a non-existing screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1244827

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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: Fri Mar 21 13:20:06 2014
  DistUpgraded: 2014-03-13 18:10:39,713 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.11.0-18-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0563]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:0563]
  InstallationDate: Installed on 2014-02-02 (46 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Dell System Vostro 3460
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Valentin Clavreul
Yeah I have recovered my laptop ! (well an expert of my company did so)

I don't know how this is related but here are his steps :
* removed a ppa that I previously added 
(/etc/apt/sources.list.d/webupd8team-gvfs-libmtp-precise.list)
* reinstalled a few corresponding packages (gvfs, libglib2.0-0)
* reconfigure libgdk-pixbuf2.0-0

It seems libglib2.0-0 was causing the problem. I don't know if this will
be okay for most people, but it should help at least debug :-)

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1289515] Re: Sound volume resets after making a call

2014-03-21 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1292174] Re: [trusty] webapp launches, container remains blank

2014-03-21 Thread nicolas kleinklaus
I have exactly the same problem as in #6 comment. webapps open in new
forefox window (no with dedicated browser) and no Icon is displayed in
the Launcher

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

Title:
  [trusty] webapp launches, container remains blank

Status in WebApps: libunity:
  New
Status in Chromium extension: Unity Integration:
  New
Status in Firefox extension: Unity Integration:
  New
Status in Unity WebApps QML component:
  Triaged
Status in The Webapps-core project:
  New
Status in “libunity-webapps” package in Ubuntu:
  New
Status in “unity-chromium-extension” package in Ubuntu:
  New
Status in “unity-firefox-extension” package in Ubuntu:
  New
Status in “unity-webapps-qml” package in Ubuntu:
  New

Bug description:
  After installation of webapp via either chromium or firefox, attempt
  to launch webapp other than Amazon renders no page.

  Tested on unity-webapps-launchpad, unity-webapps-googleplus, unity-
  webapps-facebookmessenger.

  Expected result: webapp launches properly within container and
  corresponding web page displays.

  Actual result: webapp launches within container and remains blank, no
  web page displays.

  Example image attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1292174/+subscriptions

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


[Desktop-packages] [Bug 1295665] [NEW] changing resolution with menu or with xrandr command fails

2014-03-21 Thread Jaime Pérez
Public bug reported:

When changing resolution with menu or with xrandr command fails. Random
colors and figures appear on the screen. I have tried both xorg-ati and
fglrx drivers and the problem appears.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-18.38-lowlatency 3.13.6
Uname: Linux 3.13.0-18-lowlatency x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Mar 21 13:48:28 2014
DistUpgraded: 2014-03-07 12:48:53,211 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates, 13.350.1, 3.13.0-18-lowlatency, x86_64: installed
 virtualbox, 4.3.6, 3.13.0-17-lowlatency, x86_64: installed
 virtualbox, 4.3.6, 3.13.0-18-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244]
InstallationDate: Installed on 2014-02-08 (40 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: MSI MS-7640
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-lowlatency 
root=UUID=94224f17-82cd-44ee-91a4-2243806ae66c ro debug ignore_loglevel 
crashkernel=384M-:128M
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-03-07 (14 days ago)
dmi.bios.date: 10/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V19.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-GD65 (MS-7640)
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.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: MS-7640
dmi.product.version: 3.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.11+14.04.20140310-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-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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 Mar 21 13:46:31 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Optical Mouse MOUSE, id 8
 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 9
 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.0-1ubuntu7
xserver.video_driver: radeon

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


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

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

Title:
  changing resolution with menu or with xrandr command fails

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When changing resolution with menu or with xrandr command fails.
  Random colors and figures appear on the screen. I have tried both
  xorg-ati and fglrx drivers and the problem appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-lowlatency 3.13.6
  Uname: Linux 3.13.0-18-lowlatency x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 21 13:48:28 2014
  DistUpgraded: 2014-03-07 12:48:53,211 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.13.0-18-lowlatency, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-17-lowlatency, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-18-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced 

[Desktop-packages] [Bug 1289515] Re: Sound volume resets after making a call

2014-03-21 Thread Tanu Kaskinen
On Fri, 2014-03-21 at 10:27 +0100, David Henningsson wrote:
 In case a port has not yet been saved, which is e g often the case
 if a sink/source has only one port, reading volume/mute will be done
 without port, whereas writing volume/mute will be done with port.
 
 Work around this by setting a default port before the fixate hook,
 so module-device-restore can read volume/mute for the correct port.
 
 BugLink: https://bugs.launchpad.net/bugs/1289515
 Signed-off-by: David Henningsson david.hennings...@canonical.com

Thanks, this also fixes this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=55262

A couple of comments below.

 ---
  src/pulsecore/sink.c   |   11 +++
  src/pulsecore/source.c |   11 +++
  2 files changed, 22 insertions(+)
 
 diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
 index 08143e9..9c4b0c3 100644
 --- a/src/pulsecore/sink.c
 +++ b/src/pulsecore/sink.c
 @@ -235,6 +235,17 @@ pa_sink* pa_sink_new(
  pa_device_init_icon(data-proplist, true);
  pa_device_init_intended_roles(data-proplist);
  
 +if (!data-active_port  !data-save_port) {

How is data-save_port relevant here? If active_port is NULL, save_port
should always be false (true wouldn't have any meaning).

 +void *state;
 +pa_device_port *p, *p2 = NULL;
 +
 +PA_HASHMAP_FOREACH(p, data-ports, state)
 +if (!p2 || p-priority  p2-priority) {
 +p2 = p;
 +pa_sink_new_data_set_port(data, p2-name);

I'd prefer calling pa_sink_new_data_set_port() only once, i.e. outside
the loop.

 +}
 +}

This partially duplicates the code that is run later:

if (!s-active_port) {
void *state;
pa_device_port *p;

PA_HASHMAP_FOREACH(p, s-ports, state) {
if (p-available == PA_AVAILABLE_NO)
continue;

if (!s-active_port || p-priority  s-active_port-priority)
s-active_port = p;
}
if (!s-active_port) {
PA_HASHMAP_FOREACH(p, s-ports, state)
if (!s-active_port || p-priority  s-active_port-priority)
s-active_port = p;
}
}

I think we should do the fallback port initialization only once, in the
location where you added the new code. We should use the full logic of
the old fallback initialization code.

-- 
Tanu


** Bug watch added: freedesktop.org Bugzilla #55262
   https://bugs.freedesktop.org/show_bug.cgi?id=55262

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

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1295663] [NEW] time and day widget shows the wrong date at midnight

2014-03-21 Thread Brian
Public bug reported:

At midnight, the time and date widget that is part of the desktop
widget-bar will show the wrong day.  At midnight, click on the time to
expose the calendar.  The day on the calendar will be marked with a
rectangle. The rectangle will be marking the wrong day between midnight
and 12:01 AM.  That is, the rectangle will be in the wrong place if the
calendar is exposed any time in the first 60 seconds after midnight.
This is repeatable.

Description:Ubuntu 12.04.4 LTS
Release:12.04

gnome-panel:
  Installed: 1:3.4.1-0ubuntu1.2
  Candidate: 1:3.4.1-0ubuntu1.2
  Version table:
 *** 1:3.4.1-0ubuntu1.2 0
500 http://ca.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:3.4.1-0ubuntu1 0
500 http://ca.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.4.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
Uname: Linux 3.2.0-60-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Fri Mar 21 08:40:14 2014
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise running-unity third-party-packages

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

Title:
  time and day widget shows the wrong date at midnight

Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  At midnight, the time and date widget that is part of the desktop
  widget-bar will show the wrong day.  At midnight, click on the time to
  expose the calendar.  The day on the calendar will be marked with a
  rectangle. The rectangle will be marking the wrong day between
  midnight and 12:01 AM.  That is, the rectangle will be in the wrong
  place if the calendar is exposed any time in the first 60 seconds
  after midnight.  This is repeatable.

  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  gnome-panel:
Installed: 1:3.4.1-0ubuntu1.2
Candidate: 1:3.4.1-0ubuntu1.2
Version table:
   *** 1:3.4.1-0ubuntu1.2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-panel 1:3.4.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Mar 21 08:40:14 2014
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1295635] Re: when I start gnome-disk-utility, the top part part of its window is under the top bar of unity

2014-03-21 Thread SteliosSk
** Description changed:

  As described, in ubuntu trusty, when I start gnome-disk-utlity, the top
- part of its window is under the top bar of unity. Please see picture at
+ part of its window (which has the min-max-close buttons) is under the
+ top bar of unity. Please see picture at
  https://dl.dropboxusercontent.com/u/19393967/gnome-disk-utility.png
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:24:38 2014
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-03-07 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  ProcEnviron:
   LANGUAGE=el
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  when  I start gnome-disk-utility, the top part part of its window is
  under the top bar of unity

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  As described, in ubuntu trusty, when I start gnome-disk-utlity, the
  top part of its window (which has the min-max-close buttons) is under
  the top bar of unity. Please see picture at
  https://dl.dropboxusercontent.com/u/19393967/gnome-disk-utility.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 13:24:38 2014
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-03-07 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  ProcEnviron:
   LANGUAGE=el
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1295659] Re: Xorg crashed with SIGABRT

2014-03-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035719/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035722/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035734/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035736/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035737/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035738/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1295659/+attachment/4035739/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1033533
   Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW 
rendering

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT

Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Unknown which user action contributed to this

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.0-1ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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
  CrashCounter: 1
  Date: Fri Mar 21 11:48:03 2014
  DistUpgraded: 2014-01-31 23:52:38,971 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-18-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:049a]
  InstallationDate: Installed on 2011-12-04 (838 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011)
  MachineType: Dell Inc. Precision WorkStation T7400
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=cea7b9f7-43ba-442c-ad69-638a70ffde6d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to trusty on 2014-01-31 (48 days ago)
  UserGroups:
   
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0RW199
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT7400:pvr:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140310-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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: 

Re: [Desktop-packages] [Bug 1284134] Re: Xorg crash

2014-03-21 Thread Barry Warsaw
On Mar 21, 2014, at 11:43 AM, Jakob Bornecrantz wrote:

Did you fully upgrade the VM?

Yes.

Tho I no longer need to press enter to close emacs, could this have something
to do with it?

I'm not sure what this means.  Did you try the recipe in comment #5 and
#7?

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

Title:
  Xorg crash

Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  I use the Nouveau theme of Gnome-Do, and I bind its invocation to Alt-
  Ctrl-Space.  Invoking Gnome-Do crashes X and leaves me back at the
  login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-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
  CurrentDmesg:
   [   13.651845] init: plymouth-stop pre-start process (1605) terminated with 
status 1
   [   13.678625] dm-0: WRITE SAME failed. Manually zeroing.
  Date: Mon Feb 24 09:11:37 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-12-06 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic 
root=UUID=94d2915e-fb19-4acc-a25c-72a220adc614 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  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-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: Mon Feb 24 09:10:52 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors: No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: vmware

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Hongbo Zhu
dpkg -l | grep libglib
ii  libglib-perl   2:1.241-1
interface to the GLib and GObject libraries
ii  libglib2.0-0   2.32.4-0ubuntu1  
GLib library of C routines
ii  libglib2.0-0:i386  2.32.4-0ubuntu1  
GLib library of C routines
ii  libglib2.0-0-dbg   2.32.4-0ubuntu1  
Debugging symbols for the GLib libraries
ii  libglib2.0-0-refdbg2.32.4-0ubuntu1  
GLib library of C routines - refdbg library
ii  libglib2.0-bin 2.32.4-0ubuntu1  
Programs for the GLib library
ii  libglib2.0-cil 2.12.10-2ubuntu4 
CLI binding for the GLib utility library 2.12
ii  libglib2.0-cil-dev 2.12.10-2ubuntu4 
CLI binding for the GLib utility library 2.12
ii  libglib2.0-data2.32.4-0ubuntu1  
Common files for GLib library
ii  libglib2.0-dev 2.32.4-0ubuntu1  
Development files for the GLib library
ii  libglib2.0-doc 2.32.4-0ubuntu1  
Documentation files for the GLib library
ii  libglibmm-2.4-1c2a 2.32.0-0ubuntu1  
C++ wrapper for the GLib toolkit (shared libraries)
ii  libglibmm-2.4-dbg  2.32.0-0ubuntu1  
C++ wrapper for the GLib toolkit (debug symbols)

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1295670] [NEW] Nautilus doesn't save folders view style

2014-03-21 Thread Sergei Solo
Public bug reported:

Nautilus fork Files doesn't save folders view style (List or Icons
view) after closing window and open it again. Original Nautilus does it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 21 17:06:24 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
InstallationDate: Installed on 2014-03-18 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Description changed:

- Nautilus fork Files doesn't save folders view style after closing
- window and open it again. Original Nautilus does it.
+ Nautilus fork Files doesn't save folders view style (List or Icons
+ view) after closing window and open it again. Original Nautilus does it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 17:06:24 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-03-18 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nautilus doesn't save folders view style

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Nautilus fork Files doesn't save folders view style (List or Icons
  view) after closing window and open it again. Original Nautilus does
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 21 17:06:24 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-03-18 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Richard Potter
My system is ubuntu 12.04 on Linux 3.8.0-37-generic. As said in #16, I
removed that ppa and all is well.

# ppa-purge ppa:webupd8team/gvfs-libmtp

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

-- 
Mailing list: https://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 1292174] Re: [trusty] webapp launches, container remains blank

2014-03-21 Thread David Barth
Le 21/03/2014 13:44, nicolas kleinklaus a écrit :
 I have exactly the same problem as in #6 comment. webapps open in new
 forefox window (no with dedicated browser) and no Icon is displayed in
 the Launcher
Is the Firefox window blank in this case? Or is that an icon problem you 
are reporting?

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

Title:
  [trusty] webapp launches, container remains blank

Status in WebApps: libunity:
  New
Status in Chromium extension: Unity Integration:
  New
Status in Firefox extension: Unity Integration:
  New
Status in Unity WebApps QML component:
  Triaged
Status in The Webapps-core project:
  New
Status in “libunity-webapps” package in Ubuntu:
  New
Status in “unity-chromium-extension” package in Ubuntu:
  New
Status in “unity-firefox-extension” package in Ubuntu:
  New
Status in “unity-webapps-qml” package in Ubuntu:
  New

Bug description:
  After installation of webapp via either chromium or firefox, attempt
  to launch webapp other than Amazon renders no page.

  Tested on unity-webapps-launchpad, unity-webapps-googleplus, unity-
  webapps-facebookmessenger.

  Expected result: webapp launches properly within container and
  corresponding web page displays.

  Actual result: webapp launches within container and remains blank, no
  web page displays.

  Example image attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1292174/+subscriptions

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


[Desktop-packages] [Bug 1291608] Re: No user icons provided / user icons not used

2014-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.6.3-0ubuntu54

---
gnome-control-center (1:3.6.3-0ubuntu54) trusty; urgency=medium

  * debian/control.in, debian/gnome/control-center-data.install,
debian/gnome-control-center-shared-data.install:
- create a new binary with data files that are needed by g-c-c and u-c-c
  (the default selection of user icons for example) (lp: #1291608)
 -- Sebastien Bacher seb...@ubuntu.com   Fri, 21 Mar 2014 12:25:38 +0100

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  No user icons provided / user icons not used

Status in Ayatana Design:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  GNOME Control Centre provided a default set of user icons so users
  could pick an icon for themself. Since we've migrated to Unity Control
  Centre we no longer have any default icons.

  The options seem to be:
  1. Split the icons out of gnome-control-center and ship them with both GNOME 
Control Centre and Unity Control Centre.
  2. Provide a set of Ubuntu themed icons, e.g. the Ubuntu pictograms [1].
  3. Remove support from Unity Control Centre for user icons since they're not 
actually used anywhere.

  What does design think about option 3? I note the design [2] shows
  icons but it doesn't indicate if they're used anywhere. If not option
  3, can we get a good set of pictograms to use?

  [1] 
http://design.canonical.com/2011/06/whats-round-and-sticky-and-how-you-can-make-some/
  [2] https://wiki.ubuntu.com/UserAccounts

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

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


[Desktop-packages] [Bug 329898] Re: The HP 1018 printer not work out of the box if used non-US locale

2014-03-21 Thread Till Kamppeter
Can someone of the HPLIP developers at HP look at this? It seems that
hp-plugin does not work with non-English locales.

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

Title:
  The HP 1018 printer not work out of the box if used non-US locale

Status in HP Linux Imaging and Printing:
  New
Status in Release Notes for Ubuntu:
  Won't Fix
Status in “hplip” package in Ubuntu:
  Fix Released
Status in “ibus” package in Ubuntu:
  Fix Released
Status in “hplip” source package in Lucid:
  Won't Fix
Status in “ibus” source package in Lucid:
  Invalid
Status in “hplip” source package in Maverick:
  Won't Fix
Status in “ibus” source package in Maverick:
  Won't Fix

Bug description:
  This bug is continuation of the bug 217215. To avoid any problems
  related to attempts describe I decided to start with 'clean account'.
  (and created the new bug entry)

  Clean account means:
  1) Remove hplip*, foo2zjs, footomatic package.
  2) Remove any further files related to hp1018
  find /usr/share -name *1018*
  ./foo2zjs/firmware/sihp1018.img
  ./ppd/hpijs/HP/hp_laserjet_1018-hpijs.ppd
  3) Remove orphaned /usr/share/hplip directory

  After restarting the printer a system message appear pointing that new 
hardware had been installed and suggesting that hpijs package support the HP 
1018 printer. 
  I:
  - installed hpijs with depends
  - Ran Printer configure tool: a driver for HP 1018 hadn't been found 
  - so I chose suggested HP 1015 driver
  - printer didn't react for send packages.

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

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


[Desktop-packages] [Bug 1244087] Re: Ubuntu 13.10 Main Menu editor Problem

2014-03-21 Thread hariprasad
To move menu item from one submenu to another it is needed to know the name of 
destination submenu. It is in property Categories, i.e. 
Categories=Application;Development;Java;IDE. Desktop (.desktop suffix) files 
are located on two places:
~/.local/share/applications locally in your home and /usr/share/applications 
globally. Compare the both directories, find out appropriate files and 
synchronize them. I think, that they should be the same. In my case both files 
were identical, but in /usr/share/applications was attribute Hidden=true, so i 
remove it to be both files identical.

The second case is, if the .desktop file is only in local menu. Check it
and add Categories property if needed. Remove Hidden property or set it
false. Check duplicities (many items has name alacarte-made-nn.desktop)
check them, rename them, remove duplicities!

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

Title:
  Ubuntu 13.10 Main Menu editor Problem

Status in One Hundred Papercuts:
  Confirmed
Status in “alacarte” package in Ubuntu:
  Confirmed

Bug description:
  I just ungraded to *Ubuntu 13.10* using ) *Gnome (classic) Desktop*.

  The [Main Menu] editor does NOT work properly.

  I cannot ADD items.

  I CAN edit and move existing items only.

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

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


[Desktop-packages] [Bug 1295668] [NEW] Window buttons disappear in 2-screen mode with vertical bar

2014-03-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a vertical panel with window switcher in 13.10 gnome classic.
This is ok when on single screen on booted with dual screen.
When booted without external screen and then docked, the window switcher 
disappear.
See the screenshots.

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

-- 
Window buttons disappear in 2-screen mode with vertical bar
https://bugs.launchpad.net/bugs/1295668
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-panel in Ubuntu.

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


[Desktop-packages] [Bug 1174253] Re: Segfault (core dumped) in gdk-pixbuf on upgrade

2014-03-21 Thread Marc Deslauriers
@Hongbo Zhu:

You are using a version of glib2.0 that is incompatible with the version
of gdk-pixbuf Ubuntu 12.04. You probably installed it from a PPA.

You need to revert the glib2.0 packages to the versions that come with
Ubuntu 12.04 to solve your issue.

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

Title:
  Segfault (core dumped) in gdk-pixbuf on upgrade

Status in “gdk-pixbuf” package in Ubuntu:
  Confirmed

Bug description:
  In two machines I had errors in the upgrade from Precise to Raring.

  Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using 
.../librsvg2-2_2.36.4-1_i386.deb) ...
  Unpacking replacement librsvg2-2:i386 ...
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  Setting up librsvg2-2:i386 (2.36.4-1) ...
  Setting up librsvg2-2:amd64 (2.36.4-1) ...
  Setting up librsvg2-common:i386 (2.36.4-1) ...
  Setting up librsvg2-common:amd64 (2.36.4-1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Processing triggers for libgdk-pixbuf2.0-0:i386 ...
  Segmentation fault (core dumped)
  Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
  Segmentation fault (core dumped)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%

  I guess that due to that error, the gdk-pixbuf-query-loaders crashes
  later in the installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 12:17:40 2013
  InstallationDate: Installed on 2009-11-25 (1251 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1174253/+subscriptions

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


[Desktop-packages] [Bug 1242018] [NEW] Lost some icons after upgrade to 13.10

2014-03-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Last night I upgraded from 13.04 to 13.10. It went surprisingly well.
Just about everything works except that I lost my shutdown icon and the
hibernate selection in my sessions menu. I was able to hibernate via the
terminal so I know it stil works but I would prefer to do it from the
sessions menu, as usual. I would also like to get the shutdown icon back
in my gnome bar. Can someone direct me to the proper procedure?

Thanks in advance.

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


** Tags: bot-comment
-- 
Lost some icons after upgrade to 13.10
https://bugs.launchpad.net/bugs/1242018
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus in Ubuntu.

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


[Desktop-packages] [Bug 1295668] Re: Window buttons disappear in 2-screen mode with vertical bar

2014-03-21 Thread Thaddäus Tintenfisch
** Package changed: xubuntu-meta (Ubuntu) = gnome-panel (Ubuntu)

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

Title:
  Window buttons disappear in 2-screen mode with vertical bar

Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  I have a vertical panel with window switcher in 13.10 gnome classic.
  This is ok when on single screen on booted with dual screen.
  When booted without external screen and then docked, the window switcher 
disappear.
  See the screenshots.

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

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


[Desktop-packages] [Bug 1294370] Re: PostScript level2 is always generated with pdftops renderer

2014-03-21 Thread Till Kamppeter
Please follow the instructions of the section CUPS error_log on
https://wiki.ubuntu.com/DebuggingPrintingProblems for a print job with
which you observe the problem. Do not compress the error_log file when
you attach it.


** Changed in: cups-filters (Ubuntu)
   Status: New = Incomplete

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

Title:
  PostScript level2 is always generated with pdftops renderer

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

Bug description:
  I built cups-filters 1.0.44 for Ubuntu 12.04 with pdftops being
  poppler's pdftops. I'm using it with Ricoh MP C3300  PosrtScript PPD
  [1], and looking at the code it should call pdftops with -level3
  parameter. However, it looks like HP printer detection takes place and
  -level2 is always generated.

  Here is strace output: 
  [pid  7373] execve(/usr/bin/pdftops, [pdftops, -level2, -noembtt, 
-origpagesizes, -nocenter, -r, 300, /tmp/p2.pdf, -], [/* 28 vars 
*/] unfinished ...

  Shouldn't it generate level3 unless the printer is HP laserjet?

  1. http://www.openprinting.org/ppd-o-matic.php?driver=Postscript-
  Ricohprinter=Ricoh-Aficio_MP_C3300show=1

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

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


[Desktop-packages] [Bug 1209246] Re: HPLIP GUI doesn't handle authentication properly

2014-03-21 Thread Till Kamppeter
Closing for Ubuntu as we are on 3.14.3 in Trusty now.


** Changed in: hplip (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  HPLIP GUI doesn't handle authentication properly

Status in HP Linux Imaging and Printing:
  Fix Released
Status in “hplip” package in Ubuntu:
  Fix Released
Status in “hplip” package in Debian:
  New

Bug description:
  I installed hplip-gui hoping it would provide a graphical install
  process for a networked HP printer.

  Following through the install process for a networked printer, I found
  that the UI wasn't able to authenticate properly. Although the printer
  identity could be properly detected from its IP address, every time
  the hp-plugin install asked me for a password and the install failed,
  claiming it could not authenticate, even when I used the proper
  password for my account.

  My user account is an sudoer and is also a member of lpadmin.

  A workaround was to run... 
  sudo hp-setup
  ...which then caused the printer drivers to be installed properly, though it 
failed with a dbus error when setting up the printer as it was running within 
sudo. 

  I then proceeded to add the printer through the regular UI (which was
  also able to autodetect the printer from its IP address, and match the
  already auto-downloaded driver).

  Subsequent runs of the HPLip Toolbox from my regular user account were
  able to proceed to installing the printer.

  I think this is a simple issue of not properly negotiating the
  authentication of the user, either via a printer group, or possibly to
  cups. Given all the amazing work which has gone into HPlip-gui it
  seems a shame to fail with such a simple bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: hplip-gui 3.13.4-1build1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.12-0ubuntu2
  Architecture: i386
  Date: Wed Aug  7 14:43:36 2013
  Lpstat: device for HP-LaserJet-400-colorMFP-M475dw: socket://148.88.141.83
  MachineType: Dell Inc. Inspiron N5110
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: HP-LaserJet-400-colorMFP-M475dw: HP LJ 300-400 color MFP M375-M475 
Postscript (recommended)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic 
root=UUID=c9767810-263a-424a-80cd-714fd4a9afa1 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HVRTT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1242018] Re: Lost some icons after upgrade to 13.10

2014-03-21 Thread John Kim
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. The best solution now is to do a fresh reinstall of your system. 
Otherwise, please execute the following command, as it will automatically 
gather debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and 
the name of the package affected. You can learn more about this functionality 
at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: ubuntu = nautilus (Ubuntu)

** Changed in: nautilus (Ubuntu)
   Status: New = Incomplete

** Tags added: saucy

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

Title:
  Lost some icons after upgrade to 13.10

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Last night I upgraded from 13.04 to 13.10. It went surprisingly well.
  Just about everything works except that I lost my shutdown icon and
  the hibernate selection in my sessions menu. I was able to hibernate
  via the terminal so I know it stil works but I would prefer to do it
  from the sessions menu, as usual. I would also like to get the
  shutdown icon back in my gnome bar. Can someone direct me to the
  proper procedure?

  Thanks in advance.

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

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


[Desktop-packages] [Bug 1175601] Re: Two Chromium background instances and a browser window open on boot without my permission

2014-03-21 Thread Aren Cambre
That's interesting: clearing the session cache seems to have improved
things. I wonder if there is some odd interaction between the session
cache and Chromium?

After clearing the cache, the Chromium icon in the bar at top,
representing the background process, reappears whenever I reboot, but no
windows are opened. I even opened Chromium to two news sites, rebooted,
and later opened Chromium to Gmail and Facebook, rebooted, and in
neither case did Chromium windows open after I logged in, just the
Chromium icon in the top bar.

If I uncheck Chromium from the Application Autostart tab, it's rechecked
once Chromium restarts.

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

Title:
  Two Chromium background instances and a browser window open on boot
  without my permission

Status in “chromium-browser” package in Ubuntu:
  Invalid
Status in “xfce4-session” package in Ubuntu:
  New

Bug description:
  When I log into my user session (type in my password on the login
  prompt after boot), Chromium auto-starts, and two instances of its
  background process automatically open: per the attached image, two
  Chromium icons appear in the top bar. Also, an instance of the browser
  appears in the middle of the screen.

  When this happens, I get an inconsistent browsing experince in
  Chromium, where it is randomly unable to connect to web sites or
  download components referenced by web pages (e.g., CSS files, JS
  files, etc.).

  I can fix by closing the browser and also both the background
  sessions, then restarting Chromium.

  I have never configured Chromium to start up when I log into my
  session. This has happened without my explicit permission or consent.

  If I go to Session and Startup's Application Autostart tab, Chromium
  appears in the list and is checked. I did not configure this.

  Expected behavior: No part of Chromium opens at all, not even a
  background process, until I launch the browser for the first time.

  I am using a copy of Xubuntu 13.04 that was upgraded from Xubuntu
  12.10. This problem was happening for several weeks back with Xubuntu
  12.10, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: chromium-browser 25.0.1364.160-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May  2 08:18:13 2013
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-01-02 (119 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to raring on 2013-04-30 (1 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'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n'

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

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


[Desktop-packages] [Bug 1073949] Re: system-config-printer found the suitable printer driver for EPSON printer, but can't install

2014-03-21 Thread Till Kamppeter
Epson's server is fixed now. Please try again and tell whether the
problem is solved.

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

Title:
  system-config-printer found the suitable printer driver for EPSON
  printer, but can't install

Status in “system-config-printer” package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu, very few (EPSON only I know) printer vendor supports automatic 
driver download feature.
  When I tried the feature with EPSON PX-503A in Oneiric and Precise, it worked 
fine.
  But I also tried my new Quantal system, s-c-p seems to found correct the 
printer driver (see attached screenshot), but not installed when I press 
Forward button; nothing happens and no driver package is downloaded or 
installed.

  
  Reproduce Process:

  1. In s-c-p, click add button and select the network printer EPSON PX-503A.
  2. Ubuntu says looking for the drivers..., then attached screenshot is 
appeared. It seems correct.
  3. Press Forward button.

  Expected Result:

  - The found driver package will be downloaded and automatically
  installed, then we can select the right PPD in s-c-p.

  Current Result:

  - Nothing happens, and s-c-p says select Generic PPD.

  
  I'm not sure which module has a problem (s-c-p or ubuntu-driver), sorry if my 
choose of the package is wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: system-config-printer-common 1.3.11+20120807-0ubuntu10
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Thu Nov  1 22:08:16 2012
  InstallationDate: Installed on 2011-08-26 (433 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110803.1)
  MachineType: LENOVO 30515EJ
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  ProcEnviron:
   LANGUAGE=ja:en
   TERM=screen-bce
   PATH=(custom, no user)
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=10880fa0-c788-489b-a013-1fa7690bcc94 ro quiet splash vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (14 days ago)
  dmi.bios.date: 06/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8RET26WW (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 30515EJ
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8RET26WW(1.08):bd06/20/2011:svnLENOVO:pn30515EJ:pvrThinkPadX120e:rvnLENOVO:rn30515EJ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 30515EJ
  dmi.product.version: ThinkPad X120e
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1073949/+subscriptions

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


  1   2   3   4   >