problem with 10.1 and x11 - UNIX Resources Network

UNIX Resources » Linux » Linux Forum » Slackware Linux Discussions » Page.71 » problem with 10.1 and x11

The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.

China Linux Forum(finished)

Linux Forum(finished)

FreeBSD China(finished)

LinuxForum General Chat

Linux Advocacy

Introductions

Development Release

Linux Security

Linux Software

Linux Hardware Problems

Linux Video Problems

Linux Sound Problems

Linux Networking Support

Linux Printing Support

Linux Human Interface Devices Support

Linux Data Storage Support

Linux Applications Support

Linux Installation Support

Linux Laptops Support

Linux Motherboard, Chipsets, CPU, Memory

Miscellaneous

Mandrake Linux Support

Redhat / Fedora Linux Support

Slackware Linux Support

Linux Database Servers

Linux Email Servers

Linux FTP Servers

Linux Squid Proxy Server

Linux Webmin / Usermin Help

Qmail Toaster Help

Linux Games

Windows Game Emulation

Linux Discussions

General Linux Discussions

Red Hat Linux Discussions

More Red Hat Linux Discussions

Mandrake Linux Discussions

Slackware Linux Discussions

SuSE Linux Discussions

Debian Discussions

Samba Help

Linux Security

Linux Networking

Gentoo Help

Operating System Rant Forum

Hardware Rants

problem with 10.1 and x11

[Original] [Print] [Top]

I've encountered an intermittent problem using slackware 10.1.
Initially the problem appeared on a PC after I upgraded from slack 9.1
-] 10.0 -] 10.1. However I've since discovered the problem also occurs
on a freshly installed 10.1 system with different hardware. I never had
this problem with slackware 9.1 and I'm pretty sure I didn't have it
with 10.0 either. (I've been mostly using 9.1 since it came out.) For
the packages that I've built myself, I used the same source archives
(upgraded over time) and build procedures on all 3 slack releases (9.1,
10.0, and 10.1).

Problem:

An intermittent invisible window in the taskbar prevents logout from
icewm. This invisible window appears in the taskbar with no title and
has the same foot icon present in icewm's Confirm Logout dialog box
(xp-new-default 1.1 theme). As expected with my icewm config, clicking
on this window in the taskbar toggles between showing and hiding a
window icon (but no window) on the desktop. The invisible window cannot
be closed and the only way out of icewm is to CTRL-ALT-BACKSPACE. Using
ps showed no abnormal processes running. I've noticed that this
invisible window sometimes is created after moving the mouse cursor from
within an application window (not unique to a single application) up and
across its titlebar and back down. An area of the screen flashes and
the newly created window then minimizes itself to the taskbar.

What I've tried so far:

I searched usenet and found nothing on this. Searching icewm bugs list,
showed an old report that the rox pinboard was preventing logout. I'll
try running without the rox pinboard for a while. I ran chkrootkit to
check for rootkits and it found nothing. I am running a firewall and
don't believe I've been hacked, but I guess that's always a possibility
(although this problem occurs on a fresh install with no net access). I
have already uninstalled x11, icewm, and rox - then reinstalled
slackware x11 packages, then rebuilt icewm, and rox on a
clean/standalone PC (never been on any network), and finally reinstalled
the new icewm and rox packages on the affected PC - the problem still
occurs.

Running xwininfo on the invisible window shows the following:

0xa001c1 (has no name) ("icewm" "taskbar")

System Config:

slackware 10.1 with x11 6.8.2 updates
2.4.29 kernel (custom build, same config as with 9.1 and 10.0)
icewm 1.2.20 and rox 2.2.0 as my desktop (same source and build scripts
used to build my slack 9.1 and 10.0 systems)

It's quite possible I made some stupid error, but I'm suspecting some
sort of library/API incompatibility/bug. Hopefully someone can point me
in the right direction to figure this out. I probably should have left
my rock solid 9.1 systems alone...

Peter

[Original] [Print] [Top]

Subject: problem with 10.1 and x11 Author: Joost Kremers Posted: 2005-02-28 15:48:39 Length: 1,003 byte(s)
[Original] [Print] [Top]
psantoro wrote: QUOTE Running xwininfo on the invisible window shows the following: 0xa001c1 (has no name) ("icewm" "taskbar") this seems to be telling: you're appear to be dealing with a window that is created for the icewm taskbar. i'd suggest to first try another wm and see if the problem persists. if not, you're almost certainly dealing with a bug/feature in icewm, and you might find more help on the icewm mailing list: [http://lists.sourceforge.net/lists/listinfo/icewm-user] -- Joost Kremers joostkremers@yahoo.com Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9)
[Original] [Print] [Top]

Subject: problem with 10.1 and x11 Author: psantoro Posted: 2005-03-01 05:13:08 Length: 1,664 byte(s)
[Original] [Print] [Top]
Joost Kremers wrote: QUOTE psantoro wrote: Running xwininfo on the invisible window shows the following: 0xa001c1 (has no name) ("icewm" "taskbar") this seems to be telling: you're appear to be dealing with a window that is created for the icewm taskbar. i'd suggest to first try another wm and see if the problem persists. if not, you're almost certainly dealing with a bug/feature in icewm, and you might find more help on the icewm mailing list: http://lists.sourceforge.net/lists/listinfo/icewm-user I've already reported it to the icewm-user mailing list, but I thought slackware 10.1 users would also like to know. I believe I've narrowed this problem down. This invisible window only appears to be created when the xp-new theme (http://themes.freshmeat.net/redir/xpnew/34295/url_tgz/xpnew-default-1.1.tar.gz) is used with slackware 10.1. It could be a problem with an updated component of slackware 10.1, but it's most likely a bug in icewm's theme handling code. Or maybe my PCs just don't like anything related to Windows? Only my children use this theme, so the simple solution to this problem is to use another theme - and that appears to be a good workaround. Peter
[Original] [Print] [Top]

« Previous thread
tracking of Rosetta probe flyby

Slackware Linux Discussions
Page. 71

Next thread »
New project: The Slack World

Web	unixresources.net

This page created on 2007-08-01 12:45:26, cost 0.023733854293823 ms.