date:20140331

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

Title:
  Can't log in to Flickr

Status in Online Accounts: Account plugins:
  Confirmed
Status in “account-plugins” package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a new Flickr account, I am able to successfully log
  in, however it just redirects to the home page of Flickr's mobile
  site, instead of asking to grant access to the application, so the
  OAuth key is never obtained.

  account-plugin-flickr 0.11+14.04.20140325-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1299659/+subscriptions

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

[Desktop-packages] [Bug 1300599] Re: xscreensaver-demo crashed with SIGSEGV in gdk_window_set_transient_for()

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

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 #1104761, 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/1300599/+attachment/4057205/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057207/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057208/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057209/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057210/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057211/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300599/+attachment/4057212/+files/ThreadStacktrace.txt

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

** 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 xscreensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1300599

Title:
  xscreensaver-demo crashed with SIGSEGV in
  gdk_window_set_transient_for()

Status in “xscreensaver” package in Ubuntu:
  New

Bug description:
  Step to reproduce:
  Choose Help>About from the menu bar

  Expected behavior:
  About box appears

  Actual behavior:
  No about box appears, program crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xscreensaver 5.15-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 23:59:50 2014
  ExecutablePath: /usr/bin/xscreensaver-demo
  InstallationDate: Installed on 2014-03-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcCmdline: xscreensaver-demo
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f55ce9d1979 :   
testb  $0x30,0x84(%rsi)
   PC (0x7f55ce9d1979) ok
   source "$0x30" ok
   destination "0x84(%rsi)" (0x0084) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop:
   gdk_window_set_transient_for () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
   about_menu_cb ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xscreensaver-demo crashed with SIGSEGV in 
gdk_window_set_transient_for()
  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/xscreensaver/+bug/1300599/+subscriptions

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

[Desktop-packages] [Bug 1101951] Re: Webcam with cheese not working - shader fails to compile

2014-03-31 Thread Bug Watch Updater

** Changed in: cheese
   Status: Confirmed => Expired

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

Title:
  Webcam with cheese not working - shader fails to compile

Status in Cheese Camera Application:
  Expired
Status in Clutter GStreamer Bindings:
  Fix Released
Status in “cheese” package in Ubuntu:
  Invalid
Status in “clutter-gst-2.0” package in Ubuntu:
  Fix Released

Bug description:
  (cheese:3741): Cogl-WARNING **: Failed to link GLSL program:
  error: linking with uncompiled shader

  blank image
  --- 
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-01-19 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130118)
  MarkForUpload: True
  Package: cheese 3.6.2-0ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Tags:  raring
  Uname: Linux 3.8.0-1-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1300588] Re: Xorg crashed with SIGABRT

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057147/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057149/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057160/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057162/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057163/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057164/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300588/+attachment/4057165/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1033533
   Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW 
rendering

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT

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

Bug description:
  work in eclipse

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.0-1ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  CurrentDmesg:
   [   50.127481] type=1400 audit(1396328209.435:68): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=1809 comm="apparmor_parser"
   [   50.127486] type=1400 audit(1396328209.435:69): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=1809 comm="apparmor_parser"
   [   50.127956] type=1400 audit(1396328209.439:70): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=1809 comm="apparmor_parser"
  Date: Tue Apr  1 08:53:46 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1861]
  InstallationDate: Installed on 2014-03-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=782471ff-e022-4d58-ab34-d4d5e291290f ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55 LX
  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.:bvr1201:bd04/25/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55LX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.

[Desktop-packages] [Bug 1116071] Re: Google search povider for en-GB locale incorrectly adds "gl" parameter forcing UK-based search results

2014-03-31 Thread hackel

We need someone located in the UK to remove the "gl" parameter and see
if Google is properly detecting their location automatically.  In my
experience, it does a very good job of this, but if not then obviously I
agree all the UK users shouldn't have to deal with US results.  In my
case, this parameter also affects Google Shopping results, showing me
only products in UK stores in GBP.  Thankfully it is easy to use a
modified google.xml file.

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

Title:
  Google search povider for en-GB locale incorrectly adds "gl" parameter
  forcing UK-based search results

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  The Google search provider in 
/usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml adds the 
parameter

  According to Google: "The gl parameter value is a two-letter country code. 
For WebSearch results, the gl parameter boosts search results whose country of 
origin matches the parameter value."  This is the wrong behaviour in this 
instance.  The choice of the en-GB search plugin is based on the *language* 
spoken by the user.  I want to speak proper English, so I choose en-GB, even 
though I am located in the U.S.  I don't want to see UK-based search results, 
instead I want my search results to be based on my actual location, which 
either I have explicitly set or which Google is detecting automatically.

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

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

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2014-03-31 Thread Jeroen T. Vermeulen

** Description changed:

  My display's native resolution is 2560×1440 pixels.  Prior to, I think,
  Saucy I could only reach this resolution by adding it using xrandr, and
  then calling xrandr on boot/login to select that resolution.  The
  Display preferences did not show any higher options than 1920×1200.
  
  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
- Again, the Display preferences list that as the highest possible
- resolution.  But this time, attempts to ‘xrandr --admode’ my native
+ Again, the Display preferences list that resolution as the highest
+ possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.
  
  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to work
  with.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
+  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   16510 
-  vendor DEL
+  product id   16510
+  vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

Title:
  Screen resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did n

[Desktop-packages] [Bug 1073114] Re: Online Smart Scopes Do Not Respect User Privacy

2014-03-31 Thread Benjamin Kerensa

@mlaverdiere: I agree this announcement addresses any privacy concerns
users should have do we have a likely milestone to attach it to and is
it worth marking Fix Committed?

** Changed in: libunity (Ubuntu Quantal)
   Status: Confirmed => Won't Fix

** Changed in: libunity (Ubuntu Raring)
   Status: Confirmed => Won't Fix

** Changed in: unity-lens-shopping (Ubuntu Quantal)
   Status: Confirmed => Won't Fix

** Changed in: unity-lens-shopping (Ubuntu Raring)
   Status: Confirmed => Won't Fix

** Changed in: unity-lens-shopping (Ubuntu)
Milestone: None => later

** Changed in: libunity (Ubuntu)
Milestone: None => later

** Changed in: unity-lens-shopping (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: libunity (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Online Smart Scopes  Do Not Respect User Privacy

Status in “libunity” package in Ubuntu:
  In Progress
Status in “unity-lens-shopping” package in Ubuntu:
  In Progress
Status in “libunity” source package in Quantal:
  Won't Fix
Status in “unity-lens-shopping” source package in Quantal:
  Won't Fix
Status in “libunity” source package in Raring:
  Won't Fix
Status in “unity-lens-shopping” source package in Raring:
  Won't Fix

Bug description:
  See this from the Electronic Frontier Foundation (EFF), a well
  respected "international non-profit digital rights advocacy and legal
  organization" (as described on Wikipedia):
  https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads-
  and-data-leaks

  Obviously, despite some improvements that have came late in the 12.10
  development cycle, there are still serious privacy concerns with the
  unity shopping lens.  To be more precise, here are the main problems
  to be fixed according to EFF:

  - Disable "Include online search results" by default.

  - Explain in detail what Canonical does with search queries and IP
  addresses, how long it stores them, and in what circumstances it gives
  them to third parties.

  - Make the Search Results tab of the Privacy settings let users toggle
  on and off specific online search results, as some users might want
  Amazon products in their search results, but never anything from
  Facebook.

  Here is another related bug:

   #1055952 Direct data leaking to Amazon:
  https://bugs.launchpad.net/ubuntu/+source/unity-lens-
  shopping/+bug/1055952

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-shopping 6.8.0-0ubuntu1
  Uname: Linux 3.5.6-030506-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Oct 30 06:35:38 2012
  InstallationDate: Installed on 2012-02-12 (260 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: unity-lens-shopping
  UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago)

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

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

[Desktop-packages] [Bug 1278467] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

2014-03-31 Thread Juliusz Kotarski

nie mam zdania w tym względzie

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  notify_have_shell()

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

Bug description:
  This error shows up after each boot.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-settings-daemon 3.8.6.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 10 07:09:41 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2014-01-29 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7faee44f1b37:mov(%rax),%rdi
   PC (0x7faee44f1b37) ok
   source "(%rax)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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 () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

6) I have also tried with nvidia-prime and bbswitch purged as well
(bumblebee has never been installed). same problem.

Raj

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

Title:
  DPMS support broken, fails to wake up the monitor after putting it to
  sleep

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

Bug description:
  Also affects nvidia-graphics-drivers-319

  The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
  but with Nvidia instead of AMD/ATI drivers.

  HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
  display

  Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
  Only a restart of the Xserver will bring back the display at that point.

  A cycle of
  xset dpms force off; sleep 30; xset dpms force on
  will leave the display dark.

  At the moment I help myself by not allowing DPMS to switch off the display:
  neuffer@charion:~$ xset dpms 0 0 0

  neuffer@charion:~$ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1253009] Re: [FFe] Please sync latest upstream release (0.9x) from Debian experimental - Pitivi developers recommends to use 0.92 or later

2014-03-31 Thread Timo Jyrinki

** Description changed:

  Ubuntu Trusty still has old and outdated Pitivi version - 0.15, while Pitivi 
developers recommends to use 0.92 or later, see download page on 
http://pitivi.org :
  Various Linux distributions provide Pitivi in their repositories, but the 
version provided may be too old. For an optimal experience, make sure you are 
using Pitivi 0.92
  
  Please sync latest upstream Pitivi release (0.9x) from Debian
  experimental - AFAIK we have enough time until 14.04 import freeze to
  find if latest Pitivi release series is good enough for including into
  LTS release.
  
  Pitivi Wiki also contains info, that 0.15 release is lower quality than 0.92:
  That said, one month after 0.91, with the feedback we have received so far, 
we are pretty confident that the new release series is of much higher quality 
than the 0.15 series and older.
  See http://wiki.pitivi.org/wiki/0.93
  and http://wiki.pitivi.org/wiki/0.92
+ 
+ Addendum/Mirv: pitivi 0.15 end user experience as it is currently on
+ Ubuntu makes most people to back away from it - it requires specific
+ settings to not crash or hang, for example (I've found webm container to
+ usually work, but the last time I tried that didn't work either which
+ may be some bitrotting happening)

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

Title:
  [FFe] Please sync latest upstream release (0.9x) from Debian
  experimental - Pitivi developers recommends to use 0.92 or later

Status in “pitivi” package in Ubuntu:
  New
Status in “pitivi” package in Baltix:
  Triaged

Bug description:
  Ubuntu Trusty still has old and outdated Pitivi version - 0.15, while Pitivi 
developers recommends to use 0.92 or later, see download page on 
http://pitivi.org :
  Various Linux distributions provide Pitivi in their repositories, but the 
version provided may be too old. For an optimal experience, make sure you are 
using Pitivi 0.92

  Please sync latest upstream Pitivi release (0.9x) from Debian
  experimental - AFAIK we have enough time until 14.04 import freeze to
  find if latest Pitivi release series is good enough for including into
  LTS release.

  Pitivi Wiki also contains info, that 0.15 release is lower quality than 0.92:
  That said, one month after 0.91, with the feedback we have received so far, 
we are pretty confident that the new release series is of much higher quality 
than the 0.15 series and older.
  See http://wiki.pitivi.org/wiki/0.93
  and http://wiki.pitivi.org/wiki/0.92

  Addendum/Mirv: pitivi 0.15 end user experience as it is currently on
  Ubuntu makes most people to back away from it - it requires specific
  settings to not crash or hang, for example (I've found webm container
  to usually work, but the last time I tried that didn't work either
  which may be some bitrotting happening)

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

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

[Desktop-packages] [Bug 1287396] Re: [hsw mesa] GPU lockup IPEHR: 0x7a000003

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

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

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

Title:
  [hsw mesa] GPU lockup  IPEHR: 0x7a03

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

Bug description:
  I'm not sure if this is a bug in the driver or the kde lock subsystem.

  The system was powering down the display because of timeout, when I
  interrupted it. Got a black screen with the cursor. Cursor would move
  as I moved the mouse, but nothing else would display, despite hitting
  alt-tab, esc, and other keys.

  I hit ctl-alt-backspace and was prompted to file this bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  Date: Mon Mar  3 16:38:24 2014
  DistUpgraded: 2014-02-20 22:35:53,373 ERROR got an error from dpkg for pkg: 
'gcc-4.9-base': 'no package named `gcc-4.9-base' is installed, cannot configure'
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x7a03 IPEHR: 0x0b140001 Ubuntu 
14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05e3]
  InstallationDate: Installed on 2014-02-20 (10 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: Dell Inc. XPS 12-9Q33
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic 
root=UUID=085f457a-4960-450b-ad94-40bdb43fcfd4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x7a03 IPEHR: 0x0b140001
  UpgradeStatus: Upgraded to trusty on 2014-02-21 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/26/2013:svnDellInc.:pnXPS12-9Q33:pvrA02:rvnDellInc.:rnXPS12-9Q33:rvrA02:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Mar  3 16:38:17 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1

[Desktop-packages] [Bug 1300558] Re: AMD Radeon HD 5000/6000/7350/8350 Series [1002:68f9] Unable to hibernate with radeon driver

2014-03-31 Thread Po-Hsu Lin

This issue could be solved by installing the fglrx proprietary driver.

** Description changed:

  CID: 201108-8338
  
  This sysem cannot hibernate with the radeon driver.
  
  Steps:
  1. Install 12.04.4 + update, boot to desktop.
  2. Try to hibernate this system with "sudo pm-hibernate"
  3. If hibernated, wake it up by pressing the power button.
  
  Expected result:
  * Hibernate works fine.
  
  Actual result:
  * This system will wake itself up automatically, error message could be found 
in dmesg, also, it will cause Xorg crash in few minutes.
  
  [  216.329713] radeon :01:00.0: GPU lockup CP stall for more than 
1msec
  [  216.329715] radeon :01:00.0: GPU lockup (waiting for 
0x0004 last fence id 0x0002)
  [  216.329718] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
  [  216.329721] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB 
on ring 5 (-35).
  
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
  
+ WORKAROUND:
+ * Install the proprietary driver could solve this issue
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-18-generic 3.11.0-18.32~precise1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-18-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  ubuntu 1551 F pulseaudio
-  /dev/snd/controlC0:  ubuntu 1551 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ubuntu 1551 F pulseaudio
+  /dev/snd/controlC0:  ubuntu 1551 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
-  Card hw:0 'PCH'/'HDA Intel PCH at 0xfe70 irq 46'
-Mixer name : 'Realtek ALC662 rev1'
-Components : 'HDA:10ec0662,17aa307c,00100101'
-Controls  : 36
-Simple ctrls  : 18
+  Card hw:0 'PCH'/'HDA Intel PCH at 0xfe70 irq 46'
+    Mixer name : 'Realtek ALC662 rev1'
+    Components : 'HDA:10ec0662,17aa307c,00100101'
+    Controls  : 36
+    Simple ctrls  : 18
  Card1.Amixer.info:
-  Card hw:1 'Generic'/'HD-Audio Generic at 0xfe64 irq 48'
-Mixer name : 'ATI R6xx HDMI'
-Components : 'HDA:1002aa01,00aa0100,00100200'
-Controls  : 7
-Simple ctrls  : 1
+  Card hw:1 'Generic'/'HD-Audio Generic at 0xfe64 irq 48'
+    Mixer name : 'ATI R6xx HDMI'
+    Components : 'HDA:1002aa01,00aa0100,00100200'
+    Controls  : 7
+    Simple ctrls  : 1
  Card1.Amixer.values:
-  Simple mixer control 'IEC958',0
-Capabilities: pswitch pswitch-joined penum
-Playback channels: Mono
-Mono: Playback [on]
+  Simple mixer control 'IEC958',0
+    Capabilities: pswitch pswitch-joined penum
+    Playback channels: Mono
+    Mono: Playback [on]
  Date: Mon Mar 31 22:37:53 2014
  HibernationDevice: RESUME=UUID=ab871f11-e346-4694-b52f-879962d2a394
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: LENOVO FF
  MarkForUpload: True
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=24ed35d5-757c-40e7-a1fd-b3e820f89035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.11.0-18-generic N/A
-  linux-backports-modules-3.11.0-18-generic  N/A
-  linux-firmware 1.79.11
+  linux-restricted-modules-3.11.0-18-generic N/A
+  linux-backports-modules-3.11.0-18-generic  N/A
+  linux-firmware 1.79.11
  RfKill:
-  
+ 
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9QKT14AUS
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9QKT14AUS:bd03/11/2011:svnLENOVO:pnFF:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: FF
  dmi.product.version: Lenovo Product
  dmi.sys.vendor: LENOVO

** Package changed: linux-lts-saucy (Ubuntu) => xorg-lts-transitional
(Ubuntu)

** Package changed: xorg-lts-transitional (Ubuntu) => xorg-l

[Desktop-packages] [Bug 1300574] [NEW] Custom indicators not shown after restarting Unity

2014-03-31 Thread hackel

Public bug reported:

Tested on Unity 7.1.2+14.04.20140328.1-0ubuntu1

If Unity restarts, either by crashing or manually with "restart unity-
panel-service" or "unity --replace", when Unity comes back, I can no
longer see my custom indicators.  I am still able to see the default
indicators (sync, messages, sound, datetime, and session), but not the
ones I have installed: sensors, cpufreq, multiload, weather, etc.  These
indicators are still running and appear in the process list, I just
can't see them in the panel.  I still see notifications from them.  If I
kill and restart any of these indicators, they run fine, but I still
cannot see them in the panel.  The only way I have found to get them
back is to completely log out and  back in.

I can't figure out what differentiates these "custom" indicators from
the default ones that would cause them not to appear.  With weather-
indicator, I even created an upstart job to control it.  If no one else
is able to reproduce this, please let me know how best to debug it
further.

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

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

Title:
  Custom indicators not shown after restarting Unity

Status in “unity” package in Ubuntu:
  New

Bug description:
  Tested on Unity 7.1.2+14.04.20140328.1-0ubuntu1

  If Unity restarts, either by crashing or manually with "restart unity-
  panel-service" or "unity --replace", when Unity comes back, I can no
  longer see my custom indicators.  I am still able to see the default
  indicators (sync, messages, sound, datetime, and session), but not the
  ones I have installed: sensors, cpufreq, multiload, weather, etc.
  These indicators are still running and appear in the process list, I
  just can't see them in the panel.  I still see notifications from
  them.  If I kill and restart any of these indicators, they run fine,
  but I still cannot see them in the panel.  The only way I have found
  to get them back is to completely log out and  back in.

  I can't figure out what differentiates these "custom" indicators from
  the default ones that would cause them not to appear.  With weather-
  indicator, I even created an upstart job to control it.  If no one
  else is able to reproduce this, please let me know how best to debug
  it further.

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

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

[Desktop-packages] [Bug 1300558] [NEW] AMD Radeon HD 5000/6000/7350/8350 Series [1002:68f9] Unable to hibernate with radeon driver

You have been subscribed to a public bug:

CID: 201108-8338

This sysem cannot hibernate with the radeon driver.

Steps:
1. Install 12.04.4 + update, boot to desktop.
2. Try to hibernate this system with "sudo pm-hibernate"
3. If hibernated, wake it up by pressing the power button.

Expected result:
* Hibernate works fine.

Actual result:
* This system will wake itself up automatically, error message could be found 
in dmesg, also, it will cause Xorg crash in few minutes.

[  216.329713] radeon :01:00.0: GPU lockup CP stall for more than 1msec
[  216.329715] radeon :01:00.0: GPU lockup (waiting for 0x0004 
last fence id 0x0002)
[  216.329718] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
[  216.329721] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on 
ring 5 (-35).

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]

