-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Cross-post for those not signed up on the trinity-announce mailing list: http://trinity-announce.pearsoncomputing.net/?0::31
Note that a lot of work has gone into improving the download/mirror system since RC1; please test and report any issues with installation and/or download to this list.
Thanks!
Tim
On Tuesday 02 December 2014 22:14:23 Timothy Pearson wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Cross-post for those not signed up on the trinity-announce mailing list: http://trinity-announce.pearsoncomputing.net/?0::31
Note that a lot of work has gone into improving the download/mirror system since RC1; please test and report any issues with installation and/or download to this list.
Can one just upgrade from rc1? Or do I need to reinstall?
Sorry that I hadn't reported back. I have been away. First impressions very favourable. I'm not allowed to love it, am I? But thank you so much for Bitstream Vera fonts!!!
I have to set Mint to allow root log in in order to use the Control Center to alter things that require administrator mode, before I can fully test. But shall obviously do so - I am just not as fast as you lot.
Lisi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Tuesday 02 December 2014 22:14:23 Timothy Pearson wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Cross-post for those not signed up on the trinity-announce mailing list: http://trinity-announce.pearsoncomputing.net/?0::31
Note that a lot of work has gone into improving the download/mirror system since RC1; please test and report any issues with installation and/or download to this list.
Can one just upgrade from rc1? Or do I need to reinstall?
Upgrading from 3.5.13.x or any of the release candidates (in this case just RC1) is both supported and encouraged. When upgrading from 3.5.13.x just make sure you are not logged in to an active TDE session or you may run into (fixable) problems.
Sorry that I hadn't reported back. I have been away. First impressions very favourable. I'm not allowed to love it, am I? But thank you so much for Bitstream Vera fonts!!!
I have to set Mint to allow root log in in order to use the Control Center to alter things that require administrator mode, before I can fully test. But shall obviously do so - I am just not as fast as you lot.
Glad you like it!
Tim
Are there any release notes that sumarize list of new features and bugfixes since previous stable release?
Janek
On 12/03/2014 07:30 PM, Jan Stolarek wrote:
Are there any release notes that sumarize list of new features and bugfixes since previous stable release?
Janek
There is a page in the etherpad: trinity.etherpad.trinitydesktop.org/78 I am also working on a release note page for R14.0.0, but it is not yet complete.
Cheers Michele
just a note for those who speak/read german: http://www.pro-linux.de/news/1/21799/trinity-mit-zweitem-veroeffentlichungsk... comments/trinity promotion welcome :)
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
just a note for those who speak/read german: http://www.pro-linux.de/news/1/21799/trinity-mit-zweitem-veroeffentlichungsk... comments/trinity promotion welcome :)
Werner
I can only read a little bit of German but what I was able to pick up looks good. Kudos to the person(s) who translated/picked up our release candidate notification!
Tim
ok, here is a first short report about RC2: - installation/upgrade from 3.5.13.2 (debian wheezy) did not go through in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though. - seems to work mostly, so far, but still some glitches: - konact works, but crashes reproducable upon exit. - some applications are missing/not available: kate kwrite kradio should I file bug reports about that ? Werner
On Thursday 04 December 2014 11.37:33 Werner Joss wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through in
one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
I also had to use apt-get dist-update to get R14 running, but only one time.
But I have another problem: On R14 I can setup a "link to device" (an nfs share here) but it's not working: once the link is created, I get four tabs (General, permissions, meta-info and preview) where I used to have five ("device" is gone).
So the link is not working (mounting per hand does work). I rely heavily on these links so R14 is not usable at this point for me. I don't know if this is one of the "not yet ready" elements or a "bug"?
Thierry
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Thursday 04 December 2014 11.37:33 Werner Joss wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
I also had to use apt-get dist-update to get R14 running, but only one time.
But I have another problem: On R14 I can setup a "link to device" (an nfs share here) but it's not working: once the link is created, I get four tabs (General, permissions, meta-info and preview) where I used to have five ("device" is gone).
So the link is not working (mounting per hand does work). I rely heavily on these links so R14 is not usable at this point for me. I don't know if this is one of the "not yet ready" elements or a "bug"?
Thierry
This sounds like something that might have slipped through testing as I am not familiar with the feature you describe. In general, ever since R14 RC2 all software should be ready in its final functional form (even in RC1 this was mostly true but we ran into major problems with the compositor for that release); the only changes between RC2 and Final are to resolve some remaining crashes, minor defects, updated the documentation, etc.
Can you provide me with detailed reproduction instructions so that I can check for a quick fix?
Thanks!
Tim
On Thursday 04 December 2014 14.37:16 Timothy Pearson wrote:
On Thursday 04 December 2014 11.37:33 Werner Joss wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
I also had to use apt-get dist-update to get R14 running, but only one time.
But I have another problem: On R14 I can setup a "link to device" (an nfs share here) but it's not working: once the link is created, I get four tabs (General, permissions, meta-info and preview) where I used to have five ("device" is gone).
So the link is not working (mounting per hand does work). I rely heavily on these links so R14 is not usable at this point for me. I don't know if this is one of the "not yet ready" elements or a "bug"?
Thierry
This sounds like something that might have slipped through testing as I am not familiar with the feature you describe. In general, ever since R14 RC2 all software should be ready in its final functional form (even in RC1 this was mostly true but we ran into major problems with the compositor for that release); the only changes between RC2 and Final are to resolve some remaining crashes, minor defects, updated the documentation, etc.
Can you provide me with detailed reproduction instructions so that I can check for a quick fix?
Thanks!
Tim
So, this is what I can provide:
- two screenshots. Both show on the left the "create link" dialog (Create New -> Link to Device -> nfs). It shows five tabs, the middle one being "Device".
On the right you see the properties of an existing "Link to Device".
On the desktop of 3.5.13.2 you have the middle tab. On the desktop of 3.5.14.0.0 it does not show. The Link does not get the correct icon and it does not work either (although mount <mount point> works, so the nfs mount does work).
I also compared the Desktop Files, they are identical, so the problem is deeper.
Thierry
What the mother...
Why didn't you just send a copy of your binary tarballs? and thanks for the backup... I hope I do not forget to send this twice, too...
BTW, where can I get the wallpapers?
Regards, Jagged
On Friday 05 December 2014 17.11:58 Jagged O'Neill wrote:
What the mother...
Why didn't you just send a copy of your binary tarballs?
Sorry, don't unbderstand this one...
and thanks for the backup... I hope I do not forget to send this twice, too...
Sorry for this. I forgot to change the Identity to gmail (which usually results in my mail being refused by the list)... but it did come through. If this one does too then now trinity-users lets me send from my regular email account
BTW, where can I get the wallpapers?
Search the Internet :)
Regards, Jagged
Thierry
On Friday 05 December 2014 16:11:58 Jagged O'Neill wrote:
BTW, where can I get the wallpapers?
I'm sure that there must be others - but there are so many here that there must be something to your taste.
Lisi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through in
one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
Can you provide more specifics? I have not encountered these issues, especially the missing kate/kwrite problems. kradio-trinity is now tderadio-trinity so perhaps that's why it could not be found?
Thanks!
Tim
On Thursday 04 December 2014 14:32:58 Timothy Pearson wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
Can you provide more specifics? I have not encountered these issues, especially the missing kate/kwrite problems.
well, it looks like that: 'aptitude search kate' gives: c kate-trinity - advanced text editor for KDE and is not installable: 'sudo aptitude install kate-trinity': Kein Installationskandidat für kate-trinity gefunden
whereas 'aptitude search kwrite' gives: p kwrite - Einfacher grafischer Texteditor which is the kde4 version
kradio-trinity is now tderadio-trinity so perhaps that's why it could not be found?
'aptitude search tderadio' gives nothing.
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Thursday 04 December 2014 14:32:58 Timothy Pearson wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go
through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
Can you provide more specifics? I have not encountered these issues, especially the missing kate/kwrite problems.
well, it looks like that: 'aptitude search kate' gives: c kate-trinity - advanced text editor for KDE and is not installable: 'sudo aptitude install kate-trinity': Kein Installationskandidat für kate-trinity gefunden
whereas 'aptitude search kwrite' gives: p kwrite - Einfacher grafischer Texteditor which is the kde4 version
kradio-trinity is now tderadio-trinity so perhaps that's why it could not be found?
'aptitude search tderadio' gives nothing.
Werner
Looks like a problem with your APT sources then. Can you post the portion of your /etc/apt/sources.list file pertaining to TDE?
Thanks!
Tim
On Thursday 04 December 2014 15:19:59 Werner Joss wrote:
On Thursday 04 December 2014 14:32:58 Timothy Pearson wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it stopped with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
Can you provide more specifics? I have not encountered these issues, especially the missing kate/kwrite problems.
well, it looks like that: 'aptitude search kate' gives: c kate-trinity - advanced text editor for KDE and is not installable: 'sudo aptitude install kate-trinity': Kein Installationskandidat für kate-trinity gefunden
whereas 'aptitude search kwrite' gives: p kwrite - Einfacher grafischer Texteditor which is the kde4 version
kradio-trinity is now tderadio-trinity so perhaps that's why it could not be found?
'aptitude search tderadio' gives nothing.
hm, seems I messed something up here... I copied the relevant lines for wheezy from https://wiki.trinitydesktop.org/Ubuntu_Trinity_Beta_Repository_Installation_... to a file named /etc/apt/sources.list.d/trinity from which I thought all files in that location would be processed by aptitude. that seems not to be the case, as now I copied the lines to the bottom of my /etc/apt/sources.list file. now kate, kwrite could be installed, and tderadio-trinity is also there :) will do a full dist-upgrade and then report back... Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Thursday 04 December 2014 15:19:59 Werner Joss wrote:
On Thursday 04 December 2014 14:32:58 Timothy Pearson wrote:
ok, here is a first short report about RC2:
- installation/upgrade from 3.5.13.2 (debian wheezy) did not go
through
in one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it
stopped
with dependency errors. finally, competed, though.
- seems to work mostly, so far, but still some glitches:
- konact works, but crashes reproducable upon exit.
- some applications are missing/not available:
kate kwrite kradio should I file bug reports about that ? Werner
Can you provide more specifics? I have not encountered these issues, especially the missing kate/kwrite problems.
well, it looks like that: 'aptitude search kate' gives: c kate-trinity - advanced text editor for KDE and is not installable: 'sudo aptitude install kate-trinity': Kein Installationskandidat für kate-trinity gefunden
whereas 'aptitude search kwrite' gives: p kwrite - Einfacher grafischer Texteditor which is the kde4 version
kradio-trinity is now tderadio-trinity so perhaps that's why it could not be found?
'aptitude search tderadio' gives nothing.
hm, seems I messed something up here... I copied the relevant lines for wheezy from https://wiki.trinitydesktop.org/Ubuntu_Trinity_Beta_Repository_Installation_... to a file named /etc/apt/sources.list.d/trinity from which I thought all files in that location would be processed by aptitude. that seems not to be the case, as now I copied the lines to the bottom of my /etc/apt/sources.list file. now kate, kwrite could be installed, and tderadio-trinity is also there :) will do a full dist-upgrade and then report back... Werner
I'm pretty sure a ".list" suffix is required for files under /etc/apt/sources.list.d/.
Tim
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after installing tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
Thanks!
Tim
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after installing tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after installing tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work? DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such as the tdepim suite.
If you can, please use DrKonqui to generate the crash report. The gdb backtrace provided unfortunately doesn't show anything I can fix.
Thanks!
Tim
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after installing tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such as the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
btw., the crash only occurs when I have used akregator (fetched new feeds) from inside kontact before, so seems to be related to that, somehow.
werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after
installing
tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such as the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
It *should* be automatic; I've never seen a case where DrKonqui does not pop up when a program crashes--provided DrKonqui is actually installed and you are running programs from within a TDE desktop session.
If DrKonqui is not popping up, and since you were able to get a backtrace, then I presume you are running akregator from within gdb? Try running it outside of gdb to see if you get the DrKonqui crash popup.
Thanks!
Tim
On Friday 05 December 2014 16:18:24 Timothy Pearson wrote:
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
- konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after
installing
tdepim-trinity-dbg) of the crash? Using the "Report Crash" button is preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such as the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
It *should* be automatic; I've never seen a case where DrKonqui does not pop up when a program crashes--provided DrKonqui is actually installed and you are running programs from within a TDE desktop session.
If DrKonqui is not popping up, and since you were able to get a backtrace, then I presume you are running akregator from within gdb? Try running it outside of gdb to see if you get the DrKonqui crash popup.
sorry, Tim, I provided wrong information - it was indeed drkonqi where I got the mentioned report from :
3652 ? S 0:00 drkonqi -display :0 --appname kontact --signal 11 --pid 3456 --appversion 1.2.9 (enterprise35 0.20100827.1168748) --programname Kontact --bugaddress http://bugs.trinitydesktop.org --startupid debian;1417804842;441769;3412_TIME55532
(I just presumed there must be some drkonqi caption or thelike in the crash popup window...)
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Friday 05 December 2014 16:18:24 Timothy Pearson wrote:
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
> - konact works, but crashes reproducable upon exit.
Forgot to address this. Have you sent in a backtrace (after
installing
tdepim-trinity-dbg) of the crash? Using the "Report Crash" button
is
preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such
as
the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
It *should* be automatic; I've never seen a case where DrKonqui does not pop up when a program crashes--provided DrKonqui is actually installed and you are running programs from within a TDE desktop session.
If DrKonqui is not popping up, and since you were able to get a backtrace, then I presume you are running akregator from within gdb? Try running it outside of gdb to see if you get the DrKonqui crash popup.
sorry, Tim, I provided wrong information - it was indeed drkonqi where I got the mentioned report from :
3652 ? S 0:00 drkonqi -display :0 --appname kontact --signal 11 --pid 3456 --appversion 1.2.9 (enterprise35 0.20100827.1168748) --programname Kontact --bugaddress http://bugs.trinitydesktop.org --startupid debian;1417804842;441769;3412_TIME55532
(I just presumed there must be some drkonqi caption or thelike in the crash popup window...)
Werner
And it was my fault for not reading to the end of the provided file. I assumed since the crash was not sent in to the TDE dump server that you had just attached GDB to the process...
In any case it still doesn't look like I can glean much from the dump as the trace is shortened by the possibly corrupted stack.
Tim
On Friday 05 December 2014 20:32:45 Timothy Pearson wrote:
On Friday 05 December 2014 16:18:24 Timothy Pearson wrote:
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote: > > - konact works, but crashes reproducable upon exit. > > Forgot to address this. Have you sent in a backtrace (after
installing
> tdepim-trinity-dbg) of the crash? Using the "Report Crash" button
is
> preferred as I will get a properly formatted dump.
ok, the crash report is here: https://paste.kde.org/pzbyjlkfa hope it helps (done after installing tdepim debug package)
Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs such
as
the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
It *should* be automatic; I've never seen a case where DrKonqui does not pop up when a program crashes--provided DrKonqui is actually installed and you are running programs from within a TDE desktop session.
If DrKonqui is not popping up, and since you were able to get a backtrace, then I presume you are running akregator from within gdb? Try running it outside of gdb to see if you get the DrKonqui crash popup.
sorry, Tim, I provided wrong information - it was indeed drkonqi where I got the mentioned report from :
3652 ? S 0:00 drkonqi -display :0 --appname kontact --signal 11 --pid 3456 --appversion 1.2.9 (enterprise35 0.20100827.1168748) --programname Kontact --bugaddress http://bugs.trinitydesktop.org --startupid debian;1417804842;441769;3412_TIME55532
(I just presumed there must be some drkonqi caption or thelike in the crash popup window...)
Werner
And it was my fault for not reading to the end of the provided file. I assumed since the crash was not sent in to the TDE dump server that you had just attached GDB to the process...
In any case it still doesn't look like I can glean much from the dump as the trace is shortened by the possibly corrupted stack.
ok, here is another dump: https://paste.kde.org/pvrbpvonl maybe this is more useful ?
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Friday 05 December 2014 20:32:45 Timothy Pearson wrote:
On Friday 05 December 2014 16:18:24 Timothy Pearson wrote:
On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
> On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote: >> > - konact works, but crashes reproducable upon exit. >> >> Forgot to address this. Have you sent in a backtrace (after
installing
>> tdepim-trinity-dbg) of the crash? Using the "Report Crash"
button
is
>> preferred as I will get a properly formatted dump. > > ok, the crash report is here: > https://paste.kde.org/pzbyjlkfa > hope it helps (done after installing tdepim debug package) > > Werner
Did DrKonqui not work?
no, unfortunately not, it is installed, though.
DrKonqi generates additional helpful information vs. a straight gdb 'bt', especially with multithreaded programs
such
as
the tdepim suite.
is there a way to trigger drkonqi start when a crash happens ?
It *should* be automatic; I've never seen a case where DrKonqui does
not
pop up when a program crashes--provided DrKonqui is actually
installed
and you are running programs from within a TDE desktop session.
If DrKonqui is not popping up, and since you were able to get a backtrace, then I presume you are running akregator from within gdb? Try
running
it outside of gdb to see if you get the DrKonqui crash popup.
sorry, Tim, I provided wrong information - it was indeed drkonqi where I got the mentioned report from :
3652 ? S 0:00 drkonqi -display :0 --appname kontact
--signal
11 --pid 3456 --appversion 1.2.9 (enterprise35 0.20100827.1168748) --programname Kontact --bugaddress http://bugs.trinitydesktop.org --startupid debian;1417804842;441769;3412_TIME55532
(I just presumed there must be some drkonqi caption or thelike in the crash popup window...)
Werner
And it was my fault for not reading to the end of the provided file. I assumed since the crash was not sent in to the TDE dump server that you had just attached GDB to the process...
In any case it still doesn't look like I can glean much from the dump as the trace is shortened by the possibly corrupted stack.
ok, here is another dump: https://paste.kde.org/pvrbpvonl maybe this is more useful ?
Werner
Yes, it is more useful--at least this one correctly identified the origin of the crash.
Can you file a bug report on this? I am likely to lose track of it otherwise, and doing so will allow other developers to pick it up if they can get to it before I have time.
Tim
On Friday 05 December 2014 20:57:03 Timothy Pearson wrote:
ok, here is another dump: https://paste.kde.org/pvrbpvonl maybe this is more useful ?
Werner
Yes, it is more useful--at least this one correctly identified the origin of the crash.
Can you file a bug report on this? I am likely to lose track of it otherwise, and doing so will allow other developers to pick it up if they can get to it before I have time.
ok, done: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2235
Werner
-
Jagged O'Neill -
Jan Stolarek -
Lisi Reisz -
Michele Calgaro -
Thierry de Coulon -
Thierry de Coulon -
Timothy Pearson -
Werner Joss