← Back to team overview

desktop-packages team mailing list archive

[Bug 706231] Re: Ubuntu 10.10 gets freeze in few minutes, when the power supply is disconnected (working with battery)

 

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!


** Changed in: gnome-utils (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  Ubuntu 10.10 gets freeze in few minutes, when the power supply is
  disconnected (working with battery)

Status in “gnome-utils” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-utils

  Sometimes is just booting the system, and other wait for some minutes.
  I have used 32 and 64bit, and the error is the same.
  No problem if the pc is working connected to the power supply.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-system-log 2.31.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
  Uname: Linux 2.6.35-24-generic-pae i686
  Architecture: i386
  Date: Sat Jan 22 11:33:49 2011
  ExecutablePath: /usr/bin/gnome-system-log
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-utils
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1523): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:1531): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
   (evolution-alarm-notify:1524): libecal-WARNING **: Cannot get cal from factory: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

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