Slackware :: Freezes After Certain Screensavers Operate For A While?
Nov 7, 2010
So I've been using Slackware for a long time but I'm not really sure where to start with this bug. Basically I'm on an old P4 Dell system that I just got for free (so semi-old hardware)
I have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards.
just installed openSuse on my desktop. Ever since I've been having problems with screensavers. When I open screensaver preferences, I can click on and see previews of all of the 2D screensavers, but the 3D screensavers just give me a black screen as a previews (even when I ask for a fullscreen preview). how-to fix this situation so that I can run 3D screensavers?
I just noticed that my screensaver was not working in Fedora 14 x86_64 / Gnome. I searched in Yumex on "screensaver" and reinstalled all that were marked as installed, but no joy. Not only does the screensaver not come on (it is set to 30 minutes) but if I go into Preferences > Screensaver and click on one of the choices it does not display the selected screensaver in the preview window. That is, none of them display except Floating Feet and Floating Fedora Bubbles. What is going on is to discover where those two screensavers come from as opposed to the others. i.e., what packages are they from?
I'm running KDE, with 11.2 32-Bit. At first, my screen saver worked just fine, coming on after 130 min, being just long enough to watch a movie. Since changing the screen saver, but not the duration before activation my screen saver comes on every 20 min. I have tried changing and saving settings in YaST and going back to the original choice of screensaver, neither of which have worked.
I run a molecular biology lab and we like to run the "Molecule" GL screensaver in order to look cool (I know it doesn't actually save screens, and it wastes energy, but you know..). I'm about to install Opensuse 11.3 on all 24 of our laptops and I find that the number of GL screensavers installed as standard is greatly reduced from previous Opensuse releases. Any idea where I can get the "Molecule" and other screensavers?
I am running KDE and have the following relevant packages installed: kdeartwork4-screensaver xscreensaver xscreensaver-data xscreensaver-data-extra gnome-screensaver gnome-screensaver-extra This apparently gives me just 8 GL screensavers - there used to be a great many more?
I recently updated to OpenSUSE 11.3 with KDE 4.4.4 . I do not find the great series of screensavers which existed in previous versions. I look in sysemsettings, desktop, but there I find only two version of blank screen as screensaver and no way to install something else.
I was wondering if there is an application that allows the computer to chose a screensaver at random from a specific list that you make. I know that you can make the computer choose any screensaver at random, but I want it to choose only the ones I specify at random. I have about 6 screensavers that I want it to choose at random.
don't use gnome/KDE or XFCE, I use Ratpoison. Because of this, the normal state of my computer is to show my wallpaper which rotates often enough that I don't need or want a screensaver.How do I stop the screen from going black every ten minutes? This is also bad when I watch a movie.
I copied some xscreensavers into the screensavers folder which is in usr/applications/screensavers. Now when I go to my screensaver application, they don't show up at all. What should I do? I am running Ubuntu 10.10.
I have slackware 13.37-64 bit with nvidia gforce 210. Since i did the installation and use the default graphic card driver (nouveau) i see that after some hours of using it suddenly freezes. I can't do anything, even use alt_ctl_backspace or alt_ctl_del for reboot, so i use the button of the pc to reboot. The only thing that i have noticed is that it happens that every time it freezes i am using firefox. But i don't know if it has every relation with this. Since i'm not very experienced user and can't understand the log files i have put here the pieces of /var/log/syslog and /var/log/messages related to the time that the freeze happens:
/var/log/syslog:
Code: May 3 01:29:51 slaris udevd[1517]: bind failed: Address already in use May 3 01:29:51 slaris kernel: [ 0.281291] ACPI: PCI Interrupt Link [LN0A] enabled at IRQ 19
I just install rss-glx, - the really slick screensavers package, but there are no new screensavers being listed in the GNOME preferences panel in F13. How do I get these nice screensavers into the screensaver preferences?
I've recently installed the package xscreensaver-gl-extra, and noticed not one of the screensavers on that package works - all I get is a blank screen on all of them. However, I remember those screensavers working under Jaunty on exactly the same hardware (didn't test them on Karmic).How can I make them work again?
I'm running a generic kernel with Slackware64 13.37 multilib. Every now and then it freezes at the boot time. It probably happens 1 every 5-7 times, so it's not a big problem, but it indicates that something is not right.
After some idle time Slackware hangs up/freezes. When, for an example, i turn on music i can hear it on idle time but after some time music still plays but i'm losing picture (monitor detects no signal), num lock is locked, led on keyboard are turned on but won't turn off while pressing num lock. I've switched off power saving options in Slackware and on bios setup.
My spec is:
X4 620 (without overclocking) AMD 760G (Radeon HD 3000) Catalyst 11.5 for Radeon graphic.
BTW - computer works fine with Windows. Also, with Slackware i can work for an hours, many hours and everything is fine but as soon as i leave it for some amount of time = it hangs/freezes. There is something wrong with hibernation. Not always computern is turned off correctly. TV is switched off, slackware logged off but i hear drives working and cooler fans. It should be switched off completly.
Some program's like Adobe Reader, Open Office and some other, when opening them, the screen is not readable an attachment )My hardware is:Code:00:02.0 VGA compatible controller:Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)It did not happen on the same hardware with OpenSuse or rhel5 installed
I installed Slackware 13.1 a little bit ago, played around with it, performed an upgrade with Slackpkg, messed around with some settings, and chose a new theme. I had set the runlevel to 4 and when I rebooted after choosing a new login theme the screen just went black at the point where the login prompt should have appeared. I couldn't even get into the CLI. Using a LiveCD, I set the run level to 3 again and was able to log in, but when I try to start X the screen goes black and freezes again, so I believe my new login theme is the culprit. Is there a way to change to the default login theme from the CLI?
so, I compiled the 2.6.35.7 kernel yesterday and used the config from 2.6.35.6 doing make oldconfig,etc
its the vanilla kernel with BFS, BFQ[*], Tuxonice, aufs2, & squashfs-lzma patches after compiling and rebooting I have noticed that the mouse freezes whenever the pc cpu is running high cpu % this didnt happen before with any other kernel and as I said, I used the 2.6.35.6 config Has anyone else had issues with 2.6.35.7 kernel? hardware is amd athlon64 3300+ 2.4ghz 1GB RAM, on 32bit Slackware -current I am going to compile the vanilla kernel now and see what happens.
New build of Slackware 13.1 x86_64 in Dell E4310 laptop. The stock install works fine barring a few bits of hardware but after recompiling the kernel X loads and immediately freezes, whence I need to soft power down (I cannot switch back to a console). On capturing stderr from the command line, when executing startx I get various warnings including:(polkit-gnome-authentication-agent-1:2368): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failedCan't really tell if the above is relevant... Sorry I can't dump the lot because the machine isn't on the net yet.
There is nothing errorwise in the Xorg log after a reboot. The very last line relates to a video mode with modeline info etc. I have compiled either into the kernel, or as modules everything I think I need though unfortunately I seem to have to load them all manually, so I hav no idea of I've missed something important. This includes all the Intel drivers i915, drm, intel_agp etc.Googling suggests bugs with polkit and I don't know why gnome has anything to do with my system in any case.Other thing that I find annoying is that xorg.conf no longer exists and I am relying on the HAL daemon, about which I know nothing. It took me ages to find how to change the X keyboard map - very frustrating. How do I confirm which video driver etc.?
When using the very nice opengl screensavers, rss-glx, etc. the screensavers are very choppy.I tried modifying my xorg.conf but still no go.Anyway to get the rss-glx screensavers to run at normal speed?I read online that Intel disable the hardware acceleration.This is a work laptop but I just wanted to see if I could get it going.
I have a Dell D620 and I can't use any screensavers. Rather, no screensavers work. Just for giggles, I booted a Kubuntu 11.04 CD, updated the sources.list, installed rss-glx and was able to use the rss-glx and other opengl screensavers. The reason I say opengl is because those are the ones that I use but no screensavers work.
I am unable to run Veracrypt on Debian 8.3 64 bit. Yet I have applied the installation procedure.
I downloaded the 1.16-veracrypt-setup.tar.bz2 archive and I unpacked in a directory veracrypt I created in my home.
I get 4 files: veracrypt-1.16-console-setup-x64; veracrypt-1.16-console-setup-x86; veracrypt-1.16-setup-gui-x64; veracrypt-1.16-setup-gui-x86
I keep 2 that match my 64-bit architecture, ie: 1.16 veracrypt-console-setup-and-x64-veracrypt 1.16-setup-gui-x64.
I log in as root in the terminal. I slip the veracrypt-1.16-setup-gui-x64 file. Validate the installation choices by default. After completing the installation, I see the icon Veracrypt and when I click on the Veracrypt application does not start.
I've used Jaunty since it came out have been quite happy with it. However, it is no longer supported and I can't access updates. When 9.10 came along, I tried to install it but found my system would randomly freeze. In fact, it randomly freezes with 10.04 as well. I tried Linux Mint's equivalent to Ubuntu's 9.10 and 10.04 and have the same problem. I've visited discussion boards and see that this is a huge problem for many Ubuntu users --- but I've never found a solution that works.
I assume the problem is in the kernel and am interested in seeing if 10.04 will run on that kernel version. My questions are these:
a) Is my conclusion that the source of my problem is the kernel a reasonable conclusion to reach?
b) If the conclusion is reasonable, is it possible to run 10.04 using the same kernel that 9.04 came in?
c) If the answer to C is, "Yes," then is there a tutorial that will walk me through how to install kernels?
I installed SalixOS on my laptop just to play with when I'm bored. My laptop is nothing special, it's a couple of years old has a pentium dual core t2390 at 1.86Ghz and 3 GB ddr2 RAM with Intel video.
I then have a beast i7 920 clocked to 3331Mhz 6GB RAM, and an NVIDIA GT220. Full screen ..... at 720p is fine unless I move the mouse, then the whole picture freezes. Persistant mouse movement will freeze the screen for a few minutes. This machine runs both slack64 current and slack13 32 bits.
The slack box does much better with 32 bit flash than 64, but it still doesn't do nearly as well as the laptop.
With Salix and Slack being so close to each other supposedly I can't figure out why the hardware seems to be irrelevant. The only thing I can think of would be the video codecs installed by Salix, whereas I built a bunch of codecs myself for Slack.