Everytime my system boots, it displays 4 tux penguins above the text... however; on one of my older systems, it only displays 1 tux penguin... and on another it displays 2...So each time I boot, I have curiosity about this trivial issue, and now I can't take it anymore; I need to find out: what controls the number of tuxes when booting?
View 3 RepliesI have xine in gnome on Slackware 13.1. On every other distro I've used, even when xine is in fullscreen, I can still hit 'g' to pop up the controls. But in slackware 13.1, fullscreen hides the controls. Anybody know if it's some strange way the slackware package was built? Or is a xine version thing where this behavior was changed? Or something with gnome? I don't recall the other versions of xine I had on other distros, but even Mint 8 that I have installed right now shows me the controls even in fullscreen.
View 2 Replies View RelatedJust thought I'd give you guys a heads up incase you wern't aware, someone over on the ubuntu forums wrote a program in java that changes the lights on your alienware laptop. It may work with the desktop's as well.
I'll just post a link to my build script and you can follow it from there: [url]
Also, if you build HAL against libsmbios (from Dell) You'll get some bonus keys working as well, such as the eject key.
I love this new alienware M15X... It's a freaking beast of a laptop with 2 quad i7core procs....
I have a PowerPC installation (fully patched) of Ubuntu 10, and I pulled down the MythTV suite on top (since there is no Mythbuntu/PPC that I found). I'm having an issue where after I scan for channels with my tuner using mythtv-setup, I can't set the starting channel number. Its almost as if nothing ever populates into the drop down. This seems to be specific to the combination that I have - Ubuntu 10 + PPC + Myth 0.23. If I use another x86 + Myth .21 and the same Tuner (HDHomeRun), I can set the starting channel fine. A Mac OS 10.4 + Myth .21 also allowed me to set the channel. I've rebuilt this install twice now and it won't allow me to set it. I can see the scanned data in the mythconverg database, so I know its there.
View 1 Replies View RelatedHow do i re size my Slackware partition without deleting it and starting over, I'm new to Slackware and the work i have done i don't feel like doing again.I have set my swap and my actual HDD partition for Slackware to +8048M, I am correct in saying that fdisk can only delete and start fresh, I was a Ubuntu/Fedora user if i could get something like Gparted up that would be great but i don't mind some reading and learning some more terminal based stuff.Planning on working out the kinks and dealing with the learning curve, Love to learn.
View 12 Replies View RelatedKernel 2.6.21.5, Slackware 12.0
Code:
root@darkstar:~# blkid
/dev/sda: LABEL="MAESTRO!" UUID="4730-D359" TYPE="vfat"
/dev/hdc: LABEL="STORE1 ver. 2 (overrules ver. 1)" TYPE="iso9660"
[code]...
As you can see, the first command gives numbers like C841-0655. But for the optical disks (iso9660) it gives them not. Neither does the second one. This number is known as 'Volume serial number' in MS-DOS, and is printed on console with the command 'dir' not only for the HDD partitions but for the optical disks too. how to get an optical disk Volume serial number? Notice that this number is inherent to the media (is a property of the media, under any O.S.).
I have a problem about my eth. i have 2 network cards. my problem is after i boot my computer with -current my eth0 keep changing number, why this happen? im not using dhcp and i assign an static ip in my eth0.
Code:
There seems to be a typo on Slackware.com security advisory webpage for the updated ssl packages (but not for the actual packages on ftp.slackware.com). The webpage says this:
openssl-0.9.8m-i486-1_slack12.2.tgz
openssl-solibs-0.9.8m-i486-1_slack12.2.tgz
The package in the ftp.slackware.com/12.2/patches/packages repository is:
openssl-0.9.8n-i486-1_slack12.2.tgz
openssl-solibs-0.9.8n-i486-1_slack12.2.tgz
I am guessing its a typo on the webpage because I already have an 'm' installed.
I run both slackware and the stupid OS "windows " on my laptop, after choosing Slackware -> Loading tux Read BIOS data check succesfull. Undefined video mode number:? Press enter to view a list or space to ...... (actually i don't remember " or wait 30 seconds.
I press enter and select a video mode then continue loading , but i dont want to do that every time so i edited lilo.conf and changed vga = ? to different numbers but it did not work.
I have done nothing with the system, but starting this morning, i experienced a strange condition on my desktop. I'm unable to open any applications at all. It will close instantly.
When i tried to run from terminal, it will give me an error like this:
Quote:
I checked using
Code:
And i got around 234 which is too much that it takes almost all of the open files allowed. Logging out to text and brings back X will solve the problem, but it's only a temporary solution until X opens more sockets again. I'm running -Current (32 bit)
It seems that there's a hackish solution in here: [url]. Dunno whether it's a nice solution or not, but i'm willing to try it.
I ran installpkg on seamonkey 2.0.4, on Slackware 13.0, and it appeared to install OK. I can run /usr/bin/seamonkey -version and I get the 2.0.4 version number. However, when I run it without arguments, no windows get opened, and there are no errors that I have located (eg messages, syslog). This is probably something real obvious, but I'm drawing a blank. BTW, firefox runs OK.
View 12 Replies View RelatedI've apparently messed up something I guess with the rc.M file. When I boot the system it goes to
Code: Starting HAL Daemon: /usr/sbin/hald --daemon=yes
and it freezes.
I have a 16GB flash drive with grub2 installed on it so I can boot Linux iso's in place of burning 200 CD's. I looked at the isolinux.cfg file and came up with this:
Code:
menuentry "Slackware 13.1 64bit" {
linux /boot/slackware/13.1/64-bit/bzImage initrd=/boot/slackware/13.1/64-bit/initrd.img load_ramdisk=1 prompt_ramdisk=0 rw SLACK_KERNEL=huge.s root=/dev/ram0
}
However the kernel panics because it cannot mount the root file system. It gives me the options of using my partitions. What should I put for the root parameter?
I'm having trouble starting non-kde window managers. From the start-up command line, I get an error message about the XServer when typing "fluxbox" in as a command. However, when I put fluxbox in as a command in konsole, it gives an error message (which makes sense because I was using kde). I also can't start xfce as it is not a recognized command.
View 8 Replies View RelatedIs there a way to start X programs as root from a root login shell?
I generally get an error about being unable to open the display.
My Slackware64 13.1 system is running off a notebook that does not leave the desk often so I stay connected via a ethernet cable. Recently I set up the wireless configuration for my home network and while I would like to have it so that it automatically goes to the wireless interface when the wired is down, I do not think that is possible without wicd or some other network manager. Anyway, whenever I start up Slackware both the wired and wireless interfaces activate and acquire their own IP addresses. What I would like is for the wireless configuration to remain dormant so that all I would have to do is issue "ifconfig wlan0 up" to turn on the wireless interface/connection. Is this possible? As it stands I have to manually issue the "ifconfig wlan0 down" to turn it off once the system boots up and I log in.
View 4 Replies View RelatedKDE 3.5.4Kernel 2.6.17.13Slack 11A few weeks ago, my system locked up and I had to do a hard reboot (hold down power button). When I powered back on, the programs (KDE System Guard, Konsole window, MythFrontEnd) that were running at the time of the lockup appeared again. I exited System Guard and the Konsole window and then restarted normally. However, they keep appearing in the same spot when I log in to KDE. I looked through some logs in /var/log, but I don't see anything I haven't seen before.I deleted the /home/myuser/.kde/cache-hostname folder and its contents while in single-user mode, but that had no impact
View 4 Replies View RelatedI'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
Code:
# udev rules for gpsd
# $Id: gpsd.rules 5861 2009-08-03 13:41:01Z bzed $
[code]....
How to stop starting daemons at boot time? For example:rc.bluetooth
View 3 Replies View RelatedI download "VirtualBox-3.1.2-56127-Linux_amd64.run" and installed it, and got a messages like this " virtualbox have been installed successfully in my system", but when I run virtualbox, I've been told "/etc/init.d/vboxdrv setup" something like that. And I run virtualbox in terminal, got this:
Warning: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.29.6) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
I run "/etc/rc.d/rc.vboxdrv start" as a root, got messages like this :
Starting VirtualBox kernel module ...failed!
(modprobe vboxdrv failed.)
In 13.1, I added these lines to /etc/rc.d/rc.local
Code:
su - g -c startx
firefox
xrvt
jedit
kwrite
Everything starts except jedit. Yet when I put jedit in at the terminal, it starts normally. But jedit in rc.local does do something, it mutes all sounds for all users. Googling the problem produced only the ideas that $JAVA_HOME or $PATH was the problem. But I don't believe that is so in this case:
Code:
root@darkstar:~# echo $PATH
/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/jre/bin:/usr/lib/java/bin:/usr/lib/kde4/libexec:/usr/lib/qt/bin:/usr/share/texmf/bin
root@darkstar:~# echo $JAVA_HOME
/usr/lib/java
root@darkstar:~# su g
g@darkstar:/root$ echo $PATH
/usr/local/bin:/bin:/usr/bin
g@darkstar:/root$ echo $JAVA_HOME
/usr/lib/java
g@darkstar:/root$
But even if it were, why should the command to start Jedit produce different actions depending on whether it is executed in a script or at a terminal?
I just installed today's updates (apart from XFCE, which I had installed from Robby's website) and get the following error when I try to start exaile:
Code:
INFO : Loading Exaile 0.3.0.1...
INFO : Loading settings...
INFO : Setting up deferred idle manager function...
INFO : Loading plugins...
INFO : Loading collection...
INFO : Loading devices...
INFO : HAL Providers: [<cd.CDHandler object at 0x15c2e50>]
INFO : Loading interface...
/usr/lib64/exaile/xlgui/__init__.py:82: GtkWarning: Unable to locate theme engine in module_path: "thinice", 'ExaileWindow', 'exaile')
Segmentation fault
I'm looking at the changelogs and can't figure out which one is the culprit.
I've just recently install slackware 13.1 on IBM R40e laptop but every time i try to start fluxbox with
startfluxbox it just comes up:
However xdm works.
The specs of the computer:
IBM R40e 2684 L9G
2.4GHz Intel celeron processor
128MB ram
ATI radeon 330M 16MB integrated
30GB hard drive
DVD rom drive
I'm not sure if it's of any use but here's my xorg.conf file:
Code:
I am trying to switch to KDE4.4.5 on my main machine. I installed the KDE packages and also the german language file. Everything works fine except the language settings. When I try to start it crash and a KDE crash dialog opens that gives this "developer information":
Code:
Application: System Settings (systemsettings), signal: Segmentation fault
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module>
from gobject import register
[code].....
It works on my netbook. I run on both machines Slackware 13.1. The only difference I can think of is that KDE was pre-installed on my netbook and I just upgraded it. On my main machine I installed all packages except the packages of kde and kdei.
Slack 13.0 X sometimes fails to start after boot about 50% of the time. linux says "starting X11 session" then I get a blank screen with a flashing cursor and absolutely nothing else. I can <ctrl>-<alt>-<F7> and get a text prompt, log in, and startx from a command prompt. After that, I can reboot once or twice and still get a graphic login, but will soon revert to the dumped condition. I have reinstalled X and KDE twice now as well as deleting my .kde folder. This condition started when I inadvertently ran out of disk space on my /home drive. Since then I have migrated /home to a larger drive and watch it's disk space very carefully.
View 14 Replies View RelatedIf I set the clock to speak the time, I get this when it tries: starting kttsd failed. I've looked at the various posts, but haven't yet found an actual solution. I've tried to run kttsmgr, but for some reason the "run" dialog doesn't seem to do anything - no error, nothing. Type kttsmgr, press enter since there is not obvious other way to execute the command, and nothing happens.
Is this a module that does not come with KDE? And I give - I can't find time format anywhere. How do you change the clock that appears in the lower right corner to 12 hour instead of what appears to be default 24 hour? I don't see it in "Digital Clock Settings", and I don't see it in System Settings - Date & Time. This is a clean install of slackware 13.1, and whatever version of KDE comes with it.
When I start acroread (and as far as I can tell it's only that program), I get the error message
But the program still starts, no problem. Happens with both
I just installed GNOME SlackBuild and it just errors on no xclients file and drops me in to fail safe mode where do I get an xclients file ?ORhow do I make one ?
View 3 Replies View RelatedI would like to know what is the file I need to edit to change the "startx" command from starting kde. I would like for it to start gnome instead. I just cant seem to find it. I'm using slackware 13.0.
View 12 Replies View RelatedWhy does unix ps -l whows one number in column "PRI" but in same time ps -o pri shows another number? cpu and nice are zero for those processes
View 1 Replies View Related