date:20130814

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

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 #1211887, 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/1212120/+attachment/3772093/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772095/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772096/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772097/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772098/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772099/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212120/+attachment/3772100/+files/ThreadStacktrace.txt

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

** 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 software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1212120

Title:
  software-center crashed with signal 5 in _XReadEvents()

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

Bug description:
  Ubuntu 13.10 x86_64 on VirtualBox.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.08-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 10:36:55 2013
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2013-08-03 (10 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: software-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: software-center crashed with signal 5 in _XReadEvents()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212014] Re: Sync x11-apps 7.7+1 (main) from Debian unstable (main)

2013-08-14 Thread Daniel Holbach

This bug was fixed in the package x11-apps - 7.7+1
Sponsored for Robert Hooker (sarvatt)

---
x11-apps (7.7+1) unstable; urgency=low

  [ Robert Hooker ]
  * Add transset to conflicts/replaces to fix upgrades.
  * Add rendercheck to x11-apps.
  * ico 1.0.4
  * xcalc 1.0.5
  * xconsole 1.0.5
  * xditview 1.0.3
  * xedit 1.2.1
  * xgc 1.0.4
  * xmag 1.0.5
  * bitmap 1.0.7
  * transset 1.0.1
  * Add an update-copyright target to refresh debian/copyright using
upstream's COPYING files, thanks to Julien Cristau.
  * Refresh copyright.

  [ Julien Cristau ]
  * xconsole 1.0.6.
  * xload 1.1.2.
  * xwd 1.0.6
  * Add build-dep on bison to make xgc's configure happy.

 -- Julien Cristau jcris...@debian.org  Tue, 13 Aug 2013 12:50:41
+0200

** Changed in: x11-apps (Ubuntu)
   Status: New = Fix Released

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

Title:
  Sync x11-apps 7.7+1 (main) from Debian unstable (main)

Status in “x11-apps” package in Ubuntu:
  Fix Released

Bug description:
  Please sync x11-apps 7.7+1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Sync from unreleased debian git. (LP: 1078401)
* Add transset to conflicts/replaces to fix upgrades.
* Add rendercheck to x11-apps.
* Merge new release from debian unstable.
* Dropped 100-fix-linking-with-no-add-needed.patch, upstream.
* Fix recommends. Previously it was recommending xbitmap which didn't
  exist, the package is xbitmaps. (LP: #930176)

  All of these changes are in debian now and included in this release.

  Changelog entries since current saucy version 7.7~3ubuntu1:

  x11-apps (7.7+1) unstable; urgency=low

[ Robert Hooker ]
* Add transset to conflicts/replaces to fix upgrades.
* Add rendercheck to x11-apps.
* ico 1.0.4
* xcalc 1.0.5
* xconsole 1.0.5
* xditview 1.0.3
* xedit 1.2.1
* xgc 1.0.4
* xmag 1.0.5
* bitmap 1.0.7
* transset 1.0.1
* Add an update-copyright target to refresh debian/copyright using
  upstream's COPYING files, thanks to Julien Cristau.
* Refresh copyright.

[ Julien Cristau ]
* xconsole 1.0.6.
* xload 1.1.2.
* xwd 1.0.6
* Add build-dep on bison to make xgc's configure happy.

   -- Julien Cristau jcris...@debian.org  Tue, 13 Aug 2013 12:50:41
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1212014/+subscriptions

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

[Desktop-packages] [Bug 1211678] Re: Animation path woun't be saved

2013-08-14 Thread Pavel Fischer

apport information

** Tags added: apport-collected raring

** Description changed:

  If I create an animation (e.g. Left) and move the start and end points
  with mouse, path wount be stored, but UI shows the correct one. It will
  be saved only, if i change the path positions with keyboard arrows.
  
  Steps to reproduce:
  1. Create an Object
  2. Add an animation (e.g. Left)
  3. Change the positions of the start/stop points with mouse.
  4. Start the presentation
+ --- 
+ ApportVersion: 2.9.2-0ubuntu8.3
+ Architecture: amd64
+ DistroRelease: Ubuntu 13.04
+ InstallationDate: Installed on 2013-07-23 (21 days ago)
+ InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
+ MarkForUpload: True
+ Package: libreoffice 1:4.0.2-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
+ Tags:  raring
+ Uname: Linux 3.8.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1211678/+attachment/3772120/+files/Dependencies.txt

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

Title:
  Animation path woun't be saved

Status in “libreoffice” package in Ubuntu:
  Incomplete

Bug description:
  If I create an animation (e.g. Left) and move the start and end points
  with mouse, path wount be stored, but UI shows the correct one. It
  will be saved only, if i change the path positions with keyboard
  arrows.

  Steps to reproduce:
  1. Create an Object
  2. Add an animation (e.g. Left)
  3. Change the positions of the start/stop points with mouse.
  4. Start the presentation
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-07-23 (21 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  Package: libreoffice 1:4.0.2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212065] Re: Xorg crashed with SIGABRT in sna_crtc_set_mode_major()

2013-08-14 Thread Chris Wilson

Something like:


diff --git a/src/sna/sna_driver.c b/src/sna/sna_driver.c
index 7f2c0ac..93843d1 100644
--- a/src/sna/sna_driver.c
+++ b/src/sna/sna_driver.c
@@ -1110,13 +1110,15 @@ Bool sna_init_scrn(ScrnInfoPtr scrn, int entity_num)
 
scrn-PreInit = sna_pre_init;
scrn-ScreenInit = sna_screen_init;
-   scrn-SwitchMode = sna_switch_mode;
-   scrn-AdjustFrame = sna_adjust_frame;
-   scrn-EnterVT = sna_enter_vt;
-   scrn-LeaveVT = sna_leave_vt;
+   if (!hosted()) {
+   scrn-SwitchMode = sna_switch_mode;
+   scrn-AdjustFrame = sna_adjust_frame;
+   scrn-EnterVT = sna_enter_vt;
+   scrn-LeaveVT = sna_leave_vt;
+   scrn-ValidMode = sna_valid_mode;
+   scrn-PMEvent = sna_pm_event;
+   }
scrn-FreeScreen = sna_free_screen;
-   scrn-ValidMode = sna_valid_mode;
-   scrn-PMEvent = sna_pm_event;
 
xf86SetEntitySharable(entity_num);
xf86SetEntityInstanceForScreen(scrn, entity_num,

Need to check that we can forgo declaring some of those and that XMir
wraps the ones it requires for itself.

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

Title:
  Xorg crashed with SIGABRT in sna_crtc_set_mode_major()

Status in “xorg-server” package in Ubuntu:
  In Progress

Bug description:
  description: xmir crashes to greeter when running nexuiz phoronix test

  steps:
  1. sudo apt-get update
  2. sudo apt-get install unity-system-compositor
  3. sudo reboot
  4. sudo apt-get install phoronix-test suite
  5. phoronix-test-suite install nexuiz
  6. phoronix-test-suite benchmark pts/nexuiz

  expected results:
  nexuiz test runs

  actual results:
  nexuiz test fails to run, xmir crashes to greeter

  Additional info:
  nexuiz benchmark runs without crashing, withou unity-system-compositor 
installed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDmesg:
   [   12.247108] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   12.247438] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   15.361232] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
   [   15.361268] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [  886.272269] init: plymouth-stop pre-start process (12585) terminated with 
status 1
  Date: Wed Aug 14 01:42:03 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3084]
  InstallationDate: Installed on 2013-08-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130813)
  MachineType: LENOVO 3302F3U
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 2 
-mirSocket /tmp/mir_socket -nolisten tcp
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-1-generic 
root=UUID=fc6bb71b-79d2-4987-9a18-24f120afee8d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   VidModeSetViewPort ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in VidModeSetViewPort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: utah
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT69AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  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:bvr9SKT69AUS:bd05/17/2013:svnLENOVO:pn3302F3U:pvrThinkCentreM82:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 3302F3U
  dmi.product.version: ThinkCentre M82
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1

[Desktop-packages] [Bug 1212065] Re: Xorg crashed with SIGABRT in sna_crtc_set_mode_major()

2013-08-14 Thread Chris Wilson

Enter/LeaveVT must be defined.

Upstream and branches fixed.

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

Title:
  Xorg crashed with SIGABRT in sna_crtc_set_mode_major()

Status in “xorg-server” package in Ubuntu:
  In Progress

Bug description:
  description: xmir crashes to greeter when running nexuiz phoronix test

  steps:
  1. sudo apt-get update
  2. sudo apt-get install unity-system-compositor
  3. sudo reboot
  4. sudo apt-get install phoronix-test suite
  5. phoronix-test-suite install nexuiz
  6. phoronix-test-suite benchmark pts/nexuiz

  expected results:
  nexuiz test runs

  actual results:
  nexuiz test fails to run, xmir crashes to greeter

  Additional info:
  nexuiz benchmark runs without crashing, withou unity-system-compositor 
installed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDmesg:
   [   12.247108] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   12.247438] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   15.361232] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
   [   15.361268] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [  886.272269] init: plymouth-stop pre-start process (12585) terminated with 
status 1
  Date: Wed Aug 14 01:42:03 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3084]
  InstallationDate: Installed on 2013-08-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130813)
  MachineType: LENOVO 3302F3U
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 2 
-mirSocket /tmp/mir_socket -nolisten tcp
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-1-generic 
root=UUID=fc6bb71b-79d2-4987-9a18-24f120afee8d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   VidModeSetViewPort ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in VidModeSetViewPort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: utah
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT69AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  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:bvr9SKT69AUS:bd05/17/2013:svnLENOVO:pn3302F3U:pvrThinkCentreM82:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 3302F3U
  dmi.product.version: ThinkCentre M82
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu3
  xserver.bootTime: Wed Aug 14 01:42:05 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputRaritan D2CIM-VUSB   KEYBOARD, id 9
   inputRaritan D2CIM-VUSB   MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.2-0ubuntu9

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

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

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

2013-08-14 Thread Paijo

Workaround to fix is:
= Install other desktop environment (e.g. Mate, KDE/plasma, Gnome, xfce, or 
something else), and work without unity.
It works. I did it and install gnome-shell.

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

Title:
  [Libreoffice] Mnemonics do not work in Unity

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

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

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

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

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

[Desktop-packages] [Bug 1212123] Re: Erratic cursor movement when using Coordinate Transformation Matrix

2013-08-14 Thread Shih-Yuan Lee

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

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

Title:
  Erratic cursor movement when using Coordinate Transformation Matrix

Status in “xorg-server” package in Ubuntu:
  New
Status in “xorg-server-lts-quantal” package in Ubuntu:
  New

Bug description:
  = Affected Packages =

  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2 in precise
  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise3 in precise

  = Reproduce Steps =

  1. Boot into Ubuntu 12.04.2 live system

  2. Expand the laptop display to the external one.
  For example, `xrandr --output eDP1 --auto --output HDMI1 --auto --right-of 
eDP1`

  3. Restrict the movements of the touchscreen to the laptop display.
  For example, `xinput map-to-crtc 'ELAN Touchscreen' eDP1`

  P.S. `xinput map-to-crtc` will calculate and set Coordinate
  Transformation Matrix correspondingly.

  = Expected Result =

  I can operate the touchscreen on the laptop display as usual.

  = Actual Result =

  It becomes abnormal and shows erratic cursor movement.

  P.S. Ubuntu 13.04 is OK.

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

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

[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected

2013-08-14 Thread Bug Watch Updater

** Changed in: fonts-arphic-uming (Debian)
   Status: Fix Committed = Fix Released

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

Title:
  Fontconfig warning: Having multiple values in test isn't supported
  and may not works as expected

Status in “culmus” package in Ubuntu:
  Fix Released
Status in “fonts-arphic-ukai” package in Ubuntu:
  Fix Released
Status in “fonts-arphic-uming” package in Ubuntu:
  Fix Released
Status in “fonts-baekmuk” package in Ubuntu:
  Fix Released
Status in “fonts-droid” package in Ubuntu:
  Fix Released
Status in “fonts-nanum” package in Ubuntu:
  Fix Released
Status in “fonts-nanum-coding” package in Ubuntu:
  Fix Released
Status in “fonts-sil-andika” package in Ubuntu:
  Fix Released
Status in “fonts-tlwg” package in Ubuntu:
  Fix Released
Status in “fonts-unfonts-core” package in Ubuntu:
  Fix Released
Status in “fonts-unfonts-extra” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “ttf-wqy-zenhei” package in Ubuntu:
  Fix Released
Status in “culmus” source package in Quantal:
  Fix Released
Status in “fonts-arphic-ukai” source package in Quantal:
  Fix Released
Status in “fonts-arphic-uming” source package in Quantal:
  Fix Released
Status in “fonts-baekmuk” source package in Quantal:
  Fix Released
Status in “fonts-droid” source package in Quantal:
  Fix Released
Status in “fonts-nanum” source package in Quantal:
  Fix Released
Status in “fonts-nanum-coding” source package in Quantal:
  Fix Released
Status in “fonts-sil-andika” source package in Quantal:
  Fix Released
Status in “fonts-tlwg” source package in Quantal:
  Fix Released
Status in “fonts-unfonts-core” source package in Quantal:
  Fix Released
Status in “fonts-unfonts-extra” source package in Quantal:
  Fix Released
Status in “language-selector” source package in Quantal:
  Fix Released
Status in “libreoffice” source package in Quantal:
  Confirmed
Status in “ttf-wqy-zenhei” source package in Quantal:
  Fix Released
Status in “fonts-arphic-ukai” package in Debian:
  Fix Released
Status in “fonts-arphic-uming” package in Debian:
  Fix Released
Status in “fonts-baekmuk” package in Debian:
  Fix Released
Status in “fonts-droid” package in Debian:
  Fix Released
Status in “fonts-nanum” package in Debian:
  Fix Released
Status in “fonts-sil-andika” package in Debian:
  Fix Committed
Status in “fonts-unfonts-core” package in Debian:
  Fix Released
Status in “fonts-unfonts-extra” package in Debian:
  Fix Released
Status in “ttf-wqy-zenhei” package in Debian:
  New
Status in Fedora:
  Unknown

Bug description:
  In 12.10, fontconfig prints warnings similar to the following whenever
  fontconfig is invoked:

  Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf,
  line 11: Having multiple values in test isn't supported and may not
  works as expected

  This affects fonts from a number of packages:
  fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf
  fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf
  fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf
  fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf
  fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf
  fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf
  fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf
  fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf
  fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf

  [Test Case]
  1) Install the fonts in question
  2) Open a terminal
  3) Launch 'gedit' from the terminal

  Expected results:
  gedit launches, no fontconfig warnings in the terminal

  Actual results:
  gedit launches, fontconfig warnings are displayed in the terminal

  [Regression Potential]
  In case of a regression, the font in question can be affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Thu Aug  9 10:02:59 2012
  Dependencies:

  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fonts-unfonts-core
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago)

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

have you sent email to the author

ALSA: hda/ca0132: Add PCM enhancements
Change the max channels of analog playback to 6.


 .channels_min = 2,
- .channels_max = 2,
+ .channels_max = 6,
.ops = {


but max channels still 2 

info-name = CA0132 Analog;
info-stream[SNDRV_PCM_STREAM_PLAYBACK] = ca0132_pcm_analog_playback;
info-stream[SNDRV_PCM_STREAM_PLAYBACK].nid = spec-dacs[0];
info-stream[SNDRV_PCM_STREAM_PLAYBACK].channels_max =
spec-multiout.max_channels;


spec-multiout.dac_nids = spec-dacs;
spec-multiout.num_dacs = 3;
spec-multiout.max_channels = 2;

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

Title:
  Creative Recon3d  Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in The Linux Kernel:
  New
Status in “alsa-driver” package in Ubuntu:
  Triaged

Bug description:
  [WORKAROUND] Run the following command:

  echo options snd-hda-intel position_fix=1 | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 743541] Re: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

2013-08-14 Thread Joshua Tasker

Because the latest version isn't in the official repo?

So, either install 13.06.01 manually, or get it from the PPA.

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

Title:
  indicator-weather crashed with SIGSEGV in
  dbusmenu_menuitem_build_variant()

Status in DBus Menu:
  Incomplete
Status in Indicator-Weather:
  Fix Released
Status in “indicator-weather” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: indicator-weather

  This crash just appear.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: indicator-weather 11.03.20+repack-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar 27 13:45:25 2011
  ExecutablePath: /usr/bin/indicator-weather
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302)
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xd69bb9 dbusmenu_menuitem_build_variant+409:
mov(%esi),%eax
   PC (0x00d69bb9) ok
   source (%esi) (0x0234) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-weather
  StacktraceTop:
   dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.3
   ?? () from /usr/lib/libdbusmenu-glib.so.3
   ?? () from /usr/lib/libdbusmenu-glib.so.3
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: indicator-weather crashed with SIGSEGV in 
dbusmenu_menuitem_build_variant()
  UpgradeStatus: Upgraded to natty on 2011-03-25 (2 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1212134] [NEW] [CA0106 - CA0106, playback] fails after a while

2013-08-14 Thread john nunnington

Public bug reported:

sound stops working after an indeterminate period.

Sound is restored by either logging out and back in or 'pulseaudio
--start' and reselecting the output device in the 'Sound Settings' and
selecting [in my case Analogue Output, Ca0106 SoundBlaster' with mode of
5.1].

