date:20130624

** Branch linked: lp:ubuntu/eglibc

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

Title:
  Pulseaudio applications hang (Totem, GNOME Shell etc.)

Status in The GNU C Library:
  Fix Released
Status in “eglibc” package in Ubuntu:
  Fix Released
Status in “totem” package in Ubuntu:
  Invalid
Status in “eglibc” source package in Precise:
  Confirmed
Status in “totem” source package in Precise:
  Invalid
Status in “eglibc” source package in Quantal:
  Confirmed
Status in “totem” source package in Quantal:
  Invalid
Status in “eglibc” package in Debian:
  Fix Released

Bug description:
  At least so here.
  Best way to see would be to use totem for a while, window usually becomes 
unresponsive fairly soon.
  Possible Test case(s):
  Add a couple of music tracks to the playlist, switch from one to the other & 
back again with next & previous buttons. (may cause lockup

  Close Totem(Videos), re-open & add back the same tracks & or try them from 
the "Movie"
   menu dropdown.
  Usually here they won't  play & or be switchable, ect.

  Add a couple of tracks to playlist, click on track names a few times
  to start playback/switch tracks

  Doesn't seem to matter if totem is started normally (no app menu in
  ubuntu session), with the app menu (Exec=env UBUNTU_MENUPROXY=0 totem)
  or from the sound menu

  With the pulseaudio plugin removed & the gst alsa plugin installed
  totem behaves much better though on very rare occasion will become
  unresponsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Sat Dec  1 01:49:22 2012
  InstallationDate: Installed on 2012-10-23 (38 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1194369] [NEW] nautilus crashed with SIGSEGV in gtk_action_get_name()

2013-06-24 Thread Matthew J. Ballard

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

Public bug reported:

