[Expired for yelp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: yelp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/b
Ok. I installed Maverick, and now the situation has became even worst.
Help program crashes during its startup. The main windows tries to open,
but after a while it crashes (without displaying nothing).
My previous complaint was about the procedure
https://wiki.ubuntu.com/DebuggingProcedures whic
Cesare Mastroianni, thank you for working on this bug and making Ubuntu
better. In order to test this issue in Maverick, one may do so via a
Live CD environment -> http://releases.ubuntu.com/10.10/ and/or in a
VirtualBox VM environment ( apt-get install virtualbox-ose or
http://www.virtualbox.org/w
Sorry to bother You with further comments.
Let me complain about this bug management method.
I notified You a REAL bug. I spent many time (hours) to investigate the
problem according to the instruction You wrote me. I discovered that the
crash vanished when running the application "from inside" v
[Expired for yelp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: yelp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
https://bugs.launchpad.net/b
Can't say about Maverick, I never tried it. Sorry.
CM
--
gnome-help crashed (segmentation fault) while printing
https://bugs.launchpad.net/bugs/580206
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bugs mai
Does this happen in Maverick?
** Changed in: yelp (Ubuntu)
Status: New => Incomplete
--
gnome-help crashed (segmentation fault) while printing
https://bugs.launchpad.net/bugs/580206
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
... last TXT file of the day - running valgrind with options "--track-
origins=yes --leak-check=full -v" ...
** Attachment added: "TXT file generated by valgrind more verbose options (no
crash - many errors)"
http://launchpadlibrarian.net/50911107/valgrind-log-2.txt
--
gnome-help crashed (se
Sorry to bother You again ... Even if the execution of gnome-help inside
valgrind doesn't generate any crash, I saw that the log output of
valgrind is not "empty". Maybe the new attached TXT file could display
some info about the bug.
I'm not able to understand, but it seems that valgrind detected
After a long time and a difficult task (at least for me) I had the
dbgsym installed. Then I run valgrind. Please, see comment #7: when I
run gnome-help "inside" valgrind the bug disappear, I mean gnome-help
won't crash while printing (please, remember that the bug actually was a
crash when printing
Thanks.
I have a problem. I run "./list-dbgsym-packages.sh -p `pidof gnome-help`
-a -t" and I received a long list of dbgsym packages. I passed that list
to "sudo apt-get install" and I received back an error issue. I
translate it from Italian to English (I hope to be able to):
"Some packages ca
We need a valgrind log with the yelp, libgtk2 and libglib2 dbgsym
packages installed, the one you submitted is missing a lot of symbols.
we prefer reports submitted with apport, so please do it that way next
time, to know how to do it, follow the instructions i've previously said
to You. Thanks.
*
Thanks again for Your help.
I should say that the crash bug of Yelp happens here daily, and that
this SW is not usable for printing. Today I collected another crash for
You to help in debugging. Valgrin is not able to catch the problem (see
my comment #7), but GDB is able.
So, please, see the att
Hi there.
I try to use valgrind. I then run gnome-help from "inside" valgrind. I
repeated EXACTLY the same steps-actions that usually generate the crash.
No crash happened. See attached file gnome-help-NOT-crash.txt
Then I ran gnome-help alone, without valgrind. I repeated EXACTLY the
same steps-
** Attachment added: "gnome-help command CRASH logfile"
http://launchpadlibrarian.net/48800770/_usr_bin_yelp.1000.crash
--
gnome-help crashed (segmentation fault) while printing
https://bugs.launchpad.net/bugs/580206
You received this bug notification because you are a member of Ubuntu
Deskto
See attached TXT file from the latest crash today.
CM
** Attachment added: "gnome-help command line output - CRASH"
http://launchpadlibrarian.net/48799725/gnome-help-crash.txt
** Changed in: yelp (Ubuntu)
Status: Invalid => New
--
gnome-help crashed (segmentation fault) while printi
Hi there. Please, would You explain me why has this bug now been changed to
"Invalid" ?
Many thanks in advance.
Ciao from Italy
CM
--
gnome-help crashed (segmentation fault) while printing
https://bugs.launchpad.net/bugs/580206
You received this bug notification because you are a member of Ub
** Changed in: yelp (Ubuntu)
Status: New => Invalid
--
gnome-help crashed (segmentation fault) while printing
https://bugs.launchpad.net/bugs/580206
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bugs
Many thanks. See here new info and comments.
1) The problem reported yesterday happened onto a i386 computer. Today I
found again the same crash problem onto a AMD Sempron machine, running
the same up-to-date Lucid system.
2) No crash file was generated, nor running gnome-help inside GDB, nor
run
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48411064/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/48411065/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/48411066/ProcStatus.txt
** Attachm
21 matches
Mail list logo