When the sound stops the 'Play sound Through' list is empty

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Wed Aug 14 19:21:19 2013
InstallationDate: Installed on 2013-04-13 (122 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: CA0106 Soundblaster - CA0106
Symptom_PulseAudioLog:
 
Symptom_Type: Sound works for a while, then breaks
Title: [CA0106 - CA0106, playback] fails after a while
UpgradeStatus: Upgraded to raring on 2013-06-09 (65 days ago)
dmi.bios.date: 03/26/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX V2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug raring

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

Title:
  [CA0106 - CA0106, playback] fails after a while

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

Bug description:
  sound stops working after an indeterminate period.

  Sound is restored by either logging out and back in or 'pulseaudio
  --start' and reselecting the output device in the 'Sound Settings' and
  selecting [in my case Analogue Output, Ca0106 SoundBlaster' with mode
  of 5.1].

  When the sound stops the 'Play sound Through' list is empty

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Wed Aug 14 19:21:19 2013
  InstallationDate: Installed on 2013-04-13 (122 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: CA0106 Soundblaster - CA0106
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [CA0106 - CA0106, playback] fails after a while
  UpgradeStatus: Upgraded to raring on 2013-06-09 (65 days ago)
  dmi.bios.date: 03/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 987028] Re: cant boot.says stoping crash report generation failed

2013-08-14 Thread Mike Hodo

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

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

Title:
  cant boot.says stoping crash report generation failed

Status in “nautilus” package in Ubuntu:
  Fix Released

Bug description:
  error stopping crash report generation failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CasperVersion: 1.287
  Date: Sun Apr 22 22:07:06 2012
  ExecutablePath: /usr/bin/nautilus
  LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

using hda-emu , it create 4 capture devices and digital capture is not
device 1 (defined in hda-intel.conf)


autoconfig: line_outs=2 (0xb/0x11/0x0/0x0/0x0) type:line
   speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
   hp_outs=2 (0x10/0xf/0x0/0x0/0x0)
   mono: mono_out=0x0
   dig-out=0xc/0xd
   inputs:
 Mic=0x12
 Line=0x13
   dig-in=0xe
# Building PCMs...

Attach PCM dev 0, name CA0132 Analog, type audio, play #1, capture #1

Attach PCM dev 1, name CA0132 Analog Mic-In2, type audio, play #0,
capture #1

Attach PCM dev 2, name CA0132 What U Hear, type audio, play #0, capture
#1

Attach PCM dev 3, name CA0132 Digital, type SPDIF, play #1, capture #1
# Init and building controls...

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

Title:
  Creative Recon3d  Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in The Linux Kernel:
  New
Status in “alsa-driver” package in Ubuntu:
  Triaged

Bug description:
  [WORKAROUND] Run the following command:

  echo options snd-hda-intel position_fix=1 | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1210938] Re: No window decoration on GNOME Fallback

2013-08-14 Thread Ch. Hanisch

Show here:
~$ compiz --replace
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
compiz (core) - Info: Loading plugin: ccp
compiz (core) - Info: Starting plugin: ccp
compizconfig - Info: Backend : gsettings
compizconfig - Info: Integration : true
compizconfig - Info: Profile : unity
compiz (core) - Info: Loading plugin: composite
compiz (core) - Info: Starting plugin: composite
compiz (core) - Info: Loading plugin: opengl
compiz (core) - Info: Unity is fully supported by your hardware.
compiz (core) - Info: Unity is fully supported by your hardware.
compiz (core) - Info: Starting plugin: opengl
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU
compiz (core) - Info: Loading plugin: imgjpeg
compiz (core) - Info: Starting plugin: imgjpeg
compiz (core) - Info: Loading plugin: compiztoolbox
compiz (core) - Info: Starting plugin: compiztoolbox
compiz (core) - Info: Loading plugin: decor
compiz (core) - Info: Starting plugin: decor
compiz (core) - Info: Loading plugin: gnomecompat
compiz (core) - Info: Starting plugin: gnomecompat
compiz (core) - Info: Loading plugin: copytex
compiz (core) - Info: Starting plugin: copytex
compiz (core) - Info: Loading plugin: move
compiz (core) - Info: Starting plugin: move
compiz (core) - Info: Loading plugin: mousepoll
compiz (core) - Info: Starting plugin: mousepoll
compiz (core) - Info: Loading plugin: text
compiz (core) - Info: Starting plugin: text
compiz (core) - Info: Loading plugin: place
compiz (core) - Info: Starting plugin: place
compiz (core) - Info: Loading plugin: vpswitch
compiz (core) - Info: Starting plugin: vpswitch
compiz (core) - Info: Loading plugin: imgpng
compiz (core) - Info: Starting plugin: imgpng
compiz (core) - Info: Loading plugin: imgsvg
compiz (core) - Info: Starting plugin: imgsvg
compiz (core) - Info: Loading plugin: regex
compiz (core) - Info: Starting plugin: regex
compiz (core) - Info: Loading plugin: animation
compiz (core) - Info: Starting plugin: animation
compiz (core) - Info: Loading plugin: grid
compiz (core) - Info: Starting plugin: grid
compiz (core) - Info: Loading plugin: resize
compiz (core) - Info: Starting plugin: resize
compiz (core) - Info: Loading plugin: wobbly
compiz (core) - Info: Starting plugin: wobbly
compiz (core) - Info: Loading plugin: session
compiz (core) - Info: Starting plugin: session
I/O warning : failed to load external entity 
/home/opa/.compiz/session/10a72398353bc280711376466860491750033570008
compiz (core) - Info: Loading plugin: workarounds
compiz (core) - Info: Starting plugin: workarounds
compiz (core) - Info: Loading plugin: kdecompat
compiz (core) - Info: Starting plugin: kdecompat
compiz (core) - Info: Loading plugin: fade
compiz (core) - Info: Starting plugin: fade
compiz (core) - Info: Loading plugin: cube
compiz (core) - Info: Starting plugin: cube
compiz (core) - Info: Loading plugin: td
compiz (core) - Info: Starting plugin: td
compiz (core) - Info: Loading plugin: rotate
compiz (core) - Info: Starting plugin: rotate
compiz (core) - Info: Loading plugin: unitymtgrabhandles
compiz (core) - Info: Starting plugin: unitymtgrabhandles
compiz (core) - Info: Loading plugin: expo
compiz (core) - Info: Starting plugin: expo
compiz (core) - Info: Loading plugin: scale
compiz (core) - Info: Starting plugin: scale
compiz (core) - Info: Loading plugin: ezoom
compiz (core) - Info: Starting plugin: ezoom
compiz (core) - Info: Loading plugin: unityshell
compiz (core) - Info: Starting plugin: unityshell
WARN  2013-08-14 09:56:17 unity.glib.dbus.server GLibDBusServer.cpp:580

[Desktop-packages] [Bug 1212134] Re: [CA0106 - CA0106, playback] fails after a while

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

the card only support 48000Hz


Default sample spec: s16le 2ch 44100Hz
Default channel map: front-left,front-right
Default sink name: alsa_output.pci-_04_05.0.analog-surround-51
Default source name: alsa_input.pci-_00_14.2.analog-stereo

** This bug has been marked a duplicate of bug 1202094
   [CA0106 - CA0106, playback] No sound at all

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

Title:
  [CA0106 - CA0106, playback] fails after a while

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

Bug description:
  sound stops working after an indeterminate period.

  Sound is restored by either logging out and back in or 'pulseaudio
  --start' and reselecting the output device in the 'Sound Settings' and
  selecting [in my case Analogue Output, Ca0106 SoundBlaster' with mode
  of 5.1].

  When the sound stops the 'Play sound Through' list is empty

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Wed Aug 14 19:21:19 2013
  InstallationDate: Installed on 2013-04-13 (122 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: CA0106 Soundblaster - CA0106
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [CA0106 - CA0106, playback] fails after a while
  UpgradeStatus: Upgraded to raring on 2013-06-09 (65 days ago)
  dmi.bios.date: 03/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1212123] Re: Erratic cursor movement when using Coordinate Transformation Matrix

** Branch linked: lp:~fourdollars/xorg-server/lp1212123

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

Title:
  Erratic cursor movement when using Coordinate Transformation Matrix

Status in “xorg-server” package in Ubuntu:
  New
Status in “xorg-server-lts-quantal” package in Ubuntu:
  New

Bug description:
  = Affected Packages =

  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2 in precise
  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise3 in precise

  = Reproduce Steps =

  1. Boot into Ubuntu 12.04.2 live system

  2. Expand the laptop display to the external one.
  For example, `xrandr --output eDP1 --auto --output HDMI1 --auto --right-of 
eDP1`

  3. Restrict the movements of the touchscreen to the laptop display.
  For example, `xinput map-to-crtc 'ELAN Touchscreen' eDP1`

  P.S. `xinput map-to-crtc` will calculate and set Coordinate
  Transformation Matrix correspondingly.

  = Expected Result =

  I can operate the touchscreen on the laptop display as usual.

  = Actual Result =

  It becomes abnormal and shows erratic cursor movement.

  P.S. Ubuntu 13.04 is OK.

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

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

[Desktop-packages] [Bug 1202094] Re: [CA0106 - CA0106, playback] No sound at all

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

Title:
  [CA0106 - CA0106, playback] No sound at all

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

Bug description:
  Since I have upgraded my Ubuntu from 11.10 to 12.04, my soundcard (see
  below) is recognised by my system but it plays no sound after a
  startup.  I need to manually execute 'sudo alsa force-reload' in order
  to get a functioning soundcard. When executed, the terminal output
  shows me:

  Terminating processes: 2042 2511
  2511.
  Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-intel 
snd-hda-codec snd-usb-audio snd-usbmidi-lib snd-hwdep snd-ca0106 snd-ac97-codec 
snd-pcm snd-page-alloc snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq 
snd-seq-device snd-timer (failed: modules still loaded: snd-hda-codec-hdmi 
snd-hda-codec snd-hwdep snd-pcm snd-page-alloc snd-timer).
  Loading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-intel 
snd-hda-codec snd-usb-audio snd-usbmidi-lib snd-hwdep snd-ca0106 snd-ac97-codec 
snd-pcm snd-page-alloc snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq 
snd-seq-device snd-timer.

  After that, my soundcard plays sound without any problems, until the next 
reboot. It still exist in the latest version of Ubuntu:
  lsb_release -rd
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  My soundcard is:
  lspci -nnk | grep -i audio -A2
  07:06.0 Multimedia audio controller [0401]: Creative Labs CA0106 Soundblaster 
[1102:0007]
Subsystem: Creative Labs SB0570 [SB Audigy SE] [1102:100a]
Kernel driver in use: snd_ca0106

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene10904 F pulseaudio
   /dev/snd/controlC1:  eugene10904 F pulseaudio
  Date: Wed Jul 17 09:22:48 2013
  InstallationDate: Installed on 2013-01-06 (191 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 successful
  Symptom_Card: Trust 2MP Auto Focus Webcam  - Trust 2MP Auto Focus Webcam
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene10904 F pulseaudio
   /dev/snd/controlC1:  eugene10904 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: Upgraded to saucy on 2013-07-01 (15 days ago)
  dmi.bios.date: 08/26/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS CROSSHAIR ACPI BIOS Revision 1207
  dmi.board.name: CROSSHAIR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSCROSSHAIRACPIBIOSRevision1207:bd08/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCROSSHAIR:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-10T23:40:22.478897

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

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

[Desktop-packages] [Bug 647349] Re: package software-center 2.0.7 failed to install/upgrade with python-central error on 9.10 - 10.04 upgrade

2013-08-14 Thread Matthew Paul Thomas

** Changed in: software-center (Ubuntu)
   Status: Fix Committed = Confirmed

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

Title:
  package software-center 2.0.7 failed to install/upgrade with python-
  central error on 9.10 - 10.04 upgrade

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

Bug description:
  Binary package hint: software-center

  The report on the error came after I had updated the system using Update 
Manager.
  I am dual booted Ubuntu 10.04/Vista.

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: software-center 2.0.7
  ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Sat Sep 25 08:38:41 2010
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: software-center
  Title: package software-center 2.0.7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-central/+bug/647349/+subscriptions

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

[Desktop-packages] [Bug 1211937] Re: Nautilus leaks memory right after system start

2013-08-14 Thread Andreas E.

I had expected ubuntu-bug adds more detailed/valuable information about
the bug. If there is more info needed, I could reproduce it and give
what ever info requested.

This was after a fresh install of Ubuntu, but with old user configuration 
imported. Turning of Nautilus to manage the desktop does indeed workaround the 
issue, although it shouldn't happen at all.
In any case I see this not only as a problem in this nautilus build, but also 
in resource/RAM management in the OS: A process that requires more RAM than can 
be afforded to maintain the system's responsiveness should be halted or killed.

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

Title:
  Nautilus leaks memory right after system start

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Directly after logging in, nautilus starts to take more memory with a speed 
of ~4 MB/s. After 10-20 minutes the system freezes so extremely that it doesn't 
respond to any input (alt+f1, reisub).
  This could be caused by something related to the desktop since nautilus is 
used to render the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Tue Aug 13 20:52:16 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'640x750+0+24'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'152'
  InstallationDate: Installed on 2013-08-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1212088] Re: Screen freezes, mouse keyboard not responds

Can you try with a 3.11 kernel?

** Changed in: xorg-server (Ubuntu)
   Status: New = Incomplete

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

Title:
  Screen freezes, mouse  keyboard  not responds

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

Bug description:
  Screen freezes, mouse  keyboard  not responds. But alt+F1 works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Aug 14 12:00:50 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz 
Edition] [1002:6818] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e217]
  InstallationDate: Installed on 2013-08-12 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic 
root=UUID=dab41fce-bfe4-4748-86aa-4ae14d5dcaa3 ro quiet splash
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-M LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5304:bd11/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu8
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu8
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Aug 14 10:47:47 2013
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.2-0ubuntu9

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

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

[Desktop-packages] [Bug 1208986] Re: Xorg crashed with SIGSEGV in __mpn_divrem()

** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGSEGV in __mpn_divrem()

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

Bug description:
  I don't know what was happened

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Aug  7 00:28:39 2013
  DistUpgraded: 2013-07-25 08:18:43,729 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:397d]
  InstallationDate: Installed on 2012-05-31 (431 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423.2)
  MachineType: LENOVO HuronRiver Platform
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-6-generic 
root=/dev/mapper/vg-root ro quiet splash i915.i915_enable_rc6=1 
i915.semaphores=1 pcie_aspm=force vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0xb7159597 __mpn_divrem+7:   call   0xb72565b3 
__x86.get_pc_thunk.bx
   PC (0xb7159597) ok
   source 0xb72565b3 (0xb72565b3) ok
   destination (%esp) (0xbf5ec000) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   __mpn_divrem (qp=0xbf5ec120, qextra_limbs=qextra_limbs@entry=0, 
np=0xbf5ec150, nsize=3, dp=0xbf5ec0f0, dsize=2) at divrem.c:56
   hack_digit () at printf_fp.c:250
   ___printf_fp (fp=fp@entry=0xbf5ec838, info=info@entry=0xbf5ec3e4, 
args=args@entry=0xbf5ec394) at printf_fp.c:943
   _IO_vfprintf_internal (s=0xbf5ec838, format=optimized out, ap=0xbf5eeec4 
) at vfprintf.c:1654
   buffered_vfprintf (s=s@entry=0xb830ddb0, format=format@entry=0xb772c060 
[%10.3f] , args=args@entry=0xbf5eeebc \240\032/\335\360\235\364@) at 
vfprintf.c:2341
  Title: Xorg crashed with SIGSEGV in __mpn_divrem()
  UpgradeStatus: Upgraded to saucy on 2013-07-25 (12 days ago)
  UserGroups: lp lpadmin
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu2
  version.libdrm2: libdrm2 2.4.46-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu3
  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: Wed Aug  7 00:29:39 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.2-0ubuntu3
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1177784] Re: SEGV in X Server When Resizing Window

2013-08-14 Thread Guillermo Lo Coco

Me too. Im tired of propietary drivers.
INTEL GPU works much much better in Linux, I promise myself the next gpu will 
be Intel. This nightmare Im having should come to an end.

Every time I resize or move something, lubuntu restart to login screen
and lost all changes in Kicad. Damn.

** Attachment added: Dmesg
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1177784/+attachment/3772186/+files/fglrx_fuck.txt

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

Title:
  SEGV in X Server When Resizing Window

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

Bug description:
  Whenever I attempt to resize a window I get a SEGV in the X server and
  reset to login screen.  Running Lubuntu 13.04 with dual 7970 cards
  physically connected for Crossfire but not enabled in X.

  Using the catalyst 13.4 driver from the AMD website resulting in the
  following packages:

  ii  fglrx 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators
  ii  fglrx-amdcccle2:12.104-0ubuntu1   
amd64Catalyst Control Center for the AMD graphics accelerators
  ii  fglrx-dev 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators (devel files)

  xorg packages installed are as follows:

  ii  xorg  1:7.7+1ubuntu4  
amd64X.Org X Window System
  ii  xorg-docs-core1:1.6-1ubuntu2  
all  Core documentation for the X.org X Window System
  ii  xorg-sgml-doctools1:1.10-1
all  Common tools for building X.Org SGML documentation
  ii  xserver-xorg  1:7.7+1ubuntu4  
amd64X.Org X server
  ii  xserver-xorg-core 2:1.13.3-0ubuntu6   
amd64Xorg X server - core server
  ii  xserver-xorg-input-all1:7.7+1ubuntu4  
amd64X.Org X server -- input driver metapackage
  ii  xserver-xorg-input-evdev  1:2.7.3-0ubuntu2b2  
amd64X.Org X server -- evdev input driver
  ii  xserver-xorg-input-mouse  1:1.7.2-3   
amd64X.Org X server -- mouse input driver
  ii  xserver-xorg-input-synaptics  1.6.2-1ubuntu6  
amd64Synaptics TouchPad driver for X.Org server
  ii  xserver-xorg-input-vmmouse1:12.9.0-0ubuntu3   
amd64X.Org X server -- VMMouse input driver to use with VMWare
  ii  xserver-xorg-input-wacom  1:0.19.0-0ubuntu1   
amd64X.Org X server -- Wacom input driver
  ii  xserver-xorg-video-all1:7.7+1ubuntu4  
amd64X.Org X server -- output driver metapackage
  ii  xserver-xorg-video-ati1:7.1.0-0ubuntu2
amd64X.Org X server -- AMD/ATI display driver wrapper
  ii  xserver-xorg-video-cirrus 1:1.5.2-0ubuntu1
amd64X.Org X server -- Cirrus display driver
  ii  xserver-xorg-video-fbdev  1:0.4.3-0ubuntu1
amd64X.Org X server -- fbdev display driver
  ii  xserver-xorg-video-intel  2:2.21.6-0ubuntu4   
amd64X.Org X server -- Intel i8xx, i9xx display driver
  ii  xserver-xorg-video-mach64 6.9.3-0ubuntu1  
amd64X.Org X server -- ATI Mach64 display driver
  ii  xserver-xorg-video-mga1:1.6.2-0ubuntu1
amd64X.Org X server -- MGA display driver
  ii  xserver-xorg-video-modesetting0.7.0-0ubuntu2  
amd64X.Org X server -- Generic modesetting driver
  ii  xserver-xorg-video-neomagic   1:1.2.7-0ubuntu1
