desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #02860
[Bug 826937] Re: gwibber crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: 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.
*** This bug is a duplicate of bug 749842 ***
https://bugs.launchpad.net/bugs/749842
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #749842, 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.
** Tags removed: need-duplicate-check
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/bugs/826937/+attachment/2280834/+files/Dependencies.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/826937/+attachment/2280835/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/826937/+attachment/2280836/+files/ProcStatus.txt
** This bug has been marked a duplicate of bug 749842
gwibber crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: 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.
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/826937
Title:
gwibber crashed with DBusException in call_blocking():
org.freedesktop.DBus.Error.NoReply: 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.
Status in “gwibber” package in Ubuntu:
New
Bug description:
Tried to open Gwibber after booting. Internet connection was a little
unstable (router overheated).
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 3.0.0.1-0ubuntu3
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: Mon Aug 15 20:17:35 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: 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.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/826937/+subscriptions