WORKAROUND:
* Install the proprietary driver could solve this issue

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.11.0-18-generic 3.11.0-18.32~precise1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-18-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 1551 F pulseaudio
 /dev/snd/controlC0:  ubuntu 1551 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfe70 irq 46'
   Mixer name   : 'Realtek ALC662 rev1'
   Components   : 'HDA:10ec0662,17aa307c,00100101'
   Controls  : 36
   Simple ctrls  : 18
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfe64 irq 48'
   Mixer name   : 'ATI R6xx HDMI'
   Components   : 'HDA:1002aa01,00aa0100,00100200'
   Controls  : 7
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Mar 31 22:37:53 2014
HibernationDevice: RESUME=UUID=ab871f11-e346-4694-b52f-879962d2a394
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
IwConfig:
 eth0  no wireless extensions.

 lono wireless extensions.
MachineType: LENOVO FF
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=24ed35d5-757c-40e7-a1fd-b3e820f89035 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-18-generic N/A
 linux-backports-modules-3.11.0-18-generic  N/A
 linux-firmware 1.79.11
RfKill:

SourcePackage: linux-lts-saucy
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 9QKT14AUS
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvr9QKT14AUS:bd03/11/2011:svnLENOVO:pnFF:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: FF
dmi.product.version: Lenovo Product
dmi.sys.vendor: LENOVO

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


** Tags: 201108-8338 amd64 apport-bug certification-grey hibernate precise 
qa-kernel-lts-testing running-unity taipei-lab
-- 
AMD Radeon HD 5000/6000/7350/8350 Series [1002:68f9] Unable to hibernate with 
radeon driver
https://bugs.launchpad.net/bugs/1300558
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg-lts-transitional in Ubuntu.

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

[Desktop-packages] [Bug 864735] Re: [ATI HDMI] HDMI Audio Disabled by Default (since oneiric)

2014-03-31 Thread Daniel Letzeisen

This should be fixed in Ubuntu 14.04/Trusty (or using a kernel >=
3.13.x). If anyone still experiences issues with audio using newer
kernel, please file a new bug.

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Low

** Changed in: alsa-driver (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [ATI HDMI] HDMI Audio Disabled by Default (since oneiric)

Status in “alsa-driver” package in Ubuntu:
  Fix Released

Bug description:
  Since kernel 3.0, upstream has disabled audio output for all ATI cards
  in the Radeon driver by default.

  === Workaround 1 ===

  Edit /etc/default/grub and change this line:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to this line

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.audio=1"

  Now run "sudo update-grub", then reboot your computer.

  === Or workaround 2 ===

  Install the proprietary Catalyst driver.

  ===

  There's no sound at all and videos playback in fast forward when
  outputting through the HDMI controller. This is a regression since it
  worked well in previous releases.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  melvin 8335 F pulseaudio
   /dev/snd/pcmC1D3p:   melvin 8335 F...m pulseaudio
   /dev/snd/controlC0:  melvin 8335 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe6f4000 irq 16'
     Mixer name : 'Realtek ALC1200'
     Components : 'HDA:10ec0888,10ec0888,00100101'
     Controls  : 38
     Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
     Mixer name : 'ATI RS690/780 HDMI'
     Components : 'HDA:1002791a,00791a00,0010'
     Controls  : 4
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Sun Oct  2 12:46:40 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110929)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: RS780 Azalia controller - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [GT5676, ATI RS690/780 HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7B3G1P04
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Not Available
  dmi.board.vendor: Gateway
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7B3G1P04:bd02/18/2008:svnGateway:pnGT5676:pvr7B3G1P04:rvnGateway:rnNotAvailable:rvrNotAvailable:cvnGateway:ct3:cvr1.0:
  dmi.product.name: GT5676
  dmi.product.version: 7B3G1P04
  dmi.sys.vendor: Gateway

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-03-31 Thread Seth Miers

I have this problem on my ASUS UX32VD

Has anyone discovered a synaptics fix?

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” package in Ubuntu:
  Opinion

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see "synaptics: ETPS/2 Elantech Touchpad: 
touchpad found" each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1165232] Re: Openchrome (1:0.3.1-0ubuntu1) crash system after start X

2014-03-31 Thread Alberto Jovito

** Tags added: saucy

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

Title:
  Openchrome (1:0.3.1-0ubuntu1) crash system after start X

Status in openchrome:
  Fix Released
Status in “xserver-xorg-video-openchrome” package in Ubuntu:
  Fix Released

Bug description:
  When you start Ubuntu / Xubuntu / Lubuntu 12:10 or 13:04 (Beta), the
  system hangs before loading the graphical environment (system freezes
  with the screen totally black).

  My video device:
  01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 
[Chrome 9 HC] (rev 01)

  The Ubuntu installation is only possible using the parameter
  xforcevesa in GRUB from Live CD / USB. After installation you need to
  configure xorg.conf to load the VESA driver and to start with the
  correct resolution.

  Bugs have been reported:
  https://bugs.freedesktop.org/show_bug.cgi?id=58409
  https://bugs.freedesktop.org/show_bug.cgi?id=53307

  Fixed:
  https://bugs.freedesktop.org/show_bug.cgi?id=53307#c21

  I compiled the version of Git and solved the problem. I would ask that
  the fix was included in the repositories.

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

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

[Desktop-packages] [Bug 1220865] Re: [nvidia-prime] Xorg freeze after resume from suspend

2014-03-31 Thread Seth Miers

I still have this problem on 3/31/2014
It seems to go along with the touchpad bug as well:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1220426

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

Title:
  [nvidia-prime] Xorg freeze after resume from suspend

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

Bug description:
  Resuming from suspend freezes my display while usind nvidia+intel option with 
nvidia-prime.
  I have to do a VT switch to get it moving again, but rendering is garbled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-9ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.1-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 Sep  4 20:48:44 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319-updates, 319.32, 3.11.0-4-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Always occurs after resume from suspend
  GpuHangStarted: Immediately after installing this version of Ubuntu
  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-08-30 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829)
  MachineType: ASUSTeK Computer Inc. N43SL
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=dd997685-cbb7-4674-843c-8b773b41224b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N43SL.302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N43SL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN43SL.302:bd02/15/2011:svnASUSTeKComputerInc.:pnN43SL:pvr1.0:rvnASUSTeKComputerInc.:rnN43SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N43SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  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-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Sep  4 18:05:52 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

[Desktop-packages] [Bug 1228841] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

** Tags added: trusty

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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