amd64X.Org X server -- Neomagic display driver
  ii  xserver-xorg-video-nouveau1:1.0.7-0ubuntu1
amd64X.Org X server -- Nouveau display driver
  ii  xserver-xorg-video-openchrome 1:0.3.1-0ubuntu1
amd64X.Org X server -- VIA display driver
  ii  xserver-xorg-video-qxl0.1.0-0ubuntu3  
amd64X.Org X server -- QXL display driver
  ii  xserver-xorg-video-r128   6.9.1-0ubuntu1  
amd64X.Org X server -- ATI r128 display driver
  ii  xserver-xorg-video-radeon 1:7.1.0-0ubuntu2
amd64X.Org X server -- AMD/ATI Radeon display driver
  ii  xserver-xorg-video-s3 1:0.6.5-0ubuntu3
amd64X.Org X server -- legacy S3 display

[Desktop-packages] [Bug 1177784] Re: SEGV in X Server When Resizing Window

2013-08-14 Thread Guillermo Lo Coco

[  1125.646] (EE) 
[  1125.646] (EE) Backtrace:
[  1125.646] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76c0f49]
[  1125.646] (EE) 1: /usr/bin/X (0xb7513000+0x1b1e86) [0xb76c4e86]
[  1125.646] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb74f040c]
[  1125.646] (EE) 3: /usr/lib/i386-linux-gnu/libpixman-1.so.0 
(0xb734f000+0x83cbe) [0xb73d2cbe]
[  1125.646] (EE) 4: /usr/lib/i386-linux-gnu/libpixman-1.so.0 
(0xb734f000+0x4c12f) [0xb739b12f]
[  1125.647] (EE) 5: /usr/lib/i386-linux-gnu/libpixman-1.so.0 (pixman_blt+0x7d) 
[0xb735554d]
[  1125.647] (EE) 6: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x327) 
[0xb60a7887]
[  1125.647] (EE) 7: 
/usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/glesx.so
 (0xb438a000+0x693b1) [0xb43f33b1]
[  1125.647] (EE) 8: 
/usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/glesx.so
 (0xb438a000+0x6b64c) [0xb43f564c]
[  1125.647] (EE) 9: /usr/bin/X (0xb7513000+0x12e041) [0xb7641041]
[  1125.647] (EE) 
[  1125.647] (EE) Segmentation fault at address 0xab195000
[  1125.647] 
Fatal server error:
[  1125.647] Caught signal 11 (Segmentation fault). Server aborting
[  1125.647] 
[  1125.647] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[  1125.647] (EE) Please also check the log file at /var/log/Xorg.0.log for 
additional information.
[  1125.647] (EE) 
[  1125.650] (II) evdev: Power Button: Close
[  1125.650] (II) UnloadModule: evdev
[  1125.653] (II) evdev: Power Button: Close
[  1125.653] (II) UnloadModule: evdev
[  1125.660] (II) evdev: Sleep Button: Close
[  1125.661] (II) UnloadModule: evdev
[  1125.669] (II) evdev: UVC Camera (046d:0825): Close
[  1125.669] (II) UnloadModule: evdev
[  1125.673] (II) evdev: MOSART Semi. 2.4G Keyboard Mouse: Close
[  1125.673] (II) UnloadModule: evdev
[  1125.682] (II) evdev: MOSART Semi. 2.4G Keyboard Mouse: Close
[  1125.683] (II) UnloadModule: evdev
[  1125.689] (II) evdev: AT Translated Set 2 keyboard: Close
[  1125.689] (II) UnloadModule: evdev
[  1125.690] (II) AIGLX: Suspending AIGLX clients for VT switch
[  1125.692] (II) fglrx(0): Backup framebuffer data.
[  1125.807] (II) fglrx(0): Backup complete.
[  1126.216] Server terminated with error (1). Closing log file.

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

Title:
  SEGV in X Server When Resizing Window

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

Bug description:
  Whenever I attempt to resize a window I get a SEGV in the X server and
  reset to login screen.  Running Lubuntu 13.04 with dual 7970 cards
  physically connected for Crossfire but not enabled in X.

  Using the catalyst 13.4 driver from the AMD website resulting in the
  following packages:

  ii  fglrx 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators
  ii  fglrx-amdcccle2:12.104-0ubuntu1   
amd64Catalyst Control Center for the AMD graphics accelerators
  ii  fglrx-dev 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators (devel files)

  xorg packages installed are as follows:

  ii  xorg  1:7.7+1ubuntu4  
amd64X.Org X Window System
  ii  xorg-docs-core1:1.6-1ubuntu2  
all  Core documentation for the X.org X Window System
  ii  xorg-sgml-doctools1:1.10-1
all  Common tools for building X.Org SGML documentation
  ii  xserver-xorg  1:7.7+1ubuntu4  
amd64X.Org X server
  ii  xserver-xorg-core 2:1.13.3-0ubuntu6   
amd64Xorg X server - core server
  ii  xserver-xorg-input-all1:7.7+1ubuntu4  
amd64X.Org X server -- input driver metapackage
  ii  xserver-xorg-input-evdev  1:2.7.3-0ubuntu2b2  
amd64X.Org X server -- evdev input driver
  ii  xserver-xorg-input-mouse  1:1.7.2-3   
amd64X.Org X server -- mouse input driver
  ii  xserver-xorg-input-synaptics  1.6.2-1ubuntu6  
amd64Synaptics TouchPad driver for X.Org server
  ii  xserver-xorg-input-vmmouse1:12.9.0-0ubuntu3   
amd64X.Org X server -- VMMouse input driver to use with VMWare
  ii  xserver-xorg-input-wacom  1:0.19.0-0ubuntu1   
amd64X.Org X server -- Wacom input driver
  ii  xserver-xorg-video-all1:7.7+1ubuntu4  
amd64X.Org X server -- output driver metapackage
  ii  xserver-xorg-video-ati1:7.1.0-0ubuntu2

[Desktop-packages] [Bug 1209368] Re: pxpress posint fails with: aticonfig: No supported adapters detected

2013-08-14 Thread Alberto Milone

then I suspect it's just that aticonfig detected gpus that aren't
officially supported. This only depends on the driver/hardware
combination and, if the driver works correctly, this is a non issue as
the package was installed correctly. Still, I understand that it can be
confusing but I'd rather not suppress the error output so that we can
catch any other issues.

** Changed in: fglrx-pxpress (Ubuntu)
   Status: New = Won't Fix

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

Title:
  pxpress posint fails with: aticonfig: No supported adapters detected

Status in “fglrx-pxpress” package in Ubuntu:
  Won't Fix

Bug description:
  pxpress installation returns error on multiple system configs:

  Unpacking fglrx-pxpress (0.3)
  Setting up fglrx-pxpress

  aticonfig: no supported adapters detected

  GPUs affected:

  [AMD/ATI] Sun XT [Radeon HD 8670A]

  fglrx version:

  Package: fglrx
  Status: install ok installed
  Priority: extra
  Section: restricted/misc
  Installed-Size: 242621
  Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com
  Architecture: amd64
  Source: fglrx-installer
  Version: 2:13.101-0ubuntu3

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

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

[Desktop-packages] [Bug 1043129] Re: [UIFe] Black borders on some active controls

2013-08-14 Thread Alexander Andjelkovic

** Changed in: lubuntu-artwork
   Status: Fix Committed = Fix Released

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

Title:
  [UIFe] Black borders on some active controls

Status in Artwork for Lubuntu:
  Fix Released
Status in The Unico Gtk+ Theming Engine:
  Opinion
Status in “gtk3-engines-unico” package in Ubuntu:
  Opinion
Status in “lubuntu-artwork” package in Ubuntu:
  Fix Released
Status in “gtk3-engines-unico” source package in Quantal:
  Opinion
Status in “lubuntu-artwork” source package in Quantal:
  Fix Released

Bug description:
  UIFe request :
  Currently, the GTK3 theme has some bugs exposed by the new version of gtk3 
and unico. It needs to be updated to the new versions to display correctly.
  But, currently, the only solution we have is to massively modify the theme, 
which make a diff between the 2 versions very big. Also, such changes make the 
gtk3 widget a lot better, but changes a bit the way gtk3 widgets looks like.

  The new updated theme was already tested by the designers and me, with
  no problem.

  Considering the Lubuntu documentation is gathered on
  https://help.ubuntu.com/community/Lubuntu/Documentation, with a very
  few screenshots up-to-date, the impact for the documentation should be
  very low.

  Also, Lubuntu is still using GTK2 a lot, so the changes are limited to
  several support application (archive, update-manager ...).

  I attached a screenshot of an example of one of the most impacted
  application (to the left side is before the update, the right side is
  after).

  A package is available for testing in my PPA :
  https://launchpad.net/~gilir/+archive/lubuntu

  Original bug report :
  Some GTK controls, specially checkboxes (appear as a square ignoring the 
x), progressbars, buttons and tabs have a black border. It doesn't happen on 
inactive controls, which respect the colour definitions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1043129/+subscriptions

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

[Desktop-packages] [Bug 1211678] Re: Animation path woun't be saved

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete = New

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

Title:
  Animation path woun't be saved

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  If I create an animation (e.g. Left) and move the start and end points
  with mouse, path wount be stored, but UI shows the correct one. It
  will be saved only, if i change the path positions with keyboard
  arrows.

  Steps to reproduce:
  1. Create an Object
  2. Add an animation (e.g. Left)
  3. Change the positions of the start/stop points with mouse.
  4. Start the presentation
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-07-23 (21 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  Package: libreoffice 1:4.0.2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1195811] Re: nouveau: Abnormally high FPS (no vsync) on natively mir testing demo-clients.

2013-08-14 Thread Daniel van Vugt

mlankhost confirms this issue is what he's working on...
http://cgit.freedesktop.org/~mlankhorst/linux/commit/?id=4d2b97bdaebd7686075bce5ad1a498918d2ab17f^
http://cgit.freedesktop.org/~mlankhorst/linux/commit/?id=4d2b97bdaebd7686075bce5ad1a498918d2ab17f

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

Title:
nouveau: Abnormally high FPS (no vsync) on natively mir testing demo-
clients.

Status in Mir:
Triaged
Status in “linux” package in Ubuntu:
In Progress

Bug description:
I installed Ubuntu 13.10 (yesterday) in order to test Xmir and Mir natively
(examples-clients). Xmirg worked flawlessly. The only problem was the
duplicate mouse cursor(s).
But I noticed an abnormally high FPS in some clients demo when I tested Mir
natively per these instructions
http://unity.ubuntu.com/mir/using_mir_on_pc.html

I recorded the test case using external camera. Apologies for the quality
but you will see the values.
http://www.youtube.com/watch?v=zil-lRNlaks

I attached an apport.log just for more info if are needed.

I'm not a technical guy and I filled this report prompted by @duflu in IRC
#ubuntu-mir
You can read the mini conversation here.
http://irclogs.ubuntu.com/2013/06/28/%23ubuntu-mir.html

This test had the same results either if X only was running in VT7 (Video)
or Xmir.
I hope I helped... in something.

Regards
NikTh

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

[Desktop-packages] [Bug 1195811] Re: nouveau: Abnormally high FPS (no vsync) on natively mir testing demo-clients.

2013-08-14 Thread Daniel van Vugt

** Package changed: mesa (Ubuntu) = linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

** Changed in: linux (Ubuntu)
   Status: New = In Progress

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

Title:
  nouveau: Abnormally high FPS (no vsync) on natively mir testing demo-
  clients.

Status in Mir:
  Triaged
Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  I installed Ubuntu 13.10 (yesterday)  in order to test Xmir and Mir natively 
(examples-clients). Xmirg worked flawlessly. The only problem was the 
duplicate mouse cursor(s).
  But I noticed an abnormally high FPS in some clients demo when I tested Mir 
natively per these instructions
  http://unity.ubuntu.com/mir/using_mir_on_pc.html

  I recorded the test case using external camera.  Apologies for the quality 
but you will see the values.
  http://www.youtube.com/watch?v=zil-lRNlaks

  I attached an apport.log just for more info if are needed.

  I'm not a technical guy and I filled this report prompted by @duflu in IRC 
#ubuntu-mir
  You can read the mini conversation here.
  http://irclogs.ubuntu.com/2013/06/28/%23ubuntu-mir.html

  This test had the same results either if X only was running in VT7 (Video)  
or Xmir.
  I hope I helped... in something.

  Regards
   NikTh

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

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

[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected

** Branch linked: lp:debian/fonts-arphic-uming

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

Title:
  Fontconfig warning: Having multiple values in test isn't supported
  and may not works as expected

Status in “culmus” package in Ubuntu:
  Fix Released
Status in “fonts-arphic-ukai” package in Ubuntu:
  Fix Released
Status in “fonts-arphic-uming” package in Ubuntu:
  Fix Released
Status in “fonts-baekmuk” package in Ubuntu:
  Fix Released
Status in “fonts-droid” package in Ubuntu:
  Fix Released
Status in “fonts-nanum” package in Ubuntu:
  Fix Released
Status in “fonts-nanum-coding” package in Ubuntu:
  Fix Released
Status in “fonts-sil-andika” package in Ubuntu:
  Fix Released
Status in “fonts-tlwg” package in Ubuntu:
  Fix Released
Status in “fonts-unfonts-core” package in Ubuntu:
  Fix Released
Status in “fonts-unfonts-extra” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “ttf-wqy-zenhei” package in Ubuntu:
  Fix Released
Status in “culmus” source package in Quantal:
  Fix Released
Status in “fonts-arphic-ukai” source package in Quantal:
  Fix Released
Status in “fonts-arphic-uming” source package in Quantal:
  Fix Released
Status in “fonts-baekmuk” source package in Quantal:
  Fix Released
Status in “fonts-droid” source package in Quantal:
  Fix Released
Status in “fonts-nanum” source package in Quantal:
  Fix Released
Status in “fonts-nanum-coding” source package in Quantal:
  Fix Released
Status in “fonts-sil-andika” source package in Quantal:
  Fix Released
Status in “fonts-tlwg” source package in Quantal:
  Fix Released
Status in “fonts-unfonts-core” source package in Quantal:
  Fix Released
Status in “fonts-unfonts-extra” source package in Quantal:
  Fix Released
Status in “language-selector” source package in Quantal:
  Fix Released
Status in “libreoffice” source package in Quantal:
  Confirmed
Status in “ttf-wqy-zenhei” source package in Quantal:
  Fix Released
Status in “fonts-arphic-ukai” package in Debian:
  Fix Released
Status in “fonts-arphic-uming” package in Debian:
  Fix Released
Status in “fonts-baekmuk” package in Debian:
  Fix Released
Status in “fonts-droid” package in Debian:
  Fix Released
Status in “fonts-nanum” package in Debian:
  Fix Released
Status in “fonts-sil-andika” package in Debian:
  Fix Committed
Status in “fonts-unfonts-core” package in Debian:
  Fix Released
Status in “fonts-unfonts-extra” package in Debian:
  Fix Released
Status in “ttf-wqy-zenhei” package in Debian:
  New
Status in Fedora:
  Unknown

Bug description:
  In 12.10, fontconfig prints warnings similar to the following whenever
  fontconfig is invoked:

  Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf,
  line 11: Having multiple values in test isn't supported and may not
  works as expected

  This affects fonts from a number of packages:
  fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf
  fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf
  fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf
  fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf
  fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf
  fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf
  fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf
  fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf
  fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf

  [Test Case]
  1) Install the fonts in question
  2) Open a terminal
  3) Launch 'gedit' from the terminal

  Expected results:
  gedit launches, no fontconfig warnings in the terminal

  Actual results:
  gedit launches, fontconfig warnings are displayed in the terminal

  [Regression Potential]
  In case of a regression, the font in question can be affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Thu Aug  9 10:02:59 2012
  Dependencies:

  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fonts-unfonts-core
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago)

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

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

[Desktop-packages] [Bug 1211417] Re: whoopsie takes 100% CPU on the phone

2013-08-14 Thread Evan Dandrea

Valgrind isn't showing anything particularly relevant. The uninitialised
value error is present in all bzr revisions of whoopsie when using this
version of libc (2.17-91ubuntu1 - probably earlier ones too as I just
upgraded it).

** Attachment added: vgdump.txt
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1211417/+attachment/3772239/+files/vgdump.txt

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

Title:
  whoopsie takes 100% CPU on the phone

Status in Touch Preview Images:
  Confirmed
Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “whoopsie” package in Ubuntu:
  Confirmed

Bug description:
  device: mako
  Whoopsie 0.2.20

  I just noted whoopise taking 100% cpu on two of the devices in the
  lab, its quite critical since it may kill our phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions

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

[Desktop-packages] [Bug 1177784] Re: SEGV in X Server When Resizing Window

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

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

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

Title:
  SEGV in X Server When Resizing Window

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

Bug description:
  Whenever I attempt to resize a window I get a SEGV in the X server and
  reset to login screen.  Running Lubuntu 13.04 with dual 7970 cards
  physically connected for Crossfire but not enabled in X.

  Using the catalyst 13.4 driver from the AMD website resulting in the
  following packages:

  ii  fglrx 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators
  ii  fglrx-amdcccle2:12.104-0ubuntu1   
amd64Catalyst Control Center for the AMD graphics accelerators
  ii  fglrx-dev 2:12.104-0ubuntu1   
amd64Video driver for the AMD graphics accelerators (devel files)

  xorg packages installed are as follows:

  ii  xorg  1:7.7+1ubuntu4  
amd64X.Org X Window System
  ii  xorg-docs-core1:1.6-1ubuntu2  
all  Core documentation for the X.org X Window System
  ii  xorg-sgml-doctools1:1.10-1
all  Common tools for building X.Org SGML documentation
  ii  xserver-xorg  1:7.7+1ubuntu4  
amd64X.Org X server
  ii  xserver-xorg-core 2:1.13.3-0ubuntu6   
amd64Xorg X server - core server
  ii  xserver-xorg-input-all1:7.7+1ubuntu4  
amd64X.Org X server -- input driver metapackage
  ii  xserver-xorg-input-evdev  1:2.7.3-0ubuntu2b2  
amd64X.Org X server -- evdev input driver
  ii  xserver-xorg-input-mouse  1:1.7.2-3   
amd64X.Org X server -- mouse input driver
  ii  xserver-xorg-input-synaptics  1.6.2-1ubuntu6  
