shutdown status "application input_server might be blocked on a modal panel"

[dfourth]

recently updated system from R1A4.1 to hrev45085 and began receiving this message on every shutdown. It seems to have reappeared, as I noticed an older closed bug (#1491 I believe) from 2007. I have only been using Haiku since R1A3 and this is the first time I've noticed it.

My system: AMD Phenom II 2.59 GHz 6 processors 6143MiB memory, 5% used by system Kernel dated Dec 25 2012 00:35:07

[axeld]

This may only happen if there are more than one input_server on the disk, and the wrong one is chosen for whatever reason (ie. one that is not in /system). Removing that second instance should fix the issue for you.

Whether or not this is a bug in Haiku depends on how you updated. If you just renamed the /system folder (not copied it), and replaced it with the one from hrev45085 things like this might actually happen without the system being able to notice.

[anevilyak]

(In #9329) Inadvertent duplicate.

[dfourth]

That is indeed the method used to update the system, as it seemed the most straightforward for real hardware (based on my readings from the Haiku.org website) without requiring a CD to be burned etc. The old system folder has been moved off to a backup partition that is not mounted. Tracker's Find can only locate a single instance of input_server, and only one instance is found when viewing running processes. Repeated power cycles without starting any additional applications results in the same error at shutdown each time. If there is a second instance of input_server anywhere in the system, I am unable to locate it. I have attached my device and driver list, should it be of any value.

[axeld]

That's interesting, thanks for the update. The message should only come if Haiku does not recognize the input_server as a system component. Apparently, that check fails for you for whatever reason. The shutdown process checks if the app is in /system/app or /system/server, and won't ask the user if this is the case.

Could you please attach the output of the roster command?

[dfourth]

~> roster

team path port flags signature

---

74 /boot/system/servers/registrar 23 6 (application/x-vnd.haiku-registrar) 80 /boot/system/servers/net_server 51 6 (application/x-vnd.haiku-net_server) 79 /boot/system/servers/debug_server 42 6 (application/x-vnd.Haiku-debug_server) 96 /boot/system/servers/syslog_daemon 85 6 (application/x-vnd.Haiku-SystemLogger)

108 /boot/system/servers/input_server 102 6 (application/x-vnd.Be-input_server) 118 /boot/system/servers/mount_server 145 6 (application/x-vnd.Haiku-mount_server) 138 /boot/system/servers/print_server 172 6 (application/x-vnd.Be-PSRV) 137 /boot/system/servers/midi_server 197 6 (application/x-vnd.Haiku-midi_server) 136 /boot/system/servers/media_server 198 6 (application/x-vnd.Be.media-server) 141 /boot/system/servers/cddb_daemon 259 6 (application/x-vnd.Haiku-cddb_daemon) 162 /boot/syst...rs/media_addon_server 280 6 (application/x-vnd.Be.addon-host) 143 /boot/system/servers/power_daemon 279 4 (application/x-vnd.Haiku-powermanagement) 135 /boot/system/Deskbar 306 2 (application/x-vnd.Be-TSKB) 134 /boot/system/Tracker 305 2 (application/x-vnd.Be-TRAK) 142 /boot/syst...s/notification_server 317 6 (application/x-vnd.Haiku-notification_server) 806 /boot/apps/WebPositive 3499 0 (application/x-vnd.Haiku-WebPositive) 987 /boot/system/apps/Terminal 4012 1 (application/x-vnd.Haiku-Terminal)

~>

The layout stinks from the copy/paste, but didn't seem worth the effort to reformat. Any clues from this?

[dfourth]

Curiouser and curiouser... after posting the results from the roster command, the subsequent shutdown did NOT produce the input_server error. As is was after 3am my time, I let it go and went to bed. Upon starting this up this morning, I immediately shut it down and again observered no input_server error message. I have no idea what might have changed or if this is an intermittent problem. Either way, it isn't possible to debug something that isn't showing symptoms, so I imagine it would be best to end this ticket and possibly resurrect it if the issue pops up again.

[Karvjorm]

I have this problem also and I think it started when I tested MsgSpy and it was installed in ~/config/add-ons/input_server/filters/

Then I removed MsgSpy, but PortSpy is still there and this problem occurs during each shutdown. I have supposed, that input_server filters cannot handle shutdown messages.

[Karvjorm]

No, I removed PortSpy, but input_server shutdown problem is still left.

[Karvjorm]

OK, it looks like input_server is not a system component just like Deskbar, media_addon_server and sshd. I have some problem during startup and I have to restart Deskbar via ctr-alt-del window.

[Karvjorm]

This is my syslog

[axeld]

Karvjorm, could you also provide the output of the roster command?

[Karvjorm]

roster command

[Karvjorm]

Snapshot of ctr-alt-del window (input_server non-blue text)

[Karvjorm]

There are two strange details in my system. First, I once tested PowerStatus replicant, and aborted it (if I recall it correct) because there was already a PowerStatus replicant on Deskbar. But anyway, I got a battery outline on my desktop (and it is still there though I have surely upgrade Haiku twice after it. Could this battery outline be that blocking component? I do not know any way to remove it.

During another test some test program placed another replicant on the Deskbar and I cannot remove it either. I can't remember what replicant it was, some in src/test source code branch.

[Karvjorm]

Non-removable powerstatus shown by cursor and another replicant right to network status

[Karvjorm]

I wonder if the Deskbar settings would show all the present replicants on Deskbar. And then it would provide some radio buttons to remove them one by one.

[Karvjorm]

The Quit menu line does not work, if I select it in my Desktop PowerStatus. If I turn off "Show text label/Show status icon/Show time" menu lines, PowerStatus replicant disappears, but it is still there if I click the correct coordinate of the Desktop with the mouse cursor.

[Karvjorm]

OK, when I turned on "Show replicants" in Deskbar menu, I was able to see a PowerStatus handle quite far away from the battery outline. And by clicking that handle I was able to close Phantom PowerStatus on my Desktop and it is gone now. But input_server shutdown problem is still there. My working method is always trial-and-error. ;-)