I recently updated to the nightly release of haiku. Everything seemed well until suddenly my deskbar disappeared. Now it doesn’t work even after a reboot. In addition to that, some apps won’t start until I kill it using the terminal. What do I do?
Look into the /var/log/syslog if there are Deskbar related entries.
What’s the “it” here?
The Deskbar process
Ah, so the Deskbar team is started, but no Deskbar appears on screen. Maybe the syslog will enlighten us.
Try launching those apps that won’t start from Terminal. Maybe there’s some helpful output.
Fresh boot:
Running cat /var/log/syslog | grep -i bar returns nothing.
After starting falkon no window appears
running a kill command on the Deskbar process makes Falkon visible, and a new Deskbar process with a different pid appears.
Still no new entries about Deskbar in syslog after this. There is also a syslog.1 file that is about half an hour old that contains some stuff about deskbar, but it might be from before it broke.
I unfortunately don’t see a way to attach them here. What would be the best way to share my syslog and syslog.1?
Here’s the part of syslog.1 that contains stuff about Deskbar
KERN: stack trace, current PC 0x2306f4cccd7 </boot/system/Deskbar> _ZN7TBarApp13FetchTeamIconEii + 0x57: KERN: (0x7f4c56f26ed0) 0x2306f4ea81f </boot/system/Deskbar> _ZN10TTeamGroup14CacheTeamIconsEii + 0x5f KERN: (0x7f4c56f26f20) 0x2306f4eefc0 </boot/system/Deskbar> _ZN14TSwitchManager15MessageReceivedEP8BMessage + 0x290 KERN: (0x7f4c56f26f90) 0x1d1b361f6f9 </boot/system/lib/libbe.so> _ZN7BWindow11task_looperEv + 0x1d9 KERN: (0x7f4c56f27020) 0x1d1b355e7c1 </boot/system/lib/libbe.so> _ZN7BLooper7_task0_EPv + 0x21 KERN: (0x7f4c56f27040) 0xeca2122f59 </boot/system/lib/libroot.so> thread_entry + 0x19 USER: void KoDocument::setMimeTypeAfterLoading(const QString&) "application/vnd.oasis.opendocument.spreadsheet" USER: kf.notifications: No event config could be found for event id "DocumentLoaded" under notifyrc file for app "calligrasheets" KERN: debug_server: Killing team 153 (/boot/system/Deskbar) KERN: debug_server: TeamDebugHandler::Init(): Failed to get info for team 153: Operation on invalid team KERN: debug_server: KillTeam(): Error getting info for team 153: Operation on invalid team KERN: debug_server: Killing team 153 ()
This seems to coincide with the moment it broke as I remember having issues with saving a file in Calligra Sheets the moment it broke
There may be other interesting stuff in the lines directly before the pasted snippets. Looks like Deskbar crash after bootup (TBarApp::FetchTeamIcon). What’s your hrev? It’s supposed to be fixed by @madmax with hrev59981.
I just did a full-sync so it should be the latest nightly. Looking in the boot options it says “r1~beta6_hrev59992”.
On the other hand I did the full-sync after Deskbar broke. Is there maybe a way to reset it’s data?
one might try deleting its settings in /boot/home/config/settings/deskbar
You mean even after the update you see no Deskbar and have to kill its process to start some apps? As zuMi implies, maybe some settings files were corrupted in one of the crashes and deleting them might fix it.
But it would be nice to know what’s happening instead of just solving it. So if you can, run Debugger, attach it to the wayward Deskbar process and see what it is stuck into. Or at least backup the settings before deleting them, so that maybe we can reproduce the issue.
BTW, you can have a look at some of those files with the message command, at least when they are not corrupted.
When I tried attaching the debugger I couldn’t find anything unfortunately.
I moved the settings into a different folder and restarted. I can send them to you if you want.
The deskbar works now, but one odd behaviour is that it freezes up whenever I try to install the powr status replicant inside it. I think that might have been the issue.
replicants settins are in the same directory, you can try to move it, kill Deskbar and see what happens
I have the same issues on my Dell laptop. I did kinda tracked it to the power status app but just reinstalled from scratch since I just use Haiku for experimentation on the Dell right now. This issue has gone on for over year on and off for me and I figured it was just a hardware bug. Should probably look into it more as others have an issue as well.
The power status app works fine as a desktop replicant (outside of the deskbar) for me right now. It’s just that the two seem to have a weird interaction when put together.
Edit: BTW I’m on an old Dell laptop too!
Hmm, may have something to do with a driver in the power system either not turning on soon enough or at all.
I drive for a living and don’t get much time to play but this and getting my MacBook Air running again will be a couple small projects once beta 6 gets out and stabilized throughout including the Depot.
It seems the issue is related to having PowerStatus in the deskbar, not to broken settings, so I don’t think that’s necessary. You can get rid of the copy if your Deskbar is to your liking now.
I faked a battery in the driver interface and did not have problems. When I went back to the original binary, it detected no batteries and just removed itself from the deskbar with no issues.
If someone can reproduce the problem reliably and is daring enough to do it on purpose, I have added traces to PowerStatus here. Save your ~/config/settings/deskbar/replicants for easy recovery. Download the modified version, unzip, run it, put it in the deskbar and then do whatever you need to trigger the issue. The traces will go to the syslog, the start with 'USER: PS '. Be aware that the battery info updates every two seconds or so, and each update may spit several log lines.
You may want to try again after hrev60109. @phoudoin has fixed an infinite loop in Deskbar when looking for a place to put replicants.
@PulkoMandy also fixed a bug in PowerStatus which was making the width of its replicant too large, taking the whole Deskbar replicants tray advertised width. Which, unfortunately, can be wrong, and leading to an infinite lookup for a location in that replicans tray.
I think both his fix and mine actually should fix this issue.
1 Like