| Summary: | kde freezes completely while accessing Kmenu -> Print System when cups server is not found | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeprint | Reporter: | Unknown <null> |
| Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | normal | CC: | jlayt |
| Priority: | NOR | ||
| Version: | 0.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Do you have cups *installed* on that system? I have cups installed, but not running, and get no freeze. (BTW, for the purposes of bugs.kde.org, freeze isn't a crash) I have cups installed in my system but it is _not_ running. The results are the same. I tried with cups running in my system - same result. Next I started a kprinter in terminal and changed from LPR... to CUPS server (in home) and it started a message "Initializing...." and then the window became really huge (horizonztally stretched) and I could not cancel it or do anything but to kill x-server. (Sorry for the freeze/crash misunderstanding) Many thanks, "then the window became really huge (horizonztally stretched)" reminds me of something I read elsewhere, recently. And it concerned the very first KDE 3.5.5 packages that came out of SUSE. IIRC, this was fixed by SUSE sometime later.... Maybe an update helps yout too? Yes an update corrected the huge window problem. But still "Kmenu -> Print SYstem freezes up in the situation described above. Does the freeze also happen, if you start "kprinter" via the "[alt]+[f2]" shortcut?
Please post the content of the following commands:
grep -i ServerName ~/.cupsrc
grep -i ServerName ~/.cups/client.conf
grep -i ServerName /etc/cups/client.conf
cat $(kde-config --localprefix)/share/config/kdeprintrc
cat $(kde-config --localprefix)/share/config/kprinterrc
Last, run this command from a konsole to get a log of which files your kprinter tries to open:
strace -eopen kprinter | tee ~/kprinter.freeze.log
It will allow you to
a) watch the output inside the console and also see the last few lines before
it freezes
b) look at the file ~/kprinter.freeze.log later and search for a reason that
may cause the freeze
Actually, how long have you waited for the longest time so far, before you decided it is a freeze that will last forever? Maybe it is just some timeout that is set to an insane level, somewhere?
What you also could try: create a completely new user on your system, start KDE as that user, and see if the print system also freezes for that user....
Waiting for feedback from reporter. Setting timeout to 7th of February. A logout and login KDE helped. Looks like the update fixed the bug. Sorry for inconvenience. Works for reporter Closing old Resolved status bug. |
Version: 0.0.1 (using KDE KDE 3.5.5) Installed from: SuSE RPMs Compiler: SUSE 10.2 default OS: Linux Settings in Control Center: Control Center-> DEsktop \ -> Panels \ ->Menus I have enabled "Optional Menus" -> Print System Hence it appears in my Kmenu. In my work, I use "CUPS" printing. So my kprinter is configured properly for that. From my HOME ,I cannot access the CUPS server. Now from home when I (by chance) move the mouse pointer inside "Print System -> KDE Print System" whole "kde" freezes. (shown with ***) ....Actions .... Print SYstem -> KDE Print system *** ----------- Run Command ----------- Switch User Lock Session Logout ...... KMENU During this freeze (Alt-F2 doesnot work or I cannot launch a konsole to kill anything) I have a gkrellm and it does not show any spike in CPU and GTK applications (firefox, gkrellm) work fine. Only way to recover for me is to shift to "Console" Ctrl-Alt-F1 and kill KDE and relogin. The workaround is: If I start kprinter from a konsole (commandline) after coming home, kprinter window is a bit frozen (initializing) but then after a few seconds it comes alive. Now change "Print system currenty used -> LPR..." After this kmenu -> Print System will not freeze entire KDE. Many thanks,