Gslapt will not launch, and an auto-login question.

[Diogones]

I have recently decided to make the swap from another Linux distro to Salix, and I must say, it is a great OS. It has a beautiful desktop, a fast response time, and most apps anyone could want right out of the box. As a newcomer to Salix and to Slackware in general, I do have a couple of issues that I hope you fine folks here may be able to help me with.

For some reason, after updating a few packages with gslapt the package manager will no longer launch. I can get it to open if I run the launch command through a root terminal. Whenever I select it from the Salix menu however, it will appear briefly on the taskbar and then disappear. I have reinstalled it, but no luck.

I also just have a brief question about setting the option for auto-logging in on startup. It's always nice to have, as it saves the trouble of entering in the user password when the computer starts. However, when I set this option and rebooted my computer, the X environment wouldn't load, and I was forced to restart through a command line. I'm not sure if I didn't configure it correctly, or if it's something else.

Besides these two issues, I can't say I've found anything wrong with Salix, and the developers deserve a Job Well Done! Hooray for Salix!

[gapan]

What updates were those? Are you using any other repositories except the default ones? Do you get the root password prompt when launching from the menu?

And post the contents of your ~/.xsession-errors after an unsuccessful login.

[Diogones]

Holy smokes, gapan, I didn't know that you were a wizard in the Salix community! That explains how you were able to help me out with those Salix live problems I had! Good to see you again! It's a small world after all. Well, you were right: after trying out Salix, I've decided to stick with it as I enjoy using it. Thanks for your quick reply; helpful as always.

In response to your questions, the updates were just for the apps that have been included with Salix, such as Pidgin and Firefox. There was an update to Xfce, so I wasn't sure if that could have affected my ability to log in. Yes, I am using a different repository in addition to the default setup: darkstar.ist.utl.pt/slackware/addon/slacky/slackware-13.1/

I was using that to get Chromium, but unfortunately I wasn't able to get the browser to launch after I downloaded and installed the package from that repo.
No, I am not prompted for the root password when I launch from the menu - all that appears is a brief gslapt icon on the taskbar, and then it disappears and nothing happens.

I'm sorry, but I don't know where to find the ~/.xsession-error log, and when I do find it, do you want me to add it as an attachment or copy the entire text straight to my reply? I always like to ask because I've visited different forums that have different rules concerning large blocks of text.

[laprjns]

I'm sorry, but I don't know where to find the ~/.xsession-error log, and when I do find it, do you want me to add it as an attachment or copy the entire text straight to my reply? I always like to ask because I've visited different forums that have different rules concerning large blocks of text.

You can find it in your users home directory.

Code: Select all

rich[~]$ ls -a .xse*
.xsession  .xsession-errors

I don't think you can attach files. If its not too long then copy as text using the code tags. Or you could use http://salix.pastebin.com/ and use a link.

[Diogones]

Thank you for helping me find the xsession-error file laprjns. After looking it over, it doesn't appear to be too much, so I'll just add it here verbatim:

Code: Select all

xfce4-panel:1852): xfce4-panel-WARNING **: Failed to create plugin "quicklauncher"
err:module:import_dll Library bass.dll (which is needed by L"Z:\\home\\judy\\Desktop\\Patience.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\judy\\Desktop\\Patience.exe" failed, status c0000135
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1489a8,0x1488a8): stub
fixme:mmdevapi:AEV_GetVolumeRange stub
err:mmtime:TIME_MMTimeStop Timer still active?!
err:module:import_dll Library bass.dll (which is needed by L"Z:\\home\\judy\\Desktop\\Patience.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\judy\\Desktop\\Patience.exe" failed, status c0000135
err:module:import_dll Library bass.dll (which is needed by L"Z:\\home\\judy\\Desktop\\Patience.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\judy\\Desktop\\Patience.exe" failed, status c0000135
err:module:import_dll Library bass.dll (which is needed by L"Z:\\home\\judy\\Desktop\\Patience.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\judy\\Desktop\\Patience.exe" failed, status c0000135

** (xfce4-menu-plugin:1856): CRITICAL **: Unable to get keyboard/mouse grab.
fixme:msg:ChangeWindowMessageFilter c046 00000001
fixme:win:DisableProcessWindowsGhosting : stub
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
fixme:sfc:SfcIsFileProtected ((nil), L"Z:\\home\\judy\\Games\\Patience\\unins000.exe") stub
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x148908,0x148808): stub
fixme:mmdevapi:AEV_GetVolumeRange stub

(xfwm4:1847): Gdk-CRITICAL **: gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed

(xfwm4:1847): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(xfwm4:1847): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
err:mmtime:TIME_MMTimeStop Timer still active?!
fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:exec:SHELL_execute flags ignored: 0x00004100
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x148a88,0x148988): stub
fixme:mmdevapi:AEV_GetVolumeRange stub
err:mmtime:TIME_MMTimeStop Timer still active?!
** Message: xfsm-shutdown-helper.c:268: Using HAL to shutdown/reboot the computer.
Error: No running window found
fixme:exec:SHELL_execute flags ignored: 0x00000100

I'm not sure what that all means, but maybe it could explain why I have trouble logging on automatically?

[gapan]

Yes, I am using a different repository in addition to the default setup: darkstar.ist.utl.pt/slackware/addon/slacky/slackware-13.1/

There's your problem. You "upgraded" some salix packages with some from that repository and they simply don't work. I'm guessing it was at least the ktsuss package. Remove that repository from your slapt-get sources and then do another upgrade. That should bring everything back.

[Diogones]

Thanks for the suggestion, gapan: now my gslapt works normally again! However, I still have issues logging in, and not just with the auto-login feature. Sometimes I will boot Salix and log in normally, only to be greeted with the loading screen and nothing else. X won't load up, and I'm force to close out to a terminal and reboot. But I have noticed that when I log in after switching session types, (from xfce to last session) I am able to access Salix normally. Could there be something wrong with how I'm setting my session configuration? I do have it set to automatically save my session - is that adversely affecting it somehow?

[gapan]

Your sessions is probably somehow broken. I've seen that "save session" checkbox in xfce do more harm than good. You only notice that it actually saved a broken session when you try to log in back again. Create a new user and try with that. If there are no problems, it's your session settings. If it doesn't work, it means you still have some broken software in your system or that some of that software that you installed from other repos broke your user settings somehow.. In any case, read this: http://www.salixos.org/wiki/index.php/C ... itories%3F

[mimosa]

I've seen that "save session" checkbox in xfce do more harm than good.

It's certainly a nuisance at at times. I unticked it, and then rather than getting a blank session, I got whatever I had the last time it was ticked, forevermore. The only way I could find to get rid of it was by closing all apps and windows, turning it on, rebooting, then turning it off again. That's bad design. However, it could be quite useful to get, not your last session, but a session of your own devising (open firefox, for instance, or a terminal) but without having click on anything to choose it each time. And I did just that for a while, by leaving the apps I wanted open before rebooting and unticking.

[Diogones]

Well gapan and mimosa, you were both right: Salix wasn' t to blame, it was the XFCE session manager. The "save session" checkbox was causing my log in problems, and I agree completely with you; the checkbox is somewhat confusing. So I followed your steps mimosa, closing all active programs, checking the box, rebooting, logging in, and unchecking it. Since then, I've been able to log in without any issues, and now I am finally happy to report that there is no more freezing at the session screen. Thank you for the link, gapan, and I've sure learned my lesson using non-Salix repos. I have one quick question - how to I configure auto login? When I check the log in tab, the user name box is empty. After I fill it with mine and reboot, it won't auto log in. Am I missing a step?