amd64Synaptics TouchPad driver for X.Org server
  ii  xserver-xorg-input-vmmouse1:12.9.0-0ubuntu3   
amd64X.Org X server -- VMMouse input driver to use with VMWare
  ii  xserver-xorg-input-wacom  1:0.19.0-0ubuntu1   
amd64X.Org X server -- Wacom input driver
  ii  xserver-xorg-video-all1:7.7+1ubuntu4  
amd64X.Org X server -- output driver metapackage
  ii  xserver-xorg-video-ati1:7.1.0-0ubuntu2
amd64X.Org X server -- AMD/ATI display driver wrapper
  ii  xserver-xorg-video-cirrus 1:1.5.2-0ubuntu1
amd64X.Org X server -- Cirrus display driver
  ii  xserver-xorg-video-fbdev  1:0.4.3-0ubuntu1
amd64X.Org X server -- fbdev display driver
  ii  xserver-xorg-video-intel  2:2.21.6-0ubuntu4   
amd64X.Org X server -- Intel i8xx, i9xx display driver
  ii  xserver-xorg-video-mach64 6.9.3-0ubuntu1  
amd64X.Org X server -- ATI Mach64 display driver
  ii  xserver-xorg-video-mga1:1.6.2-0ubuntu1
amd64X.Org X server -- MGA display driver
  ii  xserver-xorg-video-modesetting0.7.0-0ubuntu2  
amd64X.Org X server -- Generic modesetting driver
  ii  xserver-xorg-video-neomagic   1:1.2.7-0ubuntu1
amd64X.Org X server -- Neomagic display driver
  ii  xserver-xorg-video-nouveau1:1.0.7-0ubuntu1
amd64X.Org X server -- Nouveau display driver
  ii  xserver-xorg-video-openchrome 1:0.3.1-0ubuntu1
amd64X.Org X server -- VIA display driver
  ii  xserver-xorg-video-qxl0.1.0-0ubuntu3  
amd64X.Org X server -- QXL display driver
  ii  xserver-xorg-video-r128   6.9.1-0ubuntu1  
amd64X.Org X server -- ATI r128 display driver
  ii  xserver-xorg-video-radeon 1:7.1.0-0ubuntu2
amd64X.Org X server -- AMD/ATI Radeon display driver
  ii  xserver-xorg-video-s3 1:0.6.5-0ubuntu3
amd64X.Org X server -- legacy S3 display driver
  ii  xserver-xorg-video-savage 1:2.3.6-0ubuntu1
amd64X.Org X server -- Savage display driver
  ii  xserver-xorg-video-siliconmotion  1:1.7.7-0ubuntu1
amd64X.Org X server -- SiliconMotion display driver

[Desktop-packages] [Bug 1212200] [NEW] package xul-ext-ubufox (not installed) failed to install/upgrade: trying to overwrite '/usr/share/xul-ext/ubufox/defaults/preferences/ubuntu-mods.js', which is a

2013-08-14 Thread Ricky B.

Public bug reported:

Could not install Nvidia drivers : Ref:
http://www.linwik.com/configuring_a_nvidia_graphics_chip_for_ubuntu_10.04

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: xul-ext-ubufox (not installed)
ProcVersionSignature: Ubuntu 2.6.32-50.112-generic-pae 2.6.32.61+drm33.26
Uname: Linux 2.6.32-50-generic-pae i686
Architecture: i386
Date: Wed Aug 14 11:41:54 2013
ErrorMessage: trying to overwrite 
'/usr/share/xul-ext/ubufox/defaults/preferences/ubuntu-mods.js', which is also 
in package ubufox 0:1.9~rc2-2easypeasy0
InstallationMedia: EasyPeasy 1.6
SourcePackage: ubufox
Title: package xul-ext-ubufox (not installed) failed to install/upgrade: trying 
to overwrite '/usr/share/xul-ext/ubufox/defaults/preferences/ubuntu-mods.js', 
which is also in package ubufox 0:1.9~rc2-2easypeasy0

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


** Tags: apport-package i386 lucid ubuntu-une

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

Title:
  package xul-ext-ubufox (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/xul-ext/ubufox/defaults/preferences
  /ubuntu-mods.js', which is also in package ubufox
  0:1.9~rc2-2easypeasy0

Status in “ubufox” package in Ubuntu:
  New

Bug description:
  Could not install Nvidia drivers : Ref:
  http://www.linwik.com/configuring_a_nvidia_graphics_chip_for_ubuntu_10.04

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: xul-ext-ubufox (not installed)
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic-pae 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic-pae i686
  Architecture: i386
  Date: Wed Aug 14 11:41:54 2013
  ErrorMessage: trying to overwrite 
'/usr/share/xul-ext/ubufox/defaults/preferences/ubuntu-mods.js', which is also 
in package ubufox 0:1.9~rc2-2easypeasy0
  InstallationMedia: EasyPeasy 1.6
  SourcePackage: ubufox
  Title: package xul-ext-ubufox (not installed) failed to install/upgrade: 
trying to overwrite 
'/usr/share/xul-ext/ubufox/defaults/preferences/ubuntu-mods.js', which is also 
in package ubufox 0:1.9~rc2-2easypeasy0

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

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

[Desktop-packages] [Bug 1007765] Re: brightness adjusting crashes system

2013-08-14 Thread Anoop

This is an update to my post No.93... Not a single time i have have faced any 
problem with the brigtness button :
after SPARX No.17 comment ( sorry for saying that it was Marwans)

This bug is FIXED for me by adding these kernel options:

GRUB_CMDLINE_LINUX_DEFAULT=quiet splash pcie_aspm=force
acpi_backlight=vendor

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

Title:
  brightness adjusting crashes system

Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When adjusting my laptops brightness the system crashes.

  what logs do in need to add and how to get them?

  System:
  -- Dell Studio 1558
  -- Ubuntu 12.04

  Video showing the process: http://www.youtube.com/watch?v=Vxp_rWXHnrg
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  CompizPlugins: [core,composite,opengl,neg,commands,put]
  CompositorRunning: None
  DistUpgraded: 2012-01-26 12:27:33,165 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 5.100.82.38+bdcom, 3.2.0-23-generic, x86_64: installed
   bcmwl, 5.100.82.38+bdcom, 3.2.0-24-generic, x86_64: installed
   fglrx, 8.960, 3.2.0-20-generic, x86_64: installed
   fglrx, 8.960, 3.2.0-23-generic, x86_64: installed
   fglrx, 8.960, 3.2.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4500/5100 
Series] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0413]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use) 
[auto-install]
   xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, 
Enabled, In use)
  MachineType: Dell Inc. Studio 1558
  NonfreeKernelModules: fglrx wl
  Package: xorg 1:7.6+12ubuntu1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=cd6ba6ea-6e63-41cc-b872-c101873444c6 ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Tags:  precise ubuntu
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: Upgraded to precise on 2012-01-26 (129 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd09/13/2010:svnDellInc.:pnStudio1558:pvrA10:rvnDellInc.:rn:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Studio 1558
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Desktop-packages] [Bug 1207985] Re: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-data.owner == 0« nicht erfüllt.

Sounds like an unitialized mutex. This is a problem on i386, but not really on 
amd64 so you won't hit it there.
Are you doing anything specific when triggering this bug?

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

Title:
  compiz assert failure: compiz: pthread_mutex_lock.c:65:
  __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht
  erfüllt.

Status in “unity” package in Ubuntu:
  Triaged
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  Just followed this guide:
  http://unity.ubuntu.com/mir/using_mir_on_pc.html. After restarting
  lightdm, unity won't start.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130802-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  AssertionMessage: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: 
Zusicherung »mutex-__data.__owner == 0« nicht erfüllt.
  Date: Sat Aug  3 15:00:00 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-08-03 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity
  StacktraceTop:
   __assert_fail_base (fmt=0x7f370806fdbb Address 0x7f370806fdbb out of 
bounds, assertion=assertion@entry=0x7f370ec207ef mutex-__data.__owner == 0, 
file=file@entry=0x7f370ec20dfe pthread_mutex_lock.c, line=line@entry=65, 
function=function@entry=0x7f370ec208c0 __PRETTY_FUNCTION__.8369 
__pthread_mutex_lock) at assert.c:92
   __GI___assert_fail (assertion=0x7f370ec207ef mutex-__data.__owner == 0, 
file=0x7f370ec20dfe pthread_mutex_lock.c, line=65, function=0x7f370ec208c0 
__PRETTY_FUNCTION__.8369 __pthread_mutex_lock) at assert.c:101
   __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at 
pthread_mutex_lock.c:65
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: compiz assert failure: compiz: pthread_mutex_lock.c:65: 
__pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 784366] Re: caption plugin for texlive needs to be updated

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

** Changed in: texlive-base (Ubuntu)
   Status: New = Confirmed

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

Title:
  caption plugin for texlive needs to be updated

Status in “texlive-base” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: texlive-base

  With some latex files, figure captions are not processed correctly.
  This is due to an outdated caption.sty shipping with texlive on
  Ubuntu.

  The problem has already been described in detail at
  tex.stackexchange.com:

  http://tex.stackexchange.com/questions/2462/enumerate-and-itemize-
  undefined-captions-not-working

  The solution is to ship the latest version of caption from CTAN:

  http://mirror.ctan.org/macros/latex/contrib/caption.zip

  as part of texlive in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/784366/+subscriptions

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

[Desktop-packages] [Bug 784366] Re: caption plugin for texlive needs to be updated

2013-08-14 Thread Álvaro Morán

Another example that only works with the latex version of the caption
package: http://tex.stackexchange.com/questions/128103/hang-caption-in-
lstlisting/128141#128141

The example was written by its maintainer

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

Title:
  caption plugin for texlive needs to be updated

Status in “texlive-base” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: texlive-base

  With some latex files, figure captions are not processed correctly.
  This is due to an outdated caption.sty shipping with texlive on
  Ubuntu.

  The problem has already been described in detail at
  tex.stackexchange.com:

  http://tex.stackexchange.com/questions/2462/enumerate-and-itemize-
  undefined-captions-not-working

  The solution is to ship the latest version of caption from CTAN:

  http://mirror.ctan.org/macros/latex/contrib/caption.zip

  as part of texlive in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/784366/+subscriptions

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

[Desktop-packages] [Bug 1207985] Re: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-data.owner == 0« nicht erfüllt.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

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

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

Title:
  compiz assert failure: compiz: pthread_mutex_lock.c:65:
  __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht
  erfüllt.

Status in “unity” package in Ubuntu:
  Invalid
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  Just followed this guide:
  http://unity.ubuntu.com/mir/using_mir_on_pc.html. After restarting
  lightdm, unity won't start.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130802-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  AssertionMessage: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: 
Zusicherung »mutex-__data.__owner == 0« nicht erfüllt.
  Date: Sat Aug  3 15:00:00 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-08-03 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity
  StacktraceTop:
   __assert_fail_base (fmt=0x7f370806fdbb Address 0x7f370806fdbb out of 
bounds, assertion=assertion@entry=0x7f370ec207ef mutex-__data.__owner == 0, 
file=file@entry=0x7f370ec20dfe pthread_mutex_lock.c, line=line@entry=65, 
function=function@entry=0x7f370ec208c0 __PRETTY_FUNCTION__.8369 
__pthread_mutex_lock) at assert.c:92
   __GI___assert_fail (assertion=0x7f370ec207ef mutex-__data.__owner == 0, 
file=0x7f370ec20dfe pthread_mutex_lock.c, line=65, function=0x7f370ec208c0 
__PRETTY_FUNCTION__.8369 __pthread_mutex_lock) at assert.c:101
   __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at 
pthread_mutex_lock.c:65
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: compiz assert failure: compiz: pthread_mutex_lock.c:65: 
__pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function

Maverick EOL - Won't Fix.

** Changed in: linux (Ubuntu Maverick)
   Status: Confirmed = Invalid

** Tags added: bios-outdated-1903 needs-upstream-testing

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

Title:
  ALT+PrtSc not recognised: breaks built-in screenshot function

Status in Release Notes for Ubuntu:
  Invalid
Status in “compiz” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete
Status in “metacity” package in Ubuntu:
  Invalid
Status in “compiz” source package in Maverick:
  Invalid
Status in “linux” source package in Maverick:
  Invalid
Status in “metacity” source package in Maverick:
  Invalid

Bug description:
  Binary package hint: xkeyboard-config

  On an EN-GB keyboard (and maybe others) ALT+PrtSc is the default
  keyboard shortcut for Take a screenshot of a window as configured in
  System - Preferences - Keyboard Shortcuts. However the system
  doesn't seem to respond to that keyboard combination at all. Pressing
  ALT+PrtSc on a default Maverick install does nothing. Indeed
  attempting to _set_ that keyboard shortcut in the Keyboard Shortcuts
  dialog results in it not being registered.

  Workaround:
  sudo sysctl -w kernel.sysrq=0

  Steps to reproduce:-

  1) Try to screenshot the entire desktop with PrtSc - this works
  2) Try to take a screenshot of one active window with ALT+PrtSc - nothing 
happens.

  Additionally

  1) Navigate to System - Preferences - Keyboard Shortcuts
  2) Scroll down to Desktop - Take a screenshot of a window, and then click 
that line in order to set a keyboard shortcut for the action
  3) Press ALT+PrtSc - nothing happens
  4) Press a different keyboard combination such as CTRL+PrtSc or 
Super/Windows+PrtSc - this works

  Additionally

  1) Open a terminal
  2) Run 'xev' and then press ALT+PrtSc. Observe data in the xev terminal 
window when ALT is pressed, but nothing for ALT+PrtSc

  Seems a fairly critical regression bug given we document this keyboard
  shortcut in the help, and it's very commonly used by documenters and
  people getting support. It works fine in previous releases.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xkb-data 1.8-1ubuntu8
  ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  256.53  Fri Aug 27 20:27:48 
PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4)
  Architecture: amd64
  CurrentDmesg:
   [   22.090007] eth1: no IPv6 routers present
   [  691.401253] show_signal_msg: 9 callbacks suppressed
   [  691.401258] gnome-help[2307]: segfault at 35a3f08 ip 7f9f58d3043e sp 
7d377130 error 4 in libxml2.so.2.7.7[7f9f58cae000+147000]
  Date: Sun Sep 19 14:19:15 2010
  Dependencies:

  DkmsStatus:
   nvidia-current, 256.53, 2.6.35-22-generic, x86_64: installed
   nvidia-current, 256.53, 2.6.35-21-generic, x86_64: installed
   nvidia-current, 256.53, 2.6.35-20-generic, x86_64: installed
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=fb22b4e1-1576-4bf8-8272-15300bc7de38 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: xkeyboard-config
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801
  dmi.board.name: P5N32-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/642792/+subscriptions

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

[Desktop-packages] [Bug 1212212] Re: Xorg crashed with SIGABRT in OsAbort()

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

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 #1188123, 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/1212212/+attachment/3772316/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772318/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772329/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772331/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772332/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772333/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212212/+attachment/3772334/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1188123
   Xorg crashed with SIGABRT in OsAbort()

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  Crash on shutdown/restart

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu3
  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
  CurrentDmesg:
   [   15.993185] r8169 :02:00.0 eth0: link up
   [   15.993196] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Wed Aug 14 19:19:12 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:21b2]
  InstallationDate: Installed on 2013-06-22 (53 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=6211c40e-0663-4efe-9135-f14c26310ebd ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7f81a1c19060, argc=9, ubp_av=0x7fff038f1fb8, 
init=optimised out, fini=optimised out, rtld_fini=optimised out, 
stack_end=0x7fff038f1fa8) at libc-start.c:260
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/30/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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-0ubuntu2

[Desktop-packages] [Bug 1212212] [NEW] Xorg crashed with SIGABRT in OsAbort()

2013-08-14 Thread Michael Blennerhassett

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

Public bug reported:

Crash on shutdown/restart

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.2-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12-0ubuntu3
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
CurrentDmesg:
 [   15.993185] r8169 :02:00.0 eth0: link up
 [   15.993196] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Wed Aug 14 19:19:12 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:21b2]
InstallationDate: Installed on 2013-06-22 (53 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=6211c40e-0663-4efe-9135-f14c26310ebd ro quiet splash
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x7f81a1c19060, argc=9, ubp_av=0x7fff038f1fb8, 
init=optimised out, fini=optimised out, rtld_fini=optimised out, 
stack_end=0x7fff038f1fa8) at libc-start.c:260
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 12/30/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-MA780G-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA780G-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
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-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
xserver.bootTime: Wed Aug 14 19:22:34 2013
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input  USB Keyboard   KEYBOARD, id 8
 input  USB Keyboard   KEYBOARD, id 9
 inputMicrosoft  Microsoft Basic Optical Mouse v2.0  MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.14.2-0ubuntu9

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


** Tags: amd64 apport-crash compiz-0.9 saucy ubuntu

** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  Crash on shutdown/restart

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu3
  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
  CurrentDmesg:
   [   15.993185] r8169 :02:00.0 eth0: link up
   [   15.993196] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Wed Aug 14 19:19:12 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg

[Desktop-packages] [Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function

Alan Pope, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications-Accessories-Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux replace-with-bug-number

Also, could you please test the latest upstream kernel available following 
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional 
upstream developers to examine the issue. Please do not test the daily folder, 
but the one all the way at the bottom. Once you've tested the upstream kernel, 
please comment on which kernel version specifically you tested. If this bug is 
fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why 
specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.


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

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

Title:
  ALT+PrtSc not recognised: breaks built-in screenshot function

Status in Release Notes for Ubuntu:
  Invalid
Status in “compiz” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete
Status in “metacity” package in Ubuntu:
  Invalid
Status in “compiz” source package in Maverick:
  Invalid
Status in “linux” source package in Maverick:
  Invalid
Status in “metacity” source package in Maverick:
  Invalid

Bug description:
  Binary package hint: xkeyboard-config

  On an EN-GB keyboard (and maybe others) ALT+PrtSc is the default
  keyboard shortcut for Take a screenshot of a window as configured in
  System - Preferences - Keyboard Shortcuts. However the system
  doesn't seem to respond to that keyboard combination at all. Pressing
  ALT+PrtSc on a default Maverick install does nothing. Indeed
  attempting to _set_ that keyboard shortcut in the Keyboard Shortcuts
  dialog results in it not being registered.

  Workaround:
  sudo sysctl -w kernel.sysrq=0

  Steps to reproduce:-

  1) Try to screenshot the entire desktop with PrtSc - this works
  2) Try to take a screenshot of one active window with ALT+PrtSc - nothing 
