I started my desktop one day last week and wanted to open such a device, but Dolphin would not let me. I was surprised because the previous day I had no trouble opening Dolphin. Something must have happened overnight.
Instead that morning Dolphin crashed and returned a going away message which said the following, among other things:
The application Dolphin (d3lphin) crashed and caused the signal 11 (SIGSEGV).
Another message provided by the TDE crash handler read as follows:
Could not generate a backtrace because the debugger 'gbd' was not found.
I understand that the generic term for what happened is called a 'segmentation fault' and I know what that phrase means. What I do not know however it what to do to fix one when it occurs.
I did however discover that I could access from a terminal and through Gwenview all my portable devices. Even so, the absence of Dolphin limited my full and effective use of the computer.
I also tried using Konqueror but encountered problems with it as well. When I tried to open a device I expected that I would be able to view a list of the directories in the selected device. Instead Kwrite was activated, but said that it could not proceed because what Kwrite found there were directories rather than files.
I would certainly be grateful for any help to me free myself from this dilemma.
Regards, Ken Heard
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 2023/03/12 05:00 PM, Ken Heard via tde-users wrote:
I would certainly be grateful for any help to me free myself from this dilemma.
A bit more info would help...
0) is it a repeatable issue (a.k.a. did you try again and did it do the same)? 1) which TDE version? which distro? 2) steps to reproduce the issue
Cheers Michele
On 2023-03-12 15:21, Michele Calgaro via tde-users wrote:
On 2023/03/12 05:00 PM, Ken Heard via tde-users wrote:
I would certainly be grateful for any help to me free myself from this dilemma.
A bit more info would help...
- is it a repeatable issue (a.k.a. did you try again and did it do the
same)?
Yes is is repeatable and has been that way for three days including today. Every time I click on the 'media' directory Dolphin crashes as described.
- which TDE version? which distro?
mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing bullseye deps main Debian Bullseye statble
- steps to reproduce the issue
I am not sure what you mean by 'reproduce the issue'. All I know is that one morning last week I could not use Dolphin to open portable storage devises; whereas the previous evening just before closing the computer I was able to do so.
Cheers Michele
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
- is it a repeatable issue (a.k.a. did you try again and did it do the same)?
Yes is is repeatable and has been that way for three days including today. Every time I click on the 'media' directory Dolphin crashes as described.
Does this happen also after a reboot or logout/login?
- which TDE version? which distro?
mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing bullseye deps main Debian Bullseye statble
Thanks, I am on bookworm, but other than that I also use testing, I should be able to try on my system tomorrow.
- steps to reproduce the issue
I am not sure what you mean by 'reproduce the issue'.
What do you do to have the issue? for example, plug in USB stick and try to mount from Dolphin? I can try the same steps on my system if you can be a bit more detailed.
Cheers Michele
Eureka! I found the source of my problem and fixed it. A full report will follow. Thanks Michele for your help; you showed me the way.
Regards, ken
On 2023-03-12 15:00, Ken Heard via tde-users wrote:
I started my desktop one day last week and wanted to open such a device, but Dolphin would not let me. I was surprised because the previous day I had no trouble opening Dolphin. Something must have happened overnight.
Instead that morning Dolphin crashed and returned a going away message which said the following, among other things:
The application Dolphin (d3lphin) crashed and caused the signal 11 (SIGSEGV).
Another message provided by the TDE crash handler read as follows:
Could not generate a backtrace because the debugger 'gbd' was not found.
I understand that the generic term for what happened is called a 'segmentation fault' and I know what that phrase means. What I do not know however it what to do to fix one when it occurs.
I did however discover that I could access from a terminal and through Gwenview all my portable devices. Even so, the absence of Dolphin limited my full and effective use of the computer.
I also tried using Konqueror but encountered problems with it as well. When I tried to open a device I expected that I would be able to view a list of the directories in the selected device. Instead Kwrite was activated, but said that it could not proceed because what Kwrite found there were directories rather than files.
I would certainly be grateful for any help to me free myself from this dilemma.
Regards, Ken Heard
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 2023/03/13 06:13 PM, Ken Heard via tde-users wrote:
Eureka! I found the source of my problem and fixed it. A full report will follow. Thanks Michele for your help; you showed me the way.
Regards, ken
Will be happy to hear the full story :-) I didn't have problems here, so I suspected it was something local, but glad to hear further when you have time. Cheers Michele
-
Ken Heard -
Ken Heard -
Michele Calgaro