Recent Changes in Current (or things that go bump in the night).
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Rep:
Recent Changes in Current (or things that go bump in the night).
First, Xscreensaver and the changes in X do not seem to get along.
Just as the screensaver is about to kick in, the screen goes to a solid color and then locks up tight as a drum. No way out, except to hit the reset button. Happens in both KDE and Xfce. The Nvidia drivers were re-installed after all the recent X changes.
Second, in KDE 4.10, the desktop icons are locked in place and cannot be moved, and, yes, I've checked all the settings.
Third, the last change in the iptables has made the firewall I use (Alien's easy firewall) "obsolete."
Last, for now, going back a few versions of KDE, it is not possible to change the size of the desktop icons. You can go thought the motions, but the changes are not applied.
Third, the last change in the iptables has made the firewall I use (Alien's easy firewall) "obsolete."
That happened to me as well. I just re-installed Eric's firewall and then it worked just fine. I think I removed the old rc.firewall in /etc/rc.d, then generated a new script at Eric's page (chmod +x) and put it back in /etc/rc.d
I'm not having any screensaver issues in XFce 4.10.
First, Xscreensaver and the changes in X do not seem to get along.
Just as the screensaver is about to kick in, the screen goes to a solid color and then locks up tight as a drum. No way out, except to hit the reset button. Happens in both KDE and Xfce. The Nvidia drivers were re-installed after all the recent X changes.
Does this only happen when you attempt to start an OpenGL screensaver?
Quote:
Second, in KDE 4.10, the desktop icons are locked in place and cannot be moved, and, yes, I've checked all the settings.
How did you add these icons to your desktop? If I "unlock widgets" I am able to drag my desktop application icons to any other place on the desktop by grabbing the "context menu" or whatever that grey bar is called, with my left mouse button. These re-placed icons will stay in their new locations after logout/login.
Quote:
Third, the last change in the iptables has made the firewall I use (Alien's easy firewall) "obsolete."
I recently made a change to the easy firewall generator because of changed functionality in iptables, after Escaflown emailed me this bit of text:
Code:
With the new iptable, all the command with "-m state" were giving me the
following warning: "Warning: The state match is obselete. Use conntrack
instead." I had to change "-m state" with "-m conntrack --cstate " to get
rid of them.
Perhaps that fixes your problems too. Like hitest said, visit http://slackware.com/~alien/efg/ again and re-generate your rc.firewall.
I believe there is a small typo in the email snippet from Escaflown.
should read "-m conntrack --ctstate "
See 'man iptables-extensions' for details.
My thanks for pointing out this change. It had escaped my notice. Perhaps this should be given greater prominence.
Yeah I copied Escaflown's email into the above post verbatim, but I used the correct "-m conntrack --ctstate " in my update to http://slackware.com/~alien/efg/
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
@hitest and Alien Bob,
Many Thanks. Re-running the script fixed the problem.
As to more things that go bump in the night, since the upgrade of hplip, it is auto-magically turning on my printer.
Wicd: The gui comes up and when I tell it to connect it starts and then stalls. I have to click on "disconnect all" a few times, and then on "refresh" a few times, then "connect" and it finally makes the connection.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
First, Xscreensaver and the changes in X do not seem to get along.
Just as the screensaver is about to kick in, the screen goes to a solid color and then locks up tight as a drum. No way out, except to hit the reset button. Happens in both KDE and Xfce. The Nvidia drivers were re-installed after all the recent X changes.
Quote:
Originally Posted by Alien Bob
Does this only happen when you attempt to start an OpenGL screensaver?
It happens as the screensaver starts to kick in at the allotted time, i.e., xx minutes after no activity on the desktop.
Last edited by cwizardone; 02-27-2013 at 06:14 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
Fontconfig
When upgrading fontconfig it issued this error:
Quote:
Executing install script for fontconfig-2.10.2-x86_64-1.txz.
Fontconfig warning: "/etc/fonts/conf.d/44-wqy-zenhei.conf", line 11: Having multiple values in <test> isn't supported and may not work as expected
Package fontconfig-2.10.2-x86_64-1.txz installed.
This same error is displayed on every boot up just after the line, "triggering udev events."
Last edited by cwizardone; 02-27-2013 at 11:18 PM.
First, Xscreensaver and the changes in X do not seem to get along.
Just as the screensaver is about to kick in, the screen goes to a solid color and then locks up tight as a drum. No way out, except to hit the reset button. Happens in both KDE and Xfce. The Nvidia drivers were re-installed after all the recent X changes.
I suppose it is related to my problem that occured after the update - after suspending my laptop, it takes about 3 minutes for the login screen to appear; during that time it shows my desktop, but it's unrensponsive to anything but shutdown button. Maybe you should give your screensaver a little bit more time and see if it goes?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
The "fixed" fontconfig, reports the same error as the first build:
Quote:
Executing install script for fontconfig-2.10.2-x86_64-2.txz.
Fontconfig warning: "/etc/fonts/conf.d/44-wqy-zenhei.conf", line 11: Having multiple values in <test> isn't supported and may not work as expected
Package fontconfig-2.10.2-x86_64-2.txz installed.
Package fontconfig-2.10.2-x86_64-1 upgraded with new package ./fontconfig-2.10.2-x86_64-2.txz.
The "fixed" fontconfig, reports the same error as the first build:
Shouldn't be happening unless the old wqy-zenhai-font-ttf package is still on your system. I checked it here, anyway, and don't get an error from fc-cache unless I install the old one.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
Thank you Mr. Volkerding. That is exactly what happened. I had downloaded the new package, but somehow managed to not install it... Still scratching my head over that one.
Last edited by cwizardone; 03-02-2013 at 08:31 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.