happens.

  Additionally

  1) Navigate to System - Preferences - Keyboard Shortcuts
  2) Scroll down to Desktop - Take a screenshot of a window, and then click 
that line in order to set a keyboard shortcut for the action
  3) Press ALT+PrtSc - nothing happens
  4) Press a different keyboard combination such as CTRL+PrtSc or 
Super/Windows+PrtSc - this works

  Additionally

  1) Open a terminal
  2) Run 'xev' and then press ALT+PrtSc. Observe data in the xev terminal 
window when ALT is pressed, but nothing for ALT+PrtSc

  Seems a fairly critical regression bug given we document this keyboard
  shortcut in the help, and it's very commonly used by documenters and
  people getting support. It works fine in previous releases.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xkb-data 1.8-1ubuntu8
  ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  256.53  Fri Aug 27 20:27:48 
PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4)
  Architecture: amd64
  CurrentDmesg:
   [   22.090007] eth1: no IPv6 routers present
   [  691.401253] show_signal_msg: 9 callbacks suppressed
   [  691.401258] gnome-help[2307]: segfault at 35a3f08 ip 7f9f58d3043e sp 
7d377130 error 4 in libxml2.so.2.7.7[7f9f58cae000+147000]
  Date: Sun Sep 19 14:19:15 2010
  Dependencies:

  DkmsStatus:
   nvidia-current, 256.53, 2.6.35-22-generic, x86_64: installed
   nvidia-current, 256.53,

[Desktop-packages] [Bug 1212216] [NEW] python-loader:type 'exceptions.ImportError':No module named pythonloader

2013-08-14 Thread cpina

Public bug reported:

Summary:
System version: Ubuntu 12.04.2 LTS, Release 12.04
Package: libreoffice . Version:  1:4.1.0-0ubuntu1-precise1~ppa1
Expected to happen: Mendeley Desktop plugin working like in previous 
Libreoffice or Libreoffice from mainstream.
What happened: it fails with a python-loader error. Possible workaround: export 
PYTHONPATH=/usr/lib/libreoffice/program/

Longer description and workaround:
When trying to use Mendeley Desktop Libreoffice extension (and, I see on the 
Internet, other extensions) it doesn't work. Appears:

BASIC runtime error.
An exception ocurred
Type: com.sun.star.uno.RuntimeException
Message: python-loader:type 'exceptions.ImportError': No module named 
pythonloader, traceback follows
no traceback available
.


This can be reproduced using libreoffice version
1:4.1.0-0ubuntu1-precise1~ppa1

It's working correctly using Libreoffice from www.libreoffice.org.

A possible workaround is to launch Libreoffice this way:
export PYTHONPATH=/usr/lib/libreoffice/program/ ; libreoffice
(note that pythonloader.py is in that directory)

See a confirmation here:
https://github.com/Mendeley/openoffice-plugin/issues/11

So it fails libreoffice 4.1 PPA but not the upstream one, and there is a
workaround (too complicated for some users).

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

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

Title:
  python-loader:type 'exceptions.ImportError':No module named
  pythonloader

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Summary:
  System version: Ubuntu 12.04.2 LTS, Release 12.04
  Package: libreoffice . Version:  1:4.1.0-0ubuntu1-precise1~ppa1
  Expected to happen: Mendeley Desktop plugin working like in previous 
Libreoffice or Libreoffice from mainstream.
  What happened: it fails with a python-loader error. Possible workaround: 
export PYTHONPATH=/usr/lib/libreoffice/program/

  Longer description and workaround:
  When trying to use Mendeley Desktop Libreoffice extension (and, I see on the 
Internet, other extensions) it doesn't work. Appears:
  
  BASIC runtime error.
  An exception ocurred
  Type: com.sun.star.uno.RuntimeException
  Message: python-loader:type 'exceptions.ImportError': No module named 
pythonloader, traceback follows
  no traceback available
  .
  

  This can be reproduced using libreoffice version
  1:4.1.0-0ubuntu1-precise1~ppa1

  It's working correctly using Libreoffice from www.libreoffice.org.

  A possible workaround is to launch Libreoffice this way:
  export PYTHONPATH=/usr/lib/libreoffice/program/ ; libreoffice
  (note that pythonloader.py is in that directory)

  See a confirmation here:
  https://github.com/Mendeley/openoffice-plugin/issues/11

  So it fails libreoffice 4.1 PPA but not the upstream one, and there is
  a workaround (too complicated for some users).

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

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

[Desktop-packages] [Bug 1212216] Re: python-loader:type 'exceptions.ImportError':No module named pythonloader

cpina, thank you for reporting this and trying to help make Ubuntu better. 
However, the LibreOffice PPA is not a software package provided by the official 
Ubuntu repositories. Because of this the Ubuntu project can not support or fix 
your particular bug. Please report this bug to the provider of the software 
package. As per https://launchpad.net/~libreoffice/+archive/ppa :
For questions and bugs with software in this PPA please contact LibreOffice 
Packaging https://launchpad.net/~libreoffice .

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories .

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

** Changed in: libreoffice (Ubuntu)
   Status: New = Invalid

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

Title:
  python-loader:type 'exceptions.ImportError':No module named
  pythonloader

Status in “libreoffice” package in Ubuntu:
  Invalid

Bug description:
  Summary:
  System version: Ubuntu 12.04.2 LTS, Release 12.04
  Package: libreoffice . Version:  1:4.1.0-0ubuntu1-precise1~ppa1
  Expected to happen: Mendeley Desktop plugin working like in previous 
Libreoffice or Libreoffice from mainstream.
  What happened: it fails with a python-loader error. Possible workaround: 
export PYTHONPATH=/usr/lib/libreoffice/program/

  Longer description and workaround:
  When trying to use Mendeley Desktop Libreoffice extension (and, I see on the 
Internet, other extensions) it doesn't work. Appears:
  
  BASIC runtime error.
  An exception ocurred
  Type: com.sun.star.uno.RuntimeException
  Message: python-loader:type 'exceptions.ImportError': No module named 
pythonloader, traceback follows
  no traceback available
  .
  

  This can be reproduced using libreoffice version
  1:4.1.0-0ubuntu1-precise1~ppa1

  It's working correctly using Libreoffice from www.libreoffice.org.

  A possible workaround is to launch Libreoffice this way:
  export PYTHONPATH=/usr/lib/libreoffice/program/ ; libreoffice
  (note that pythonloader.py is in that directory)

  See a confirmation here:
  https://github.com/Mendeley/openoffice-plugin/issues/11

  So it fails libreoffice 4.1 PPA but not the upstream one, and there is
  a workaround (too complicated for some users).

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

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

[Desktop-packages] [Bug 1212221] [NEW] empathy crashed with SIGSEGV in ffi_call_unix64()

2013-08-14 Thread Muelli

Public bug reported:

