I can't see anything wrong with Apport here, and the blob upload code
hasn't changed in years literally.
I can perfectly well reproduce the error on production:
wget -O - --post-data="FORM_SUBMIT=1&field.blob=/etc/fstab"
https://launchpad.net/+storeblob
--2010-03-15 13:15:29-- https://launchp
For debugging this slightly better I committed a change to Apport to
display the exception string in the "network error" dialog box.
I can replicate it here, too.
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are
** Changed in: apport (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Martin Pitt
(pitti)
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
It doesn't work on Karmic as well. Besides, Lucid beta will be out in 3
days, not working apport will be a serious drawback...
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Somewhat similar (yet different) to what dino99 reports I find various
errors in my /home .xsession-errors and .xsession-errors.old:
One example:
system-config-printer-applet: failed to start PrinterDriversInstaller service:
org.freedesktop.DBus.Error.AccessDenied: Connection ":1.52" is not allo
Same here, I am trying to report a critical bung in plymouth. This is
the console output:
l...@grisell:~$ apport-bug plymouth
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such
file or directory
QFileSystemWatcher: failed to add paths: /home/leo/.config/ibus/bus
Bus::op
retry to send a crash today, and got:
(users-admin:7241): Gtk-CRITICAL **: gtk_list_store_set_valist:
assertion `VALID_ITER (iter, list_store)' failed
(users-admin:7241): Liboobs-WARNING **: There was an unknown error
communicating with the backends: Did not receive a reply. Possible
causes inclu
try to report today, here is the output:
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 354, in
app.run_argv()
File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 538, in run_argv
return self.run_update_report()
File "/usr/lib/python2.6/dist-pack
Il giorno sab, 13/03/2010 alle 21.18 +, Rick Spencer ha scritto:
> Can you guys please take a look when you get in on Monday? It's not a
> great situation when folks can't log bugs on the development release.
> Thanks.
I will se if I will get it again in Monday.
Regards,
Lorenzo D. (alias Bl
Can you guys please take a look when you get in on Monday? It's not a
great situation when folks can't log bugs on the development release.
Thanks.
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
** Changed in: launchpad
Assignee:
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
** Changed in: launchpad
Status: New => Confirmed
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100304)
Package: apport 1.13-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: luci
This happens also on ubuntu 9.10. Seems it's an launchpad problem. I get
"Can't connect to crash database, please check your internet
connection".
Regards,
Lorenzo D. (alias BlackZ).
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notifica
same problem by me: apport-cli on ubuntu lucid server:
*** Uploading problem information
The collected information is being sent to the bug tracking system.
This might take a few minutes.
68%
*** Error: Network problem
Cannot connect to crash database, please check your Internet connection.
Pre
My post #12 does not make sense. I shouldn't try to think so early in
the day.
I tried again to file a bug report using "ubuntu-bug" in Jaunty and the
browser behavior there is correct but I get the same error message.
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/53
** Description changed:
Binary package hint: apport
On latest lucid, apport will not connect via a verified establish
Internet connection.
STR:
1) Attempt to submit a crash report from /var/crash
2) Apport dialog titled "Network Problem" with the text, "Cannot connect to
crash d
I'm adding a launchpad task. 'HTTP Error 500: Internal Server Error'
doesn' t sound like a bug in apport and apport still uploads fine to
staging.launchpad.net
** Also affects: launchpad
Importance: Undecided
Status: New
--
Apport cannot connect to crash database
https://bugs.launchpad
This may be totally unrelated, but I also notice now that if I have
updates, and if I use Update Manager to review them, if I click on a
Launchpad link to review the changelog, instead of launching Firefox (or
opening a new tab if FF is open in another window) it staggers &
stumbles and finally ope
Ditto here, can't report severe hardware crashes !
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Looks like it finishes uploading the crash data, then fails just before
the browser would ordinarily be opened to finish the bug report
This can't be helping the Lucid release. I've had about 10 crashers fail
to submit over the past couple of days, and not a single success in that
time.
--
Appor
apport-cli gives a similar error message:
The collected information is being sent to the bug tracking system.
This might take a few minutes.
92%
*** Error: Network problem
Cannot connect to crash database, please check your Internet connection.
--
Apport cannot connect to crash database
https:/
** Changed in: apport (Ubuntu)
Importance: Undecided => High
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I had it using the crash reporter icon that appears in the top tray. It
gathered data, got partway through sending, and then whammo. Could not
connect to database. I thought it might've been my cell modem, but I
guess it wasn't.
--
Apport cannot connect to crash database
https://bugs.launchpad.ne
I get the same error message when attempting to file a bug with gnome-
control-center. I do manage to get as far as clicking on "Send Report".
I get this error message in the terminal (which is printed even before I click
"Send Report"):
Gtk-Message: Failed to load module "pk-gtk-module": libpk-g
i've reported today without problem ( bug 537962), so it might be a
"time out" problem or else on launchpad side and not a problem of apport
itself.
But still wonder why all the crashes are "silent" and half of them are
owned by root, strange.
--
Apport cannot connect to crash database
https://b
I've this problem
$ dpkg -s apport
Package: apport
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 2004
Maintainer: Martin Pitt
Architecture: all
Version: 1.13-0ubuntu2
Replaces: apport-cli, apport-gtk (<< 0.51)
Depends: python (>= 2.4), python-apport (>= 0.120), ls
The same message on 2.6.32- Lucid desktop16-generic #25-Ubuntu SMP Tue
Mar 9 16:33:52 UTC 2010 i686 GNU/Linux.
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
getting this on kubuntu 10.04 amd64 also .
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
I suspect this is actually a Launchpad problem. I've tried reporting
bugs using apport in both Lucid and Jaunty this AM and always get the
same error message:
Could not upload report data to crash database:
HTTP Error 500: Internal Server Error
--
Apport cannot connect to crash database
https:/
I just got that message too while trying to report a bug about the
kubuntu lucid i386 live disk that I had running in KVM.
** Tags added: lucid
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
Apport cannot connect to crash database
https://bugs.launchpad.net/bugs/538097
You re
30 matches
Mail list logo
