Tiny Core Extensions > TCE Bugs

emelfm2 segfaults on "back" button

(1/4) > >>

Leee:
I've run into an issue with emelfm2 and I wonder if there's some simple fix that I'm overlooking.

* I'm using Core 14.0 / x86_64, loading Xorg-7.7, Xprogs, aterm, jwm, wbar and emelfm2
* I start emelfm2 and in either pane navigate to some other directory than where it started
* I move the mouse up to that pane's "back" button and hover there
* a drop-down menu of directories to which I might want to go back appears
* I move the mouse cursor down onto that menu
* if I click on one of the entries, it works as expected
* if I move the mouse off the bottom or either side of the drop-down menu, it segfaults and the emelfm2 window closes
* if I move the mouse back up to the "back" button, it is ok if I'm moving the mouse quickly but there is a little gap between the drop-down menu and the button so if I'm too slow crossing it, it still segfaults.The end result is that simply moving the mouse cursor around on the screen will crash emelfm2 if it happens to cross the "back" button.


If I've started emelfm2 from a terminal session, the messages below are displayed in the terminal:
--- Code: ---tc@box:~$
tc@box:~$ emelfm2 &
tc@box:~$
(emelfm2:27483): GLib-GObject-CRITICAL **: 21:34:38.424: g_object_get_data: assertion 'G_IS_OBJECT (object)' failed

(emelfm2:27483): GLib-GObject-CRITICAL **: 21:34:38.424: g_object_set_data_full: assertion 'G_IS_OBJECT (object)' failed

[1]+  Segmentation fault         emelfm2
tc@box:~$

--- End code ---

The following lines are appended to the output of dmesg:

--- Code: ---emelfm2[27483]: segfault at 200000001 ip 00007fd6b8f123a7 sp 00007ffd8797e100 error 4 in libgtk-x11-2.0.so.0.2400.32[7fd6b8e80000+193000] likely on CPU 0 (core 0, socket 0)
Code: 55 48 89 fd 53 52 e8 10 fe ff ff f6 40 48 01 0f 85 06 01 00 00 4c 8b 75 70 48 89 c3 45 31 ed 41 bc 01 00 00 00 4d 85 f6 74 31 <49> 8b 3e e8 1a fa ff ff 48 89 c7 48 89 c2 e8 b2 ea ff ff 85 c0 74
--- End code ---


I'm using emelfm2 with Core 14.0 on x86_64 but I've verified this issue exists in every version of Core for the x_86_64 architecture later than 4.7.7 that includes emelfm2 in its repo - though the repos for 5.x through 8.x don't provide emelfm2.

I tried to fire up 4.7.7 to test there but that kernel doesn't boot on my current hardware.
When I used 4.7.7 for several years, I was using x86 architecture and I don't remember having this issue then... but I haven't done any 32 bit testing this week.
I can work around the issue by simply removing the "back" button from the toolbars of both panes of the emelfm2 window, but the "back" functionality seems pretty useful (when it works).


CentralWare:
Did you try FM3 by chance?

gadget42:
tl;dr: attempted to familiarize myself with this situation/software and find accurate and current information/resources/sources...failed.

off-topic perhaps, but still hopefully a thoughtful note/question(s)

is it just me or has wikipedia gone to the dogs?

followed a few links at https://en.wikipedia.org/wiki/EmelFM2 and was not impressed
(glad i didn't contribute the last time they had a begfest)
"references" "external links" and "repository" links all either didn't resolve or were questionable(for me at least)

where do we go to get accurate/correct/current/legitimate information?
(and how do we know we are all actually using/visiting the _same_ _exact_ code/content/source/webpage/website?)

more links:
https://emelfm.sourceforge.net/
https://emelfm2.net/

error message when attempting to follow link:
https://emelfm.sourceforge.net/old/

--- Quote ---An error has been encountered in accessing this page.

1. Server: emelfm.sourceforge.net
2. URL path: /old/
3. Error notes: NONE
4. Error type: 403
5. Request method: GET
6. Request query string: NONE
7. Time: 2024-02-05 10:16:19 UTC (1707128179)
--- End quote ---

CentralWare:
https://emelfm.sourceforge.net/ timed out a few times over the past 10 minutes; finally came up with way-back

--- Quote ---This website emelfm.sourceforge.net/ is currently offline. Cloudflare's Always Onlineā„¢ shows a snapshot of this web page from the Internet Archive's Wayback Machine. To check for the live version, click Refresh.
--- End quote ---

https://emelfm2.net/ is, however, online

https://github.com/tom2tom/emelfm2

Wiki...  has been crying the gimme' blues (last few+ years) about "hey, if you don't pay us, we're going to quit!" (lately they made it sound like a brutal take-over) but we'll see...  even Google looks as though they're just waiting for wiki to die -- most of their search results no longer contain "Cached" options -- either they're no longer storing data (unlikely) or they're getting ready to charge for it! :)

gadget42:
https://arstechnica.com/gadgets/2024/02/google-search-kills-off-cached-webpages/


--- Quote ---Cached links used to live under the drop-down menu next to every search result on Google's page. As the Google web crawler scoured the Internet for new and updated webpages, it would also save a copy of whatever it was seeing. That quickly led to Google having a backup of basically the entire Internet, using what was probably an uncountable number of petabytes of data. Google is in the era of cost savings now, so assuming Google can just start deleting cache data, it can probably free up a lot of resources.
--- End quote ---

*going to continue this on a new thread since it is way OT...give me a few minutes...

Navigation

[0] Message Index

[#] Next page

Go to full version