I was double clicking a contact in the roster

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.4-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Wed Aug 14 13:56:27 2013
Disassembly: = 0x0001: Cannot access memory at address 
0x0001
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2013-06-18 (57 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0x0001:  Cannot access memory at address 
0x0001
 PC (0x0001) not located in a known VMA region (needed executable 
region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
 _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
Title: empathy crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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


** Tags: amd64 apport-crash need-amd64-retrace raring

** Information type changed from Private to Public

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

Title:
  empathy crashed with SIGSEGV in ffi_call_unix64()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I was double clicking a contact in the roster

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 13:56:27 2013
  Disassembly: = 0x0001:   Cannot access memory at address 
0x0001
  ExecutablePath: /usr/bin/empathy
  InstallationDate: Installed on 2013-06-18 (57 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x0001:Cannot access memory at address 
0x0001
   PC (0x0001) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
   _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
  Title: empathy crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1212221]

StacktraceTop:
 ?? ()
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x707b2c50, fn=fn@entry=0x422310 
event_activated_cb, rvalue=0x707b2b80, 
avalue=avalue@entry=0x707b2b20) at ../src/x86/ffi64.c:522
 g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310 
event_activated_cb, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
 _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840

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

Title:
  empathy crashed with SIGSEGV in ffi_call_unix64()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I was double clicking a contact in the roster

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 13:56:27 2013
  Disassembly: = 0x0001:   Cannot access memory at address 
0x0001
  ExecutablePath: /usr/bin/empathy
  InstallationDate: Installed on 2013-06-18 (57 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x0001:Cannot access memory at address 
0x0001
   PC (0x0001) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
   _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
  Title: empathy crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1212221] StacktraceSource.txt

** Attachment added: StacktraceSource.txt
   
https://bugs.launchpad.net/bugs/1212221/+attachment/3772354/+files/StacktraceSource.txt

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

Title:
  empathy crashed with SIGSEGV in ffi_call_unix64()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I was double clicking a contact in the roster

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 13:56:27 2013
  Disassembly: = 0x0001:   Cannot access memory at address 
0x0001
  ExecutablePath: /usr/bin/empathy
  InstallationDate: Installed on 2013-06-18 (57 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x0001:Cannot access memory at address 
0x0001
   PC (0x0001) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
   _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
  Title: empathy crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1212221] Stacktrace.txt

** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212221/+attachment/3772353/+files/Stacktrace.txt

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

Title:
  empathy crashed with SIGSEGV in ffi_call_unix64()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I was double clicking a contact in the roster

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 13:56:27 2013
  Disassembly: = 0x0001:   Cannot access memory at address 
0x0001
  ExecutablePath: /usr/bin/empathy
  InstallationDate: Installed on 2013-06-18 (57 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x0001:Cannot access memory at address 
0x0001
   PC (0x0001) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
   _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
  Title: empathy crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1212221] ThreadStacktrace.txt

** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212221/+attachment/3772355/+files/ThreadStacktrace.txt

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1212221/+attachment/3772344/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  empathy crashed with SIGSEGV in ffi_call_unix64()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I was double clicking a contact in the roster

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 13:56:27 2013
  Disassembly: = 0x0001:   Cannot access memory at address 
0x0001
  ExecutablePath: /usr/bin/empathy
  InstallationDate: Installed on 2013-06-18 (57 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x0001:Cannot access memory at address 
0x0001
   PC (0x0001) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, 
instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, 
n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550
   _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, 
args=0x707b2f88, n_params=2, param_types=0xed0f00) at 
/build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
  Title: empathy crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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

[Desktop-packages] [Bug 1098233] Re: flashplugin-installer do not honore proxy settings

2013-08-14 Thread Waseem Elliot

Aso affects 12.04

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

Title:
  flashplugin-installer do not honore proxy settings

Status in Adobe Flash Plugin Tools:
  New
Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 12.10
  Release:  12.10
  Codename: quantal

  flashplugin-installer:
    Installato: 11.2.202.258ubuntu0.12.10.1
    Candidato:  11.2.202.261ubuntu0.12.10.1
    Tabella versione:
   11.2.202.261ubuntu0.12.10.1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal-updates/multiverse i386 
Packages
  500 http://archive.ubuntu.com/ubuntu/ quantal-security/multiverse 
i386 Packages
   *** 11.2.202.258ubuntu0.12.10.1 0
  100 /var/lib/dpkg/status
   11.2.202.243ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/multiverse i386 Packages

  flashplugin-installer do not honore proxy settings so cannot download
  the proxy so my update are frozen on

  Elaborazione dei trigger per update-notifier-common...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz

  already reported:
  https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1037662

  Very old issue still not solved... :-(

  # Workaround for user with same issue 

  As a workaround... while the apt-get update process is frozen on the
  row below

  Elaborazione dei trigger per update-notifier-common...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz

  Opening another terminal...
  wget 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz
  sudo /usr/lib/flashplugin-installer/install_plugin 
$(pwd)/adobe-flashplugin_11.2.202.261.orig.tar.gz
  rm adobe-flashplugin_11.2.202.261.orig.tar.gz

  then to release the frozen update process, type:

  sudo killall dpkg

  or reboot the pc, then type:

  sudo dpkg --configure -a

  to check and put in a good state the apt env...

  # --

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: flashplugin-installer 11.2.202.258ubuntu0.12.10.1
  Uname: Linux 3.7.1-030701-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Thu Jan 10 15:39:05 2013
  MarkForUpload: True
  SourcePackage: flashplugin-nonfree
  UpgradeStatus: Upgraded to quantal on 2012-07-02 (192 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1098233/+subscriptions

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

[Desktop-packages] [Bug 784366] Re: caption plugin for texlive needs to be updated

2013-08-14 Thread Álvaro Morán

I have developed a quick fix, just create this makefile and run it:

all: compile install

download:
if [ ! -f ./caption/caption.ins ]; then \
wget http://mirrors.ctan.org/macros/latex/contrib/caption.zip ;\
unzip caption.zip ;\
fi

compile: download
cd caption;\
latex caption.ins

documentation: compile
cd caption;\
latex caption-eng.tex;\
#latex caption-deu.tex;\
#latex caption-rus.tex;

install:
if [ `whoami` != root ]; then \
echo This must be run as root ;\
else \
RUTACAPTION=$$(kpsewhich caption.sty|xargs dirname) ;\
echo The files in $$RUTACAPTION will be backed up in a folder 
called caption.old ;\
cp -R $$RUTACAPTION caption.old ;\
cp  ./caption/*.sty $$RUTACAPTION ;\
sudo texhash ;\
fi

clean:
rm caption.zip
rm -R caption

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

Title:
  caption plugin for texlive needs to be updated

Status in “texlive-base” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: texlive-base

  With some latex files, figure captions are not processed correctly.
  This is due to an outdated caption.sty shipping with texlive on
  Ubuntu.

  The problem has already been described in detail at
  tex.stackexchange.com:

  http://tex.stackexchange.com/questions/2462/enumerate-and-itemize-
  undefined-captions-not-working

  The solution is to ship the latest version of caption from CTAN:

  http://mirror.ctan.org/macros/latex/contrib/caption.zip

  as part of texlive in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/784366/+subscriptions

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

[Desktop-packages] [Bug 1130500] Re: Not visible main window

2013-08-14 Thread Ketil Malde

I saw this, but removing .purple/prefs.xml fixed it (i.e. it displayed
the window again when I started pidgin, but of course I lost a bunch of
my preferences.)

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

Title:
  Not visible main window

Status in “pidgin” package in Ubuntu:
  Confirmed

Bug description:
  On start the main window Pidgin is not visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pidgin 1:2.10.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Wed Feb 20 09:28:16 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to raring on 2013-02-06 (13 days ago)

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

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

[Desktop-packages] [Bug 1062077] Re: [HP TouchSmart tm2-2010eg] Linux hangs with: [drm:atom_op_jump] ERROR atombios stuck in loop for more than 5secs aborting

2013-08-14 Thread Simon K

So after finding an Windows image and flashing my Bios to F.25 the
problem is still the there.

What happened:
I installed WinVista, flashed my BIOS (The Insyde-Setup sayed: old ID: 1486, 
old Version: F.12 - new ID: 1486, new Version: F.25)
After finishing the setup my PC shutdown. The power seemed to be disconnected 
abruptly (like when I disconnect my power-cable and there is no battery while 
the notebook is running)

After that I started my notebook, the BIOS seems to sometimes not register my 
keys (i.e. I can't open some pages from others, where I could before).
Ubuntu didn't show anything on the build in screen. I plugged in an external 
screen, started Ubuntu and switched, via tty1, the graphicscard to Intel only 
(IGD).
At this point I started Ubuntu in the Recovery Mode (via Grub) and activated 
Xorg failsafe. It did however hang a huge time without starting any X. So I 
rebooted.
After a new restart I could change my brightness with my FN-keys again (my 
Notebook starts with a blank screen every time, I have to higher the brightness 
then).


octavian-tm2:~$ sudo dmidecode -s bios-version  sudo dmidecode -s 
bios-release-date
[sudo] password for octavian: 
F.25
02/18/2011

I hope the important informations where mentioned by me.

PS: I've tested a few times, subjectively I would say that it got better
(it hangs for a shorter time period), this however needs more testing to
be sure.

** Tags removed: bios-outdated-f.25

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

Title:
  [HP TouchSmart tm2-2010eg] Linux hangs with: [drm:atom_op_jump]
  *ERROR* atombios stuck in loop for more than 5secs aborting

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed

Bug description:
  Symptom: Linux isn't displaying changes after switching to tty1 and
  back to unity

  Steps to reproduce:
  1. Starting up to Unity
  2. Switch to tty1 (Strg + Alt + F1)
  3. Switching back to Unity

  or:
  Resuming the system from suspend leads to the same isssue.This method isn't 
as reliable as the method stated above

  What happens:
  The screen freezes. Magic Keys [Alt + Print + S/U/B] are working thou (so 
linux-kernel is responding?!) I can't switch to tty1 either. The system becomes 
responding again after ~2min. Switching VTs is possible afterwards but leads to 
the same bug again.

  What is expected:
  Showing up a responding Unity.

  Interesting Sitenote:
  My radeon is switched off using: 
echoOFF/sys/kernel/debug/vgaswitcheroo/switch
  By turning ON the graphiccard the above stated problem doesn't appear.

  A short extract of kern.log (full one is attached):
  Oct  5 09:06:06 Octavian-Notebook kernel: [  186.691685] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:06 Octavian-Notebook kernel: [  186.691700] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692930] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692949] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692960] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C040 (len 861, 
WS 0, PS 0) @ 0xC09D
  Oct  5 09:06:16 Octavian-Notebook kernel: [  197.021996] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:16 Octavian-Notebook kernel: [  197.022011] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE0C (len 72, 
WS 0, PS 0) @ 0xCE3B
  Oct  5 09:06:22 Octavian-Notebook kernel: [  202.223115] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:22 Octavian-Notebook kernel: [  202.223134] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:27 Octavian-Notebook kernel: [  207.424244] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:27 Octavian-Notebook kernel: [  207.424259] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:32 Octavian-Notebook kernel: [  212.625368] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:32 Octavian-Notebook kernel: [  212.625387] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:37 Octavian-Notebook kernel: [  217.826526] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:37 Octavian-Notebook kernel: [  217.826545]

[Desktop-packages] [Bug 879950] Re: pidgin not showing up

2013-08-14 Thread Ketil Malde

Removing .purple/prefs.xml fixed it for me.

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

Title:
  pidgin not showing up

Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “pidgin” package in Unity Linux:
  New

Bug description:
  Pidgin is just not visible. It shows on the message menu, it whos on
  Unity and it even shows on the global Menu, it's just... not on
  screen. This problem is happening often but i don't know as a result
  of what, since it works upon launching, but may not upon relaunching.
  After Pidgin put together the information for thisre port, the window
  shoed up again but disappeared from Unity, although currently working.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pidgin 1:2.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Oct 22 17:03:25 2011
  ExecutablePath: /usr/bin/pidgin
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (6 days ago)

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

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

[Desktop-packages] [Bug 1098233] Re: flashplugin-installer do not honore proxy settings

2013-08-14 Thread Jan Groenewald

I think the problem is un update-notifier

This bit of code checks the environment 
0 jan@muizenberg:/var/autofs/misc/home/jan$grep -C3 nv 
/usr/lib/update-notifier/package-data-downloader
Failed downloads are reported to the user via the
update-notifier interface.

# Get our proxy settings from the environment
proxies = {}
try:
for proto in ('http','https','ftp'):
try:
proxies[proto] = os.environ[proto+_proxy]
except KeyError:
pass


0 jan@muizenberg:/var/autofs/misc/home/jan$dpkg -S 
/usr/lib/update-notifier/package-data-downloader
update-notifier-common: /usr/lib/update-notifier/package-data-downloader

Both these /etc/environment and /etc/apt/apt.conf are ignored:

0 jan@muizenberg:/var/autofs/misc/home/jan$cat /etc/environment 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
http_proxy=http://proxy.aims.ac.za:3128/;
https_proxy=https://proxy.aims.ac.za:3128/;
ftp_proxy=ftp://proxy.aims.ac.za:3128/;
0 jan@muizenberg:/var/autofs/misc/home/jan$cat /etc/apt/apt.conf
Acquire::http::proxy http://proxy.aims.ac.za:3128/;;
Acquire::https::proxy https://proxy.aims.ac.za:3128/;;
Acquire::ftp::proxy ftp://proxy.aims.ac.za:3128/;;
0 jan@muizenberg:/var/autofs/misc/home/jan$

However when I run

env | grep prox

from either root's crontab -e or from /etc/crontab as root, I do see the
appropriate proxies set. I thought this was where os.environ would get
the value, but it does not. You can stick a print statement in  /usr/lib
/update-notifier/package-data-downloader to see that omission.

Some history
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1005837
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/983559
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/982684
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/979477

Some of those workarounds seem way too long. For us it works to go from
the command line (not from cron) , where your http_proxy is set:

apt-get --reinstall install flashplugin-installer

In real life, many of my users flash stops working each time there is an
update to flashplugin-installer, because they are not familiar with the
command line. In addition, their entire apt system stays broken with
this error popping up every subsequent time they install/update anything
else graphically.

So, while it is marked as WONTFIX here:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/983559
seems to be due to this:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/983559/comments/4

That still leaves many users in a bad position. Despite the comment 4
linked above explaining why apt.conf should not be read. However, it
goes on to say:

So you can specify a system proxy by setting the http_proxy variable in
/etc/environment. Depending on how you're gaining root privileges for
apt, you may still run into problems due to bug #982684, which will
hopefully be fixed soon.

That other bug #982684 is fixed released April 2013, but I don't really
see how it affects the cronjob /etc/cron.daily/update-notifier, though
I'm not sure the cronjob uses sudo or pkexec.

In any case, on Ubuntu 12.04.2, the proxy still isn't read from
/etc/environment. If that is really fixed then the problem will go away
for many users who do set /etc/environment (knowingly by editing the
file, or unknowningly from the Dash  Network  Proxy  Manual  Apply
Systemwide, which seems to write to /etc/environment).

And while that will fix it for my computer lab institutional desktops,
imaged by me, all the visiting laptops set the proxy via PAC file, not
via manual  apply system wide, so that they still don't have the
problem fixed.

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

Title:
  flashplugin-installer do not honore proxy settings

Status in Adobe Flash Plugin Tools:
  New
Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 12.10
  Release:  12.10
  Codename: quantal

  flashplugin-installer:
    Installato: 11.2.202.258ubuntu0.12.10.1
    Candidato:  11.2.202.261ubuntu0.12.10.1
    Tabella versione:
   11.2.202.261ubuntu0.12.10.1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal-updates/multiverse i386 
Packages
  500 http://archive.ubuntu.com/ubuntu/ quantal-security/multiverse 
i386 Packages
   *** 11.2.202.258ubuntu0.12.10.1 0
  100 /var/lib/dpkg/status
   11.2.202.243ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/multiverse i386 Packages

  flashplugin-installer do not honore proxy settings so cannot download
  the proxy so my update are frozen on

  Elaborazione dei trigger per update-notifier-common...

[Desktop-packages] [Bug 1212216] Re: python-loader:type 'exceptions.ImportError':No module named pythonloader

2013-08-14 Thread cpina

Thanks Christopher. I was there ( https://bugs.launchpad.net/~libreoffice ) but 
I couldn't see how to report bugs from their Bugs section (I see how to 
search, not create new ones/report). Will follow up in another way with the ppa 
team (I see that apt-cache show libreoffice shows another way to report bugs, 
in a mailing list).
Regards,

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

Title:
  python-loader:type 'exceptions.ImportError':No module named
  pythonloader

Status in “libreoffice” package in Ubuntu:
  Invalid

Bug description:
  Summary:
  System version: Ubuntu 12.04.2 LTS, Release 12.04
  Package: libreoffice . Version:  1:4.1.0-0ubuntu1-precise1~ppa1
  Expected to happen: Mendeley Desktop plugin working like in previous 
Libreoffice or Libreoffice from mainstream.
  What happened: it fails with a python-loader error. Possible workaround: 
export PYTHONPATH=/usr/lib/libreoffice/program/

  Longer description and workaround:
  When trying to use Mendeley Desktop Libreoffice extension (and, I see on the 
Internet, other extensions) it doesn't work. Appears:
  
  BASIC runtime error.
  An exception ocurred
  Type: com.sun.star.uno.RuntimeException
  Message: python-loader:type 'exceptions.ImportError': No module named 
pythonloader, traceback follows
  no traceback available
  .
  

  This can be reproduced using libreoffice version
  1:4.1.0-0ubuntu1-precise1~ppa1

  It's working correctly using Libreoffice from www.libreoffice.org.

  A possible workaround is to launch Libreoffice this way:
  export PYTHONPATH=/usr/lib/libreoffice/program/ ; libreoffice
  (note that pythonloader.py is in that directory)

  See a confirmation here:
  https://github.com/Mendeley/openoffice-plugin/issues/11

  So it fails libreoffice 4.1 PPA but not the upstream one, and there is
  a workaround (too complicated for some users).

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

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

[Desktop-packages] [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

2013-08-14 Thread John Lea

** Description changed:

  Binary package hint: nautilus
  
  What happens - I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.
  
  --
  
  Desired resolution:
  
  - Remove the Sharing Options right click menu option from Nautilus.
+ - Remove the 'Share' tab from the Nautilus 'Properties' window
  - If a advanced user chooses to install the required packages, the menu 
should re-appear in Nautilus.

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

Status in Ayatana Design:
  Fix Committed
Status in gnome-user-share:
  New
Status in “gnome-user-share” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  What happens - I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.

  --

  Desired resolution:

  - Remove the Sharing Options right click menu option from Nautilus.
  - Remove the 'Share' tab from the Nautilus 'Properties' window
  - If a advanced user chooses to install the required packages, the menu 
should re-appear in Nautilus.

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

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

[Desktop-packages] [Bug 1210575] Re: Right-click emulation of Onboard does not work

2013-08-14 Thread marmuta

Done, I think, you can try it. All click buttons should work and the new
click simulator is the default now. You can run Onboard without the
environment variable.

bzr pull
./setup.py build
killall onboard; ./onboard

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

Title:
  Right-click emulation of Onboard does not work

Status in Onboard on-screen keyboard:
  New
Status in “onboard” package in Ubuntu:
  New

Bug description:
  If I turn on the mouse button mode of onboard I get some additional
  keys where one is a mouse pointer pointing to the upper right. This
  issupposed to emulate the right mouse button on the touch screen. I
  have clicked this key via the touch screen and then clicked on the
  desktop background. Only after a second click reveals the appropriate
  right-click menu. For a terminal window I do not get the right-click
  menu at all.

  I am using current Saucy with the standard Unity desktop and onboard
  from the Onboard PPA: ppa:onboard/ppa.

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

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

[Desktop-packages] [Bug 1198942] Re: Hybrid Graphics and general enablement for fglrx and nvidia in Precise for 12.04.3

2013-08-14 Thread Alberto Milone

I tested fglrx-installer-experimental-13 (2:13.101-0ubuntu0.0.2) and
fglrx-pxpress with and without jockey on my Dell Inspiron N4110 and they
worked without problems. Thanks to PowerXpress I can use the discrete
card.

I also tested nvidia-319 and nvidia-319-updates (one at a time) together
with nvidia-prime (with and without jockey) on my Lenovo L480S. It all
works correctly with Hybrid graphics.

I haven't experienced any regressions with systems with a single GPU
(e.g. my Inspiron 1122). All drivers show up and install correctly.
Neither nvidia-prime nor fglrx-pxpress is installed in this case (as
expected).

Also, using stacks older than Raring's (lts-raring), no drivers show up
on systems with hybrid graphics, as expected.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Hybrid Graphics and general enablement for fglrx and nvidia in Precise
  for 12.04.3

Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “fglrx-pxpress” package in Ubuntu:
  Fix Released
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-173-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Committed
Status in “fglrx-pxpress” source package in Precise:
  Fix Committed
Status in “jockey” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-173-updates” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-304” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-304-updates” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-319” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-319-updates” source package in Precise:
  Fix Committed
Status in “nvidia-prime” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  As per the topic, the purpose of this report is to make sure that
  users get graphics drivers that work with Raring's X/Kernel in Precise
  12.04.3.

  This work also enables support for Hybrid graphics (as planned) and
  requires changes in Jockey in addition to the drivers.

  This SRU involves the following packages

  jockey
  nvidia-prime
  fglrx-pxpress
  nvidia-graphics-drivers-319
  nvidia-graphics-drivers-319-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173-updates
  nvidia-settings-319
  nvidia-settings-319-updates
  nvidia-settings-304
  nvidia-settings-304-updates
  nvidia-persistenced
  fglrx-installer-updates
  fglrx-installer-experimental-13

  
  Only jockey, nvidia-graphics-drivers-173-updates and fglrx-installer-updates 
already existed in the archive, the rest is in NEW.

  The changes in jockey are all documented in jockey's changelog. I
  added tests in the test suite to make sure that we simulate hybrid
  graphics systems (using fake devices) and test the relevant code
  paths.

  In short, we don't provide graphics drivers on unsupported systems
  with hybrid graphics, thus preventing users from breaking their
  systems. When hybrid graphics is available and supported (i.e. there
  is a driver which supports it and the Raring stack is installed) not
  only do we provide the drivers, we also take care of installing either
  fglrx-pxpress or nvidia-prime, which will take care of any required
  configuration so that, on next boot, things will work with no user
  interaction. Quite an improvement compared with a certain xserver
  failure in case of a misconfigured or unsupported system.

  As for the drivers, they all work with kernels up to 3.10 and include the 
following features:
   * NVIDIA's 319 series add support for hybrid graphics, in addition to being 
a LTS series. They also replace any experimental driver we uploaded.
   * current users of nvidia-current and nvidia-current-updates will be 
migrated to nvidia-304 and nvidia-304-updates (same driver release, only 
different name).
   * All (obsolete) experimental nvidia drivers will be migrated to 
nvidia-319-updates.
   * fglrx-updates will be updated to the latest stable release.
   * fglrx-experimental-13 will replace all experimental releases and add 
stable support for hybrid graphics.
   * nvidia-persistenced is a daemon (only for the 319 series) which, by 
default, preserves the standard behaviour of the nvidia driver. It makes it 
easier for users to

[Desktop-packages] [Bug 1059083] Re: Log in automatically choice does not work.

2013-08-14 Thread Rajiv Shah

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

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Log in automatically choice does not work.

Status in Light Display Manager:
  New
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  Selected option to log in automatically during install. After reboot,
  login screen shows up with no password field. Have to click user name
  to get password prompt. After entering password, you are returned to
  the login screen. If you select XFCE session, login works. After
  logging out, you can then select Xubuntu session and login works.
  Subsequent logins work okay after rebooting.

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

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

[Desktop-packages] [Bug 1210575] Re: Right-click emulation of Onboard does not work

2013-08-14 Thread Till Kamppeter

It is all working correctly now, including double click and drag
emulation. Thank you very much.

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

Title:
  Right-click emulation of Onboard does not work

Status in Onboard on-screen keyboard:
  New
Status in “onboard” package in Ubuntu:
  New

Bug description:
  If I turn on the mouse button mode of onboard I get some additional
  keys where one is a mouse pointer pointing to the upper right. This
  issupposed to emulate the right mouse button on the touch screen. I
  have clicked this key via the touch screen and then clicked on the
  desktop background. Only after a second click reveals the appropriate
  right-click menu. For a terminal window I do not get the right-click
  menu at all.

  I am using current Saucy with the standard Unity desktop and onboard
  from the Onboard PPA: ppa:onboard/ppa.

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

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

[Desktop-packages] [Bug 1038280] Re: (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack != NULL' failed

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

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

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

Title:
  (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

Status in “liferea” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I search the feed crashes liferea.

  Unfortunately, no apport window opens.

  When you start in the terminal the following messages:

  michael@Michael-Thinkpad-X121e:~$ liferea

  (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

  Liferea did receive signal 11 (Speicherzugriffsfehler).
  You have probably triggered a program bug. I will now try to 
  create a backtrace which you can attach to any support requests.

  michael@Michael-Thinkpad-X121e:~$ liferea

  (liferea:5123): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

  Liferea did receive signal 11 (Speicherzugriffsfehler).
  You have probably triggered a program bug. I will now try to 
  create a backtrace which you can attach to any support requests.

  michael@Michael-Thinkpad-X121e:~$

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

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

[Desktop-packages] [Bug 1038280] Re: (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack != NULL' failed

2013-08-14 Thread MinasFilm

xubuntu 12.04
1.9.99-4597ppa6~precise1

the error persists

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

Title:
  (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

Status in “liferea” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I search the feed crashes liferea.

  Unfortunately, no apport window opens.

  When you start in the terminal the following messages:

  michael@Michael-Thinkpad-X121e:~$ liferea

  (liferea:4912): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

  Liferea did receive signal 11 (Speicherzugriffsfehler).
  You have probably triggered a program bug. I will now try to 
  create a backtrace which you can attach to any support requests.

  michael@Michael-Thinkpad-X121e:~$ liferea

  (liferea:5123): GLib-CRITICAL **: g_strstr_len: assertion `haystack !=
  NULL' failed

  Liferea did receive signal 11 (Speicherzugriffsfehler).
  You have probably triggered a program bug. I will now try to 
  create a backtrace which you can attach to any support requests.

  michael@Michael-Thinkpad-X121e:~$

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

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

[Desktop-packages] [Bug 1098233] Re: flashplugin-installer do not honore proxy settings

2013-08-14 Thread Jan Groenewald

Actually, this piece of code seems to work fine
# Get our proxy settings from the environment
proxies = {}
try:
for proto in ('http','https','ftp'):
try:
proxies[proto] = os.environ[proto+_proxy]
except KeyError:
pass
print proxies # my code

if proxies:
urllib._urlopener = urllib.FancyURLopener(proxies)
except Exception:

and then the urllib.urlretrieve should work, and it does when run
manually, but somehow not from the cron job. I can't see why.

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

Title:
  flashplugin-installer do not honore proxy settings

Status in Adobe Flash Plugin Tools:
  New
Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 12.10
  Release:  12.10
  Codename: quantal

  flashplugin-installer:
    Installato: 11.2.202.258ubuntu0.12.10.1
    Candidato:  11.2.202.261ubuntu0.12.10.1
    Tabella versione:
   11.2.202.261ubuntu0.12.10.1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal-updates/multiverse i386 
Packages
  500 http://archive.ubuntu.com/ubuntu/ quantal-security/multiverse 
i386 Packages
   *** 11.2.202.258ubuntu0.12.10.1 0
  100 /var/lib/dpkg/status
   11.2.202.243ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/multiverse i386 Packages

  flashplugin-installer do not honore proxy settings so cannot download
  the proxy so my update are frozen on

  Elaborazione dei trigger per update-notifier-common...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz

  already reported:
  https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1037662

  Very old issue still not solved... :-(

  # Workaround for user with same issue 

  As a workaround... while the apt-get update process is frozen on the
  row below

  Elaborazione dei trigger per update-notifier-common...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz

  Opening another terminal...
  wget 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz
  sudo /usr/lib/flashplugin-installer/install_plugin 
$(pwd)/adobe-flashplugin_11.2.202.261.orig.tar.gz
  rm adobe-flashplugin_11.2.202.261.orig.tar.gz

  then to release the frozen update process, type:

  sudo killall dpkg

  or reboot the pc, then type:

  sudo dpkg --configure -a

  to check and put in a good state the apt env...

  # --

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: flashplugin-installer 11.2.202.258ubuntu0.12.10.1
  Uname: Linux 3.7.1-030701-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Thu Jan 10 15:39:05 2013
  MarkForUpload: True
  SourcePackage: flashplugin-nonfree
  UpgradeStatus: Upgraded to quantal on 2012-07-02 (192 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1098233/+subscriptions

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

[Desktop-packages] [Bug 1005901] Re: cannot change temp dir

2013-08-14 Thread Louis Bouchard

Any chance of having this debdiff sponsored for upload ?

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

Title:
  cannot change temp dir

Status in Duplicity - Bandwidth Efficient Encrypted Backup:
  Fix Released
Status in “duplicity” package in Ubuntu:
  Fix Released
Status in “duplicity” source package in Precise:
  In Progress

Bug description:
  SRU justification :

  Duplicity does not honor the TMPDIR, TEMP, TMP or --tempdir
  redirection as expected.

  Impact :

  If the available size in /tmp is too small, restore may fail to
  complete

  Fix :

  Backport upstream fix applied in 0.6.21 (Merge proposal from the
  upstream task of this bug)

  Test Case : 
  Note: Incremental backup is necessary so both the full  difftar are required 
in /tmp which will require more than 50Mb

  1) Mount a 50Mb file system under /tmp
  ~# df -h /tmp
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sda148M  794K   45M   2% /tmp

  2) Create a 60Mb file to be backed up under /srv called data
  dd if=/proc/kcore of=/srv/data bs=1M count=60

  3) Do a full backup of /srv into /backup

  duplicity full --name test --encrypt-key A6C785C2 --sign-key A6C785C2
  --volsize 25 /srv file:///backup/duply

  4) Modify the 60Mb file so it can be picked up by the incremental backup
  dd if=/proc/kcore of=/srv/data bs=1M count=10 conv=notrunc oflag=append

  5) Do an incremental backup
  duplicity incr --name 'duply_test' --encrypt-key A6C785C2 --sign-key A6C785C2 
--volsize 25 /srv file:///backup/duply

  6) Restore the flag using TMPDIR :
  TEMPDIR=/mytemp duplicity --name 'duply_test' --encrypt-key A6C785C2 
--sign-key A6C785C2 --verbosity '4' --volsize 25 -t now file:///backup/duply 
/restore

  With the patch, the command will succeed.

  Regression :

  None expected, this code is used in the version currently available in
  Raring

  Description of the problem :

  When /tmp is too small, duplicity is sometimes unable to do a restore.
  Using TMPDIR variable or --tempdir doe not work.

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

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

[Desktop-packages] [Bug 1212261] [NEW] fglrx-installer should not depend on linux-headers

2013-08-14 Thread Tim Gardner

Public bug reported:

Drop dependency on linux-headers. The solution provided in
http://bugs.launchpad.net/bugs/284091 was incorrect with respect to LTS
kernel headers. In order for dkms packages to build without error the
correct kernel meta package must be used, i.e., one that installs the
kernel image as well as the headers. For example, linux-generic, linux-
generic-lts-quantal, linux-generic-lts-raring, etc.

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Released

** Affects: fglrx-installer (Ubuntu Precise)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: fglrx-installer (Ubuntu Saucy)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Released

** Also affects: fglrx-installer (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: fglrx-installer (Ubuntu Precise)
   Status: New = In Progress

** Changed in: fglrx-installer (Ubuntu Precise)
 Assignee: (unassigned) = Tim Gardner (timg-tpi)

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

Title:
  fglrx-installer should not depend on linux-headers

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer” source package in Precise:
  In Progress
Status in “fglrx-installer” source package in Saucy:
  Fix Released

Bug description:
  Drop dependency on linux-headers. The solution provided in
  http://bugs.launchpad.net/bugs/284091 was incorrect with respect to
  LTS kernel headers. In order for dkms packages to build without error
  the correct kernel meta package must be used, i.e., one that installs
  the kernel image as well as the headers. For example, linux-generic,
  linux-generic-lts-quantal, linux-generic-lts-raring, etc.

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

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

[Desktop-packages] [Bug 1212261] Re: fglrx-installer should not depend on linux-headers

2013-08-14 Thread Tim Gardner

Raring/Saucy appear to already have been fixed in 2:9.010-0ubuntu2

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

Title:
  fglrx-installer should not depend on linux-headers

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer” source package in Precise:
  In Progress
Status in “fglrx-installer” source package in Saucy:
  Fix Released

Bug description:
  Drop dependency on linux-headers. The solution provided in
  http://bugs.launchpad.net/bugs/284091 was incorrect with respect to
  LTS kernel headers. In order for dkms packages to build without error
  the correct kernel meta package must be used, i.e., one that installs
  the kernel image as well as the headers. For example, linux-generic,
  linux-generic-lts-quantal, linux-generic-lts-raring, etc.

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

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

[Desktop-packages] [Bug 1212261] Re: fglrx-installer should not depend on linux-headers

2013-08-14 Thread Tim Gardner

Having a linux-headers package dependency in Quantal/Raring/Saucy is
benign since there will never be an official LTS kernel installed in
those releases. I do suggest fixing the Saucy version however so that
this problem isn't propagated to 14.04.

** Also affects: fglrx-installer (Ubuntu Saucy)
   Importance: Undecided
   Status: New

** Changed in: fglrx-installer (Ubuntu Saucy)
   Status: New = In Progress

** Changed in: fglrx-installer (Ubuntu Saucy)
 Assignee: (unassigned) = Tim Gardner (timg-tpi)

** Changed in: fglrx-installer (Ubuntu Saucy)
   Status: In Progress = Fix Released

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

Title:
  fglrx-installer should not depend on linux-headers

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer” source package in Precise:
  In Progress
Status in “fglrx-installer” source package in Saucy:
  Fix Released

Bug description:
  Drop dependency on linux-headers. The solution provided in
  http://bugs.launchpad.net/bugs/284091 was incorrect with respect to
  LTS kernel headers. In order for dkms packages to build without error
  the correct kernel meta package must be used, i.e., one that installs
  the kernel image as well as the headers. For example, linux-generic,
  linux-generic-lts-quantal, linux-generic-lts-raring, etc.

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

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

[Desktop-packages] [Bug 1212123] Re: Erratic cursor movement when using Coordinate Transformation Matrix

2013-08-14 Thread Timo Aaltonen

is fixed in 13.04-

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

** Also affects: xorg-server-lts-quantal (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Also affects: xorg-server-lts-quantal (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** No longer affects: xorg-server (Ubuntu Precise)

** No longer affects: xorg-server-lts-quantal (Ubuntu Quantal)

** Changed in: xorg-server (Ubuntu Quantal)
 Assignee: (unassigned) = Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu)
   Status: New = Fix Released

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

Title:
  Erratic cursor movement when using Coordinate Transformation Matrix

Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server-lts-quantal” package in Ubuntu:
  New
Status in “xorg-server-lts-quantal” source package in Precise:
  New
Status in “xorg-server” source package in Quantal:
  New

Bug description:
  = Affected Packages =

  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2 in precise
  xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise3 in precise

  = Reproduce Steps =

  1. Boot into Ubuntu 12.04.2 live system

  2. Expand the laptop display to the external one.
  For example, `xrandr --output eDP1 --auto --output HDMI1 --auto --right-of 
eDP1`

  3. Restrict the movements of the touchscreen to the laptop display.
  For example, `xinput map-to-crtc 'ELAN Touchscreen' eDP1`

  P.S. `xinput map-to-crtc` will calculate and set Coordinate
  Transformation Matrix correspondingly.

  = Expected Result =

  I can operate the touchscreen on the laptop display as usual.

  = Actual Result =

  It becomes abnormal and shows erratic cursor movement.

  P.S. Ubuntu 13.04 is OK.

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

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

[Desktop-packages] [Bug 1212270] [NEW] freeze

2013-08-14 Thread Fabio Marconi

Public bug reported:

zzz

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: evolution 3.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Wed Aug 14 16:08:54 2013
EcryptfsInUse: Yes
MarkForUpload: True
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug saucy

** Changed in: evolution (Ubuntu)
   Status: New = Invalid

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

Title:
  freeze

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  zzz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 16:08:54 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1212269] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()

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

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 #1193522, 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/1212269/+attachment/3772479/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772481/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772482/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772483/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772484/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772485/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212269/+attachment/3772486/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1193522
   nautilus crashed with SIGSEGV in gtk_action_get_name()

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When entering the Dropbox folder that is synched by the Dropbox
  service, nautilus freezes and crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Aug 14 16:03:58 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'658x715+49+24'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'177'
  InstallationDate: Installed on 2012-12-24 (232 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa877a39dd6 gtk_action_get_name+22:   cmp
%rax,(%rdx)
   PC (0x7fa877a39dd6) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

you are using driver later than this patch since line-in and Mic-in not exist

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=55cf87fe0e9783e25f442be1e48b8319d86131ea


simple mixer control 'Line',0
  Capabilities: cvolume cswitch penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 99
  Front Left: Capture 0 [0%] [-90.00dB] [off]
  Front Right: Capture 0 [0%] [-90.00dB] [off]
Simple mixer control 'Mic',0
  Capabilities: cvolume cswitch penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 99
  Front Left: Capture 30 [30%] [-60.00dB] [on]
  Front Right: Capture 30 [30%] [-60.00dB] [on]

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

Title:
  Creative Recon3d  Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in The Linux Kernel:
  New
Status in “alsa-driver” package in Ubuntu:
  Triaged

Bug description:
  [WORKAROUND] Run the following command:

  echo options snd-hda-intel position_fix=1 | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1186800] Re: [830 v3.7 regression] Video goes blank and system hangs (using an old kernel fix it)

2013-08-14 Thread Federico Leoni

Understood Chris, sometimes I need to read with more attention, English is not 
my primary language. 
Seems my display simply can't handle 24bit color depth, if I force a 16bit 
color depth on xorg I can see great degrade of the render, clearly evident on 
desktop wallpaper (see pic).
About the 24bit framebuffer, with or without UXA xdpyinfo and fbset shows the 
same values. 

effe@C400:~$ xdpyinfo | grep of root
  depth of root window:24 planes
effe@C400:~$ sudo fbset -i

mode 1024x768
geometry 1024 768 1024 768 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
Name: inteldrmfb
Address : 0xe002
Size: 3145728
Type: PACKED PIXELS
Visual  : TRUECOLOR
XPanStep: 1
YPanStep: 1
YWrapStep   : 0
LineLength  : 4096
Accelerator : No

Probably I miss something here, anyway the important thing is I found a 
workaround. 
The only thing  I regret is I can't use liveCD to test future versions on this 
notebook as I can't set UXA via GRUB.

** Attachment added: 3.8.0-27_16bit_noUXA.png
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1186800/+attachment/3772494/+files/3.8.0-27_16bit_noUXA.png

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

Title:
  [830 v3.7 regression] Video goes blank and system hangs (using an old
  kernel fix it)

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

Bug description:
  I'm on a very old Dell C400 P3 866 with 768mb ram which still works
  rock solid. I've upgraded this system from Lubuntu 12.10 to 13.04 but
  with every kernel above V3.6.11 (took from mainline ubuntu) system
  hangs randomly.

  I tried to install Intel video drivers from
  https://01.org/linuxgraphics/ (Intel(R) Linux* Graphics Installer
  version 1.0.1 for Ubuntu* 13.04 (32-bit)) but this did not solve the
  problem. I'm not sure if is driver or kernel related since on the last
  release change the drivers curiously works using kernel V3.9 but
  before revert to this release I would like to help to find a solution.

  uname -r
  3.8.0-23-generic

  lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.21.6-0ubuntu4
Candidate: 2:2.21.6-0ubuntu4
Version table:
   *** 2:2.21.6-0ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  lspci -k
  00:02.0 VGA compatible controller: Intel Corporation 82830M/MG Integrated 
Graphics Controller (rev 04)
Subsystem: Dell Device 00c8
Kernel driver in use: i915
Kernel modules: intelfb, i915
  00:02.1 Display controller: Intel Corporation 82830M/MG Integrated Graphics 
Controller
Subsystem: Dell Device 00c8
Kernel modules: i915

  hwinfo --gfxcard
   hal.1: read hal dataprocess 2789: arguments to dbus_move_error() were 
incorrect, assertion (dest) == NULL || !dbus_error_is_set ((dest)) failed in 
file ../../dbus/dbus-errors.c line 282.
  This is normally a bug in some application using the D-Bus library.
  libhal.c 3483 : Error unsubscribing to signals, error=The name 
org.freedesktop.Hal was not provided by any .service files
  09: PCI 02.0: 0300 VGA compatible controller (VGA)  
[Created at pci.318]
Unique ID: _Znp.bU4liPq1bBD
SysFS ID: /devices/pci:00/:00:02.0
SysFS BusID: :00:02.0
Hardware Class: graphics card
Model: Intel i830
Vendor: pci 0x8086 Intel Corporation
Device: pci 0x3577 i830
SubVendor: pci 0x1028 Dell
SubDevice: pci 0x00c8 
Revision: 0x04
Driver: i915
Driver Modules: drm
Memory Range: 0xe000-0xe7ff (ro,non-prefetchable)
Memory Range: 0xf4f8-0xf4ff (rw,non-prefetchable)
IRQ: 11 (737 events)
Module Alias: pci:v8086d3577sv1028sd00C8bc03sc00i00
Driver Info #0:
  XFree86 v4 Server Module: intel
Driver Info #1:
  XFree86 v4 Server Module: intel
  3D Support: yes
  Extensions: dri
Config Status: cfg=new, avail=yes, need=no, active=unknown

  10: PCI 02.1: 0380 Display controller
[Created at pci.318]
Unique ID: ruGf.XE0Ix0G1vD2
SysFS ID: /devices/pci:00/:00:02.1
SysFS BusID: :00:02.1
Hardware Class: graphics card
Model: Intel i830
Vendor: pci 0x8086 Intel Corporation
Device: pci 0x3577 i830
SubVendor: pci 0x1028 Dell
SubDevice: pci 0x00c8 
Memory Range: 0xd800-0xdfff (ro,non-prefetchable)
Memory Range: 0xf4f0-0xf4f7 (rw,non-prefetchable)
Module Alias: pci:v8086d3577sv1028sd00C8bc03sc80i00
Driver Info #0:
  XFree86 v4 Server Module: intel
Driver Info #1:
  XFree86 v4

[Desktop-packages] [Bug 1212277] [NEW] [HuronRiver Platform, Intel CougarPoint HDMI, Digital Out, HDMI] No sound at all

2013-08-14 Thread Nisheet Lall

Public bug reported:

Sound runs normally on Laptop Speakers and external speakers as well.
When I connect the Digital TV to the HDMI port, I only get display but
no sound. HDMI sound works perfectly in Windows 7. There is no option in
sound settings for HDMI Sound either.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nisheet1732 F pulseaudio
 /dev/snd/controlC0:  nisheet1732 F pulseaudio
Date: Wed Aug 14 19:46:53 2013
InstallationDate: Installed on 2013-06-02 (73 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130601)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nisheet1732 F pulseaudio
 /dev/snd/controlC0:  nisheet1732 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [HuronRiver Platform, Intel CougarPoint HDMI, Digital Out, HDMI] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 45CN38WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: Ideapad Z570
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug saucy

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

Title:
  [HuronRiver Platform, Intel CougarPoint HDMI, Digital Out, HDMI] No
  sound at all

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

Bug description:
  Sound runs normally on Laptop Speakers and external speakers as well.
  When I connect the Digital TV to the HDMI port, I only get display but
  no sound. HDMI sound works perfectly in Windows 7. There is no option
  in sound settings for HDMI Sound either.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nisheet1732 F pulseaudio
   /dev/snd/controlC0:  nisheet1732 F pulseaudio
  Date: Wed Aug 14 19:46:53 2013
  InstallationDate: Installed on 2013-06-02 (73 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130601)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nisheet1732 F pulseaudio
   /dev/snd/controlC0:  nisheet1732 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HuronRiver Platform, Intel CougarPoint HDMI, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1210575] Re: Right-click emulation of Onboard does not work

2013-08-14 Thread marmuta

Great, thank you for your patience.

** Changed in: onboard
   Status: New = Fix Committed

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

Title:
  Right-click emulation of Onboard does not work

Status in Onboard on-screen keyboard:
  Fix Committed
Status in “onboard” package in Ubuntu:
  New

Bug description:
  If I turn on the mouse button mode of onboard I get some additional
  keys where one is a mouse pointer pointing to the upper right. This
  issupposed to emulate the right mouse button on the touch screen. I
  have clicked this key via the touch screen and then clicked on the
  desktop background. Only after a second click reveals the appropriate
  right-click menu. For a terminal window I do not get the right-click
  menu at all.

  I am using current Saucy with the standard Unity desktop and onboard
  from the Onboard PPA: ppa:onboard/ppa.

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

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

[Desktop-packages] [Bug 1198942] Re: Hybrid Graphics and general enablement for fglrx and nvidia in Precise for 12.04.3

2013-08-14 Thread Alberto Milone

I forgot to mention that I also tested the other nvidia drivers and I
didn't spot any issues

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

Title:
  Hybrid Graphics and general enablement for fglrx and nvidia in Precise
  for 12.04.3

Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “fglrx-pxpress” package in Ubuntu:
  Fix Released
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-173-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Committed
Status in “fglrx-pxpress” source package in Precise:
  Fix Committed
Status in “jockey” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-173-updates” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-304” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-304-updates” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-319” source package in Precise:
  Fix Committed
Status in “nvidia-graphics-drivers-319-updates” source package in Precise:
  Fix Committed
Status in “nvidia-prime” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  As per the topic, the purpose of this report is to make sure that
  users get graphics drivers that work with Raring's X/Kernel in Precise
  12.04.3.

  This work also enables support for Hybrid graphics (as planned) and
  requires changes in Jockey in addition to the drivers.

  This SRU involves the following packages

  jockey
  nvidia-prime
  fglrx-pxpress
  nvidia-graphics-drivers-319
  nvidia-graphics-drivers-319-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173-updates
  nvidia-settings-319
  nvidia-settings-319-updates
  nvidia-settings-304
  nvidia-settings-304-updates
  nvidia-persistenced
  fglrx-installer-updates
  fglrx-installer-experimental-13

  
  Only jockey, nvidia-graphics-drivers-173-updates and fglrx-installer-updates 
already existed in the archive, the rest is in NEW.

  The changes in jockey are all documented in jockey's changelog. I
  added tests in the test suite to make sure that we simulate hybrid
  graphics systems (using fake devices) and test the relevant code
  paths.

  In short, we don't provide graphics drivers on unsupported systems
  with hybrid graphics, thus preventing users from breaking their
  systems. When hybrid graphics is available and supported (i.e. there
  is a driver which supports it and the Raring stack is installed) not
  only do we provide the drivers, we also take care of installing either
  fglrx-pxpress or nvidia-prime, which will take care of any required
  configuration so that, on next boot, things will work with no user
  interaction. Quite an improvement compared with a certain xserver
  failure in case of a misconfigured or unsupported system.

  As for the drivers, they all work with kernels up to 3.10 and include the 
following features:
   * NVIDIA's 319 series add support for hybrid graphics, in addition to being 
a LTS series. They also replace any experimental driver we uploaded.
   * current users of nvidia-current and nvidia-current-updates will be 
migrated to nvidia-304 and nvidia-304-updates (same driver release, only 
different name).
   * All (obsolete) experimental nvidia drivers will be migrated to 
nvidia-319-updates.
   * fglrx-updates will be updated to the latest stable release.
   * fglrx-experimental-13 will replace all experimental releases and add 
stable support for hybrid graphics.
   * nvidia-persistenced is a daemon (only for the 319 series) which, by 
default, preserves the standard behaviour of the nvidia driver. It makes it 
easier for users to enable persistence mode to work around bugs in the driver 
(e.g. LP: #1202152)

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

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

[Desktop-packages] [Bug 1083811] Re: Duplicated panels using separate x screens

2013-08-14 Thread Dmitry Shachnev

Uploaded to precise-proposed. Please add the SRU information fields
before it can be accepted:
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.

** Also affects: gnome-panel (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  Duplicated panels using separate x screens

Status in Desktop panel for GNOME:
  Fix Released
Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Precise:
  New

Bug description:
  I'm trying to use separate x screens on nvidia card with 3 monitors.
  I'm expecting one top panel + one bottom panel on each screen, but
  instead i have got all panels on one screen.

  Restarting gnome panel (gnome-panel --replace) it will create two
  extra (blank) panel pairs on same screen, but new applets will be
  added on first panel pair. Screenshot ilustrating problem can be found
  here - http://askubuntu.com/questions/177226/duplicated-menu-panel-
  indicators-and-taskbar

  I tried to manualy set screen key (org-gnome-gnome-
  panel-layout-toplevels-top-panel-screen) on wich screen panel
  should appear with dconf Editor. But restarting gnome-panel that key
  will be reseted.

  Downloaded gnome-panel source code (apt-get source gnome-panel), spend
  some time trying to find problem, and probably i found it in file
  panel-toplevel.c.

  Line 4458: if (!screen || GDK_IS_SCREEN (screen))
  Line 4459: screen = gdk_screen_get_default ();

  These lines are responsible for resetting screen key. It will reset
  screen to default if currenct screen exist, but its not what we want.
  We want reset screen to default if screen dosnt exist, so line 4458
  should be -  if (!screen || !GDK_IS_SCREEN (screen))

  After compiling and installing new package, gnome panel works as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/1083811/+subscriptions

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

[Desktop-packages] [Bug 1070377] Re: Empathy change to Online Accounts no longer supports SIPE

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

** Changed in: account-plugins (Ubuntu)
   Status: New = Confirmed

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

Title:
  Empathy change to Online Accounts no longer supports SIPE

Status in Online Accounts: Account plugins:
  In Progress
Status in Chat app, and Telepathy user interface:
  Unknown
Status in Telepathy Haze:
  New
Status in “account-plugins” package in Ubuntu:
  Confirmed

Bug description:
  Many of us use SIPE as way a way to use Microsoft Communicator/Lync in
  order to IM with workplaces.   Empathy used to allow for SIPE
  connections through the pidgin-sipe package but since I switched to
  12.10 and online accounts functionality, I can no longer find a way
  to do so.

  While I can still use SIPE in pidgin, pidgin no longer integrates into
  the Unity notification system.

  In either case, it means that I no longer get notifications when
  people at work IM me.  As such, the new version of Ubuntu has greatly
  diminished my ability to use Linux at my workplace.

  A way to use SIPE (or any previously supported account type not
  supported by Online Accounts) in Empathy -- even if it requires a non
  --pretty command line/config change -- would be very welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 23 07:18:15 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1070377/+subscriptions

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

[Desktop-packages] [Bug 164120] Re: file manager hangs when mounted nfs drive is no longer accessible

2013-08-14 Thread TimGS

** Changed in: thunar
   Importance: Low = Unknown

** Changed in: thunar
   Status: Invalid = Unknown

** Changed in: thunar
 Remote watch: None = Xfce Bugzilla #6185

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

Title:
  file manager hangs when mounted nfs drive is no longer accessible

Status in File Manager for KDE:
  Incomplete
Status in Thunar file manager:
  Unknown
Status in Thunar Virtual File System:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I am using ubuntu 7.10, Gutsy 386 version.

  I am using a laptop which I use to in home and office. At home I am
  having network drive which mounted through nfs in home.

  I normally put my laptop to suspend and then bring over the same to
  work. When I access nautilus in this case, it just simply hangs it
  does not open any folder neither from Places or directly typing
  command nautilus.

  This is very annoying as I have to reboot the computer just for
  nautilus hanging.

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

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

[Desktop-packages] [Bug 1212298] Re: file-roller crashed with SIGSEGV in g_closure_invoke()

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

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 #723841, 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/1212298/+attachment/3772550/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772552/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772554/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772555/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772556/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772557/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212298/+attachment/3772558/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 723841
   file-roller crashed with SIGSEGV in 
egg_tree_multi_drag_button_release_event()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  file-roller crashed with SIGSEGV in g_closure_invoke()

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  
  Crash when try to open a folder into the file

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: file-roller 3.8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  Date: Tue Aug 13 22:38:06 2013
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2013-06-19 (55 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MarkForUpload: True
  ProcCmdline: file-roller /home/alan/Descargas/matplotlib-1.3.0.tar.gz
  ProcCwd: /home/alan
  SegvAnalysis:
   Segfault happened at: 0x805f830: mov(%ebx),%edx
   PC (0x0805f830) ok
   source (%ebx) (0x7a7903f8) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev robots sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1212298/+subscriptions

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

[Desktop-packages] [Bug 164120] Re: file manager hangs when mounted nfs drive is no longer accessible

2013-08-14 Thread TimGS

I see this issue in Thunar on Xubuntu 12.04.

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

Title:
  file manager hangs when mounted nfs drive is no longer accessible

Status in File Manager for KDE:
  Incomplete
Status in Thunar file manager:
  Unknown
Status in Thunar Virtual File System:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I am using ubuntu 7.10, Gutsy 386 version.

  I am using a laptop which I use to in home and office. At home I am
  having network drive which mounted through nfs in home.

  I normally put my laptop to suspend and then bring over the same to
  work. When I access nautilus in this case, it just simply hangs it
  does not open any folder neither from Places or directly typing
  command nautilus.

  This is very annoying as I have to reboot the computer just for
  nautilus hanging.

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

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

[Desktop-packages] [Bug 1212317] [NEW] package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2013-08-14 Thread agarciamoreira

Public bug reported:

package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to
install/upgrade: problemas de dependencias - se deja sin configurar

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: libreoffice-base-core 1:3.5.7-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
Uname: Linux 2.6.32-50-generic i686
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
Date: Wed Aug 14 11:21:36 2013
DuplicateSignature: package:libreoffice-base-core:1:3.5.7-0ubuntu4:problemas de 
dependencias - se deja sin configurar
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: libreoffice
Title: package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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


** Tags: apport-package i386 need-duplicate-check quantal

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

Title:
  package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-base-core 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic i686
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Wed Aug 14 11:21:36 2013
  DuplicateSignature: package:libreoffice-base-core:1:3.5.7-0ubuntu4:problemas 
de dependencias - se deja sin configurar
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1212324] [NEW] package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2013-08-14 Thread agarciamoreira

Public bug reported:

package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade:
problemas de dependencias - se deja sin configurar

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: libreoffice-core 1:3.5.7-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
Uname: Linux 2.6.32-50-generic i686
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
Date: Wed Aug 14 11:21:36 2013
DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu4:problemas de 
dependencias - se deja sin configurar
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
MarkForUpload: True
SourcePackage: libreoffice
Title: package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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


** Tags: apport-package i386 quantal

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

Title:
  package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic i686
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Wed Aug 14 11:21:36 2013
  DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu4:problemas de 
dependencias - se deja sin configurar
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1212320] [NEW] nautilus crashed with SIGSEGV in gtk_action_get_name()

2013-08-14 Thread m0rtal

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

Public bug reported:

Just installed Dropbox and tried to open it's folder
(/home/uzername/Dropbox/)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Wed Aug 14 18:29:27 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2013-08-14 (0 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130814)
MarkForUpload: True
ProcCmdline: nautilus --new-window
SegvAnalysis:
 Segfault happened at: 0x7f0456e53dd6 gtk_action_get_name+22: cmp
%rax,(%rdx)
 PC (0x7f0456e53dd6) ok
 source %rax ok
 destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash saucy

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Just installed Dropbox and tried to open it's folder
  (/home/uzername/Dropbox/)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 18:29:27 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-08-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130814)
  MarkForUpload: True
  ProcCmdline: nautilus --new-window
  SegvAnalysis:
   Segfault happened at: 0x7f0456e53dd6 gtk_action_get_name+22:   cmp
%rax,(%rdx)
   PC (0x7f0456e53dd6) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212324] Re: package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade: problemas de dependencias - se deja sin configurar

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic i686
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Wed Aug 14 11:21:36 2013
  DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu4:problemas de 
dependencias - se deja sin configurar
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-core 1:3.5.7-0ubuntu4 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1212317] Re: package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to install/upgrade: problemas de dependencias - se deja sin configurar

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-base-core 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic i686
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Wed Aug 14 11:21:36 2013
  DuplicateSignature: package:libreoffice-base-core:1:3.5.7-0ubuntu4:problemas 
de dependencias - se deja sin configurar
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-base-core 1:3.5.7-0ubuntu4 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to quantal on 2013-08-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1212320] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()

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

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 #1193522, 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/1212320/+attachment/3772594/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772596/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772598/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772599/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772600/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772601/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212320/+attachment/3772602/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1193522
   nautilus crashed with SIGSEGV in gtk_action_get_name()

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Just installed Dropbox and tried to open it's folder
  (/home/uzername/Dropbox/)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 18:29:27 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-08-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130814)
  MarkForUpload: True
  ProcCmdline: nautilus --new-window
  SegvAnalysis:
   Segfault happened at: 0x7f0456e53dd6 gtk_action_get_name+22:   cmp
%rax,(%rdx)
   PC (0x7f0456e53dd6) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212322] Re: software-center crashed with signal 5 in _XReadEvents()

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

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 #1196625, 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/1212322/+attachment/3772604/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772606/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772607/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772608/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772609/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772610/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212322/+attachment/3772611/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1196625
   software-center crashed with signal 5 in _XReadEvents()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  software-center crashed with signal 5 in _XReadEvents()

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

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.08-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  Date: Wed Aug 14 20:56:25 2013
  ExecutablePath: /usr/share/software-center/software-center
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: software-center
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XReadEvents () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
  Title: software-center crashed with signal 5 in _XReadEvents()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212323] Re: nm-applet crashed with SIGSEGV in g_type_check_instance_is_a()

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

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 #1197550, 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/1212323/+attachment/3772613/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772615/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772624/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772625/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772626/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772628/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212323/+attachment/3772629/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  nm-applet crashed with SIGSEGV in g_type_check_instance_is_a()

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

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Wed Aug 14 20:01:03 2013
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static 
   192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.2  metric 1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: nm-applet
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6e48e8e g_type_check_instance_is_a+78:testb  
$0x4,0xe(%edi)
   PC (0xb6e48e8e) ok
   source $0x4 ok
   destination 0xe(%edi) (0xefea) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   gtk_status_icon_set_visible () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libappindicator3.so.1
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: nm-applet crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   DLink 0097dc6f-88ba-45a7-a4f8-e54215a6436f   
802-11-wireless   0never  yes   
no /org/freedesktop/NetworkManager/Settings/2
   DIGISOL   40350f93-3dc1-4ea3-b331-c8566395316c   
802-11-wireless   1375540002   Saturday 03 August 2013 07:56:42 PM IST yes  
 no /org/freedesktop/NetworkManager/Settings/1
   Auto Ethernet 4fe0780d-1dd1-4855-9847-e601e0caa401   
802-3-ethernet1376490570   Wednesday 14 August 2013 07:59:30 PM IST yes 
  no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth1   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE

[Desktop-packages] [Bug 1212337] [NEW] accounts-daemon crashed with SIGSEGV in dbus_connection_send()

2013-08-14 Thread daniel CURTIS

Public bug reported:

Hi. After login as a user, 'accountservice' crash. It happens a couple
of times, but it is not regular. Maybe, one crash for a two days. It
seems, that it is all what I can write about this issue. So more info

* ProblemType: Crash
* Architecture: i386
* DistroRelease: Ubuntu 12.04
* Uname: Linux 3.2.0-51-generic-pae i686
* ApportVersion: 2.0.1-0ubuntu17.4
* NonfreeKernelModules: nvidia
* Package: accountsservice 0.6.15-2ubuntu9.6
* Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax

Also '/var/log/apport.log' files contains some informations about this
issue. Everything is in a attached log file. I do not know why it
started to happen. Only one thing, which I've done for a few weeks was
'conky-all' install. Nothing more, nothing less - no administrative
tasks.

Best regards.

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


** Tags: accountservice crash segfault

** Attachment added: apport log file.
   
https://bugs.launchpad.net/bugs/1212337/+attachment/3772684/+files/apport.log.2

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

Title:
  accounts-daemon crashed with SIGSEGV in dbus_connection_send()

Status in “accountsservice” package in Ubuntu:
  New

Bug description:
  Hi. After login as a user, 'accountservice' crash. It happens a couple
  of times, but it is not regular. Maybe, one crash for a two days. It
  seems, that it is all what I can write about this issue. So more info

  * ProblemType: Crash
  * Architecture: i386
  * DistroRelease: Ubuntu 12.04
  * Uname: Linux 3.2.0-51-generic-pae i686
  * ApportVersion: 2.0.1-0ubuntu17.4
  * NonfreeKernelModules: nvidia
  * Package: accountsservice 0.6.15-2ubuntu9.6
  * Segfault happened at: 0xb76bb7c3:   mov0x10(%eax),%eax

  Also '/var/log/apport.log' files contains some informations about this
  issue. Everything is in a attached log file. I do not know why it
  started to happen. Only one thing, which I've done for a few weeks was
  'conky-all' install. Nothing more, nothing less - no administrative
  tasks.

  Best regards.

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

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

[Desktop-packages] [Bug 1163886] Re: software-center crashed with signal 5 with WebKit 2.0+

2013-08-14 Thread Smot

I don't know if the attached file will help - it's a debug log from 
software-center obtained by running this:
software-center --debug 2software-center.log



** Attachment added: software-center.log
   
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1163886/+attachment/3772732/+files/software-center.log

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

Title:
  software-center crashed with signal 5 with WebKit 2.0+

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

Bug description:
  software center crashes when I open it

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: software-center 5.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  3 14:15:24 2013
  Disassembly: = 0x7f104ac4f2c5:   Cannot access memory at address 
0x7f104ac4f2c5
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2012-10-23 (161 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  Signal: 5
  SourcePackage: software-center
  Stacktrace:
   #0  0x7f104ac4f2c5 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fff92459230
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 11 (LWP 16319):
   #0  0x7f104c563ca4 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7f1017021e40
  Title: software-center crashed with signal 5
  UpgradeStatus: Upgraded to raring on 2013-04-01 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1212344] Re: Xorg crashed with SIGABRT in use_shadow()

2013-08-14 Thread Rick Spencer

** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT in use_shadow()

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

Bug description:
  Tried changing the resolution in system settings and the session
  crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 14 12:12:35 2013
  DistUpgraded: 2013-08-14 09:14:03,895 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15f2]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15f2]
  InstallationDate: Installed on 2013-04-23 (112 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
  MachineType: ASUSTeK Computer Inc. K53SV
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=f6fdd2b0-ef68-4909-bca4-655662f88aec ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   xf86CrtcSetModeTransform ()
   ?? ()
   RRCrtcSet ()
   ProcRRSetCrtcConfig ()
  Title: Xorg crashed with SIGABRT in xf86CrtcSetModeTransform()
  UpgradeStatus: Upgraded to saucy on 2013-08-14 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53SV.302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53SV
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53SV.302:bd06/17/2011:svnASUSTeKComputerInc.:pnK53SV:pvr1.0:rvnASUSTeKComputerInc.:rnK53SV:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
  dmi.product.name: K53SV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu3
  xserver.bootTime: Wed Aug 14 12:12:41 2013
  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 id9964 
   vendor AUO
  xserver.version: 2:1.14.2-0ubuntu9

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

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

[Desktop-packages] [Bug 1212339] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()

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

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 #1193522, 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/1212339/+attachment/3772685/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772687/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772688/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772689/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772690/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772691/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1212339/+attachment/3772692/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1193522
   nautilus crashed with SIGSEGV in gtk_action_get_name()

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  crashed during a copy and paste operation

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 11:01:43 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'967x612+474+267'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'231'
  InstallationDate: Installed on 2013-06-30 (45 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/bin/nautilus
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f39ee1dadd6 gtk_action_get_name+22:   cmp
%rax,(%rdx)
   PC (0x7f39ee1dadd6) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: Upgraded to saucy on 2013-07-16 (29 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   deja-dup27.3.1-0ubuntu1
   dropbox 1.6.0
   evince  3.8.2-0ubuntu5
   file-roller 3.8.3-0ubuntu1
   totem   3.8.2-0ubuntu2~raring1

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

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

[Desktop-packages] [Bug 1212344] Re: Xorg crashed with SIGABRT in use_shadow()

2013-08-14 Thread Jason Warner

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)

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

Title:
  Xorg crashed with SIGABRT in use_shadow()

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

Bug description:
  Tried changing the resolution in system settings and the session
  crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 14 12:12:35 2013
  DistUpgraded: 2013-08-14 09:14:03,895 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15f2]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15f2]
  InstallationDate: Installed on 2013-04-23 (112 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
  MachineType: ASUSTeK Computer Inc. K53SV
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=f6fdd2b0-ef68-4909-bca4-655662f88aec ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   xf86CrtcSetModeTransform ()
   ?? ()
   RRCrtcSet ()
   ProcRRSetCrtcConfig ()
  Title: Xorg crashed with SIGABRT in xf86CrtcSetModeTransform()
  UpgradeStatus: Upgraded to saucy on 2013-08-14 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53SV.302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53SV
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53SV.302:bd06/17/2011:svnASUSTeKComputerInc.:pnK53SV:pvr1.0:rvnASUSTeKComputerInc.:rnK53SV:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
  dmi.product.name: K53SV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu3
  xserver.bootTime: Wed Aug 14 12:12:41 2013
  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 id9964 
   vendor AUO
  xserver.version: 2:1.14.2-0ubuntu9

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

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

[Desktop-packages] [Bug 1212340] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()