Occurred shortly after opening a file window and double clicking on my
Downloads folder. The window turned grey, then closed with an error
report prompt shortly following.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Jun 25 01:44:11 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+564+189'"
InstallationDate: Installed on 2013-06-20 (5 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
MarkForUpload: True
ProcCmdline: nautilus --no-desktop /home/username/Dropbox
ProcEnviron:
 LD_LIBRARY_PATH=
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff85b17d9a6 : cmp
%rax,(%rdx)
 PC (0x7ff85b17d9a6) ok
 source "%rax" ok
 destination "(%rdx)" (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash saucy

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Occurred shortly after opening a file window and double clicking on my
  Downloads folder. The window turned grey, then closed with an error
  report prompt shortly following.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jun 25 01:44:11 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+564+189'"
  InstallationDate: Installed on 2013-06-20 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  MarkForUpload: True
  ProcCmdline: nautilus --no-desktop /home/username/Dropbox
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff85b17d9a6 :   cmp
%rax,(%rdx)
   PC (0x7ff85b17d9a6) ok
   source "%rax" ok
   destination "(%rdx)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

2013-06-24 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in gtk_action_get_name()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Occurred shortly after opening a file window and double clicking on my
  Downloads folder. The window turned grey, then closed with an error
  report prompt shortly following.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jun 25 01:44:11 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+564+189'"
  InstallationDate: Installed on 2013-06-20 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  MarkForUpload: True
  ProcCmdline: nautilus --no-desktop /home/username/Dropbox
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff85b17d9a6 :   cmp
%rax,(%rdx)
   PC (0x7ff85b17d9a6) ok
   source "%rax" ok
   destination "(%rdx)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 859600] Re: Please convert gnome-keyring to multiarch

2013-06-24 Thread eraserix

I've updated the description with more specific instructions on how to
test this SRU.

As for Depends vs Recommends from debian policy manual:
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality.

The Recommends field should list packages that would be found together
with this one in all but unusual installations.

I'm kind of inclined to stay with recommends. I can still store
passwords in the keyring without the pkcs11 library, no?

@graham: Thanks for the info about how the new multiarched package finds
its way to the users.

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

Title:
  Please convert gnome-keyring to multiarch

Status in “gnome-keyring” package in Ubuntu:
  Fix Released
Status in “gnome-keyring” source package in Precise:
  In Progress
Status in “gnome-keyring” source package in Quantal:
  Won't Fix
Status in “gnome-keyring” source package in Raring:
  Fix Released
Status in “gnome-keyring” package in Debian:
  New

Bug description:
  [Impact]
  Several applications are relying on this package as seen in comments 5 and 6.

  [Test case]
  Attempt to install both i386/amd64 versions of libp11-kit-gnome-keyring and 
preferably verify if the reported applications in this bug are able to run 
successfully.

  1. Run the command 'wine notepad'. Notice the warning from p11-kit.
  2. sudo apt-get install libp11-kit-gnome-keyring:i386
  3. Run the command 'wine notepad' again. Notice that the warning is gone.

  [Regression Potential]
  Minimal, several rdepends build testing have been completed successfully and 
nothing in the keyring code is attempting to dlopen any hardcoded library paths.

  gnome-keyring is still installing libraries to /usr/lib instead of the
  multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The
  attached patch does the conversion.

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

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

[Desktop-packages] [Bug 1153350] Re: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover

Hello Tigran, or anyone else affected,

Accepted unity into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/unity/7.0.0daily13.06.19~13.04-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: unity (Ubuntu Raring)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover

Status in LibreOffice Productivity Suite:
  Unknown
Status in Application Indicators:
  Invalid
Status in The Application Menu:
  New
Status in Unity:
  Fix Committed
Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “unity” source package in Raring:
  Fix Committed

Bug description:
  [Impact]

  Regression in LibreOffice's menu.

  [Test Case]

  Open LibreOffice Writer, go to global menu, click on any menu to open,
  hover over items.

  Expected: Orange highlight (from default theme, color not important)
  on mouse hover

  Actual: No highlight, except:
  - text in mid-grey colour changing a bit (brighter grey)
  - menu entries that lead to a direct action get an orange square on the left 
side
  - menu entries that lead to opening another windows just don't change
  - submenus open, but highlighting works the same way in sub-menus

  [Regression Potential]

  A revert of the offending commit.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-core 1:4.0.0~beta2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 10 12:37:34 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-03-06 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130305)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   gnome-session[12370]: WARNING: Application 'compiz.desktop' killed by signal 
9
   gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[12370]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly
   (gedit:14523): Gtk-CRITICAL **: gtk_widget_event: assertion 
`WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

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

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

[Desktop-packages] [Bug 1174495] Re: Window Managers instability with r600 radeon and high monitor resolutions

** Branch linked: lp:ubuntu/raring-proposed/compiz

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

Title:
  Window Managers instability with r600 radeon and high monitor
  resolutions

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.9 series:
  Fix Committed
Status in Mesa:
  Fix Released
Status in “cogl” package in Ubuntu:
  Confirmed
Status in “compiz” package in Ubuntu:
  Fix Committed
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Confirmed
Status in “cogl” source package in Raring:
  Confirmed
Status in “compiz” source package in Raring:
  Fix Committed
Status in “kde-workspace” source package in Raring:
  Fix Released
Status in “cogl” source package in Saucy:
  Confirmed
Status in “compiz” source package in Saucy:
  Fix Committed
Status in “kde-workspace” source package in Saucy:
  Fix Released

Bug description:
  [Impact]
  KWin 4.10.2 and Compiz 0.9.9 are using MSAA visuals with 13.04's mesa.
  This is unintended and leads to resource exhaustion which eventually crashes 
the WM.
  This affects all users on the r600 with sufficiently sized displays.

  [Test Case]
  Run Kwin or Unity with an r600 card, if it does not crash after a while we 
are happy.

  [Regression Potential]
  None, the fix was done by an upstream KWin and Mesa developer plus it has 
been incorporated into Fedora for a while plus it was used elsewhere in KWin 
already but not in this specific code path.

  [Other Info]
  None.

  --

  I think the version of kwin included in 13.04 contains a known bug as 
described here:
  https://bugs.kde.org/show_bug.cgi?id=315089
  https://bugs.freedesktop.org/show_bug.cgi?id=61182

  My understanding of the problem is as follows:
  * The Mesa radeon r600 driver recently added support for MSAA GLX visuals
  * Kwin isn't aware of MSAA properties and happens to (incorrectly) pick MSAA 
visuals for everything
  * These visuals occupy a large amount of memory when running at high monitor 
resolutions
  *  Mesa is "only" capable of mapping 256MB of visuals into CPU address space 
at once
  * Kwin's oversize visuals exceeds this limit, resulting in constant crashes

  The two radeon systems I have both crash immediately after logging in,
  when running with at a resolution of 2560x1440 and desktop effects
  enabled. After restarting kwin, a crash can be induced by performing
  actions that triggers desktop effects/animations. The resulting
  callstack is attached.

  ProblemType: BugDistroRelease: Ubuntu 13.04
  Package: kde-window-manager 4:4.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 19:53:57 2013
  InstallationDate: Installed on 2013-04-27 (2 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: TrueSourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

  --

  Compiz (unity) is affected by the same issue as shown in this
  stacktrace:

  http://paste.ubuntu.com/5661055/

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

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

[Desktop-packages] [Bug 859600] Re: Please convert gnome-keyring to multiarch

2013-06-24 Thread eraserix

** Description changed:

  [Impact]
  Several applications are relying on this package as seen in comments 5 and 6.
  
  [Test case]
- Attempt to install both i386/amd64 versions and preferably verify if the 
reported applications in this bug are able to run successfully
+ Attempt to install both i386/amd64 versions of libp11-kit-gnome-keyring and 
preferably verify if the reported applications in this bug are able to run 
successfully.
+ 
+ 1. Run the command 'wine notepad'. Notice the warning from p11-kit.
+ 2. sudo apt-get install libp11-kit-gnome-keyring:i386
+ 3. Run the command 'wine notepad' again. Notice that the warning is gone.
  
  [Regression Potential]
  Minimal, several rdepends build testing have been completed successfully and 
nothing in the keyring code is attempting to dlopen any hardcoded library paths.
  
  gnome-keyring is still installing libraries to /usr/lib instead of the
  multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The
  attached patch does the conversion.

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

Title:
  Please convert gnome-keyring to multiarch

Status in “gnome-keyring” package in Ubuntu:
  Fix Released
Status in “gnome-keyring” source package in Precise:
  In Progress
Status in “gnome-keyring” source package in Quantal:
  Won't Fix
Status in “gnome-keyring” source package in Raring:
  Fix Released
Status in “gnome-keyring” package in Debian:
  New

Bug description:
  [Impact]
  Several applications are relying on this package as seen in comments 5 and 6.

  [Test case]
  Attempt to install both i386/amd64 versions of libp11-kit-gnome-keyring and 
preferably verify if the reported applications in this bug are able to run 
successfully.

  1. Run the command 'wine notepad'. Notice the warning from p11-kit.
  2. sudo apt-get install libp11-kit-gnome-keyring:i386
  3. Run the command 'wine notepad' again. Notice that the warning is gone.

  [Regression Potential]
  Minimal, several rdepends build testing have been completed successfully and 
nothing in the keyring code is attempting to dlopen any hardcoded library paths.

  gnome-keyring is still installing libraries to /usr/lib instead of the
  multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The
  attached patch does the conversion.

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

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

[Desktop-packages] [Bug 1011073] Re: NetworkManager submenus sometimes unpopulated

** Branch linked: lp:ubuntu/raring-proposed/libdbusmenu

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

Title:
  NetworkManager submenus sometimes unpopulated

Status in DBus Menu:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in OEM Priority Project quantal series:
  New
Status in OEM Priority Project raring series:
  In Progress
Status in “libdbusmenu” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” package in Ubuntu:
  Invalid
Status in “libdbusmenu” source package in Precise:
  Fix Committed
Status in “network-manager-applet” source package in Precise:
  Invalid
Status in “libdbusmenu” source package in Quantal:
  Triaged
Status in “network-manager-applet” source package in Quantal:
  Invalid
Status in “libdbusmenu” source package in Raring:
  Fix Committed
Status in “network-manager-applet” source package in Raring:
  Invalid

Bug description:
  [Impact]

   * Affected applications with a high number of menu updates reach the maximum 
value allowed for the ID of a menuitem, and rejects further menu changes. 
Because the application underneath the menu has already removed the underlying 
actual GtkMenuItem objects, it is impossible to activate the items -- to effect 
the actions linked to the menuitems.
   * Some indicators have a relatively high and climbing memory usage due to 
the way they build menus to be displayed in the panel.

  [Test Case]

   * Run nm-applet for a while (multiple days without shutdown, without killing 
the application), notice whether the menus are still usable.
   * Run indicators for a while, observe memory usage.

  [Regression Potential]

  Indicators with a very high amount of updates may be affected as circling 
back past the maximum value, if a new menu item is created with an ID still in 
use by a menuitem that has not been removed yet, neither or only one of the two 
menu items might be available to be clicked -- this could confuse users or 
cause error messages to be displayed.
  Risk is low however since network-manager-gnome (nm-applet) is currently the 
application with the most menu updates.

  [Other Info]
   
  Submenus in Network Manager are sometimes unusable as they are not populated. 
 This happens both with the list of available networks and with the VPN list.  
When the bug happens, it occurs for *both* the wireless submenu and the VPN 
menu.  I know there are entries for those submenus as I can see them with other 
network UI mechanisms.  The issue is intermittent.

  Expected:
  Dropping down the menu then hovering over the submenu trigger-point (example: 
"More networks") shows the additional expected entries (example: more wifi 
networks to choose from).

  Actual:
  Dropping down the menu and hovering over the submenu trigger displays a 
submenu but the submenu has nothing in it and is unusable.

  Ubuntu 12.04
  network-manager 0.9.4.0-0ubuntu4.1
  Apple Macbook Pro 8,1

  03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
  02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit 
Ethernet PCIe (rev 10)

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

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

[Desktop-packages] [Bug 1168370] Re: grip-test no longer responds to input

** Branch linked: lp:ubuntu/raring-proposed/libgrip

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

Title:
  grip-test no longer responds to input

Status in libgrip: multitouch gesture library for GTK:
  Fix Released
Status in libgrip raring series:
  In Progress
Status in “libgrip” package in Ubuntu:
  Fix Released
Status in “libgrip” source package in Raring:
  Fix Committed

Bug description:
  [Impact]

   * The library was not supplying and gestures to client callers
  because of underlying change in the underlying gesture recognizer
  conflicting with an incorrect assumption in the libgrip library
  design.  The assumption was that touch input device IDs were
  persistent across gesture recognizer instances, which has never been
  guaranteed to be true.

   * This bug renders the entire libgrip functionally useless, a fairly
  serious regression.

   * The bug fix moves to the latest version of the GEIS interface so
  obviates dependency on incorrect behaviour in the previous
  implementation.

  [Test Case]

   * Using a touchscreen, invoke the eog photo viewer program and
  attempt to zoom a photo using the pinch gesture.  Without this patch,
  there will be no response,  with the patch the photo should zoom.  See
  also #1120149.

  [Regression Potential]

   * A programming error in the library could result in crashes in the
  eog or evince applications.

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

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

[Desktop-packages] [Bug 1193647] Re: ubuntu-webapps-update-index fails to parse multiline fields

2013-06-24 Thread Ilya Voronin

** Description changed:

  Ubuntu 13.04, unity-webapps-service 2.5.0~daily13.03.18-0ubuntu1
  
  I've packaged my webapp for http://www.rememberthemilk.com/. It is available 
through one of configured repositories.
  I'm expecting ubuntu-webapps-update-index to update available webapps 
database, but it fails to do it:
  
  ---
  $ /usr/bin/ubuntu-webapps-update-index
  ...
- ** Message: Investigating webapp: unity-webapps-rmilk 
- 
+ ** Message: Investigating webapp: unity-webapps-rmilk
  
  ** (process:7279): WARNING **: Failed to parse metadata line ( Remember The 
Milk Webapp for Unity
  ), skipping package
  ---
  
- This happens because my description field is multi-line:
+ This happens because package description field is multi-line:
  
  ---
  $ apt-cache dumpavail
  ...
  Package: unity-webapps-rmilk
  Priority: extra
  Section: web
  Installed-Size: 38
  Maintainer: Ilya Voronin 
  Architecture: all
  Version: 1.0-3
  Depends: unity-webapps-common, xdg-utils
  Filename: pool/main/u/unity-webapps-rmilk/unity-webapps-rmilk_1.0-3_all.deb
  Size: 2134
  MD5sum: af87b1c06c7b2fb2751dc2e6e72161b2
  SHA1: c9a14fdda9d7ae85ee2c276a5fbd963af6462624
  SHA256: 807d2b060e61341dd9f752bfc06aecfe6653d20a9b2a1cf8f85e71ea8937bd29
  Description: Unity Webapp for Remember The Milk
-  Remember The Milk Webapp for Unity
+  Remember The Milk Webapp for Unity
  Ubuntu-Webapps-Domain: rememberthemilk.com
  Ubuntu-Webapps-Name: Remember The Milk
  Ubuntu-Webapps-Includes: 
https://*.rememberthemilk.com/*;https://rememberthemilk.com/*
  
  ---

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

Title:
  ubuntu-webapps-update-index fails to parse multiline fields

Status in “libunity-webapps” package in Ubuntu:
  New

Bug description:
  Ubuntu 13.04, unity-webapps-service 2.5.0~daily13.03.18-0ubuntu1

  I've packaged my webapp for http://www.rememberthemilk.com/. It is available 
through one of configured repositories.
  I'm expecting ubuntu-webapps-update-index to update available webapps 
database, but it fails to do it:

  ---
  $ /usr/bin/ubuntu-webapps-update-index
  ...
  ** Message: Investigating webapp: unity-webapps-rmilk

  ** (process:7279): WARNING **: Failed to parse metadata line ( Remember The 
Milk Webapp for Unity
  ), skipping package
  ---

  This happens because package description field is multi-line:

  ---
  $ apt-cache dumpavail
  ...
  Package: unity-webapps-rmilk
  Priority: extra
  Section: web
  Installed-Size: 38
  Maintainer: Ilya Voronin 
  Architecture: all
  Version: 1.0-3
  Depends: unity-webapps-common, xdg-utils
  Filename: pool/main/u/unity-webapps-rmilk/unity-webapps-rmilk_1.0-3_all.deb
  Size: 2134
  MD5sum: af87b1c06c7b2fb2751dc2e6e72161b2
  SHA1: c9a14fdda9d7ae85ee2c276a5fbd963af6462624
  SHA256: 807d2b060e61341dd9f752bfc06aecfe6653d20a9b2a1cf8f85e71ea8937bd29
  Description: Unity Webapp for Remember The Milk
   Remember The Milk Webapp for Unity
  Ubuntu-Webapps-Domain: rememberthemilk.com
  Ubuntu-Webapps-Name: Remember The Milk
  Ubuntu-Webapps-Includes: 
https://*.rememberthemilk.com/*;https://rememberthemilk.com/*

  ---

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

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

[Desktop-packages] [Bug 1168370] Re: grip-test no longer responds to input

Hello Stephen, or anyone else affected,

Accepted libgrip into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/libgrip/0.3.6daily13.06.19~13.04-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libgrip (Ubuntu Raring)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  grip-test no longer responds to input

Status in libgrip: multitouch gesture library for GTK:
  Fix Released
Status in libgrip raring series:
  In Progress
Status in “libgrip” package in Ubuntu:
  Fix Released
Status in “libgrip” source package in Raring:
  Fix Committed

Bug description:
  [Impact]

   * The library was not supplying and gestures to client callers
  because of underlying change in the underlying gesture recognizer
  conflicting with an incorrect assumption in the libgrip library
  design.  The assumption was that touch input device IDs were
  persistent across gesture recognizer instances, which has never been
  guaranteed to be true.

   * This bug renders the entire libgrip functionally useless, a fairly
  serious regression.

   * The bug fix moves to the latest version of the GEIS interface so
  obviates dependency on incorrect behaviour in the previous
  implementation.

  [Test Case]

   * Using a touchscreen, invoke the eog photo viewer program and
  attempt to zoom a photo using the pinch gesture.  Without this patch,
  there will be no response,  with the patch the photo should zoom.  See
  also #1120149.

  [Regression Potential]

   * A programming error in the library could result in crashes in the
  eog or evince applications.

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

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

[Desktop-packages] [Bug 1011073] Re: NetworkManager submenus sometimes unpopulated

Hello onyxrev, or anyone else affected,

Accepted libdbusmenu into raring-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/libdbusmenu/12.10.3daily13.06.19~13.04-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libdbusmenu (Ubuntu Raring)
   Status: Triaged => Fix Committed

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

Title:
  NetworkManager submenus sometimes unpopulated

Status in DBus Menu:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in OEM Priority Project quantal series:
  New
Status in OEM Priority Project raring series:
  In Progress
Status in “libdbusmenu” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” package in Ubuntu:
  Invalid
Status in “libdbusmenu” source package in Precise:
  Fix Committed
Status in “network-manager-applet” source package in Precise:
  Invalid
Status in “libdbusmenu” source package in Quantal:
  Triaged
Status in “network-manager-applet” source package in Quantal:
  Invalid
Status in “libdbusmenu” source package in Raring:
  Fix Committed
Status in “network-manager-applet” source package in Raring:
  Invalid

Bug description:
  [Impact]

   * Affected applications with a high number of menu updates reach the maximum 
value allowed for the ID of a menuitem, and rejects further menu changes. 
Because the application underneath the menu has already removed the underlying 
actual GtkMenuItem objects, it is impossible to activate the items -- to effect 
the actions linked to the menuitems.
   * Some indicators have a relatively high and climbing memory usage due to 
the way they build menus to be displayed in the panel.

  [Test Case]

   * Run nm-applet for a while (multiple days without shutdown, without killing 
the application), notice whether the menus are still usable.
   * Run indicators for a while, observe memory usage.

  [Regression Potential]

  Indicators with a very high amount of updates may be affected as circling 
back past the maximum value, if a new menu item is created with an ID still in 
use by a menuitem that has not been removed yet, neither or only one of the two 
menu items might be available to be clicked -- this could confuse users or 
cause error messages to be displayed.
  Risk is low however since network-manager-gnome (nm-applet) is currently the 
application with the most menu updates.

  [Other Info]
   
  Submenus in Network Manager are sometimes unusable as they are not populated. 
 This happens both with the list of available networks and with the VPN list.  
When the bug happens, it occurs for *both* the wireless submenu and the VPN 
menu.  I know there are entries for those submenus as I can see them with other 
network UI mechanisms.  The issue is intermittent.

  Expected:
  Dropping down the menu then hovering over the submenu trigger-point (example: 
"More networks") shows the additional expected entries (example: more wifi 
networks to choose from).

  Actual:
  Dropping down the menu and hovering over the submenu trigger displays a 
submenu but the submenu has nothing in it and is unusable.

  Ubuntu 12.04
  network-manager 0.9.4.0-0ubuntu4.1
  Apple Macbook Pro 8,1

  03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
  02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit 
Ethernet PCIe (rev 10)

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

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

[Desktop-packages] [Bug 436648] Re: [UserInterface Freeze Exception]Change name of software-store to software center

2013-06-24 Thread amato

** Changed in: software-center (Ubuntu)
 Assignee: Michael Vogt (mvo) => amato (buononato-a)

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

Title:
  [UserInterface Freeze Exception]Change name of software-store to
  software center

Status in “software-center” package in Ubuntu:
  Fix Released
Status in “ubiquity-slideshow-ubuntu” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: software-store

  After much discussion with community members and others, sabdfl has
  determined that "Software Store" should become "Software Center" in US
  English. Note that this should be expressed as "Software Centre" in UK
  English. The package should be named "software-center".

  ProblemType: Bug
  Architecture: i386
  Date: Fri Sep 25 07:15:27 2009
  DistroRelease: Ubuntu 9.10
  Package: software-store 0.3.10
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
  SourcePackage: software-store
  Uname: Linux 2.6.31-10-generic i686

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

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

[Desktop-packages] [Bug 1174495] Please test proposed package

Hello sfar, or anyone else affected,

Accepted compiz into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.9~daily13.06.19~13.04-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Window Managers instability with r600 radeon and high monitor
  resolutions

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.9 series:
  Fix Committed
Status in Mesa:
  Fix Released
Status in “cogl” package in Ubuntu:
  Confirmed
Status in “compiz” package in Ubuntu:
  Fix Committed
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Confirmed
Status in “cogl” source package in Raring:
  Confirmed
Status in “compiz” source package in Raring:
  Fix Committed
Status in “kde-workspace” source package in Raring:
  Fix Released
Status in “cogl” source package in Saucy:
  Confirmed
Status in “compiz” source package in Saucy:
  Fix Committed
Status in “kde-workspace” source package in Saucy:
  Fix Released

Bug description:
  [Impact]
  KWin 4.10.2 and Compiz 0.9.9 are using MSAA visuals with 13.04's mesa.
  This is unintended and leads to resource exhaustion which eventually crashes 
the WM.
  This affects all users on the r600 with sufficiently sized displays.

  [Test Case]
  Run Kwin or Unity with an r600 card, if it does not crash after a while we 
are happy.

  [Regression Potential]
  None, the fix was done by an upstream KWin and Mesa developer plus it has 
been incorporated into Fedora for a while plus it was used elsewhere in KWin 
already but not in this specific code path.

  [Other Info]
  None.

  --

  I think the version of kwin included in 13.04 contains a known bug as 
described here:
  https://bugs.kde.org/show_bug.cgi?id=315089
  https://bugs.freedesktop.org/show_bug.cgi?id=61182

  My understanding of the problem is as follows:
  * The Mesa radeon r600 driver recently added support for MSAA GLX visuals
  * Kwin isn't aware of MSAA properties and happens to (incorrectly) pick MSAA 
visuals for everything
  * These visuals occupy a large amount of memory when running at high monitor 
resolutions
  *  Mesa is "only" capable of mapping 256MB of visuals into CPU address space 
at once
  * Kwin's oversize visuals exceeds this limit, resulting in constant crashes

  The two radeon systems I have both crash immediately after logging in,
  when running with at a resolution of 2560x1440 and desktop effects
  enabled. After restarting kwin, a crash can be induced by performing
  actions that triggers desktop effects/animations. The resulting
  callstack is attached.

  ProblemType: BugDistroRelease: Ubuntu 13.04
  Package: kde-window-manager 4:4.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 19:53:57 2013
  InstallationDate: Installed on 2013-04-27 (2 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: TrueSourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

  --

  Compiz (unity) is affected by the same issue as shown in this
  stacktrace:

  http://paste.ubuntu.com/5661055/

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

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

[Desktop-packages] [Bug 1075923] Re: nautilus hangs copying large directories from a samba share

2013-06-24 Thread apinunt

Could this be a handshake/timing problem?
I've experienced this problem on 3 different computers, a 15 yr old IBM 
ThinkPad notebook, a Compaq notebook with a Celeron 560 CPU, an HP desktop with 
a dual core E5300 CPU, and noticed that the IBM was most affected and along 
with the Compaq unable to play a video file off the NAS, the HP was less often 
affected and could sometimes play a video off the NAS as long as I did not 
advance the slider several minutes into the video. I just replaced the old IBM 
notebook with a Samsung NP700G7C having a quad core i7-3630QM CPU and have yet 
to be affected by the problem, able to transfer more than 36GB of files from 
the NAS without a problem and able to play videos directly off the NAS without 
locking up.

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

Title:
  nautilus hangs copying large directories from a samba share

Status in GVFS:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Triaged

Bug description:
  Problem
  ===
  Copying files to and from samba shares (this includes Windows shares) is 
unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated 
samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB.

  Workaround
  ==
  Until gvfs-smb is fixed, use the kernel samba client (cifs) that works 
reliably, is faster, but needs some terminal commands to get going:
  # sudo -s
  # mkdir /mnt/cifs
  # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER 
"//SAMBA_SERVER/SAMBA_SHARE" /mnt/cifs
  It will ask for you password, you can then access the shared files at 
/mnt/cifs.

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

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

[Desktop-packages] [Bug 1186800] Re: [830 v3.7 regression] Video goes blank and system hangs (using an old kernel fix it)

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

Title:
  [830 v3.7 regression] Video goes blank and system hangs (using an old
  kernel fix it)

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

Bug description:
  I'm on a very old Dell C400 P3 866 with 768mb ram which still works
  rock solid. I've upgraded this system from Lubuntu 12.10 to 13.04 but
  with every kernel above V3.6.11 (took from mainline ubuntu) system
  hangs randomly.

  I tried to install Intel video drivers from
  https://01.org/linuxgraphics/ (Intel(R) Linux* Graphics Installer
  version 1.0.1 for Ubuntu* 13.04 (32-bit)) but this did not solve the
  problem. I'm not sure if is driver or kernel related since on the last
  release change the drivers curiously works using kernel V3.9 but
  before revert to this release I would like to help to find a solution.

  uname -r
  3.8.0-23-generic

  lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.21.6-0ubuntu4
Candidate: 2:2.21.6-0ubuntu4
Version table:
   *** 2:2.21.6-0ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  lspci -k
  00:02.0 VGA compatible controller: Intel Corporation 82830M/MG Integrated 
Graphics Controller (rev 04)
Subsystem: Dell Device 00c8
Kernel driver in use: i915
Kernel modules: intelfb, i915
  00:02.1 Display controller: Intel Corporation 82830M/MG Integrated Graphics 
Controller
Subsystem: Dell Device 00c8
Kernel modules: i915

  hwinfo --gfxcard
  > hal.1: read hal dataprocess 2789: arguments to dbus_move_error() were 
incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in 
file ../../dbus/dbus-errors.c line 282.
  This is normally a bug in some application using the D-Bus library.
  libhal.c 3483 : Error unsubscribing to signals, error=The name 
org.freedesktop.Hal was not provided by any .service files
  09: PCI 02.0: 0300 VGA compatible controller (VGA)  
[Created at pci.318]
Unique ID: _Znp.bU4liPq1bBD
SysFS ID: /devices/pci:00/:00:02.0
SysFS BusID: :00:02.0
Hardware Class: graphics card
Model: "Intel i830"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x3577 "i830"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x00c8 
Revision: 0x04
Driver: "i915"
Driver Modules: "drm"
Memory Range: 0xe000-0xe7ff (ro,non-prefetchable)
Memory Range: 0xf4f8-0xf4ff (rw,non-prefetchable)
IRQ: 11 (737 events)
Module Alias: "pci:v8086d3577sv1028sd00C8bc03sc00i00"
Driver Info #0:
  XFree86 v4 Server Module: intel
Driver Info #1:
  XFree86 v4 Server Module: intel
  3D Support: yes
  Extensions: dri
Config Status: cfg=new, avail=yes, need=no, active=unknown

  10: PCI 02.1: 0380 Display controller
[Created at pci.318]
Unique ID: ruGf.XE0Ix0G1vD2
SysFS ID: /devices/pci:00/:00:02.1
SysFS BusID: :00:02.1
Hardware Class: graphics card
Model: "Intel i830"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x3577 "i830"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x00c8 
Memory Range: 0xd800-0xdfff (ro,non-prefetchable)
Memory Range: 0xf4f0-0xf4f7 (rw,non-prefetchable)
Module Alias: "pci:v8086d3577sv1028sd00C8bc03sc80i00"
Driver Info #0:
  XFree86 v4 Server Module: intel
Driver Info #1:
  XFree86 v4 Server Module: intel
  3D Support: yes
  Extensions: dri
Config Status: cfg=new, avail=yes, need=no, active=unknown

  Primary display adapter: #9

  Note: I was able to replicate this bug trying to install directly from
  Lubuntu 13.04 live cd. I can't complete the installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sun Jun  2 17:16:56 2013
  InstallationDate: Installed on 2013-05-29 (3 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017)
  MarkForUpload: True
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to raring on 2013-06-02 (0 days ago)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDmesg: [   84.410243] init: anacron main process (1188) killed by TERM 
sig

[Desktop-packages] [Bug 1097007] Re: emacs23 will not install on ubuntu 12.10

It seems that either xemacs21 or emacsen-common is broken on your
system.  If you still have this problem, can you remove and reinstall
emacsen-common and see if that helps?  If removing xemacs21 from your
system altogether is acceptable, try that too.

I am setting the Status of this bug report to Incomplete to mark it as
pending on further information from you.  Feel free to set it back to
New once you have supplied the requested input.  Thank you for your
patience and understanding, and sorry for this very late reply.

** Changed in: emacs23 (Ubuntu)
   Status: New => Incomplete

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

Title:
  emacs23 will not install on ubuntu 12.10

Status in “emacs23” package in Ubuntu:
  Incomplete

Bug description:
  when I try to install emacs23 I get:

   apt-get install emacs23
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  emacs23 is already the newest version.
  0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  12 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Setting up emacsen-common (2.0.3) ...
  Install emacsen-common for xemacs21
  emacsen-common: Handling install of emacsen flavor xemacs21
  /usr/lib/emacsen-common/packages/install/emacsen-common: 29: 
/usr/lib/emacsen-co
  mmon/packages/install/emacsen-common: xemacs21: not found
  ERROR: install script from emacsen-common package failed
  dpkg: error processing emacsen-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of emacs23-common:
   emacs23-common depends on emacsen-common (>= 1.4.10); however:
Package emacsen-common is not configured yet.

  dpkg: error processing emacs23-common (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of emacs23-bin-common:
   emacs23-bin-common depends on emacs23-common (= 23.4+1-4ubuntu1); however:
Package emacs23-common is not configured yet.

  dpkg: error processing emacs23-bin-common (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of emacs23:
   emacs23 depends on emacs23-bin-common (= 23.4+1-4ubuntu1); however:
Package emacs23-bin-common is not configured yet.

  dpkg: error processing emacs23 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of emacs:
   emacs depends on emacs23 | emacs23-lucid | emacs23-nox; however:
Package emacs23 is not configureNo apport report written because the error 
mes
  sage indicates its a followup error from a previous failure.
  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  d yet.
Package emacs23-lucid is not installed.
Package emacs23-nox is not installed.

  dpkg: error processing emacs (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of emacs23-el:
   emacs23-el depends on emacs23-common (= 23.4+1-4ubuntu1); however:
Package emacs23-common is not configured yet.

  dpkg: error processing emacs23-el (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of xemacs21-mule:
   xemacs21-mule depends on emacsen-common; however:
Package emacsen-common is not configured yet.

  dpkg: error processing xemacs21-mule (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of xemacs21-mule-canna-wnn:
   xemacs21-mule-canna-wnn depends on emacsen-common; however:
Package emacsen-common is not configured yet.

  dpkg: error processing xemacs21-mule-canna-wnn (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of xemacs21-nomule:
   xemacs21-nomule depends on emacsen-common; however:
Package emacsen-common is not configured yet.

  dpkg: error processing xemacs21-nomule (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of x

[Desktop-packages] [Bug 786698] Re: in build, warning unrecognized option '-2.0/'

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

** Changed in: emacs
   Status: New => Fix Released

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

Title:
  in build, warning unrecognized option '-2.0/'

Status in GNU Emacs:
  Fix Released
Status in “emacs23” package in Ubuntu:
  New

Bug description:
  Binary package hint: emacs23

  On this system:
  kaduk@caspian:~$ uname -a
  Linux caspian 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:05:27 UTC 2010 
x86_64 GNU/Linux
  kaduk@caspian:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 10.04.1 LTS
  Release:10.04
  Codename:   lucid

  Using the source package 23.1+1-4ubuntu7.2, running 'debuild' produces 
compile lines such as:
  x86_64-linux-gnu-gcc -c -D_BSD_SOURCE   -Demacs -DHAVE_CONFIG_H  -I. 
-I/tmp/kaduk-foo/emacs23-23.1+1/src -D_BSD_SOURCE -pthread -D_REENTRANT 
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-1 -2.0/ 
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 
-I/usr/include/freetype2 -I/usr/include/alsa -pthread -D_REENTRANT 
-I/usr/include/librsvg-2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/gtk-2.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DDEBIAN -g -O2 
-I/usr/include/freetype2 frame.c
  x86_64-linux-gnu-gcc: unrecognized option '-2.0/'

  Presumably that is not the intended variable expansion.

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

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

[Desktop-packages] [Bug 859600] Re: Please convert gnome-keyring to multiarch

2013-06-24 Thread Scott Ritchie

Yes, I've been holding back on a Wine SRU because I wanted it to
integrate this fix.


Similarly, I will also want to backport wine1.6 to precise when it releases 
within a few weeks, and it would be very nice to have this done by then.

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

Title:
  Please convert gnome-keyring to multiarch

Status in “gnome-keyring” package in Ubuntu:
  Fix Released
Status in “gnome-keyring” source package in Precise:
  In Progress
Status in “gnome-keyring” source package in Quantal:
  Won't Fix
Status in “gnome-keyring” source package in Raring:
  Fix Released
Status in “gnome-keyring” package in Debian:
  New

Bug description:
  [Impact]
  Several applications are relying on this package as seen in comments 5 and 6.

  [Test case]
  Attempt to install both i386/amd64 versions and preferably verify if the 
reported applications in this bug are able to run successfully

  [Regression Potential]
  Minimal, several rdepends build testing have been completed successfully and 
nothing in the keyring code is attempting to dlopen any hardcoded library paths.

  gnome-keyring is still installing libraries to /usr/lib instead of the
  multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The
  attached patch does the conversion.

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

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

[Desktop-packages] [Bug 552954] Re: "can't find the info directory"

Oh, the Lintian change is http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=535566

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

Title:
  "can't find the info directory"

Status in “emacs-jabber” package in Ubuntu:
  Fix Released
Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “ocp” package in Ubuntu:
  Fix Released
Status in “emacs-jabber” package in Debian:
  Fix Released
Status in “emacs23” package in Debian:
  New
Status in “ocp” package in Debian:
  Fix Released
Status in “util-linux” package in Debian:
  Invalid

Bug description:
  Binary package hint: emacs23

  When trying to run "info" from emacs 23.1+1-4ubuntu7 I receive the
  error "can't find the info directory" and cannot view the info
  documentation (it is blank).

  Bug#543564 in Debian might be related.

  I noticed that emacs-jabber install /usr/share/info/dir.gz. I do not
  know if this is correct behaviour (the Debian bug discussion implies
  not).

  A work around is to gunzip /usr/share/info/dir.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs-jabber/+bug/552954/+subscriptions

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

[Desktop-packages] [Bug 552954] Re: "can't find the info directory"

Lintian has a check for this since 2009.  I would be tempted to close
the bug against Ubuntu emacs23 but for the time being, I simply marked
it as Confirmed, based on the number of reported (and now fixed) tasks
for other packages.

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

** Bug watch added: Debian Bug tracker #535566
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535566

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

Title:
  "can't find the info directory"

Status in “emacs-jabber” package in Ubuntu:
  Fix Released
Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “ocp” package in Ubuntu:
  Fix Released
Status in “emacs-jabber” package in Debian:
  Fix Released
Status in “emacs23” package in Debian:
  New
Status in “ocp” package in Debian:
  Fix Released
Status in “util-linux” package in Debian:
  Invalid

Bug description:
  Binary package hint: emacs23

  When trying to run "info" from emacs 23.1+1-4ubuntu7 I receive the
  error "can't find the info directory" and cannot view the info
  documentation (it is blank).

  Bug#543564 in Debian might be related.

  I noticed that emacs-jabber install /usr/share/info/dir.gz. I do not
  know if this is correct behaviour (the Debian bug discussion implies
  not).

  A work around is to gunzip /usr/share/info/dir.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs-jabber/+bug/552954/+subscriptions

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

[Desktop-packages] [Bug 1168467] Re: "phy0 -> rt2800pci_mcu_status: Error" AND "[drm:gen6_sanitize_pm] ERROR"

chenzero: question for you.

I am seeing this error also and my computer crashes. My computer eaither 
completely crashes or sometimes the desktop freezes.
This error may occur 6 times, but the computer crashed only 3 times. Once this 
error was the last thing the computer wrote into syslog before it crashed. But 
interestingly the error does not always lead to crash. For example today I see 
I have the error 14 times but it did not crash yet.

I would be interested in knowing if the PPA upgrade  stopped your
crashes (chenzero) after having it for about 10 weeks.

Here is my hardware which is nearly identical to chenzero.
 lspci
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics 
Controller (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host 
Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI 
Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host 
Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio 
Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 
(rev c4)
00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 
(rev c4)
00:1c.5 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 6 
(rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host 
Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 IDE interface: Intel Corporation Panther Point 4 port SATA Controller 
[IDE mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation Panther Point 2 port SATA Controller 
[IDE mode] (rev 04)
02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Thames 
[Radeon 7500M/7600M Series]
07:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network 
Adapter (rev 01)
09:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet 
(rev 10)

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

Title:
  "phy0 -> rt2800pci_mcu_status: Error" AND "[drm:gen6_sanitize_pm]
  *ERROR*"

Status in “gnome-nettool” package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I am running on Ubuntu 12.04 and I have two problems
  1) phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from 
hardware
  I was trying to solve it for almost a year, I googled my a.. off and no 
solution seems to be working ???
  2) [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: 
GEN6_RP_INTERRUPT_LIMITS expected 1700, was 1206
  This one showed up right after the 3.2.0-40-generic upgrade yesterday.

  Few things you might need:
  My ethernet is working and my wireless is too BUT sometimes the laptop (HP 
Pavilion g6) wont connect after suspend nor reboot the driver from the keyboard 
button, sometimes it freezes after waking from suspend so I have to suspend it 
and wake it again.

  $ uname -r
  3.2.0-40-generic

  $ arch
  x86_64

  $ dmesg | grep rt2
  [   27.257228] rt2800pci :01:00.0: PCI INT A -> GSI 16 (level, low) -> 
IRQ 16
  [   27.257255] rt2800pci :01:00.0: setting latency timer to 64
  [   27.397045] Registered led device: rt2800pci-phy0::radio
  [   27.397060] Registered led device: rt2800pci-phy0::assoc
  [   27.397074] Registered led device: rt2800pci-phy0::quality
  [   37.371529] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
  [ 4233.578114] rt2800pci :01:00.0: PCI INT A disabled
  [ 4235.952850] rt2800pci :01:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10b)
  [ 4235.952879] rt2800pci :01:00.0: restoring config space at offset 0x1 
(was 0x17, writing 0x817)
  [ 4235.953543] rt2800pci :01:00.0: PCI INT A -> GSI 16 (level, low) -> 
IRQ 16
  [ 4237.747271] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
  [ 4364.795800] rt2800pci :01:00.0: PCI INT A disabled
  [ 4367.184560] rt2800pci :01:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10b)
  [ 4367.184589] rt2800pci :01:00.0: restoring config space at offset 0x1 
(was 0x17, writing 0x817)
  [ 4367.185341] rt2800pci :01:00.0: PCI INT A -> GSI 16 (level, low) -> 
IRQ 16
  [ 4368.214890] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
  [12402.455880] rt2800pci :01:00.0: PCI INT A disabled
  [12404.830610] rt2800pci :01:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10b)
  [12404.830639] rt2800pci :01:0

[Desktop-packages] [Bug 821339] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()

2013-06-24 Thread Pierre Demathieu fr91

when opening image in Shotwell, wich worked even.

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

Title:
  gsettings-data-convert crashed with signal 5 in g_settings_set_value()

Status in “gconf” package in Ubuntu:
  Invalid

Bug description:
  Just crashed out of the blue

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gconf2 3.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Aug  5 18:30:30 2011
  ExecutablePath: /usr/bin/gsettings-data-convert
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  ProcCmdline: gsettings-data-convert
  ProcEnviron:
   LANGUAGE=en_AU:en_GB:en
   LANG=en_AU.UTF-8
   LC_MESSAGES=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_set_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_set () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
  Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
  UpgradeStatus: Upgraded to oneiric on 2011-08-04 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare users

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

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

[Desktop-packages] [Bug 1194226] Re: fglrx not installed

2013-06-24 Thread Daniel van Vugt

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

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 1025488, 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 1025488
   fglrx (not installed): fglrx kernel module failed to build [error: implicit 
declaration of function ‘do_mmap’]

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

Title:
  fglrx  not installed

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

Bug description:
  I have tried several ways to install the proprietry driver and always
  had to revert to the radeon driver.

  The radeon driver works good, but I thought i could reduce power
  consumption with my laptop.

  It seems that people succeded in installing version 13.1 catalyst with HD 3100
  13.2 doesn't support my card anymore

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.8.0-26-generic
  Date: Sun Jun 23 14:49:52 2013
  DistUpgraded: 2013-04-25 21:10:44,470 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RS780MC [Mobility Radeon HD 3100] 
[1002:9613] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff6a]
  InstallationDate: Installed on 2011-03-20 (827 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
  MachineType: TOSHIBA Satellite L300D
  MarkForUpload: True
  PackageVersion: (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic 
root=UUID=fbcc917e-3ef5-46d8-9662-ce18a544e8b0 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx (not installed): fglrx kernel module failed to build
  UpgradeStatus: Upgraded to raring on 2013-04-25 (59 days ago)
  dmi.bios.date: 09/01/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd09/01/2009:svnTOSHIBA:pnSatelliteL300D:pvrPSLC8E-02701CGR:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite L300D
  dmi.product.version: PSLC8E-02701CGR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2.0~git20130621.2d7e8377-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2.0~git20130621.2d7e8377-0ubuntu0sarvatt~raring
  version.xserver-xorg-core: xserver-xorg-core 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.1.99+git20130531.bd2557ea-0ubuntu0sarvatt~raring
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jun 24 00:57:23 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1194329] Re: inspiron crashes unexpectadly few times per day in 12.04

Here is more info that I collected from the web that might be relevant.
https://bugs.freedesktop.org/show_bug.cgi?id=49811

http://ubuntu.5.x6.nabble.com/Precise-SRU-PATCH-0-1-Fix-Turbo-Mode-on-
Gen6-Intel-Platforms-td5016709.html

http://lists.freedesktop.org/archives/intel-gfx/2012-July/019199.html

** Bug watch added: freedesktop.org Bugzilla #49811
https://bugs.freedesktop.org/show_bug.cgi?id=49811

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

Title:
inspiron crashes unexpectadly few times per day in 12.04

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

Bug description:
2013/06/24

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
I do not know what package is causing crash but syslogs is saying that drm
(direct rendering manager) is generating errors.
3) What you expected to happen
I do not not expect any crashes.
4) What happened instead
computer crashes unexpectadly few times per day.
(5)
I sent the ubuntu-bug -w.
It was saying that this is new install of ubuntu. That is not correc. The
ubuntu is here about 7 months.
(6)
I see no files in /var/crash/

This person (see link) has very similar crashes so I would call it
confirmation of a problem.
I believe that drm (direct rendering manager) is sick.

This link is a person showing same problems as I do implicating drm.

http://askubuntu.com/questions/300147/how-can-i-troubleshoot-why-ubuntu-keeps-crashing-on-my-laptop/312343#312343

My story.
I have DELL Inspiron 14z. Run Ubuntu 12.04. Gnome classic.
I have installed VMWare and other things.
Today I have uninstalled VMware tools, but I still see the errors, although
so far in 6 hours the computer did not crash. That can change at any time.

Have been running 12.04 on this hw from the time I got the computer for about
7 months.
It was well behaved for most time.
Few weeks ago (May 2013?) it started to crash once a week and then started to
crash more.
Some bad days crashes 3 times in one day.
I suspected heat problem and replaced fan+sink and also updated BIOS
but the computer still crashed after those changes.
Ubuntu is updating itself every night.

My story is similar to Peter on the link above.
My computer worked fine, then few weeks ago started to crash
with either complete shutdown on frozen desktop.

At one time this was the last message in the log file before it
crashed completely.
I have two types of errors like Peter and both caused by drm (direct
rendering manager).
As you can see from the gap in time this was the last error before system
died.

Jun 23 18:50:54 mycomputer bluetoothd[904]: Endpoint unregistered:
sender=:1.32 path=/MediaEndpoint/A2DPSink
Jun 23 18:51:42 mycomputer kernel: [ 111.363166] [drm:gen6_sanitize_pm]
*ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected
1707, was 1700
//see time gap before reboot
Jun 23 18:55:31 mycomputer kernel: [ 340.123935] CPU2: Package power limit
notification (total events = 229)

But note that on that day I saw this error 6 times but the system
crashed only 3 times.

I also like Peter have another error:

Jun 23 19:21:55 mycomputer kernel: [ 36.323966] [drm] Driver supports
precise vblank timestamp query.
Jun 23 19:21:55 mycomputer kernel: [ 36.324114]
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

Both of these errors are caused by drm (direct rendering manager).

The sanitize_pm seems to be more correlated with crashes.
It occurred 6 times in one day. There were 3 crashes, 2 were dead computer,
1 was dead desktop). One of the 6 errors was the last log message before
computer died.

Thank you for listening.
If you need more info pls ask.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.4.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
Uname: Linux 3.2.0-48-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
CheckboxSubmission: afe2ded547557fc4fff99d53b4a3c684
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Mon Jun 24 18:34:40 2013
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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

--
Mailing list: https://launchpad.net/~des

[Desktop-packages] [Bug 1194329] [NEW] inspiron crashes unexpectadly few times per day in 12.04

Public bug reported:

2013/06/24

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
lsb_release -rd
Description:Ubuntu 12.04.2 LTS
Release:12.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
I do not know what package is causing crash but syslogs is saying that drm 
(direct rendering manager) is generating errors.
3) What you expected to happen
I do not not expect any crashes.
4) What happened instead
computer crashes unexpectadly few times per day.
(5)
I sent the ubuntu-bug -w.
It was saying that this is new install of ubuntu. That is not correc. The 
ubuntu is here about 7 months.
(6)
 I see no files in /var/crash/


This person (see link) has very similar crashes so I would call it confirmation 
of a problem.
I believe that drm (direct rendering manager) is sick.

This link is a person showing same problems as I do implicating drm.
http://askubuntu.com/questions/300147/how-can-i-troubleshoot-why-ubuntu-keeps-crashing-on-my-laptop/312343#312343
 

My story.
I have DELL Inspiron 14z. Run Ubuntu 12.04. Gnome classic.
I have installed VMWare and other things.
Today I have uninstalled VMware tools, but I still see the errors, although so 
far in 6 hours the computer did not crash. That can change at any time.

Have been running 12.04 on this hw from the time I got the computer for about 7 
months.
It was well behaved for most time.
Few weeks ago (May 2013?) it started to crash once a week and then started to 
crash more.
Some bad days crashes 3 times in one day.
I suspected heat problem and replaced fan+sink and also updated BIOS
 but the computer still crashed after those changes.
Ubuntu is updating itself every night.

My story is similar to Peter on the link above.
My computer worked fine, then few weeks ago started to crash
with either complete shutdown on frozen desktop.

At one time this was the last message in the log file before it
crashed completely.
I have two types of errors like Peter and both caused by drm (direct rendering 
manager).
As you can see from the gap in time this was the last error before system died.

Jun 23 18:50:54 mycomputer bluetoothd[904]: Endpoint unregistered: sender=:1.32 
path=/MediaEndpoint/A2DPSink
Jun 23 18:51:42 mycomputer kernel: [  111.363166] [drm:gen6_sanitize_pm] 
*ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 
1707, was 1700
//see time gap before reboot
Jun 23 18:55:31 mycomputer kernel: [  340.123935] CPU2: Package power limit 
notification (total events = 229)


But note that on that day I saw this error 6 times but the system
crashed only 3 times.

I also like Peter have another error:

Jun 23 19:21:55 mycomputer kernel: [   36.323966] [drm] Driver supports precise 
vblank timestamp query.
Jun 23 19:21:55 mycomputer kernel: [   36.324114] 
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed


Both of these errors are caused by drm (direct rendering manager).

The sanitize_pm seems to be more correlated with crashes.
It occurred 6 times in one day. There were 3 crashes, 2 were dead computer,
1 was dead desktop). One of the 6 errors was the last log message before
computer died.

Thank you for listening.
If you need more info pls ask.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.4.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
Uname: Linux 3.2.0-48-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
CheckboxSubmission: afe2ded547557fc4fff99d53b4a3c684
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Mon Jun 24 18:34:40 2013
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug direct-rendering-manager precise

** Attachment added: "my syslog file for bad day with 3 crashes"
   
https://bugs.launchpad.net/bugs/1194329/+attachment/3712951/+files/syslogs20130623.txt

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

Title:
  inspiron crashes unexpectadly few times per day in 12.04

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

Bug description:
  2013/06/24

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I do not know what package is causing crash but syslogs is saying that drm 
(direct rendering manager) is generating er

[Desktop-packages] [Bug 1194329] Re: inspiron crashes unexpectadly few times per day in 12.04