BUG Of the Day (BOTD)

Since bugs are such a common occurence in Logos, I thought there should be a 'Bug of the Day' just to celebrate the coming spring season.

Today's bug is fairly old, and I'm guessing Mac only (latest masOS, latest Verbum). Here, we've typed in a reference into a Text Comparison, hit enter, at which point, the ICC resource popup appears (along with the text comparison execution). The popup actually has nothing to do with anything on this window ... it's a resource on a window below this window. And clicking anywhere on this window (to remove it) does nothing ... solidly glued. Instead, one needs to click on the popup itself (part of the below-window) to get rid of it.

This is one of several bugs in the Text Comparison tool.

And yes, patience ... tomorrow's BOTD will be ... tomorrow (if one pops up during the day).

Find more posts tagged with

Desktop App

Comments

Dave Hooton

Today's bug is fairly old, and I'm guessing Mac only (latest masOS, latest Verbum).

Could not reproduce on Verbum, Windows 11.

Mike Binks

This is one of several bugs in the Text Comparison tool.

I tried to follow the layout as well as I could on Logos 32.0.29 on my MacBook without hitting this problem.

Perhaps the 'Bug' is not so pervasive and we need specific details on the layout and reference to replicate?

DMB

https://community.logos.com/discussion/comment/1288519#Comment_1288519

Appreciate both checks. The issue is in the TC code ... I'm guessing all the way back to the L4 Windows > Mac. Alternatively, a Mac desktop complication.

I'm not sure bugs are even staffed anymore. We'll see what today's bug will be! Excitement is in the air (along with springtine winds).

Mike Binks

https://community.logos.com/discussion/comment/1288534#Comment_1288534

Appreciate both checks. The issue is in the TC code ... I'm guessing all the way back to the L4 Windows > Mac. Alternatively, a Mac desktop complication.

I'm not sure bugs are even staffed anymore. We'll see what today's bug will be! Excitement is in the air (along with springtine winds).

Therein lies the rub.

I cannot awaken the bug in the Text Comparison code, and, because I am curious I would like so to do.

However I am unable to replicate the situation in which it occurs for lack of detail as to how to go about it.

DMB

Well, it's day 2 of the BOTD series. I wasn't sure a bug would appear. But I wasn't disappointed!

Today's bug is unusual ... I suspect a recent update. I was going to check Christian's 'reckoning' to work backwards into the aramaic. So, I went to the Leiden Peshitta, right-clicked the syriac word, and the right-click menu didn't know anything about it (empty right-side). That was strange .. there's an analytical lexicon for the NT/Syriac.

So I switched over to another NT syriac that even has an interlinear, and did a right-click ... and whoosh ... Verbum was gone.

I don't even want to try to figure out what the issue is there ... I do have the analytical linked to the syriac group ... maybe it was just too much for him. Or maybe they're working on OL fonts and forgot syriac.

Anyway, didn't take long for today's BOTD. We'll watch for tomorrow!!

Dave Hooton

https://community.logos.com/discussion/comment/1288678#Comment_1288678

Well, it's day 2 of the BOTD series. I wasn't sure a bug would appear. But I wasn't disappointed!

But how do we know it is not another response to BOTD Day 1? ....New thread?

DMB

https://community.logos.com/discussion/comment/1288708#Comment_1288708

Well, I thought of that. But I didn't want to kludge up the forum with bugs that'll never get fixed. I'm content to just observe the statistical likelihood of hitting a bug per day. I have maybe 50 frequent-use and sophisticated apps. One has a bug and I don't think it's the app's fault. Logos seems the bug-capital on my devices.

Regarding today's crash, I'm thinking the right-click menu feed is slower and slower (ergo a blank panel). So, if you don't wait a while, and then try another resource right-click, it crashes. The queries>threads aren't independent (no error catch).

Anyway, we'll see tomorrow ... maybe the statistics will fail!

Mike Binks

https://community.logos.com/discussion/comment/1288712#Comment_1288712

But I didn't want to kludge up the forum with bugs that'll never get fixed.

Come back Heller there is a place for you here.

So instead of actually analysing the problem with any particular 'mis-performance' of the program then getting an understanding of the triggers one simply lists the problems with no expectation of comment or investigation?

As I understand it the part of 'raison d'être' for the forums is to 'kludge it up with bugs' so that folk can investigate, confirm, and advise.

What one may think of as an obscure or esoteric bug may, in effect, be the root cause of other problems down the line. Fixing it may be a big help to a lot of people ignoring it may not be treating others the way we would like to be treated.

DMB

https://community.logos.com/discussion/comment/1288735#Comment_1288735

Well, it's Day 3 of BOTD. I really thought we'd go a day at least, and this would be a silly excercize. But not, sigh.

