This bug was fixed in the package apport - 2.3-0ubuntu1
---
apport (2.3-0ubuntu1) quantal; urgency=low
* New upstream release:
- launchpad.py: Rework test suite to not use Launchpad's +storeblob
facility at all any more. It almost never works on staging and is
horrib
dino99 [2012-07-03 11:39 -]:
> - there is no network speed issue here
> - some crash reports can be filled without trouble
> - but some others push that error, like nautilus & gnome-panel crashes
>
> so its strange.
It's more prone to happen for larger reports. It would happen as soon
as tra
Thanks Martin,
add some more comments:
- there is no network speed issue here
- some crash reports can be filled without trouble
- but some others push that error, like nautilus & gnome-panel crashes
so its strange.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Thanks for the updated traces! This was indeed very helpful. This
apparently happens if the data upload is either very slow, or gets
interrupted due to network hangs. I believe I fixed this now in trunk.
If you want to test it immediately, you can do
wget
http://bazaar.launchpad.net/~apport-hack
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013334
Title:
slice indices must be integers or None or have an __index__ method
To manage notifications about this bug go
Still cant report a crash on quantal i386 if i select "report this
error"
i get the error filled on title, but also:
ERROR: hook /usr/share/apport/general-hooks/medibuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 747, in
add_ho
With the updates from today(no apport ones, but many other) apport has
got some functionality back.
It can connect to launchpad in general now on my system.
Apport crashed now on the attached xsane.crash file and is able to
detect it's own crash and could report it here:
https://bugs.launchpad.n
On my Intel box:
ubuntu@ubuntu:~$ wget http://people.canonical.com/~pitti/tmp/ui.py
--2012-06-29 19:09:15-- http://people.canonical.com/~pitti/tmp/ui.py
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:80
No luck finding the .crash file, probably due to my own ineptitude.
I'm testing on actual hardware with a burned DVD and a wired DSL
connection:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Eth
Just finally giving this a new look but the heat wave here is both
cooking my brain and causing frequent power outages so I need to post
things in rather incomplete bits and pieces, just bear with me :^(
I specifically wanted to post this terminal output before searching for
the .crash file:
ubun
** Attachment added: "the xsane.crash file"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1013334/+attachment/3207854/+files/_usr_bin_xsane.1000.crash
** Changed in: apport (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member
Additional in moment I could not upload with success any crashreport.
So, the problem is not limited to the xsane crash I have attached here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013334
Tit
Request from commen 14
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1013334/comments/14
--
I will attach the xsane.crash file from this reproducing.
Your are correct, I use VirtualBox4.1.18 from Felix Greyers repositorie
f
** Description changed:
I am on Ubuntu12.10 Quantal 64bit with apport2.2.2-0ubuntu2.
On reporting a automatically gathered crash apport failed to connect to
crash database and tells (invalid):
"Network problems
Cannot connect to crash database, please check your Internet connect
@ Martin,
The tests I performed in both comment #11 and #12 were done using a live
CD, not an installed version of Ubuntu. But I'd seen this in Lubuntu
after installation, presumably due to a grub-install error during
installation.
I'm just headed off to bed ATM (too tired to make sense of anythi
I tried this on the 20120627 i386 and amd64 Ubuntu live system (I think
that's exactly the same image as you did), in kvm. First right after
booting into the live desktop, and a second time after "sudo apt-get
update". I also tried it on my workstation (current Quantal amd64).
In each of those I r
on Quantal i386 logged as gnome-classic
i also get nautilus crashing on logout, but i cant report because of
this error:
slice indices must be integers or None or have an __index__ method
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Tags added: i386
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013334
Title:
slice indices must be integers or None or have an __index__ method
To manage notifications about this bug go to:
htt
Just came in to take a break and decided to try Ubuntu live i386
20120627 (presumably Alpha 2) to see if the above could be reproduced
and it can be.
Just boot to the live desktop, open the terminal, and then run "ubuntu-
bug casper".
I'm sure it can be reproduced with other methods, particularly
I still had my Ubuntu i386 20120626.1 disc laying here that I'd first
seen this error with as reported in dup bug 1018032 so I booted it, DLed
the requested file to /home, then ran the requested command.
Next I tried running ubuntu-bug apport which failed to reproduce this
bug (but I filed bug 101
It apparently crashes somewhere in launchpad.py's upload(). But I went
through all slices in launchpad.py, and none looks prone to invalid
indexes, so right now I don't have a good guess what goes wrong.
Presumably it's not directly in launchpad.py, but in giving bad data to
the email module.
Can
Thanks! This is indeed not a networ error at all. I fixed apport's trunk
to crash properly on this error instead of claiming it to be a network
error. Unfortunately I cannot reproduce the actual issue with your
attached .crash file.
Can you reproduce the error at will? If so, I'd like to hand you
22 matches
Mail list logo