Bug description:
  Error wiping device: Command-line `wipefs -a "/dev/sdd1"' exited with 
non-zero exit status 1:
  stdout: `8 bytes were erased at offset 0x52 (vfat)
  they were: 46 41 54 33 32 20 20 20
  '
  stderr: `wipefs: error: /dev/sdd1: probing initialization failed
  ' (udisks-error-quark, 0)

  When I format a pendrive.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: i386
  Date: Sun Sep 22 13:50:32 2013
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2013-09-17 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130917)
  MarkForUpload: True
  ProcCmdline: gnome-disks
  SegvAnalysis:
   Segfault happened at: 0xb6ee9483 :   mov
(%esi),%eax
   PC (0xb6ee9483) ok
   source "(%esi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   udisks_object_get_partition_table () from 
/usr/lib/i386-linux-gnu/libudisks2.so.0
   ?? ()
   ?? ()
   gdu_window_ensure_unused_list ()
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/gnome-disk-utility/+bug/1228841/+subscriptions

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

[Desktop-packages] [Bug 1300556] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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

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 #1228841, 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/1300556/+attachment/4056984/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056986/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056987/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056988/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056989/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056990/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300556/+attachment/4056991/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1228841
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

** 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 gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1300556

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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

Bug description:
  1. Description:   Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  2. gnome-disk-utility:
Installed: 3.10.0-1ubuntu2
Candidate: 3.10.0-1ubuntu2
Version table:
   *** 3.10.0-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I tried to power down an attached USB HDD, but this error popped
  up.  The USB HDD wasn't showing up properly.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 22:59:45 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-02-15 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
  ProcCmdline: gnome-disks
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0ac1a53f7f :   
mov(%rbx),%rdi
   PC (0x7f0ac1a53f7f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_get_partition_table () from 
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/gnome-disk-utility/+bug/1300556/+subscriptions

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

[Desktop-packages] [Bug 1300557] [NEW] Screen resolution no longer works

2014-03-31 Thread Jeroen T. Vermeulen

Public bug reported:

My display's native resolution is 2560×1440 pixels.  Prior to, I think,
Saucy I could only reach this resolution by adding it using xrandr, and
then calling xrandr on boot/login to select that resolution.  The
Display preferences did not show any higher options than 1920×1200.

In Saucy, the native resolution just worked, and I could stop using
xrandr.  It also worked in Trusty in the alpha releases, up to (and I
think including) beta-1.  But today (this is not an April's fool, is
it?) I rebooted after an upgrade, and found myself back in 1920×1200.
Again, the Display preferences list that as the highest possible
resolution.  But this time, attempts to ‘xrandr --admode’ my native
resolution failed.

The error message wasn't very helpful; I'll try to reproduce it later
but it throws my display into yet a lower resolution that's hard to work
with.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr  1 09:59:00 2014
DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2013-08-03 (240 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
dmi.bios.date: 05/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-D3HP-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z87-D3HP
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Apr  1 09:52:36 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16510 
 vendor DEL
xserver.version: 2:1.15.0-1ubuntu7

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


** Tags: amd64 apport-bug compiz-0.9 resolution trusty ubuntu

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

Title:
  Screen resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that as the highest possible
  resolution.  But this time, attempts to ‘xrandr --admode’ my native
  resoluti

[Desktop-packages] [Bug 1034132] Re: [MacBook2, 1] Touchpad cursor moving in steps

2014-03-31 Thread Clinton

It is currently being reviewed. I'm guessing it will be accepted in time
for 3.15.

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

Title:
  [MacBook2,1] Touchpad cursor moving in steps

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I'm on a MacBook2,1, running a fully updated Ubuntu 12.04. When using
  the internal Touchpad (appletouch driver), the cursor only moves
  horizontally or vertically. When dragging a diagonal line, the cursor
  will move in steps, basically rendering the builtin touchpad unusable.
  This issue is also described in a forum thread:
  http://ubuntuforums.org/showthread.php?t=813884&page=6

  WORKAROUND: In precise, in the second post on page 6 describes a solution. In 
the linux kernel, in appletouch.c, change the following two defines and 
recompile:
  Original:
  #define ATP_FUZZ 16
  #define ATP_THRESHOLD 5

  New:
  #define ATP_FUZZ 0
  #define ATP_THRESHOLD 3

  I tried this and can confirm that the touchpad is now fully usable.
  However, recompiling the kernel takes several hours and *all* of the
  disk space on my laptop. Doing this on every kernel update is just not
  practical. I would therefore like to ask that this be applied as a
  patch to the default ubuntu kernel. At the very least, please make an
  optional package containing the patched appletouch driver that can be
  selectively installed by people having this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-generic 3.2.0.27.29
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  damian 1778 F pulseaudio
  CRDA:
   country AW:
    (2402 - 2482 @ 40), (N/A, 20)
    (5170 - 5250 @ 40), (N/A, 20)
    (5250 - 5330 @ 40), (N/A, 20), DFS
    (5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9044 irq 43'
     Mixer name : 'SigmaTel STAC9221 A1'
     Components : 'HDA:83847680,106b2200,00103401'
     Controls  : 25
     Simple ctrls  : 13
  Date: Tue Aug  7 21:35:12 2012
  HibernationDevice: RESUME=UUID=a7716e7d-8718-4fe9-988f-958519d6a2c2
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac 
(20120425.1)
  MachineType: Apple Inc. MacBook2,1
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic 
root=UUID=c63dd388-29f9-43dc-a835-0b471ccb2f85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-27-generic N/A
   linux-backports-modules-3.2.0-27-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB21.88Z.00A5.B07.0706270922
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4208CA9
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4208CA9
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CA9:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CA9:
  dmi.product.name: MacBook2,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1278467] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

2014-03-31 Thread Mitch Dunaway

Only got this bug twice so far at bootup.  The first time I do not
remember anything special but the second time was right after I had
installed "Ubuntu base" with the Software Updater.

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

Title:
  [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
  notify_have_shell()

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

Bug description:
  This error shows up after each boot.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-settings-daemon 3.8.6.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 10 07:09:41 2014
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationDate: Installed on 2014-01-29 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7faee44f1b37:mov(%rax),%rdi
   PC (0x7faee44f1b37) ok
   source "(%rax)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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 () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in 
ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1251849] Re: [VX820] Regression: driver does not work on Samsung NC20

2014-03-31 Thread Alberto Jovito

Ok thanks. bigboss77 also did a very good job triangulating the problem.
Everything is prepared.

Approve the package in, saucy-proposed for testing?

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

Title:
  [VX820] Regression: driver does not work on Samsung NC20

Status in openchrome:
  Confirmed
Status in “xserver-xorg-video-openchrome” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-openchrome” source package in Saucy:
  In Progress

Bug description:
  * Impact:
  - the driver doesn't work with the X.org version in 13.10

  * Test case:
  - try using 13.10 on a machine needing the openchrome driver (a samsung nc20 
for example

  * regression potential:
  - check that xorg sessions work as they should. The patches have received 
testing in Debian/Trusty and upstream, so presumably should be fairly safe. The 
number of people using openchrome is relatively small compared to the main X 
drivers, so the scope of risk is rather small here.

  ---

  I'm using a Samsung NC20 since a couple of years now. It has never
  been easy with X11 but with Ubuntu 13.10/saucy it has become an export
  issue to get this netbook running.

  Notice that this is a regression from Ubuntu 13.04/raring where
  openchrome was worked more or less flawless.

  With 13.10 however, X11 bails out and even the console is not usable
  afterwards.

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

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

[Desktop-packages] [Bug 1297692] Re: Onboard not working with wacom driver

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

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

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

Title:
  Onboard not working with wacom driver

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

Bug description:
  If I choose the wacom driver instead of the evdev driver in:

   /usr/share/X11/xorg.conf.d/10-evdev.conf

  the touchscreen works in general fine, but it is not posibible to type
  on the onscreen keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 26 09:27:31 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-11 (73 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
  SourcePackage: onboard
  UpgradeStatus: Upgraded to trusty on 2014-03-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1297692] Re: Onboard not working with wacom driver

2014-03-31 Thread Tom Kazimiers

Hi,

sorry for chiming in, but I see the very same problem on my Laptop
(Lenovo X220t Tablet) with a Wacom (mutli-)touchpad. It is not Ubuntu
what I am using, though---I am on Arch. Neither Gtk nor Xinput works as
Input Even Source. With the former nothing happens at all, but with the
latter I get a lot of these messages, when Onboard is started from the
terminal:

Gdk-CRITICAL **: gdk_device_get_axis_use: assertion 'index_ <
device->axes->len' failed

This happens with both "single" and "multi" selected as Touch Input.
When having "none" selected, I get no reaction at all. I can produce
characters by clicking on them with the mouse, though.

I attached the output from the commands you asked tuxiano for in #5 as
ep121_2.txt, just in case they might be useful.

Hopefully, my issue is related to this bug report. I am sorry if not.


** Attachment added: "ep121_2.txt"
   
https://bugs.launchpad.net/onboard/+bug/1297692/+attachment/4056964/+files/ep121_2.txt

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

Title:
  Onboard not working with wacom driver

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

Bug description:
  If I choose the wacom driver instead of the evdev driver in:

   /usr/share/X11/xorg.conf.d/10-evdev.conf

  the touchscreen works in general fine, but it is not posibible to type
  on the onscreen keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 26 09:27:31 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-11 (73 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
  SourcePackage: onboard
  UpgradeStatus: Upgraded to trusty on 2014-03-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1300549] Re: Xorg crashed with SIGABRT in DamageRegister()

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

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 #1194114, 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/1300549/+attachment/4056922/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056925/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056936/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056938/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056939/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056940/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300549/+attachment/4056941/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1194114
   [hybrid] Xorg crashed with SIGABRT in DamageRegister()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

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

Bug description:
  Bringing up a Dell XPS  L502X laptop from suspended state.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.0-1ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 31 21:37:33 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-18-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-19-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-20-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b6]
  InstallationDate: Installed on 2014-03-20 (11 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=7681551f-ecda-4422-bd5d-928060913b91 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   DamageRegister ()
   ?? ()
   BlockHandler ()
   WaitForSomething ()
   ?? ()
  Title: Xorg crashed with SIGABRT in DamageRegister()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg

[Desktop-packages] [Bug 1296966] Re: Displays: Can't modify UI scale slide with keyboard

2014-03-31 Thread Steve Magoun

This is only partially fixed in u-c-c 14.04.3+14.04.20140328-0ubuntu1.
The keyboard can now move the slider, but the UI scale does not change
when you do this. The UI scale does change when you use the mouse to
move the slider.

To reproduce, follow the instructions in the original description
Expected results:
UI slider moves and the UI scales up/down with the slider

Actual results:
UI slider moves and the UI does not scale up/down with the slider

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

Title:
  Displays: Can't modify UI scale slide with keyboard

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

Bug description:
  It should be possible to modify the UI Scale slider using the
  keyboard.

  To reproduce:
  1) Launch the Displays control panel
  2) Click the thumb/handle in the UI scale slider once, to select it. Notice 
that the handle gets an orange border, to indicate that it's selected
  3) Press the left/right arrow keys to modify the UI scale

  Expected results:
  The UI scale slider responds to the arrow keys

  Actual results:
  Nothing happens when you use the keyboard to manipulate the UI scale slider

  This is an accessibility issue. It's also a problem if you set the UI
  scale so big that the UI scale widget is no longer drawn onscreen -
  you can't use keyboard navigation to reset it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 24 17:40:33 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (111 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2
   gnome-control-center 1:3.6.3-0ubuntu54

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

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

[Desktop-packages] [Bug 296867] Re: empathy needs to support OTR encryption

2014-03-31 Thread Jordan Farrell

I am sorry if you feel that I have disappeared. I did not intend it that
way. I did what I could to help. The developers of empathy stated that
they could not implement OTR unless they had a spec first. They also
forced the issue that my spec had to include XTLS. I am only a novice
programer and certianly not a spec writer, I also volunteered for far
more then I could handle hoping that OTR would be a welcome addition to
Telepathy. Unfortunately even after the Spec was ready for review, it
never recieved a review. I also was working in Python as that is what I
program in, and Telepathy removed support for Python around this same
time. JPRvita told me that he would take my spec and complete it for
XTLS and that he could program in C. For a long time it looked like this
would work. JPRvita had a solid spec, but as happend with me the spec
was never reviewed, I am not sure what happened to him and his GSoC
XTLS/OTR Spec for Telepathy.

References:
http://jprvita.wordpress.com/2011/07/17/otr-over-xmpp-on-telepathy/
http://lists.freedesktop.org/archives/telepathy/2011-June/005583.html

Honestly my take is that this is a developer issue, they don't want OTR
and no one can force it upon them.

So I got over it and I use Pidgin.

FYI for "cbris" or "ScotlandHacks" you should use jprvita's Spec it was
much further along than mine, it is here: https://gitorious.org/jprvita-
repos/telepathy-gabble/source/

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

Title:
  empathy needs to support OTR encryption

Status in Chat app, and Telepathy user interface:
  Confirmed
Status in One Hundred Papercuts:
  Invalid
Status in Telepathy framework - library:
  Confirmed
Status in “empathy” package in Ubuntu:
  Triaged
Status in “libtelepathy” package in Ubuntu:
  Confirmed
Status in “empathy” package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: empathy

  Hello, 
  I just tried empathy (the Intrepid version) and it looked very solid and 
stable. There were a few minor things that could be improved (e.g. 
automatically resizing the contact list), but that is not the topic here.
  The reason why I won't switch to empathy from pidgin is the missing OTR 
support (http://www.cypherpunks.ca/otr/ ). This is a really important feature 
because no one should read your messages.
  There were others with the same idea (links at the bottom).
  Would be so great if it could support that important encryption standard.
  Thanks for helping out!

  Links:
  https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2
  http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html
  http://bugs.freedesktop.org/show_bug.cgi?id=16891

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

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

[Desktop-packages] [Bug 1251849] Re: [VX820] Regression: driver does not work on Samsung NC20

2014-03-31 Thread Alberto Jovito

** Description changed:

- * Impact: 
- - the driver doesn't work with the xorg version in 13.10
+ * Impact:
+ - the driver doesn't work with the X.org version in 13.10
  
  * Test case:
  - try using 13.10 on a machine needing the openchrome driver (a samsung nc20 
for example
  
  * regression potential:
- - check that xorg sessions work as they should
+ - check that xorg sessions work as they should. The patches have received 
testing in Debian/Trusty and upstream, so presumably should be fairly safe. The 
number of people using openchrome is relatively small compared to the main X 
drivers, so the scope of risk is rather small here.
  
  ---
  
- 
- I'm using a Samsung NC20 since a couple of years now. It has never been easy 
with X11 but with Ubuntu 13.10/saucy it has become an export issue to get this 
netbook running.
+ I'm using a Samsung NC20 since a couple of years now. It has never been
+ easy with X11 but with Ubuntu 13.10/saucy it has become an export issue
+ to get this netbook running.
  
  Notice that this is a regression from Ubuntu 13.04/raring where
  openchrome was worked more or less flawless.
  
  With 13.10 however, X11 bails out and even the console is not usable
  afterwards.

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

Title:
  [VX820] Regression: driver does not work on Samsung NC20

Status in openchrome:
  Confirmed
Status in “xserver-xorg-video-openchrome” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-openchrome” source package in Saucy:
  In Progress

Bug description:
  * Impact:
  - the driver doesn't work with the X.org version in 13.10

  * Test case:
  - try using 13.10 on a machine needing the openchrome driver (a samsung nc20 
for example

  * regression potential:
  - check that xorg sessions work as they should. The patches have received 
testing in Debian/Trusty and upstream, so presumably should be fairly safe. The 
number of people using openchrome is relatively small compared to the main X 
drivers, so the scope of risk is rather small here.

  ---

  I'm using a Samsung NC20 since a couple of years now. It has never
  been easy with X11 but with Ubuntu 13.10/saucy it has become an export
  issue to get this netbook running.

  Notice that this is a regression from Ubuntu 13.04/raring where
  openchrome was worked more or less flawless.

  With 13.10 however, X11 bails out and even the console is not usable
  afterwards.

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

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

[Desktop-packages] [Bug 1296966] Re: Displays: Can't modify UI scale slide with keyboard

2014-03-31 Thread Steve Magoun

** Changed in: unity-control-center (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Displays: Can't modify UI scale slide with keyboard

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

Bug description:
  It should be possible to modify the UI Scale slider using the
  keyboard.

  To reproduce:
  1) Launch the Displays control panel
  2) Click the thumb/handle in the UI scale slider once, to select it. Notice 
that the handle gets an orange border, to indicate that it's selected
  3) Press the left/right arrow keys to modify the UI scale

  Expected results:
  The UI scale slider responds to the arrow keys

  Actual results:
  Nothing happens when you use the keyboard to manipulate the UI scale slider

  This is an accessibility issue. It's also a problem if you set the UI
  scale so big that the UI scale widget is no longer drawn onscreen -
  you can't use keyboard navigation to reset it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 24 17:40:33 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (111 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2
   gnome-control-center 1:3.6.3-0ubuntu54

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

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

[Desktop-packages] [Bug 1299348] Re: fglrx (not installed): fglrx kernel module failed to build

2014-03-31 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1263224, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1263224
   fglrx (not installed): fglrx kernel module failed to build [warning: passing 
argument 1 of ‘(acpi_status (*)(u32,  void *, void *))handler’ makes integer 
from pointer without a cast]

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

Title:
  fglrx (not installed): fglrx kernel module failed to build

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

Bug description:
  00

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.11.0-18-generic
  Date: Fri Mar 28 15:21:21 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 13.101, 3.11.0-18-generic, x86_64: installed
  DuplicateSignature: dkms:fglrx:(not 
installed):/var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.c:999:5: error: too 
few arguments to function '(acpi_status (*)(u32,  void *, void *))handler'
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:2557]
  InstallationDate: Installed on 2014-03-27 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  PackageVersion: (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic.efi.signed 
root=UUID=3ff452e9-c58c-424d-a93a-d895bb32d5c9 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx (not installed): fglrx kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0711
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-MX
  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.:bvr0711:bd12/19/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Mar 29 13:29:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2~saucy1
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1299597] Re: nvidia-331-updates-uvm 331.38-0ubuntu6: nvidia-331-updates-uvm kernel module failed to build

2014-03-31 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1268257, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build [.tmp_nv.o': No such file]

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

Title:
  nvidia-331-updates-uvm 331.38-0ubuntu6: nvidia-331-updates-uvm kernel
  module failed to build

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

Bug description:
  Notification occurred after desktop appeared after a reboot.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates-uvm 331.38-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-20-generic
  Date: Fri Mar 28 23:56:36 2014
  InstallationDate: Installed on 2012-12-26 (458 days ago)
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
  PackageVersion: 331.38-0ubuntu6
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.38-0ubuntu6: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: Upgraded to trusty on 2014-03-13 (16 days ago)

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

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

[Desktop-packages] [Bug 1243557]

2014-03-31 Thread Rebecca Palmer

Created attachment 96610
kernel log 3.14rc-Mar-26

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
  status 0x0080"

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  "EQ overflow" errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section "Device"
    Identifier  "Default Device"
    Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

[Desktop-packages] [Bug 1243557]

2014-03-31 Thread Rebecca Palmer

This bug still exists in 3.14rc commit
f217c44ebd41ce7369d2df07622b2839479183b0 (26 Mar Linus' tree, Ubuntu
userspace; as the nouveau/master branch hasn't been used for 5 months,
should we stop suggesting that people test with it?).

Is there anything else I can do to help?  I will probably only have this
machine for a few more months.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
  status 0x0080"

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  "EQ overflow" errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section "Device"
    Identifier  "Default Device"
    Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-e

[Desktop-packages] [Bug 1243557]

2014-03-31 Thread Rebecca Palmer

Created attachment 96611
Xorg log 3.14rc-Mar-26

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
  status 0x0080"

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  "EQ overflow" errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section "Device"
    Identifier  "Default Device"
    Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

Have not tried that. it's kind of difficult to reconnect it that way.

The thing is that this has worked perfectly from ubuntu 10.10 (Maverick
Merkeet) all the way to Saucy Salamander. so perfectly fine with a
nVidia card and an Onkyo receiver for more than 3 1/2 years.

I upgraded the video card from an older GT 220 to a GT 640 late last
year. But that setup was working fine for months with Saucy Salamander.

The trouble only started from two Saturdays ago (22nd March 2014) when I
upgraded to Trusty. The "new" trusty nVidia driver (version 3.31) was
working fine in Saucy as well (as I needed to upgrade to that to support
the GT 640).

I've tried the following in Trusty with no results

1) tried the ubuntu and xorg-edgers version of the nvidia 3.31 driver.
also tried the nvidia-331-updates package from ubuntu as well

2) tried the nvidia 3.34 driver from xorg-edgers

3) disabled all power management using xset, commands in xorg.conf and
installing xscreensaver and setting it to disabled. this is working as
the screen never goes off.

4) rebooted into the saucy linux kernel (3.11-20) that used to work.
same effect as the trust 3.13 kernel.

5) updated everything from xorg-edgers

not sure what else to try. I doubt this is a hardware issue as the same
setup just used to work with the previous ubuntu version. no cables,
hardware etc. have changed. except for the software upgrade.

Any ideas?

Raj

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

Title:
DPMS support broken, fails to wake up the monitor after putting it to
sleep

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

Bug description:
Also affects nvidia-graphics-drivers-319

The effect is identical to
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
auto repeat: onkey click percent: 0LED mask:
XKB indicators:
00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep: off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock: off
12: Group 2: off13: Mouse Keys: off
auto repeat delay: 500repeat rate: 20
auto repeating keys: 00ffdbbf
fadfffefffed
9fff
fff7
bell percent: 50bell pitch: 400bell duration: 100
Pointer Control:
acceleration: 2/1threshold: 4
Screen Saver:
prefer blanking: yesallow exposures: yes
timeout: 0cycle: 0
Colors:
default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
Standby: 0Suspend: 0Off: 0
DPMS is Enabled
Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1237379] Re: 10de:1245 [Asus M5A99X EVO] standby doesn't work with nouveau

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

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

Title:
  10de:1245 [Asus M5A99X EVO] standby doesn't work with nouveau

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

Bug description:
  Since 13.10 my machine does not wake up from standby. I get a dark
  screen with the mousepointer.

  WORKAROUND: Use nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.18
  ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  k  2169 F pulseaudio
   /dev/snd/controlC1:  k  2169 F pulseaudio
   /dev/snd/controlC0:  k  2169 F pulseaudio
  CurrentDmesg:
   [   93.080126] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [  101.538873] show_signal_msg: 144 callbacks suppressed
   [  101.538880] dconf worker[1283]: segfault at 0 ip 7f23bc12fb7c sp 
7f23b32d6990 error 4 in libgio-2.0.so.0.3800.0[7f23bc088000+15c000]
  Date: Wed Oct  9 14:29:46 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3b68e676-fe5e-4767-9243-b24ed269e10d
  InstallationDate: Installed on 2013-10-05 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  MarkForUpload: True
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=7dbba93c-0344-435d-a1b4-79be4c5c3093 ro splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  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.:bvr0901:bd12/02/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO: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.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   11.168248] r8169 :02:00.0 eth0: link up
   [   11.168255] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:1245] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83b9]
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-031300rc1-generic 
root=UUID=319f8c0a-70e6-43c8-b885-f89b6cc3f8a4 ro quiet splash vt.handoff=7
  Tags:  trusty ubuntu reproducible compiz-0.9
  Uname: Linux 3.13.0-031300rc1-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom lpadmin plugdev sudo
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO: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:

[Desktop-packages] [Bug 1269260] Re: 8086:0166 [Lenovo ThinkPad X230] x hangs after standby

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

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

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

Title:
  8086:0166 [Lenovo ThinkPad X230] x hangs after standby

Status in “xorg” package in Ubuntu:
  New

Bug description:
  8086:0112 [drm:i915_hangcheck_elapsed] in 12.04

  Problem described there occurs regularly, meaning nearly always, after
  sleep or standby. Switching to a console before(!) entering standby
  helps to circumvent the problem. Switching to a console after wakeup
  is possible but this doesn't reanimate the X-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26
  Uname: Linux 3.5.0-45-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: kwin
  Date: Wed Jan 15 14:14:00 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: LENOVO 23065PJ
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic 
root=UUID=bbeacb23-4c3b-4048-b4b0-0a52c8c20020 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23065PJ
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn23065PJ:pvrThinkPadX230:rvnLENOVO:rn23065PJ:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23065PJ
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.12-0ubuntu3
  version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1172221] Re: 8086:0166 JavaFX not working since 12.10

jenskapitza, any change for you with the latest Oracle Java 7u51?

** Changed in: xorg-server (Ubuntu)
   Status: Expired => 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/1172221

Title:
  8086:0166 JavaFX not working since 12.10

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

Bug description:
  I've big problems to move from 12.04 to any newer version. Yes i know that it 
is supported since 14.04 but the new drivers and acpi issues are fixed in newer 
kernel.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Pegatron Device [1b0a:20c5]
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140107)
  MachineType: Medion S4216
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper 
iso-scan/filename=/iso/trusty-desktop-amd64.iso noprompt noeject
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Tags:  trusty ubuntu single-occurrence reproducible compiz-0.9
  Uname: Linux 3.12.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 507
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S4216
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr507:bd11/05/2012:svnMedion:pnS4216:pvr1.0:rvnMedion:rnS4216:rvr1.0:cvnMedion:ct10:cvr1.0:
  dmi.product.name: S4216
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Wed Jan  8 08:54:30 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12604
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

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

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

[Desktop-packages] [Bug 886773] Re: 10de:0407 [Toshiba Qosmio G40-114] Resolution is changed at startup

** Tags removed: needs-bisect
** Tags added: performing-bisect

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

Title:
  10de:0407 [Toshiba Qosmio G40-114] Resolution is changed at startup

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

Bug description:
  I encountered the following bug for the second time in ~10-15 days.
  When booting ubuntu, screen resolution is changed to something like
  800x600, I reboot immediately and the resolution is back to its normal
  size. Resolution was not changed during my session yesterday (neither
  "by hand", nor by an application).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CheckboxSubmission: e9b05430043ab78d4dfad1adca061c75
  CheckboxSystem: 8747e013a552447cbd294fa2163135be
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,move,regex,place,snap,grid,session,vpswitch,compiztoolbox,mousepoll,resize,animation,gnomecompat,imgpng,expo,wall,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDmesg: [  315.809163] CE: hpet increased min_delta_ns to 20113 nsec
  Date: Sun Nov  6 10:33:04 2011
  DistUpgraded: Log time: 2011-10-19 14:27:10.689888
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: alsa-hda, 0.201110190030~oneiric1, 3.0.0-12-generic, i686: 
installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:0001]
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  MachineType: TOSHIBA Qosmio G40
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=4482c8ac-6d58-482b-aab5-734d05591aa9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-19 (17 days ago)
  dmi.bios.date: 02/29/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 2.20
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 10
  dmi.chassis.version: IBA
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion2.20:bd02/29/2008:svnTOSHIBA:pnQosmioG40:pvrPQG40E-01G019FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTS:ct10:cvrIBA:
  dmi.product.name: Qosmio G40
  dmi.product.version: PQG40E-01G019FR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [  803.922305] EXT4-fs (sdb5): mounting ext3 file system using the ext4 
subsystem
   [  819.760041] EXT4-fs (sdb5): recovery complete
   [  819.786687] EXT4-fs (sdb5): mounted filesystem with ordered data mode. 
Opts: (null)
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:0001]
  InstallationDate: Installed on 2014-01-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140111)
  MachineType: TOSHIBA Qosmio G40
  Package: xorg-server (not installed)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic 
root=UUID=1272fb21-2bc2-487e-9489-3694635a469c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-1.16

Re: [Desktop-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager

2014-03-31 Thread Turbo

Hi,

I can confirm that comenting the line as he said, works as it should.

Just don't get it; if the solution is so easy, WHY this bug is alive
several years late.

Regards.

> Date: Sat, 29 Mar 2014 23:52:12 +
> From: 1201...@bugs.launchpad.net
> To: axe...@hotmail.com
> Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring 
> the presence of another session manager
> 
> In which case this bug is a duplicate of the long standing #1243399 and
> #268734
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1124149).
> https://bugs.launchpad.net/bugs/1201180
> 
> Title:
>   Pressing power button turns off the PC ignoring the presence of
>   another session manager
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+subscriptions

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

Title:
  Pressing power button turns off the PC ignoring the presence of
  another session manager

Status in “acpid” package in Ubuntu:
  Triaged
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling "poweroff", but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

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

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

[Desktop-packages] [Bug 1230091] Re: [enhancement] Trusted Session surface management (required for appstore app trust model), modal subwindows

2014-03-31 Thread Daniel van Vugt

** Changed in: mir
 Assignee: rosa maria (ceryscloe) => (unassigned)

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: rosa maria (ceryscloe) => (unassigned)

** Changed in: signon (Ubuntu Trusty)
 Assignee: rosa maria (ceryscloe) => (unassigned)

** Changed in: unity-mir (Ubuntu Saucy)
 Assignee: rosa maria (ceryscloe) => (unassigned)

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

Title:
  [enhancement] Trusted Session surface management (required for
  appstore app trust model), modal subwindows

Status in Content sharing/picking infrastructure and service:
  New
Status in Mir:
  Triaged
Status in Unity Mir:
  Triaged
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed
Status in “signon” package in Ubuntu:
  Confirmed
Status in “unity-mir” package in Ubuntu:
  Confirmed
Status in “signon” source package in Saucy:
  Won't Fix
Status in “unity-mir” source package in Saucy:
  Won't Fix
Status in “signon” source package in Trusty:
  Confirmed
Status in “unity-mir” source package in Trusty:
  Confirmed

Bug description:
  (I'm filing this as a bug in order to be able to point other people to
  it, and to track its progress; if there's a blueprint containing this
  task, please let me know)

  Some components (such as the Online Accounts trusted helper) need to
  be able to pop-up a window (typically, a dialog) on top of the running
  application. Such windows should be modal to the application, that is
  the user should not be able to interact with the application while the
  modal window is displayed on top of them. This also means that in the
  task switcher one shouldn't see two windows, but only the topmost
  modal window (and parts of the application window, in case the modal
  window on top is a non-fullscreen dialog).

  For developers, this API already exists in Qt: see 
https://qt-project.org/doc/qt-5.1/qtgui/qwindow.html#fromWinId
  It needs to be implemented in the QPA plugin, so feel free to add the 
relevant projects to the bug report.

  From jdstrand>
  This is a hard requirement for application confinement because of our trust 
model-- permission to access sensitive data by AppStore apps is typically 
granted or denied at the time of access (caching the result for later use as 
appropriate), so users have a context for the access being requested. We do 
this instead of throwing up a permissions prompt at installation. However, for 
it to work, trusted helpers like online accounts and location require this 
functionality from unity-mir. A trust-store is also being implemented so other 
services like calendar and contacts can do the same. Because this feature is 
not implemented, the implementation for online accounts, location and the 
trust-store is blocked and appstore apps are therefore able to access these 
services without the user knowing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/content-hub/+bug/1230091/+subscriptions

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

[Desktop-packages] [Bug 1227034] Re: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales

2014-03-31 Thread Kuangting Liu

This bug is NOT fixed! Here are my outputs of fc-match:

$ LANG=zh_CN.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
$ LANG=zh_HK.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
$ LANG=zh_TW.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"

And there is binding="strong" in my 69-language-selector-zh-cn.conf but
my screen Chinese font is still UKai.

I started with 14.04 Beta 2 when it came out and have been doing updates
everyday.

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

Title:
  Default Chinese font changed to fonts-arphic-ukai after completing
  language support installation for zh-* locales

Status in Ubuntu Kylin:
  Triaged
Status in “language-selector” package in Ubuntu:
  Fix Released

Bug description:
  After completing language support installation, fonts-arphic-ukai and
  fonts-arphic-uming are pulled into user's system and then fontconfig
  chooses Ukai over Droid Sans Fallback for the default sans-serif font.
  This is not the desired behavior as Ukai doesn't fit well into the
  category of screen fonts comparing to Droid Sans.

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

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

[Desktop-packages] [Bug 1288428] Re: unity-control-center crashed with signal 5 in g_object_new_valist() when clicking on Bluetooth with no bluez service running

2014-03-31 Thread Narcarsiss

Reboot is pending for updates that were pushed after the 14.xx beta that
is going on atm, this could be linked to that.

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

Title:
  unity-control-center crashed with signal 5 in g_object_new_valist()
  when clicking on Bluetooth with no bluez service running

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

Bug description:
  I have removed long ago bluetooth daemon fron upstart and from init.d
  - and only now I tried to click on Bluetooth in unity-control-center
  and it crashed.

  It is 100% reproducible.

  Better to hide the Bluetooth icon if no daemon is running, I think.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140305.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  5 23:40:11 2014
  ExecutablePath: /usr/bin/unity-control-center
  ProcCmdline: unity-control-center --overview
  Signal: 5
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libbluetooth.so
  Title: unity-control-center crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: Upgraded to trusty on 2013-12-20 (75 days ago)
  UserGroups: adm audio cdrom dip fuse libvirtd lpadmin netdev plugdev 
sambashare sudo
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   gnome-control-center   1:3.6.3-0ubuntu53
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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

[Desktop-packages] [Bug 1295439] Re: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

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

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

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

Title:
  nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

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

Bug description:
  I exported my VPN config from my other computer, and then attempted to
  import that config on this system. It crashed both times I tried.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 17:06:26 2014
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.19  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x252feb0: add%eax,(%rax)
   PC (0x0252feb0) in non-executable VMA region: 0x02386000-0x02866000 rw-p 
[heap]
   source "%eax" ok
   destination "(%rax)" (0x0252feb0) ok
  SegvReason: executing writable VMA [heap]
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 15ce4c2ae-2998-4497-b391-474472c20c59   
802-3-ethernet1395348855   Thu 20 Mar 2014 01:54:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   It Hurts When IP  9fc09318-c09f-43b4-97ea-6b7eb4e8100a   
802-11-wireless   1395360255   Thu 20 Mar 2014 05:04:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1295439] Re: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

2014-03-31 Thread Faris Chebib

Can confirm that importing an .ovpn which works on 13.10 just crashed my
window.

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

Title:
  nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

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

Bug description:
  I exported my VPN config from my other computer, and then attempted to
  import that config on this system. It crashed both times I tried.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 17:06:26 2014
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.19  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x252feb0: add%eax,(%rax)
   PC (0x0252feb0) in non-executable VMA region: 0x02386000-0x02866000 rw-p 
[heap]
   source "%eax" ok
   destination "(%rax)" (0x0252feb0) ok
  SegvReason: executing writable VMA [heap]
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 15ce4c2ae-2998-4497-b391-474472c20c59   
802-3-ethernet1395348855   Thu 20 Mar 2014 01:54:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   It Hurts When IP  9fc09318-c09f-43b4-97ea-6b7eb4e8100a   
802-11-wireless   1395360255   Thu 20 Mar 2014 05:04:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent

2014-03-31 Thread Lem

Just did some testing (with two gEdit windows) this morning, Ubuntu
14.04 updated to the latest packages as of today (2014-04-01). I apt-get
installed ubuntu-gnome-desktop and kubuntu-desktop on a regular Ubuntu
14.04 install.

GNOME desktop (gnome-shell): Both gEdit windows can be scrolled with the 
pointer hovering over the window, regardless of focus.
GNOME desktop classic (I guess still gnome shell?): Same as GNOME desktop, 
scrolling works while hovering, regardless of focus.
KDE plasma desktop: gEdit window needs to be focused to be scrolled
Ubuntu Unity desktop: gEdit window needs to be focused to be scrolled

And on Ubuntu 14.04 (around beta 1 packages) on a netbook with a
touchpad and mouse connected: Nautilus windows can be scrolled with the
touchpad while hovering, regardless of focus, but NOT with the mouse.

So, what makes the gnome-shell desktop different to Unity and KDE? The X
server, GTK etc are all the same.

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

Title:
  Scrolling behaviour and window focus has changed and is inconsistent

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

Bug description:
  I wasn't sure which package to file this bug against, but seeing as
  it's a general desktop usability/consistency bug, the top level
  desktop environment seemed like a good target.

  On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc),
  except for installing nvidia-319-updates, all current packages as of
  now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have
  this behaviour which is different from Ubuntu versions up to 13.04,
  and, is also inconsistent within itself. Here's what I've found:

  The scrolling behaviour has changed, and seems to be different per
  application in Ubuntu 13.10.

  The old behaviour (up to 13.04): mouse pointer above window would allow 
scrolling, regardless of focus
  Apps that use the old behaviour: libreoffice, firefox, gnome-terminal

  The new behaviour (13.10): window must be focused, and pointer hovered above 
to allow scrolling
  Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater

  
  STEPS TO REPRODUCE

  1. Open gEdit, press enter until the window is scrollable.
  2. Open Firefox, go to a webpage that's scrollable.
  3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar 
is still visible, have gEdit focused.
  4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit 
window to scroll.
  5. Move mouse pointer above Firefox but do not focus Firefox, observe 
scrollwheel causes Firefox window to scroll.
  6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes 
Firefox window to scroll
  7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel 
FAILS to cause gEdit window to scroll.

  
  This behaviour is the same with any combination of the above apps 
(libreoffice, firefox, gnome-terminal all scrollable as long as pointer is 
above them; nautilus, gedit, software-updater, ubunut-bug will not scroll 
unless focused *and* have pointer above them)

  What *SHOULD* happen, is that any window will scroll as long as the
  pointer is above it. That's how it's always been in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Oct 17 22:12:18 2013
  InstallationDate: Installed on 2013-09-30 (17 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-03-31 Thread Michael Neuffer

On 31.03.2014 18:48, Raj B wrote:
> to clarify, switching off the projector is fine. turning off the
> receiver causes the issue. In all cases, nothing is done to the computer
> itself. It is on and fully operational at all times (i.e., it is never
> suspended / shut down etc.).

What happens when you connect the projector directly to your PC?

I sometimes have a similar issue with a Samsung TV, a Denon 4308
Receiver and a Raspberry Pi. The problem here is the receiver in the middle.

Cheers
  Mike

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

Title:
  DPMS support broken, fails to wake up the monitor after putting it to
  sleep

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

Bug description:
  Also affects nvidia-graphics-drivers-319

  The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
  but with Nvidia instead of AMD/ATI drivers.

  HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
  display

  Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
  Only a restart of the Xserver will bring back the display at that point.

  A cycle of
  xset dpms force off; sleep 30; xset dpms force on
  will leave the display dark.

  At the moment I help myself by not allowing DPMS to switch off the display:
  neuffer@charion:~$ xset dpms 0 0 0

  neuffer@charion:~$ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1300514] Re: Account with UID 501 disappeared after update

2014-03-31 Thread Robert Ancell

Re-assigning to accountsservice as this is the service that lightdm
queries as to which users to show. Correct, we did change lightdm to
honour the SystemAccount flag which is what has caused this problem for
you.

** Package changed: lightdm (Ubuntu) => accountsservice (Ubuntu)

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

Title:
  Account with UID 501 disappeared after update

Status in “accountsservice” package in Ubuntu:
  New

Bug description:
  After today performing a system update from 13.10 [previously updated
  cca 1mo ago], my account with UID has disappeared from lightdm.

  /etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have
  all been configured to treat users with minimum UID 500 as regular
  users.

  The remark in users.conf mentioning AccountsService gave me a hint to
  explore what this service is.  It's very nasty that this completely
  opaque and unknown service determines whether an account will appear
  on the list or not.

  Digging around its process /usr/lib/accountsservice/accounts-daemon
  (what a nasty place to put this binary) using strace, I noticed
  /var/lib/AccountsService/users/myusername is being accessed. This may
  be obvious to developers, but to someone troubleshooting, it's bad and
  unexpected.

  I fixed my issue by editing the aforementioned file and replacing
  "SystemAccount=true" with "SystemAccount=false", killing the accounts-
  daemon and (to avoid restart) starting it in terminal. This would all
  be worth just a rant instead of a bug report, were it not for the fact
  that only today have I logged in correctly from the main screen,
  updated the system, and after only a reboot -- without touching or
  knowing about /var/lib/AccountsService/users directory -- my account
  has disappeared. Either this directory was automagically touched, or
  "SystemAccount=true" previously didn't affect lightdm.

  Please provide and expose a canonical and universal place to determine
  minimum UID for the system to treat a user account as a "human"
  account. Having three somewhat-documented files and none of them
  having effect upon accountsservice is quite bad.

  If this package is inappropriate for this bug report, please reassign.

  [The reason why UID 1000 is no-good are OS X partitions -- on which
  I'd like to be able to access my files without resorting to sudo
  voodoo. The default UID on OS X happens to be 501.]

  Package version: 0.6.34-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr  1 00:43:23 2014
  InstallationDate: Installed on 2014-02-18 (41 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1241595] Re: 10de:1056 [Dell Latitude E6520] System freezes when using nouveau driver with Nvidia NVS 4200M

Juanan, thank you for your comment. So your hardware and problem may be 
tracked, could you please file a new report by executing the following in a 
terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

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

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

Please note, not filing a new report will delay your problem being
addressed as quickly as possible.

Thank you for your understanding.

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

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

Title:
  10de:1056 [Dell Latitude E6520] System freezes when using nouveau
  driver with Nvidia NVS 4200M

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

Bug description:
  I enabled the Nouveau driver in my Ubuntu 13.10 and started using my laptop. 
After I used it for few minutes (3-4 minutes) the system froze. Only the mouse 
was working.
  After about 1 minute the mouse cursor stopped responding as well, leaving me 
with a 100% frozen laptop. I couldn't even switch to a console (Alt + F1) and 
reboot gracefully. I had to do an hard reboot. The problem arises every time I 
start my pc, I can only use it for few minutes. The mouse cursor is always the 
last to freeze.

  WORKAROUND: Enable the Nvidia proprietary drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  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: Fri Oct 18 15:24:52 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=10f4484c-5111-4b16-b2c8-56adb9691331 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

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

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

[Desktop-packages] [Bug 1297861] Re: [Gigabyte U24] Screen Freezing

** Tags added: bios-outdated-306

** Tags added: needs-trusty-test

** Summary changed:

- [Gigabyte U24] Screen Freezing
+ [Gigabyte U24T] Screen Freezing

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [Gigabyte U24T] Screen Freezing

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Screen Freezing. Turning down the volume seems to have at least
  decreased the frequency. I'm using nvidia-prime, and so had to update
  the kernel. Hope that's not the issue - cheers, Tamsyn.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  Uname: Linux 3.12.0-031200rc7-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.49  Wed Feb 12 20:42:50 
PST 2014
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 27 00:10:34 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 331.49, 3.12.0-031200rc7-generic, x86_64: installed
   virtualbox, 4.2.16, 3.12.0-031200rc7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:2452]
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:2452]
  InstallationDate: Installed on 2014-03-22 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: GIGABYTE U24
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-031200rc7-generic 
root=UUID=7e0cb542-9665-44b8-b0f8-f40082e976ed ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U24.301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U24
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU24.301:bd08/16/2013:svnGIGABYTE:pnU24:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnU24:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U24
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.911+git20140319.582adf06-0ubuntu0sarvatt~saucy
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt~saucy
  xserver.bootTime: Wed Mar 26 23:49:49 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load module "glamoregl" (module does not exist, 0)
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

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

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

[Desktop-packages] [Bug 1295439] Re: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

2014-03-31 Thread Felipe van Schaik Willig

I changed the status from Invalid to New because this issue is not
invalid. Forgive me if I overstepped boundaries, but less than a month
away from the release, this issue will make the new version unusable for
me (and I bet for a lot of people as well).

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

Title:
  nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  I exported my VPN config from my other computer, and then attempted to
  import that config on this system. It crashed both times I tried.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 17:06:26 2014
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.19  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x252feb0: add%eax,(%rax)
   PC (0x0252feb0) in non-executable VMA region: 0x02386000-0x02866000 rw-p 
[heap]
   source "%eax" ok
   destination "(%rax)" (0x0252feb0) ok
  SegvReason: executing writable VMA [heap]
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 15ce4c2ae-2998-4497-b391-474472c20c59   
802-3-ethernet1395348855   Thu 20 Mar 2014 01:54:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   It Hurts When IP  9fc09318-c09f-43b4-97ea-6b7eb4e8100a   
802-11-wireless   1395360255   Thu 20 Mar 2014 05:04:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1295439] Re: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

2014-03-31 Thread Felipe van Schaik Willig

Same error when importing my company's .ovpn saved config file. Before the 
import I dist-upgraded.
Why is this marked as invalid?

** Changed in: network-manager-applet (Ubuntu)
   Status: Invalid => New

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

Title:
  nm-connection-editor crashed with SIGSEGV in g_closure_invoke()

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  I exported my VPN config from my other computer, and then attempted to
  import that config on this system. It crashed both times I tried.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 20 17:06:26 2014
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.19  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x252feb0: add%eax,(%rax)
   PC (0x0252feb0) in non-executable VMA region: 0x02386000-0x02866000 rw-p 
[heap]
   source "%eax" ok
   destination "(%rax)" (0x0252feb0) ok
  SegvReason: executing writable VMA [heap]
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-connection-editor crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 15ce4c2ae-2998-4497-b391-474472c20c59   
802-3-ethernet1395348855   Thu 20 Mar 2014 01:54:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   It Hurts When IP  9fc09318-c09f-43b4-97ea-6b7eb4e8100a   
802-11-wireless   1395360255   Thu 20 Mar 2014 05:04:15 PM PDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1300514] Re: Account with UID 501 disappeared after update

2014-03-31 Thread Ivan Vučica

"Package Version" in the above comment refers to accountsservice
version, not lightdm. I tried to change the package I'm reporting about
in the online form.

Frankly, I'm not sure whether lightdm, accountsservice or some third
package is an appropriate target.

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

Title:
  Account with UID 501 disappeared after update

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  After today performing a system update from 13.10 [previously updated
  cca 1mo ago], my account with UID has disappeared from lightdm.

  /etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have
  all been configured to treat users with minimum UID 500 as regular
  users.

  The remark in users.conf mentioning AccountsService gave me a hint to
  explore what this service is.  It's very nasty that this completely
  opaque and unknown service determines whether an account will appear
  on the list or not.

  Digging around its process /usr/lib/accountsservice/accounts-daemon
  (what a nasty place to put this binary) using strace, I noticed
  /var/lib/AccountsService/users/myusername is being accessed. This may
  be obvious to developers, but to someone troubleshooting, it's bad and
  unexpected.

  I fixed my issue by editing the aforementioned file and replacing
  "SystemAccount=true" with "SystemAccount=false", killing the accounts-
  daemon and (to avoid restart) starting it in terminal. This would all
  be worth just a rant instead of a bug report, were it not for the fact
  that only today have I logged in correctly from the main screen,
  updated the system, and after only a reboot -- without touching or
  knowing about /var/lib/AccountsService/users directory -- my account
  has disappeared. Either this directory was automagically touched, or
  "SystemAccount=true" previously didn't affect lightdm.

  Please provide and expose a canonical and universal place to determine
  minimum UID for the system to treat a user account as a "human"
  account. Having three somewhat-documented files and none of them
  having effect upon accountsservice is quite bad.

  If this package is inappropriate for this bug report, please reassign.

  [The reason why UID 1000 is no-good are OS X partitions -- on which
  I'd like to be able to access my files without resorting to sudo
  voodoo. The default UID on OS X happens to be 501.]

  Package version: 0.6.34-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr  1 00:43:23 2014
  InstallationDate: Installed on 2014-02-18 (41 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1300514] [NEW] Account with UID 501 disappeared after update

2014-03-31 Thread Ivan Vučica

Public bug reported:

After today performing a system update from 13.10 [previously updated
cca 1mo ago], my account with UID has disappeared from lightdm.

/etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have all
been configured to treat users with minimum UID 500 as regular users.

The remark in users.conf mentioning AccountsService gave me a hint to
explore what this service is.  It's very nasty that this completely
opaque and unknown service determines whether an account will appear on
the list or not.

Digging around its process /usr/lib/accountsservice/accounts-daemon
(what a nasty place to put this binary) using strace, I noticed
/var/lib/AccountsService/users/myusername is being accessed. This may be
obvious to developers, but to someone troubleshooting, it's bad and
unexpected.

I fixed my issue by editing the aforementioned file and replacing
"SystemAccount=true" with "SystemAccount=false", killing the accounts-
daemon and (to avoid restart) starting it in terminal. This would all be
worth just a rant instead of a bug report, were it not for the fact that
only today have I logged in correctly from the main screen, updated the
system, and after only a reboot -- without touching or knowing about
/var/lib/AccountsService/users directory -- my account has disappeared.
Either this directory was automagically touched, or "SystemAccount=true"
previously didn't affect lightdm.

Please provide and expose a canonical and universal place to determine
minimum UID for the system to treat a user account as a "human" account.
Having three somewhat-documented files and none of them having effect
upon accountsservice is quite bad.

If this package is inappropriate for this bug report, please reassign.

[The reason why UID 1000 is no-good are OS X partitions -- on which I'd
like to be able to access my files without resorting to sudo voodoo. The
default UID on OS X happens to be 501.]

Package version: 0.6.34-0ubuntu6

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lightdm 1.8.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Apr  1 00:43:23 2014
InstallationDate: Installed on 2014-02-18 (41 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug saucy

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

Title:
  Account with UID 501 disappeared after update

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  After today performing a system update from 13.10 [previously updated
  cca 1mo ago], my account with UID has disappeared from lightdm.

  /etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have
  all been configured to treat users with minimum UID 500 as regular
  users.

  The remark in users.conf mentioning AccountsService gave me a hint to
  explore what this service is.  It's very nasty that this completely
  opaque and unknown service determines whether an account will appear
  on the list or not.

  Digging around its process /usr/lib/accountsservice/accounts-daemon
  (what a nasty place to put this binary) using strace, I noticed
  /var/lib/AccountsService/users/myusername is being accessed. This may
  be obvious to developers, but to someone troubleshooting, it's bad and
  unexpected.

  I fixed my issue by editing the aforementioned file and replacing
  "SystemAccount=true" with "SystemAccount=false", killing the accounts-
  daemon and (to avoid restart) starting it in terminal. This would all
  be worth just a rant instead of a bug report, were it not for the fact
  that only today have I logged in correctly from the main screen,
  updated the system, and after only a reboot -- without touching or
  knowing about /var/lib/AccountsService/users directory -- my account
  has disappeared. Either this directory was automagically touched, or
  "SystemAccount=true" previously didn't affect lightdm.

  Please provide and expose a canonical and universal place to determine
  minimum UID for the system to treat a user account as a "human"
  account. Having three somewhat-documented files and none of them
  having effect upon accountsservice is quite bad.

  If this package is inappropriate for this bug report, please reassign.

  [The reason why UID 1000 is no-good are OS X partitions -- on which
  I'd like to be able to access my files without resorting to sudo
  voodoo. The default UID on OS X happens to be 501.]

  Package version: 0.6.34-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.5-0ubuntu1
  ProcVersionSignatur

[Desktop-packages] [Bug 1300506] [NEW] emacs24 while byte compiling will keep asking for a shared lib not existing in my system

2014-03-31 Thread Antonio19

Public bug reported:

I was running emacs24 on Precise 12.04 after an install from this ppa @
https://launchpad.net/~cassou/+archive/emacs

Install worked fine. Until recently when installing new programs
(SuperCollider) which were byte compiling for emacs24.

For some mysterious reason at that time emacs24 was trying to open a
shared library libgvc.so.6 which was never present in my system for a
good reason : It will be on the soon to be released Trusty 14.04. The
library is libgvc.so.6 which is part of a Graphviz package libgvc6. At
that time I had subscribed to the GraphvizDev ppa @
https://launchpad.net/~gviz-adm/+archive/graphviz-dev which later on
forbid me to intall the package python-pygraphviz . Then I decided to
remove this ppa and install Graphviz from the regular Precise 12.04
repository for packages graphviz libcdt4 libgraphviz-dev  libcgraph5
libgvc5. This later package libgvc5 contains the shared lib libgvc.so.5
. Here is the error message :

[...]
Install cmake-data for emacs24
install/cmake-data: Byte-compiling for emacs24
emacs24: error while loading shared libraries: libgvc.so.6: cannot open shared 
object file: No such file or directory
Install dictionaries-common for emacs24
install/dictionaries-common: Byte-compiling for emacsen flavour emacs24
emacs24: error while loading shared libraries: libgvc.so.6: cannot open shared 
object file: No such file or directory
ERROR: install script from dictionaries-common package failed
dpkg: error processing emacs24 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up emacs24-common-non-dfsg (24.3+1-1~ppa1~precise1) ...
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

I tried to remove alltogether Graphviz and cmake ... to no avail. Does
anyone know why emacs24 keeps asking for this particular shared lib ?

I tried to install the packages from Trusty 14.04 as well but didn't go
far as it's a chain of broken dependencies.

Whem removing emacs24 , the system re-install emacs23 and there is no
problem in byte compiling all the installed apps. Why was it working for
some days then suddenly asking for a non existent shared lib ? Can
anyone sheds light on this ?

Is there any workaround ?

At the moment I returned to emacs23.

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

** Description changed:

  I was running emacs24 on Precise 12.04 after an install from this ppa @
  https://launchpad.net/~cassou/+archive/emacs
  
  Install worked fine. Until recently when installing new programs
  (SuperCollider) which were byte compiling for emacs24.
  
  For some mysterious reason at that time emacs24 was trying to open a
  shared library libgvc.so.6 which was never present in my system for a
- good reason : It will be on the soon to be releases Trustty 14.04. The
+ good reason : It will be on the soon to be released Trustty 14.04. The
  library is libgvc.so.6 which is part of a Graphviz package libgvc6. At
  that time I had subscribed to the GraphvizDev ppa @
  https://launchpad.net/~gviz-adm/+archive/graphviz-dev which later on
  forbid me to intall the package python-pygraphviz . Then I decided to
  remove this ppa and install Graphviz from th regular Precise 12.04
  repository for packages graphviz libcdt4 libgraphviz-dev  libcgraph5
  libgvc5. This later package libgvc5 contains the shared lib libgvc.so.5
  . Here is the error message :
  
  [...]
  Install cmake-data for emacs24
  install/cmake-data: Byte-compiling for emacs24
  emacs24: error while loading shared libraries: libgvc.so.6: cannot open 
shared object file: No such file or directory
  Install dictionaries-common for emacs24
  install/dictionaries-common: Byte-compiling for emacsen flavour emacs24
  emacs24: error while loading shared libraries: libgvc.so.6: cannot open 
shared object file: No such file or directory
  ERROR: install script from dictionaries-common package failed
  dpkg: error processing emacs24 (--configure):
-  subprocess installed post-installation script returned error exit status 1
+  subprocess installed post-installation script returned error exit status 1
  Setting up emacs24-common-non-dfsg (24.3+1-1~ppa1~precise1) ...
  E: Sub-process /usr/bin/dpkg returned an error code (1)
- $ 
+ $
  
  I tried to remove alltogether Graphviz and cmake ... to no avail. Does
  anyone know why emacs24 keeps asking for this particular shared lib ?
  
  I tried to install the packages from Trusty 14.04 as well but didn't go
  far as it's a chain of broken dependencies.
  
  Whem removing emacs24 , the system re-install emacs23 and there is no
  problem in byte compiling all the installed apps. Why was it working for
  some days then suddenly asking for a non existent shared lib ? Can
  anyone sheds light on this ?
  
  Is there any workaround ?
  
  At the moment I returned to emacs23.

** Description changed:

  I was running emacs24 on Precise 12.04 after an install from this ppa @
  https://launchp

[Desktop-packages] [Bug 1298380] Re: Amarok wont play music files

2014-03-31 Thread Tom Fields

meant 14.04

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

Title:
  Amarok wont play music files

Status in “amarok” package in Ubuntu:
  Confirmed

Bug description:
  From today, Amarok will not play any music files.  It opens fine, but
  when I click play or double click a music track, nothing happens.  Ive
  restarted twice with no change in behavior.  System is up to date.

  Kubuntu 14.04
  Amarok 2:2.8.0-0ubuntu3

  Debug output from when I click Play:

   BEGIN: void EngineController::playPause() 
  amarok:   [EngineController] PlayPause: EngineController state 0 
  amarok:   BEGIN: void EngineController::play() 
  amarok: BEGIN: void Playlist::Actions::play() 
  amarok:   BEGIN: void Playlist::Actions::play(quint64, bool) 
  amarok: BEGIN: void EngineController::play(Meta::TrackPtr, uint, 
bool) 
  amarok:   BEGIN: void EngineController::stop(bool, bool) 
  amarok:   END__: void EngineController::stop(bool, bool) [Took: 0s] 
  amarok:   [EngineController] play: bounded is  QObject(0x0)  current 
"Come On" 
  amarok:   [EngineController] Just a normal, boring track... :-P 
  amarok:   BEGIN: void EngineController::playUrl(const KUrl&, uint, 
bool) 
  amarok: [EngineController] URL:  
KUrl("file:///home/zachleigh/Music/V/Verve, The/The Verve - Urban Hymns/14 - 
Come On.flac") 
"file:///home/zachleigh/Music/V/Verve,%20The/The%20Verve%20-%20Urban%20Hymns/14%20-%20Come%20On.flac"
 
  amarok: [EngineController] Offset:  0 
  amarok:   END__: void EngineController::playUrl(const KUrl&, uint, 
bool) [Took: 0s] 
  amarok: END__: void EngineController::play(Meta::TrackPtr, uint, 
bool) [Took: 0s] 
  amarok:   END__: void Playlist::Actions::play(quint64, bool) [Took: 0s] 
  amarok: END__: void Playlist::Actions::play() [Took: 0s] 
  amarok:   END__: void EngineController::play() [Took: 0s] 
  amarok: END__: void EngineController::playPause() [Took: 0s]

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

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

[Desktop-packages] [Bug 1298380] Re: Amarok wont play music files

2014-03-31 Thread Tom Fields

Hi,

situation here with Kubuntu 10.04 Beta 2:
Amarok does not even start with phonon-backend-gstreamer (v. 0.1).

I can confirm that after purging phonon-backend-gstreamer and phonon-
backend-gstreamer-common and installing phonon-backend-gstreamer1.0, as
suggested by Leo Iannacone, Amarok now starts and works fine again.

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

Title:
  Amarok wont play music files

Status in “amarok” package in Ubuntu:
  Confirmed

Bug description:
  From today, Amarok will not play any music files.  It opens fine, but
  when I click play or double click a music track, nothing happens.  Ive
  restarted twice with no change in behavior.  System is up to date.

  Kubuntu 14.04
  Amarok 2:2.8.0-0ubuntu3

  Debug output from when I click Play:

   BEGIN: void EngineController::playPause() 
  amarok:   [EngineController] PlayPause: EngineController state 0 
  amarok:   BEGIN: void EngineController::play() 
  amarok: BEGIN: void Playlist::Actions::play() 
  amarok:   BEGIN: void Playlist::Actions::play(quint64, bool) 
  amarok: BEGIN: void EngineController::play(Meta::TrackPtr, uint, 
bool) 
  amarok:   BEGIN: void EngineController::stop(bool, bool) 
  amarok:   END__: void EngineController::stop(bool, bool) [Took: 0s] 
  amarok:   [EngineController] play: bounded is  QObject(0x0)  current 
"Come On" 
  amarok:   [EngineController] Just a normal, boring track... :-P 
  amarok:   BEGIN: void EngineController::playUrl(const KUrl&, uint, 
bool) 
  amarok: [EngineController] URL:  
KUrl("file:///home/zachleigh/Music/V/Verve, The/The Verve - Urban Hymns/14 - 
Come On.flac") 
"file:///home/zachleigh/Music/V/Verve,%20The/The%20Verve%20-%20Urban%20Hymns/14%20-%20Come%20On.flac"
 
  amarok: [EngineController] Offset:  0 
  amarok:   END__: void EngineController::playUrl(const KUrl&, uint, 
bool) [Took: 0s] 
  amarok: END__: void EngineController::play(Meta::TrackPtr, uint, 
bool) [Took: 0s] 
  amarok:   END__: void Playlist::Actions::play(quint64, bool) [Took: 0s] 
  amarok: END__: void Playlist::Actions::play() [Took: 0s] 
  amarok:   END__: void EngineController::play() [Took: 0s] 
  amarok: END__: void EngineController::playPause() [Took: 0s]

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

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

[Desktop-packages] [Bug 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)

2014-03-31 Thread Never Follow

Confirming that the bug still exists in Lubuntu 13.10, as far as the nm-
signal*secure.svg files are concerned for the default Lubuntu theme.

Workaround as above (#18); note that the default theme seems/is
'Lubuntu', so use that theme as basis:

sudo cp -a lubuntu 
cd 
sudo vi index.theme
sudo cp ../Humanity-Dark/status/22/nm-device-wired-secure.svg panel/22/

Lastly, choose the modified theme in Preferences -> Customize Look and
Feel.

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

Title:
  Network Manager Icon Is not changin when VPN is connected (nm-device-
  wired-secure icon is missing)

Status in “elementary-icon-theme” package in Ubuntu:
  Confirmed
Status in “gnome-icon-theme” package in Ubuntu:
  Confirmed
Status in “lubuntu-artwork” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” package in Ubuntu:
  Invalid
Status in “tango-icon-theme” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-icon-theme

  Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works 
fine) is see bad icons when connecting VPN and VPN is connected.
  Connected VPN icon is the same as original Network Manager. And connectin 
icon doen't show the Network manager icon only the flashing yellow lock (that 
must be over network manger icon)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-icon-theme 2.31.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr 29 01:05:10 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-icon-theme
  UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elementary-icon-theme/+bug/772709/+subscriptions

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

[Desktop-packages] [Bug 1300499] [NEW] Asus x102ba running Xubuntu 13:10 stuck at maximum brightness

2014-03-31 Thread B_a_C

Public bug reported:

I have a fresh install of Xubuntu 13:10 running very nicely on an Asus
x102ba.  Everything works OOTB except the brightness.  Function buttons
do not adjust it, and although inserting the switch
acpi_backlight=vendor into grub allows the laptop to see the backlight
settings, I still cannot adjust them -- manually or otherwise.

Let me know what other information you need, so we can resolve this bug!

^_^

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

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

Title:
  Asus x102ba running Xubuntu 13:10 stuck at maximum brightness

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

Bug description:
  I have a fresh install of Xubuntu 13:10 running very nicely on an Asus
  x102ba.  Everything works OOTB except the brightness.  Function
  buttons do not adjust it, and although inserting the switch
  acpi_backlight=vendor into grub allows the laptop to see the backlight
  settings, I still cannot adjust them -- manually or otherwise.

  Let me know what other information you need, so we can resolve this
  bug!

  ^_^

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

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

[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

to clarify, switching off the projector is fine. turning off the
receiver causes the issue. In all cases, nothing is done to the computer
itself. It is on and fully operational at all times (i.e., it is never
suspended / shut down etc.).

Raj

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

Title:
  DPMS support broken, fails to wake up the monitor after putting it to
  sleep

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

Bug description:
  Also affects nvidia-graphics-drivers-319

  The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
  but with Nvidia instead of AMD/ATI drivers.

  HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
  display

  Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
  Only a restart of the Xserver will bring back the display at that point.

  A cycle of
  xset dpms force off; sleep 30; xset dpms force on
  will leave the display dark.

  At the moment I help myself by not allowing DPMS to switch off the display:
  neuffer@charion:~$ xset dpms 0 0 0

  neuffer@charion:~$ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted

2014-03-31 Thread Behrouz Rahimzadeh

This warning disapeared  after I removed  "dnsmasq 2.59-4ubuntu0.1 ".

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

Title:
  NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump
  inconsistency detected, interrupted

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

Bug description:
  I see the following messages in /var/log/syslog:
NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump inconsistency 
detected, interrupted

  When it goes down, I have to bounce network-manager to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb  7 08:59:00 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-01-26 (12 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static 
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.11  metric 9 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca   
802-11-wireless   1360249035   Thu 07 Feb 2013 08:57:15 AM CSTyes   
no /org/freedesktop/NetworkManager/Settings/2
   Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12   
802-11-wireless   1359750784   Fri 01 Feb 2013 02:33:04 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/1
   MIA-WiFi  ea25a58d-9cb8-48a8-843a-2dc3231a1e17   
802-11-wireless   1359754973   Fri 01 Feb 2013 03:42:53 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.7.995  connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1300479] Re: "crashes when past as unformatted text is pasted over the data range just copied (replacing formulas with values)" soffice.bin crashed with SIGSEGV in ScFormulaCel

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

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 #1286536, 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/1300479/+attachment/4056654/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056656/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056658/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056659/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056660/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056661/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300479/+attachment/4056662/+files/ThreadStacktrace.txt

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

** 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1300479

Title:
  "crashes when past as unformatted text is pasted over the data range
  just copied (replacing formulas with values)" soffice.bin crashed with
  SIGSEGV in ScFormulaCell::GetCellGroup()

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Copied a range of calculated values (formulas). Then did paste
  unformatted text to replace the formulas with the actual values (for
  safer sorting).  Crashes even if I paste and the copy in a text editor
  between the copy and paste steps in Calc. Seems to happen every time

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.3~rc2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 31 15:03:39 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-12-18 (103 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f37216d58d0 <_ZN13ScFormulaCell12GetCellGroupEv>:   
mov0x38(%rsi),%rdx
   PC (0x7f37216d58d0) ok
   source "0x38(%rsi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ScFormulaCell::GetCellGroup() () from 
/usr/lib/libreoffice/program/../program/libsclo.so
   ?? () from /usr/lib/libreoffice/program/../program/libsclo.so
   ScDocumentImport::initColumn(ScColumn&) () from 
/usr/lib/libreoffice/program/../program/libsclo.so
   ScDocumentImport::finalize() () from 
/usr/lib/libreoffice/program/../program/libsclo.so
   ?? () from /usr/lib/libreoffice/program/../program/libsclo.so
  Title: soffice.bin crashed with SIGSEGV in ScFormulaCell::GetCellGroup()
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1296947] Re: libudev dependency not expressed by libgl1-mesa-glx binary package

** Branch linked: lp:debian/mesa

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

Title:
  libudev dependency not expressed by libgl1-mesa-glx binary package

Status in “mesa” package in Ubuntu:
  In Progress

Bug description:
  Mesa 10.1 has a hard dependency on libudev.so.1, which isn't
  necessarily being installed as it's not marked as a dependency of
  libgl1-mesa-glx. This is a problem for Steam games running on Intel
  graphics on amd64 hosts, as libudev:i386 isn't typically installed by
  default on these.

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

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

[Desktop-packages] [Bug 1296786] Re: Use of Uninitialized variable, when loading certain png files.

** Branch linked: lp:debian/libgdiplus

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

Title:
  Use of Uninitialized variable, when loading certain png files.

Status in “libgdiplus” package in Ubuntu:
  New

Bug description:
  Png details that causes this crash:

  Find Dictionary.png...
Image Width: 16 Image Length: 16
Bitdepth (Bits/Sample): 8
Channels (Samples/Pixel): 1
Pixel depth (Pixel Depth): 8
Colour Type (Photometric Interpretation): PALETTED COLOUR with alpha (256 
colours, 1 transparent) 
Image filter: Single row per byte filter 
Interlacing: No interlacing 
Compression Scheme: Deflate method 8, 32k window
Resolution: 2834, 2834 (pixels per meter)
FillOrder: msb-to-lsb
Byte Order: Network (Big Endian)
Number of text strings: 0 of 0

  Problem code is:

  File: pngcode.c 
  Function: gdip_load_png_image_from_file_or_stream
  Problem: use of a call to png_get_tRNS without checking return value.
  For this png return value is 0 (fail), and this causes use of a uninitialized 
variables  trans_color and num_trans.
  This causes seg fault if trans_color or num_trans. happen to be certian 
values.

  I will a minimal test case that can be build using mono.

  I will also attach a suggested patch, that checks return value of
  png_get_tRNS, and doesn't attempt to use unitilized variables.

  StackTrace looks like this:

   at  <0x>
at (wrapper managed-to-native) 
System.Drawing.GDIPlus.GdipLoadImageFromDelegate_linux 
(System.Drawing.GDIPlus/StreamGetHeaderDelegate,System.Drawing.GDIPlus/StreamGetBytesDelegate,System.Drawing.GDIPlus/StreamPutBytesDelegate,System.Drawing.GDIPlus/StreamSeekDelegate,System.Drawing.GDIPlus/StreamCloseDelegate,System.Drawing.GDIPlus/StreamSizeDelegate,intptr&)
 <0x>
at System.Drawing.Image.InitFromStream (System.IO.Stream) <0x001b3>
at System.Drawing.Image..ctor 
(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)
 <0x0010f>
at System.Drawing.Bitmap..ctor 
(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)
 <0x0002f>
at (wrapper runtime-invoke) 
.runtime_invoke_void__this___object_StreamingContext 
(object,intptr,intptr,intptr) <0x>
at  <0x>
at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke 
(System.Reflection.MonoCMethod,object,object[],System.Exception&) <0x>
at System.Reflection.MonoCMethod.InternalInvoke (object,object[]) <0x0003f>
at System.Reflection.MonoCMethod.DoInvoke 
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
 <0x00103>
at System.Reflection.MonoCMethod.Invoke 
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
 <0x00083>
at System.Reflection.MethodBase.Invoke (object,object[]) <0x00032>
at System.Runtime.Serialization.ObjectRecord.LoadData 
(System.Runtime.Serialization.ObjectManager,System.Runtime.Serialization.ISurrogateSelector,System.Runtime.Serialization.StreamingContext)
 <0x002ff>
at System.Runtime.Serialization.ObjectManager.DoFixups () <0x0015f>
at 
System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadNextObject 
(System.IO.BinaryReader) <0x00051>
at 
System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObjectGraph 
(System.Runtime.Serialization.Formatters.Binary.BinaryElement,System.IO.BinaryReader,bool,object&,System.Runtime.Remoting.Messaging.Header[]&)
 <0x0010b>
at 
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.NoCheckDeserialize
 (System.IO.Stream,System.Runtime.Remoting.Messaging.HeaderHandler) <0x00143>
at 
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize 
(System.IO.Stream) <0x0001f>
at System.Resources.ResourceReader.ReadNonPredefinedValue (System.Type) 
<0x0003f>
at System.Resources.ResourceReader.ReadValueVer2 (int) <0x00443>
at System.Resources.ResourceReader.LoadResourceValues 
(System.Resources.ResourceReader/ResourceCacheItem[]) <0x0021f>
at System.Resources.ResourceReader/ResourceEnumerator.FillCache () <0x0009b>
at System.Resources.ResourceReader/ResourceEnumerator..ctor 
(System.Resources.ResourceReader) <0x00053>
at System.Resources.ResourceReader.GetEnumerator () <0x00033>
at System.Resources.ResourceSet.ReadResources () <0x0008d>
at System.Resources.ResourceSet.GetObjectInternal (string,bool) <0x0006b>
at System.Resources.ResourceSet.GetObject (string,bool) <0x00027>
at System.Resources.RuntimeResourceSet.GetObject (string,bool) <0x00033>
at System.Resources.ResourceManager.GetObject 
(string,System.Globalization.CultureInfo) <0x000a1>
at PngTest.MainClass.Main (string[]) <0x0007c>
at (wrapper runtime-invoke) .runt

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

2014-03-31 Thread Pausanias

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

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

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Invalid
Status in Unity Greeter:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

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

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

[Desktop-packages] [Bug 1298380] Re: Amarok wont play music files

2014-03-31 Thread Harald Sitter

** Changed in: amarok (Ubuntu)
   Importance: Undecided => Critical

** Changed in: amarok (Ubuntu)
Milestone: None => ubuntu-14.04

** Changed in: amarok (Ubuntu)
 Assignee: (unassigned) => Jonathan Riddell (jr)

** Tags added: kubuntu

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

Title:
  Amarok wont play music files

Status in “amarok” package in Ubuntu:
  Confirmed

Bug description:
  From today, Amarok will not play any music files.  It opens fine, but
  when I click play or double click a music track, nothing happens.  Ive
  restarted twice with no change in behavior.  System is up to date.

  Kubuntu 14.04
  Amarok 2:2.8.0-0ubuntu3

  Debug output from when I click Play:

   BEGIN: void EngineController::playPause() 
  amarok:   [EngineController] PlayPause: EngineController state 0 
  amarok:   BEGIN: void EngineController::play() 
  amarok: BEGIN: void Playlist::Actions::play() 
  amarok:   BEGIN: void Playlist::Actions::play(quint64, bool) 
  amarok: BEGIN: void EngineController::play(Meta::TrackPtr, uint, 
bool) 
  amarok:   BEGIN: void EngineController::stop(bool, bool) 
  amarok:   END__: void EngineController::stop(bool, bool) [Took: 0s] 
  amarok:   [EngineController] play: bounded is  QObject(0x0)  current 
"Come On" 
  amarok:   [EngineController] Just a normal, boring track... :-P 
  amarok:   BEGIN: void EngineController::playUrl(const KUrl&, uint, 
bool) 
  amarok: [EngineController] URL:  
KUrl("file:///home/zachleigh/Music/V/Verve, The/The Verve - Urban Hymns/14 - 
Come On.flac") 
"file:///home/zachleigh/Music/V/Verve,%20The/The%20Verve%20-%20Urban%20Hymns/14%20-%20Come%20On.flac"
 
  amarok: [EngineController] Offset:  0 
  amarok:   END__: void EngineController::playUrl(const KUrl&, uint, 
bool) [Took: 0s] 
  amarok: END__: void EngineController::play(Meta::TrackPtr, uint, 
bool) [Took: 0s] 
  amarok:   END__: void Playlist::Actions::play(quint64, bool) [Took: 0s] 
  amarok: END__: void Playlist::Actions::play() [Took: 0s] 
  amarok:   END__: void EngineController::play() [Took: 0s] 
  amarok: END__: void EngineController::playPause() [Took: 0s]

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

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

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

2014-03-31 Thread Pausanias

Is there a workaround?

Better question: is there any hope of GNOME developers *not* breaking
critical functionality from release to release? After 12 years with
Ubuntu, I can come up with a huge list of extremely frustrating and
sometimes downright dangerous regressions, almost all of them in GNOME,
and almost all of them affecting a feature that was working perfectly
well in a previous release.

/rant

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

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Invalid
Status in Unity Greeter:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

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

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

[Desktop-packages] [Bug 1300283] Re: LibreOffice does not start in a KDE 4 session

2014-03-31 Thread Harald Sitter

** Tags added: kubuntu

** Changed in: libreoffice (Ubuntu)
Milestone: None => ubuntu-14.04

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

Title:
  LibreOffice does not start in a KDE 4 session

Status in “libreoffice” package in Ubuntu:
  Confirmed

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar 31 17:22:08 2014
  InstallationDate: Installed on 2014-03-18 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

Hi,

I was planning to start a new bug, but I believe my bug is similar to
this except that I have different symptoms.

I have a custom built media PC with a Nvidia GT 640 Rev 2 (GK208) video
card. The HDMI output is connected to an Onkyo 3010 receiver which is
then connected to a projector.

The issue I have is that everything works up to the point where I turn
off the projector (i.e., shut everything down). When that happens, I
cannot get back the display. Turning the projector on just shows a blank
screen which does not respond to any input. This is similar to the
suspend/resume and DKMS bugs already reported except that I do not
explicitly suspend or resume --- I just switch off the display (i.e.
receiver).

switching to a virtual console (Alt-F1) and then coming back shows a
garbled display where I can't see anything clearly, but at least now I
can see something. the only solution is to kill lightdm and restart the
X server.

I am using Trusty with XFCE. I have this bug with the trusty version of
the nvidia 331.38 driver and with the xorg-edgers version of 331.38 and
334.21.

The funny thing is that this used to work in Saucy. Everything was fine
with the xorg-edgers 331.38 driver (I could not use the default saucy
319 driver as it would detect my video card).

I've tried removing nvidia-prime, DKMS is disabled (the screen never
turns on if the projector is on), and neither works.

not sure what to do now. not even sure how to debug this. I was planning
to attach kprobes or something to the nvidia driver to see what signals
it is losing when the projector switches off. But I'm not sure how to
interpret that data. This is a fairly major bug as I can't turn off the
receiver anymore :-(

Thanks,

Raj

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

Title:
DPMS support broken, fails to wake up the monitor after putting it to
sleep

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

Bug description:
Also affects nvidia-graphics-drivers-319

The effect is identical to
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

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

[Desktop-packages] [Bug 1300471] [NEW] restart session button doesn't do that

2014-03-31 Thread Brian Murray

Public bug reported:

After installing samba to share a folder on my network I was notified
that I should restart my session and was presented with a restart
session button.  I clicked it and nothing happened.  This is using a
default Ubuntu 14.04 install.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: User Name 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 31 14:53:04 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2013-12-10 (110 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131210)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  restart session button doesn't do that

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  After installing samba to share a folder on my network I was notified
  that I should restart my session and was presented with a restart
  session button.  I clicked it and nothing happened.  This is using a
  default Ubuntu 14.04 install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: User Name 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 14:53:04 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-12-10 (110 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131210)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   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/1300471/+subscriptions

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

[Desktop-packages] [Bug 1300474] [NEW] tmp directory cleanup fails

2014-03-31 Thread Brian Murray

Public bug reported:

I was using ubuntu-bug -w to report a bug about a window and noticed the
following in my terminal.

bdmurray@clean-trusty-amd64:~$ ubuntu-bug -w
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python3.4/shutil.py", line 452, in rmtree
orig_st = os.lstat(path)
FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/launchpadlib.cache.lmofbkk8'

This seems to be an error with apport and the changes to how it manages
the launchpadlib cache.

** Affects: apport (Ubuntu)
 Importance: Undecided
 Assignee: Martin Pitt (pitti)
 Status: New

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

Title:
  tmp directory cleanup fails

Status in “apport” package in Ubuntu:
  New

Bug description:
  I was using ubuntu-bug -w to report a bug about a window and noticed
  the following in my terminal.

  bdmurray@clean-trusty-amd64:~$ ubuntu-bug -w
  Error in atexit._run_exitfuncs:
  Traceback (most recent call last):
File "/usr/lib/python3.4/shutil.py", line 452, in rmtree
  orig_st = os.lstat(path)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/launchpadlib.cache.lmofbkk8'

  This seems to be an error with apport and the changes to how it
  manages the launchpadlib cache.

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

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

[Desktop-packages] [Bug 1239186]

2014-03-31 Thread Robert Navarro

Where there any changes required for the posted patch?

Any indication on when it'll get pushed out so I can start running pre-
compiled kernels again?

I know how to compile my own now, thanks rubin110, but it's far more
convenient to not have to waste my time building a kernel.

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

Title:
  [Lenovo ThinkPad X220] External screens shut off randomly

Status in X.org xf86-video-intel:
  In Progress
Status in “xserver-xorg-video-intel” package in Ubuntu:
  In Progress

Bug description:
  I've been trying to figure out what's going on with my external
  display port screens with no luckbut I think I'm getting closer to
  the right direction.

  I upgraded to the latest 13.10 build and turned on DRM debugging with:

  # /etc/modprobe.d/drm.conf
  # We are turning on debug information here

  options drm debug=0xe

  In doing so my logs lit up with lots of graphics activity. However the
  two events that actually had some meaning in terms of a pain point
  where lines like this:

  Oct 12 11:22:02 rnavarro-thinkpad kernel: [  673.201706] 
[drm:ironlake_irq_handler], Pipe B FIFO underrun
  Oct 12 11:22:02 rnavarro-thinkpad kernel: [  673.201719] 
[drm:cpt_serr_int_handler], PCH transcoder B FIFO underrun

  and

  Oct 12 11:22:31 rnavarro-thinkpad kernel: [  702.411812]
  [drm:ironlake_irq_handler], Pipe A FIFO underrun

  I noticed that right before either one of my monitors would blank and
  shut off, this message would be emitted in my kern.log

  I think there was some stuff added upstream to detect this, as noted
  here:

  http://lists.freedesktop.org/archives/intel-gfx/2013-July/029882.html

  But i'm not sure what's causing it, much less how to fix it.

  What other information can I give that would help debug?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,regex,mousepoll,imgpng,vpswitch,grid,wall,gnomecompat,animation,compiztoolbox,move,place,snap,resize,unitymtgrabhandles,workarounds,fade,expo,session,scale,ezoom,unityshell]
  CompositorRunning: None
  Date: Sat Oct 12 11:45:47 2013
  DistUpgraded: 2013-10-12 10:47:24,030 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   i915-3.9-3.8, 0.02, 3.8.0-31-generic, x86_64: installed
   vboxhost, 4.2.18, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.2.18, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-06-30 (103 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: LENOVO 4286CTO
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg_rnavarro--leno-lv_root ro quiet splash i915.semaphores=0 
vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to saucy on 2013-10-12 (0 days ago)
  XorgConf:
   Section "Device"
   Identifier "intel"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Oct 12 11:20:57 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.erro

[Desktop-packages] [Bug 1300454] Re: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()

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

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 #1289125, 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/1300454/+attachment/4056552/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056554/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056555/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056556/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056557/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056558/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300454/+attachment/4056559/+files/ThreadStacktrace.txt

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

** 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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1300454

Title:
  totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()

Status in “gstreamer1.0” package in Ubuntu:
  New

Bug description:
  When browsing folders on my external (usb) drive that contain videos, totem 
seems to crash while generating a thumbnail.
  The only symptom is the crash reporter popping up.

  I am running a clean install of 14.04 beta 2 updated with the latest
  pagages this morning.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libgstreamer1.0-0 1.2.3-1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:21:28 2014
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2014-03-30 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///media/username/Seagate/backup_2014_03_30/Downloads/Arrow.S02E16.720p.HDTV.X264-DIMENSION.mkv
 /tmp/.gnome_desktop_thumbnail.I34LDX
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f00044c3297 :mov
(%rbx),%rax
   PC (0x7f00044c3297) ok
   source "(%rbx)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
  Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()
  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/gstreamer1.0/+bug/1300454/+subscriptions

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

[Desktop-packages] [Bug 1293177] Re: 'net usershare' returned error 255: net usershare add: cannot convert name "Everyone" to a SID. Access denied.

2014-03-31 Thread Brian Murray

** Changed in: nautilus-share (Ubuntu Trusty)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

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

Title:
  'net usershare' returned error 255: net usershare add: cannot convert
  name "Everyone" to a SID. Access denied.

Status in One Hundred Papercuts:
  Confirmed
Status in “nautilus-share” package in Ubuntu:
  Confirmed
Status in “samba” package in Ubuntu:
  Confirmed
Status in “nautilus-share” source package in Trusty:
  Confirmed
Status in “samba” source package in Trusty:
  Confirmed

Bug description:
  When using the "Local Network Share" tab in the folder properties
  window to try and share a folder, the result is an error message:

  'net usershare' returned error 255: net usershare add: cannot convert
  name "Everyone" to a SID. Access denied.

  pburt@magus:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  pburt@magus:~$ /etc/init.d/samba status
   * nmbd is running
   * smbd is running
  pburt@magus:~$ apt-cache policy nautilus-share
  nautilus-share:
Installed: 0.7.3-1ubuntu5
Candidate: 0.7.3-1ubuntu5
Version table:
   *** 0.7.3-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  pburt@magus:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus-share 0.7.3-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 16 12:21:59 2014
  InstallationDate: Installed on 2014-01-04 (70 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: nautilus-share
  UpgradeStatus: Upgraded to trusty on 2014-03-09 (7 days ago)

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

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

[Desktop-packages] [Bug 1300462] [NEW] Login timed out after waking from suspend

2014-03-31 Thread Christopher Barrington-Leigh

Public bug reported:

I'm using fprint package for finger-print authentication.

Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
But half the time when it recovers from suspend, the lightdm  (?) login screen  
instead says that authentication has timed out. For some reason I then have to 
wait a good 25 seconds  before I get another chance. At that point, I am able 
to enter a password or fingerprint as normal.

This "time out" should not be triggered during/after a suspend.
Also, if there is a time out for some reason, it should just wait the normal 2 
seconds required after entering an incorrect password.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.9.13-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 31 17:29:11 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-03-11 (20 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Login timed out after waking from suspend

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I'm using fprint package for finger-print authentication.

  Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
  But half the time when it recovers from suspend, the lightdm  (?) login 
screen  instead says that authentication has timed out. For some reason I then 
have to wait a good 25 seconds  before I get another chance. At that point, I 
am able to enter a password or fingerprint as normal.

  This "time out" should not be triggered during/after a suspend.
  Also, if there is a time out for some reason, it should just wait the normal 
2 seconds required after entering an incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:29:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage

2014-03-31 Thread Colin King

** Changed in: ubuntu-power-consumption
   Status: New => Fix Released

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

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in The Application Menu:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “indicator-appmenu” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+3.0” source package in Saucy:
  Fix Released
Status in “indicator-appmenu” source package in Saucy:
  Fix Released

Bug description:
  Impact: high CPU/memory usage from unity-panel-service

  Test case:

  Open a large image in the GIMP and activate a lot of items from the
  global menu. Using shortcuts is enough and faster to reproduce this
  bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
  panel-service increases steadily and it uses a lot of CPU shortly
  after activating the menu items in a short time.

  Regression potential: check that the menus are stable/working as they
  should

  -
  Just going about my business on Ubuntu Raring amd64 on an x230 and I heard 
the fan kick into action.  top showed me that unity-panel-service was consuming 
all the free cycles on one of my CPUs.  I killed it before my machine 
overheated, so I didn't attach a debugger to see why it was totally pegging out 
a  CPU.

  I'm not sure if this adds any context, but I was using a LibreOffice
  spreadsheet and I could not insert a table because the menu had lost
  it's mind, and then I observed the overly loaded CPU a very short
  while after that.

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

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

[Desktop-packages] [Bug 1234289] Re: accounts-daemon is progressively causing more wakeups over time

2014-03-31 Thread Colin King

** Changed in: ubuntu-power-consumption
   Status: New => Fix Released

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

Title:
  accounts-daemon is progressively causing more wakeups over time

Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in “accountsservice” package in Ubuntu:
  Fix Released

Bug description:
  Over the past few months accounts-daemon has been increasing the
  number of wakeup events it generates, see:

  http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task
  /accounts-daemon/details/

  In April 2013 it was averaging about 13.5 wakeups per minute, now it
  has increased to 17.5.  This isn't much overall, but it does seem like
  the trend is upwards and every wakeup takes the CPU out of deep sleep
  and hence consumes a little more power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1234289/+subscriptions

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

[Desktop-packages] [Bug 938324] Re: telepathy-haze crashed with SIGABRT in g_assertion_message()

** Tags added: trusty

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

Title:
  telepathy-haze crashed with SIGABRT in g_assertion_message()

Status in Telepathy Haze:
  Confirmed
Status in “telepathy-haze” package in Ubuntu:
  Triaged

Bug description:
  It crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: telepathy-haze 0.5.0-1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 21 19:13:34 2012
  ExecutablePath: /usr/lib/telepathy/telepathy-haze
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120205)
  ProcCmdline: /usr/lib/telepathy/telepathy-haze
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: telepathy-haze
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: telepathy-haze crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-02-20 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-haze/+bug/938324/+subscriptions

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

[Desktop-packages] [Bug 1300452] Re: telepathy-haze crashed with SIGABRT after adding an Gadu-Gadu contact

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

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 #938324, 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/1300452/+attachment/4056540/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056542/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056544/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056545/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056546/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056547/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300452/+attachment/4056548/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 938324
   telepathy-haze crashed with SIGABRT in g_assertion_message()

** 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 telepathy-haze in Ubuntu.
https://bugs.launchpad.net/bugs/1300452

Title:
  telepathy-haze crashed with SIGABRT after adding an Gadu-Gadu contact

Status in “telepathy-haze” package in Ubuntu:
  New

Bug description:
  After trying to add Gadu-Gadu contact telepathy-haze crashed.
  To reproduce this bug just try to add new GG contact by selecting Empathy -> 
Contacts -> Add Contact...

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: telepathy-haze 0.8.0-1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 23:08:10 2014
  ExecutablePath: /usr/lib/telepathy/telepathy-haze
  ProcCmdline: /usr/lib/telepathy/telepathy-haze
  Signal: 6
  SourcePackage: telepathy-haze
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
  Title: telepathy-haze crashed with SIGABRT in g_assertion_message()
  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/telepathy-haze/+bug/1300452/+subscriptions

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

[Desktop-packages] [Bug 1242914] Re: tlmgr unable to set up TLPDB

2014-03-31 Thread Yonatan Yehezkeally

@YihuiXie(xie) of course; I don't mean to imply the bug is any less
important to address because of this workaround. Just to point
@RobertBlankenship in the right direction (as he indicated he wishes).

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

Title:
  tlmgr unable to set up TLPDB

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

Bug description:
  When attempting to use tlmgr on Ubuntu 13.10, the program fails.
  Different options produce slightly different output:

  $ tlmgr --gui
  (running on Debian, switching to user mode!)
  Loading local TeX Live database;
  this may take some time, please be patient ...
  cannot setup TLPDB in /home/nskillen/texmf at /usr/bin/tlmgr line 5308.
  Compilation failed in require at /usr/bin/tlmgr line 4439.

  $ tlmgr update --all
  (running on Debian, switching to user mode!)
  cannot setup TLPDB in /home/nskillen/texmf at /usr/bin/tlmgr line 5308.

  The commands also fails when using sudo to run as root, with exactly
  the same output.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: texlive-base 2013.20130722-1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 14:16:50 2013
  InstallationDate: Installed on 2013-10-17 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: texlive-base
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1296866] Re: Allow unity-panel.menuitem to paint window title text for maximized window in new Unity Decorator(Trusty)

2014-03-31 Thread Treviño

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

** Changed in: unity
   Status: New => In Progress

** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes
   Status: New => In Progress

** Branch linked: lp:~3v1n0/ubuntu-themes/unity-panel-colors

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

Title:
  Allow unity-panel.menuitem to paint window title text for maximized
  window in new Unity Decorator(Trusty)

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Some themes (Greybird, Elementary) use dark-panel & light window
  title-bar (When it is not maximized). As new Unity window decorator
  uses same title-bar foreground color for both normal & maximized
  windows, window title on unity-panel is not properly visible as it
  becomes dark-text on dark-panel. I have attached a screenshot.

  This forces theme developer to use use same background color for both
  unity-panel & un-maximized windows, which breaks theme design. The
  idea is that theme-developers like to think unity-panel as a panel &
  not just a title-bar for maximized window.

  According to https://wiki.ubuntu.com/Unity/Theming, color set in
  UnityDecoration.top is used for both unmaximized & maximized window.

  UnityDecoration.top {
   color: @dark_fg_color
  }

  And when this is set, the color set in .unity-panel.menuitem is
  ignored for window title text in panel (it still paints some other
  text in panel like indicator-datetime)

  .unity-panel .menuitem {
  border-width: 0 1px;
  color: @panel_fg_color; # this does not affect window title text 
anymore. 
  }

  This color (OR unity.panel foreground color in UnityPanelWidget)
  should be used to paint the window tile text for maximized window, as
  it used to be in old compiz-decorator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1296866/+subscriptions

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

[Desktop-packages] [Bug 1242914] Re: tlmgr unable to set up TLPDB

2014-03-31 Thread Yihui Xie

@Yonatan Of course, installing a vanilla instance of TeXLive will work,
but that does not make much sense here for this bug report. Here we are
talking about the Ubuntu problem, and the bug was not from TeXLive.

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

Title:
  tlmgr unable to set up TLPDB

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

Bug description:
  When attempting to use tlmgr on Ubuntu 13.10, the program fails.
  Different options produce slightly different output:

  $ tlmgr --gui
  (running on Debian, switching to user mode!)
  Loading local TeX Live database;
  this may take some time, please be patient ...
  cannot setup TLPDB in /home/nskillen/texmf at /usr/bin/tlmgr line 5308.
  Compilation failed in require at /usr/bin/tlmgr line 4439.

  $ tlmgr update --all
  (running on Debian, switching to user mode!)
  cannot setup TLPDB in /home/nskillen/texmf at /usr/bin/tlmgr line 5308.

  The commands also fails when using sudo to run as root, with exactly
  the same output.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: texlive-base 2013.20130722-1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 14:16:50 2013
  InstallationDate: Installed on 2013-10-17 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: texlive-base
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1299705] Re: Ubuntu locks after unlocking

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

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

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

Title:
  Ubuntu locks after unlocking

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  Hi, on all of my 5 computers Ubuntu lock up without my will just few seconds 
after I unlock it.
  So I lock it -> then I unlock it by password, enter -> then I can do 
something in Ubuntu for few seconds -> then it locks without my will and I have 
to unlock it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 30 10:50:14 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 600
  InstallationDate: Installed on 2014-03-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317)
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 996008] Re: GUI slows down significantly after random period of time.

2014-03-31 Thread William Söderberg

I also experience this problem. I've been having it for a while. Logging
out and logging in again temporarily fixes the issue. Affects both KDE
and Gnome. Got this in /var/log/syslog when the problem happened just
now:

Mar 31 21:57:54 dreadnought kernel: [ 2390.058249] irq 16: nobody cared (try 
booting with the "irqpoll" option)
Mar 31 21:57:54 dreadnought kernel: [ 2390.058253] CPU: 0 PID: 0 Comm: 
swapper/0 Tainted: PF  O 3.11.0-18-generic #32-Ubuntu
Mar 31 21:57:54 dreadnought kernel: [ 2390.058254] Hardware name: System 
manufacturer System Product Name/P8P67-M, BIOS 1501 08/30/2011
Mar 31 21:57:54 dreadnought kernel: [ 2390.058255]  880400974c9c 
880417403e68 816e8571 880400974c00
Mar 31 21:57:54 dreadnought kernel: [ 2390.058257]  880417403e90 
810f88e2 880400974c00 0010
Mar 31 21:57:54 dreadnought kernel: [ 2390.058259]   
880417403ed0 810f8d11 815a158f
Mar 31 21:57:54 dreadnought kernel: [ 2390.058261] Call Trace:
Mar 31 21:57:54 dreadnought kernel: [ 2390.058262][] 
dump_stack+0x45/0x56
Mar 31 21:57:54 dreadnought kernel: [ 2390.058270]  [] 
__report_bad_irq+0x32/0xd0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058271]  [] 
note_interrupt+0x141/0x200
Mar 31 21:57:54 dreadnought kernel: [ 2390.058274]  [] ? 
cpuidle_enter_state+0x4f/0xc0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058276]  [] 
handle_irq_event_percpu+0xe1/0x1e0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058277]  [] 
handle_irq_event+0x3f/0x60
Mar 31 21:57:54 dreadnought kernel: [ 2390.058279]  [] 
handle_fasteoi_irq+0x5a/0x100
Mar 31 21:57:54 dreadnought kernel: [ 2390.058283]  [] 
handle_irq+0x1e/0x30
Mar 31 21:57:54 dreadnought kernel: [ 2390.058285]  [] 
do_IRQ+0x4d/0xc0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058287]  [] 
common_interrupt+0x6d/0x6d
Mar 31 21:57:54 dreadnought kernel: [ 2390.058288][] 
? cpuidle_enter_state+0x4f/0xc0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058291]  [] ? 
cpuidle_enter_state+0x48/0xc0
Mar 31 21:57:54 dreadnought kernel: [ 2390.058293]  [] 
cpuidle_idle_call+0xc9/0x210
Mar 31 21:57:54 dreadnought kernel: [ 2390.058295]  [] 
arch_cpu_idle+0xe/0x30
Mar 31 21:57:54 dreadnought kernel: [ 2390.058298]  [] 
cpu_startup_entry+0xe5/0x280
Mar 31 21:57:54 dreadnought kernel: [ 2390.058300]  [] 
rest_init+0x77/0x80
Mar 31 21:57:54 dreadnought kernel: [ 2390.058303]  [] 
start_kernel+0x40a/0x416
Mar 31 21:57:54 dreadnought kernel: [ 2390.058305]  [] ? 
repair_env_string+0x5c/0x5c
Mar 31 21:57:54 dreadnought kernel: [ 2390.058307]  [] ? 
early_idt_handlers+0x120/0x120
Mar 31 21:57:54 dreadnought kernel: [ 2390.058309]  [] 
x86_64_start_reservations+0x2a/0x2c
Mar 31 21:57:54 dreadnought kernel: [ 2390.058310]  [] 
x86_64_start_kernel+0x108/0x117
Mar 31 21:57:54 dreadnought kernel: [ 2390.058311] handlers:
Mar 31 21:57:54 dreadnought kernel: [ 2390.058323] [] 
e1000_intr [e1000]
Mar 31 21:57:54 dreadnought kernel: [ 2390.058373] [] 
nv_kern_isr [nvidia]
Mar 31 21:57:54 dreadnought kernel: [ 2390.058374] Disabling IRQ #16

willz@dreadnought:/proc$ cat interrupts | grep 16:
 16: 68  0  0  0   IO-APIC-fasteoi   eth1, 
nvidia

willz@dreadnought:/var/log$ uname -a
Linux dreadnought 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

willz@dreadnought:/var/log$ nvidia-settings -v
/usr/share/themes/Blumix1.0/gtk-2.0/gtkrc:580: Unable to locate image file in 
pixmap_path: "transparent_dot.png"
/usr/share/themes/Blumix1.0/gtk-2.0/gtkrc:583: Background image options 
specified without filename

nvidia-settings:  version 304.88  (buildd@panlong)  Thu Jul 11 10:40:14 UTC 2013
  The NVIDIA X Server Settings tool.

  This program is used to configure the NVIDIA Linux graphics driver.
  For more detail, please see the nvidia-settings(1) man page.

  Copyright (C) 2004 - 2010 NVIDIA Corporation.

Let me know if you want more information. This issue bugs me a lot.

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

Title:
  GUI slows down significantly after random period of time.

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Like a number of other users, I'm getting some variant of graphical
  slowdown after using my desktop PC for a random amount of time -
  between minutes and hours. I suspect the problem lies with compiz,
  OpenGL or graphics card drivers (NVidia in my case) as I have seen
  this behaviour with both Linux Mint 11 and 12 in the past, on the same
  PC. I don't believe there to be a hardware problem as this machine
  works perfectly fine running high-end games under Windows.

  Restarting or logging out and in often temporarily resolves the
  issue... but it eventually returns.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: compiz 1:0.9.7.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.

[Desktop-packages] [Bug 1300153] Re: login Screen is not showing correctly

2014-03-31 Thread Robert Ancell

** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu)

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

Title:
  login Screen is not showing correctly

Status in “lightdm-gtk-greeter” package in Ubuntu:
  New

Bug description:
  fresh installl of Xubuntu 14.04 final beta and the login Screen is not
  showing correctly on Lenovo Thinkpad 530.

  it shrinks to aprrox 3/4's of the Horizontal screen size. my screen is
  1366 x 768, and it looks as if it resize to around 1024 x 768.

  once logged in it goes to the correct size.. This happens even if you
  let the screen saver kick in and then you go to log back in.

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

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

[Desktop-packages] [Bug 1300428] [NEW] freeze ubuntu BUG: unable to handle kernel paging request at ffff880165ec6000

2014-03-31 Thread JmAbuDabi

Public bug reported:

This cat /var/log/kern.log
Mar 31 18:21:50 jmabudabi-pc kernel: [   44.409627] init: plymouth-stop 
pre-start process (3247) terminated with status 1
Mar 31 18:22:37 jmabudabi-pc kernel: [   91.191139] PPP BSD Compression module 
registered
Mar 31 18:22:37 jmabudabi-pc kernel: [   91.260569] PPP Deflate Compression 
module registered
Mar 31 19:22:41 jmabudabi-pc kernel: [ 3694.801200] chrome[8240]: segfault at 
44 ip 7fdcee39451f sp 7fff966b1b00 error 4 in 
fglrx_dri.so[7fdced659000+1d9a000]
Mar 31 19:22:41 jmabudabi-pc kernel: [ 3695.448823] chrome[8250]: segfault at 
44 ip 7fe7e6c7451f sp 7fff16a4e4b0 error 4 in 
fglrx_dri.so[7fe7e5f39000+1d9a000]
Mar 31 19:22:42 jmabudabi-pc kernel: [ 3696.002482] chrome[8261]: segfault at 
44 ip 7fb84235751f sp 7fff090c3bb0 error 4 in 
fglrx_dri.so[7fb84161c000+1d9a000]
Mar 31 21:59:31 jmabudabi-pc kernel: [13104.771426] chrome[12563]: segfault at 
44 ip 7f1f790a051f sp 7fff2aec4c60 error 4 in 
fglrx_dri.so[7f1f78365000+1d9a000]
Mar 31 21:59:31 jmabudabi-pc kernel: [13105.394848] chrome[12714]: segfault at 
44 ip 7f454400151f sp 7fff51b50900 error 4 in 
fglrx_dri.so[7f45432c6000+1d9a000]
Mar 31 21:59:32 jmabudabi-pc kernel: [13106.013957] chrome[12754]: segfault at 
44 ip 7f5cdb48551f sp 7fff46e7a370 error 4 in 
fglrx_dri.so[7f5cda74a000+1d9a000]
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926600] BUG: unable to handle 
kernel paging request at 880165ec6000
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926612] IP: [] 
implement+0x6a/0x110 [hid]
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926634] PGD 1c06063 PUD 1665dc063 
PMD 1648d8063 PTE 800165ec6161
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926646] Oops: 0003 [#1] SMP 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926654] CPU 0 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926657] Modules linked in: 
ppp_deflate bsd_comp ppp_async crc_ccitt pci_stub vboxpci(O) vboxnetadp(O) 
vboxnetflt(O) vboxdrv(O) rfcomm bnep bluetooth parport_pc ppdev binfmt_misc 
ext2 dm_crypt ip6t_LOG xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT ipt_LOG xt_limit xt_tcpudp xt_addrtype xt_state ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp fglrx(P) 
iptable_nat snd_hda_codec_hdmi nf_nat nf_conntrack_ipv4 iptable_mangle 
snd_seq_midi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep 
snd_pcm nf_defrag_ipv4 nf_conntrack_ftp snd_rawmidi snd_seq_midi_event snd_seq 
snd_timer snd_seq_device nf_conntrack iptable_filter snd soundcore ip_tables 
x_tables sp5100_tco psmouse serio_raw i2c_piix4 edac_core k10temp edac_mce_amd 
option usb_wwan usbserial joydev snd_page_alloc dm_multipath mac_hid it87 
hwmon_vid lp parport dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs 
zlib_deflate libcrc32c vesafb hid_logitech_dj usbhid hid usb_s
Mar 31 22:21:24 jmabudabi-pc kernel: torage wmi r8169
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926796] 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926803] Pid: 1852, comm: Xorg 
Tainted: P   O 3.2.0-56-generic #86-Ubuntu Hewlett-Packard HP Pro 3305 
Series/2AB1h
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926816] RIP: 
0010:[]  [] implement+0x6a/0x110 [hid]
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926833] RSP: 0018:88016273bc08  
EFLAGS: 00010086
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926839] RAX: 8500 RBX: 
8500 RCX: 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926845] RDX: 0040 RSI: 
880165ec5ff1 RDI: 88019ffdc000
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926851] RBP: 88016273bc38 R08: 
 R09: 880165ec5ff1
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926856] R10:  R11: 
0004 R12: 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926862] R13: 0040 R14: 
880165ec5ff9 R15: 88019ffdc000
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926870] FS:  7fdceb7198c0() 
GS:8801afc0() knlGS:00a4fb40
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926876] CS:  0010 DS:  ES:  
CR0: 80050033
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926882] CR2: 880165ec6000 CR3: 
00019ff0f000 CR4: 06f0
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926888] DR0:  DR1: 
 DR2: 
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926894] DR3:  DR6: 
0ff0 DR7: 0400
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926901] Process Xorg (pid: 1852, 
threadinfo 88016273a000, task 880164d4ae00)
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926906] Stack:
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926909]  88016273bc88 
0024 0048 88019feb3e00
Mar 31 22:21:24 jmabudabi-pc kernel: [14417.926922]  0008 
880165ec5ff1 88016273bc98 a003770d
Mar 31 22:21:24 jmabudabi-pc kernel: [1

[Desktop-packages] [Bug 1300417] Re: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()

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

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 #1288956, 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/1300417/+attachment/4056301/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056303/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056307/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056308/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056309/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056310/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300417/+attachment/4056311/+files/ThreadStacktrace.txt

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

** 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 totem in Ubuntu.
https://bugs.launchpad.net/bugs/1300417

Title:
  totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()

Status in “totem” package in Ubuntu:
  New

Bug description:
  i was copying a video (vob ) file with nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 21:53:40 2014
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2014-03-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140331)
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///media/username/AE8AEDB38AED77EB/files/Captain%20America%20-%20Il%20primo%20vendicatore%20(1080p).mkv
 /tmp/.gnome_desktop_thumbnail.MPMDDX
  SegvAnalysis:
   Segfault happened at: 0x7f3faf713297 :mov
(%rbx),%rax
   PC (0x7f3faf713297) ok
   source "(%rbx)" (0x20) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gst_buffer_new () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_buffer_new_allocate () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
  Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()
  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/totem/+bug/1300417/+subscriptions

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

[Desktop-packages] [Bug 1300283] Re: LibreOffice does not start in a KDE 4 session

2014-03-31 Thread Mark Fraser

In my case I could get the start center to launch properly, but nothing
else, but it would work properly by going into Konqueror and opening an
ods or odt file.

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

Title:
  LibreOffice does not start in a KDE 4 session

Status in “libreoffice” package in Ubuntu:
  Confirmed

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar 31 17:22:08 2014
  InstallationDate: Installed on 2014-03-18 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 810549] Re: Battery indicator turns red when charged second battery is inserted

2014-03-31 Thread zwigno

I'm running a different laptop now with only one battery so I'm going to
unsubscribe to this.

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

Title:
  Battery indicator turns red when charged second battery is inserted

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

Bug description:
  This is on a Lenovo T410s, Natty, 64-bit.  I have the second battery
  goes in the cd-rom drive slot.  If the laptop is plugged in, and both
  batteries are charged, the battery indicator will turn red with the
  empty battery icon.  Clicking on the icon will show 3 batteries
  "waiting to charge".  However, when I click on the "waiting to charge"
  text the Power Statistics menu shows everything correctly.

  Additionally, the time remaining only shows the time remaining of the
  current battery, not the total of both.

  If I only have one battery in everything seems to detect correctly.

  I'll attach screenshots.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Jul 14 10:25:30 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: LENOVO 2901CTO
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-10-generic 
root=UUID=4749b9a8-2362-4989-9472-650d92a7bbe7 ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET61WW (1.41 )
  dmi.board.name: 2901CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET61WW(1.41):bd10/27/2010:svnLENOVO:pn2901CTO:pvrThinkPadT410s:rvnLENOVO:rn2901CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2901CTO
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1300409] Re: evolution-addressbook-factory crashed with SIGSEGV in malloc_consolidate()

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

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 #1293261, 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/1300409/+attachment/4056222/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056224/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056225/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056226/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056227/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056228/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1300409/+attachment/4056229/+files/ThreadStacktrace.txt

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

** 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 evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1300409

Title:
  evolution-addressbook-factory crashed with SIGSEGV in
  malloc_consolidate()

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

Bug description:
  Dunno. I'm not a coder. Could be anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 31 15:41:27 2014
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
  InstallationDate: Installed on 2014-03-31 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 
(20140326.1)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f80f6ea1715 :   mov
0x8(%r12),%r13
   PC (0x7f80f6ea1715) ok
   source "0x8(%r12)" (0xff019008fe40) not located in a known VMA region 
(needed readable region)!
   destination "%r13" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f80c820) at malloc.c:4151
   _int_malloc (av=av@entry=0x7f80c820, bytes=bytes@entry=2032) at 
malloc.c:3423
   __libc_calloc (n=, elem_size=) at malloc.c:3219
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-addressbook-factory crashed with SIGSEGV in 
malloc_consolidate()
  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/evolution-data-server/+bug/1300409/+subscriptions

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

[Desktop-packages] [Bug 937200] Re: Fat fonts in Swing applications

2014-03-31 Thread Matthias Klose

everything is fine. just don't bother with any stable updates. will be
included with the next security updates.

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

Title:
  Fat fonts in Swing applications

Status in “fonts-unfonts-core” package in Ubuntu:
  Invalid
Status in “openjdk-7” package in Ubuntu:
  Fix Committed
Status in “fonts-unfonts-core” source package in Precise:
  Invalid
Status in “openjdk-7” source package in Precise:
  Triaged

Bug description:
  SRU justification:

  [Impact]

  When certain combinations of font packages are installed, the Java
  font loader may load certain fonts with some of their styles missing,
  meaning the wrong style is rendered when that font is chosen.

  The most well-known example is on Ubuntu systems with fonts-unfonts-
  core installed (recommended by Wine): the Ubuntu font is loaded
  without its regular style, so in Swing applications using the GTK look
  and feel, the Ubuntu font is rendered in bold weight.

  [Test Case]

  1. Install openjdk-7-jdk, ttf-ubuntu-font-family, and fonts-unfonts-
  core.

  2. Download the test case from comment #61:
  https://launchpadlibrarian.net/161520209/TestCase.java

  3. Compile and run the test case:

javac TestCase.java
java TestCase

  4. The expected output should begin with:

  Font family: Ubuntu plain=** TrueType Font: Family=Ubuntu Name=Ubuntu
  [...]

  The current (broken) output begins with:

  Font family: Ubuntu plain=null bold=** TrueType Font: Family=Ubuntu
  Name=Ubuntu Bold [...]

  Note "plain=null" in the broken output, meaning the bold style is
  going to be used when plain was requested.

  [Regression Potential]

  * The patch was authored by the maintainer of the surrounding code,
  and reviewed and accepted upstream.

  * If there is a regression, it might be reported upstream against JDK8
  or JDK9, so we should be aware of any upstream fixes in that part of
  the code.

  * If there is a regression, the symptoms are likely to be similar to
  this bug: incorrect or incomplete font loading in certain
  configurations.

  Original description:

  Since I upgraded to Ubuntu 12.04 I noticed that the fonts in Java
  Swing applications use the bold font weight. This looks really ugly
  and takes up to much space.

  1.
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  2.
  apt-cache policy openjdk-7-jdk
  openjdk-7-jdk:
    Installiert: 7~b147-2.0-1ubuntu2
    Kandidat:7~b147-2.0-1ubuntu2
    Versionstabelle:
   *** 7~b147-2.0-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
  100 /var/lib/dpkg/status

  3.
  Applications rendering with normal fonts

  4.
  Applications rendering with bold fonts

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: openjdk-7-jdk 7~b147-2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Mon Feb 20 20:44:43 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: openjdk-7
  UpgradeStatus: Upgraded to precise on 2012-02-16 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-unfonts-core/+bug/937200/+subscriptions

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

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

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

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  I put

  Section "Device"
Option "Backlight" "intel_backlight"
  EndSection

  in /etc/X11/xorg.conf and I got this error. I'm going to put it in
  /etc/X11/xorg.conf.d/20-sceen.conf.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.14.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jan 31 17:44:27 2014
  DistUpgraded: 2014-01-27 14:45:52,877 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-5-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:148a]
 Subsystem: Hewlett-Packard Company Device [103c:148a]
  InstallationDate: Installed on 2014-01-12 (18 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Mini 110-3100
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=04612c8e-2b69-468e-8d79-e1277a28f411 ro crashkernel=384M-:128M
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7f114ad1e3e0, argc=9, argv=0x747d77a8, 
init=, fini=, rtld_fini=, 
stack_end=0x747d7798) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to trusty on 2014-01-27 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 01/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 148A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 79.4B
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd01/14/2011:svnHewlett-Packard:pnHPMini110-3100:pvr058D11202D0300100:rvnHewlett-Packard:rn148A:rvr79.4B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Mini 110-3100
  dmi.product.version: 058D11202D0300100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Fri Jan 31 17:46:22 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.5-1ubuntu2

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

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

[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

2014-03-31 Thread Christian S.

OK you are right. I opened a ticket for those the fix in comment #6 does not 
work and the issue appears when a external monitor is connected when login 
(e.g. as described in #77 and 76):
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1300393

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Confirmed
Status in Release Notes for Ubuntu:
  Invalid
Status in “mesa” package in Ubuntu:
  Fix Released
Status in “nux” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  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-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

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