Today's bug I already knew about; but having updated to 31.3.32, he seems to be getting meaner.

The earlier bug (I'm sure Mac only), mistates your library size, simply by how you set you web access (on/off). 'On'delivers a nice large library ... over 6,000 great volumes. Turning web off, reduces the size to 1600. The difference is downloaded and whether the setting is on or off. Or put another way, you have to be online to see your library.

Now, today's wrinkle, is changing the web on/off switch delivers a notification to restart the app. It's possible (?) they finally recognized on the Mac, web access can only occur with a restart. In my case, the Mac stays offline and Verbum apparently can't tell. So, a restart will be required.

So, we add this bug-expansion to our work-arounds. I wouldn't doubt it's their design ...

And Mike, I do have bug reports with zero response from FL. In fact, I haven't seen the bug-lady for quite some time?

xnman

https://community.logos.com/discussion/comment/1288743#Comment_1288743

I think I'll stay with Windows OS.... I just don't seem to have the crashes and not most of the BOTD that is being talked about. Wait... maybe my system is a "special system" and somehow my malware detector is detecting all them bugs and hiding them from me. Ya think?

DMB

https://community.logos.com/discussion/comment/1288743#Comment_1288743

Day 4 of BOTD.

This bug occurred this morning. But I've seen it before randomly; just got used to it. But hit it today. I was in my NRSV, and wanted a quick look at Gen 3:13 'serpent'. What was the hebrew base usage? So, I right-clicked the NRSV english, scanned my lexicons at the bottom of the right-side of the menu. And selected the DCH entry for more review. The result is below. No serpent. The DCH is in my layout, so the process would be to switch windows, focus on the DCH tab, and then go to the serpent entry. It gets to the DCH tab and gives up.

Now, if I do it again (click on the DCH on the right-click menu), it'll work. In the example below, the hebrew for 'heart' was a previous query. One option I haven't tried, is whether the tab being 'in view' creates success, and the tab out of view, failure (bug is after bringing tab into view?).

And Xnman, I hope we're not accidentally targeting our good folks down in Phoenix ... my impression is they have to try to copy the Windows designs, and be quick about it.

Savanna Lineberger

https://community.logos.com/discussion/comment/1288832#Comment_1288832

Thank you for all your reports. There is a bit for us to catch up on in this thread, but I will spend some time working on reproducing these issues you're encountering.

DMB

https://community.logos.com/discussion/comment/1288927#Comment_1288927

Day 5 of BOTD

Thank, you, Savanna. Though my intent is primarily to see to what degree bug-dodging interrupts Bible study ... now and then, or more often. So, my bugs may be random, or not worth worrying about.

OK! Today's bug is another known 'do not do that!' and my finger hovered over the Enter key, before I remembered. Whew.

A nice feature in Logos, is, if you're in a referencial text box, typing a numeral suggests you wish to change verses. Two numerals, chapter and verse. And at least on the Mac, hitting the tab highlights the full reference. So, quick key-work allows quick reference changing.

Except on Text Comparison. A numeral with an Enter, completely changes the resource group, to the first in a list of non-Bible indices. No Bible choice, even though you're in a Bible, and your resource group is ... Bibles.

Thru the years, I thought that might be a feature ... granted poorly designed. For a long time, TC had another bug, if verse changes were not distant ... no change. They fixed that. But the odd non-standard reference handler remains.

And what happens, if my itchy Enter-finger worked this AM? I have 4 TC's linked (by language group). It'd have ruined all 4 (another bug, linking TCs). And I'd have to re-load the layout, losing my study-place. Logos doesn't have a go-back.

Whew!

--------

But there's more!

I've had a recent interest in the latin Bible. As both greek, and english developed, what about latin? Logos is pretty sparse ... no Italia/Old-Latin, And no Jerome. But beggars can't be choosers, so I added a 5th TC for latin (Clementine and Stuttgard Vulgate). Then, I turned on show-diffs and base-text. Mistake.

The tool doesn't separate the base from the actual ... just one long word, differing colors. That's ok it you know your latin ... I don't. So a right-click search tries to find the not-a-word ... with expectedly no success. Have to hand-type, hand-type, hand-type.

DMB

https://community.logos.com/discussion/comment/1288979#Comment_1288979

Day 6 of BOTD

Now technically, it's day 7 but I didn't exercize Verbum yesterday; Kindling on a book that should be in Logos.

Well, there's the new AI update, so when I updated to 32, it was slow going. While I was waiting, I chose to continue reading my book. Not good.

I opened it, and it was about 10 pages earlier than where I left it. This probably isn't a bug, but I'm not so sure. If I use the little 'go back' arrow (after some exploration), it can return to where I'm reading. But if I open the book later, it can't remember exactly where ... apparently it uses 'milestones' (more like millstones). And so, unlike Kindle, I highlight just to keep my place! Design flaw or bug, pick.

Then, I started reading but didn't remember exactly where I was (chapter, section, etc). There is the locator bar, but if you click on it, it can only show enough to fit in the slot. The animation was cute ... illustrates cute bad design. The bug part is actually over on the TOC ... it doesn't pop up anymore. I'm betting on purpose ... Faithlife just HATES to do navigation for book use ... running subscription models with incomplete policies is far more fun (ok, just observing).

After Mark did say they'd been fixing historic bugs up a storm, I did check my 'historic bugs'. Nope. That must mean there must be a whole lot? I had thought the software sure seemed buggy, but I must have under-estimated.

OK ... back to Bible study for today.

DMB

https://community.logos.com/discussion/comment/1289319#Comment_1289319

Day, a week later

Well, with all the excitement over everyone (ok, a few curmudgeons) just loving subscriptions, I completely forgot to use Logos! I mean, it's not a subscription ... what's the point?

OK, but I WAS checking out the ins/outs of the future of Logos (since I won't subscribe). Lots of promises, if you noticed. Below is an interesting example. I'm confident, this example would be a level-4 subscription ... the accent tagging. Notice, you can't read it on the left. You used to be able to click on the top-right for an expansion (a few months back maybe). Not any more.

So. I assume I'll be using Name:Oxytone, Position:Ultima, Typ. And that's ok. Do they really think, if they can't do bugs now, that they'll do bugs later? I sound negative, but there's a reality to staff/time/results. If subscriptions, they're going to need to deliver .... subscriptions.

Andrew Batishko

https://community.logos.com/discussion/comment/1291505#Comment_1291505

You should be able to hover your mouse over the truncated text either on the left or right side in order to see the full text.

DMB

https://community.logos.com/discussion/comment/1291555#Comment_1291555

I agree, I should. But it doesn't. The former report (months ago) did note it responded to clicking the top-right, but apparently that's been removed.

But thank you ...

Andrew Batishko

https://community.logos.com/discussion/comment/1291565#Comment_1291565

I agree, I should. But it doesn't.

Is that on Mac or Windows?

DMB

https://community.logos.com/discussion/comment/1291566#Comment_1291566

Mac. But this is one of several truncateds, in system panels that don't hover ... and earlier reported.

I'm good.

DMB

https://community.logos.com/discussion/comment/1291567#Comment_1291567

Next Day

Faithlife mobile, this time. I decided, after weeks, to try out the new gestures on the mobile. I had swore off Faithlife mobiles for quite some time, and wondered if they work on my iPad mini.

Now, in all fairness, my mini is 6 yrs old. Not Faithlife supported. Waiting for Mini 7 this year. Anyway, I installed, logged in, and it loaded my library data (meta, not resources). I turned everything off on the home page, saw all was well, and turned off the wifi.

That's when my library disappeared. I restarted ... still gone. Turned wifi on ... it's back. Now, fairness ... unsupported device version.

But it does illustrate that Faithlife apps die quick. I have bunches of apps running on the older ios version. The current Mac Logos is similar (same bug, and latest macOS). I'd say, don't plan on Faithlife apps surviving more than a version or so ... absent the mothership.

Deleted the app.

xnman

https://community.logos.com/discussion/comment/1291663#Comment_1291663

Next Day

Faithlife mobile, this time. I decided, after weeks, to try out the new gestures on the mobile. I had swore off Faithlife mobiles for quite some time, and wondered if they work on my iPad mini.

Now, in all fairness, my mini is 6 yrs old. Not Faithlife supported. Waiting for Mini 7 this year. Anyway, I installed, logged in, and it loaded my library data (meta, not resources). I turned everything off on the home page, saw all was well, and turned off the wifi.

That's when my library disappeared. I restarted ... still gone. Turned wifi on ... it's back. Now, fairness ... unsupported device version.

But it does illustrate that Faithlife apps die quick. I have bunches of apps running on the older ios version. The current Mac Logos is similar (same bug, and latest macOS). I'd say, don't plan on Faithlife apps surviving more than a version or so ... absent the mothership.

Deleted the app.

I understand. But in all fairness... Mobile Apps are not the same as desktop programs. I will venture to say that Logos Desktop will be around at least for a few versions...

DMB

https://community.logos.com/discussion/comment/1291691#Comment_1291691

But in all fairness... Mobile Apps are not the same as desktop programs.

Well, that's true ... best to stick with desktops, when it comes to reliability. Libby's still humming along ... almost 20 years later.