Kino-(kino:5747): Gtk-WARNING **: cannot open display: :0
I've installed Kino 0.9.5. When I try to open it I get (kino:5747): Gtk-WARNING **: cannot open display: :0
I've Googled and searched this forum. I assume I need to set a config file somewhere that tells GTK which display to use(?) Any ideas which? |
Is there any special reason you choose 0.9.5? It has been released in January 2007 and there are newer versions. I have for example 1.3 running. I had not the time to test in on Slackware 12.1 yet but at least it starts OK :)
|
I get the same error when I try to start either 1.3 or 0.9.5.
I tried 1.3 first then uninstalled that and tried 0.9.5. |
Sorry but I'm probably not much help here. I compiled kino and dependencies without problem and can start it without a problem too. Is there a chance that you are running a graphical login manager and try to start it from command line as user "root"?
|
Thanks for your replies. That was the problem, it's always the simplest things that seem to cause the most trouble.
I just installed 1.3 from source again and now it loads ok. However, I now have the following message under the IEEE 1394 tab in Preferences The IEEE 1394 Subsystem is not responding The raw1394 module must be loaded and you must have read and write access to /dev/raw1394 I remember this from when I was using Debian/Ubuntu a while ago but the remedy for that refers to a file that isn't present in Slackware, or has a different name. Also when I do modprobe raw1394 I get WARNING: Error inserting ieee1394 (/lib/modules/2.6.24.5-smp/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format I'm on unknown ground here and may well be doing something wrong. Any further help would be appreciated as I'm that much closer to being able to use Kino in Slackware. |
Something is wrong with your kernel modules package. When I try the modprobe I see this on a fresh Slackware 12.1:
Code:
# modprobe raw1394 |
Quote:
|
Thanks Eric, I was wondering whether it was something like that. I upgraded from 12.0 to 12.1. I didn't experience any problems with the upgrade. I followed the procedure from the Slackware website and everything went ok.
Could the upgrade be the cause? If so, is there anything I can do about it? Here's what I get when I duplicate your output: # modprobe raw1394 WARNING: Error inserting ieee1394 (/lib/modules/2.6.24.5-smp/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format # ls -1 /dev/raw1394 /dev/raw1394 # lsmod |grep 1394 raw1394 27096 0 Alien Bob, thanks, I have made sure I'm a member of the video group. |
Quote:
|
Hi... Just thought I'd chime in here as I too am getting that same errors when I try to load the 1394 modules.
My scenario: Fresh install of 12.1, followed by fresh install of latest GnomeSlackBuild for SW12.1 (which includes Kino 1.3 in its installation). Would dearly love to get to the bottom of this as I like Slack and I need Kino/dvgrab! If there's any more info I can provide just let me know. cheers Edit: Kernel info... bash-3.1$ uname -a Linux Slack12 2.6.24.5-smp #2 SMP Wed Apr 30 13:41:38 CDT 2008 i686 Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz GenuineIntel GNU/Linux |
Do you only get an error message or is dvgrab really not working properly? I'm not sure what happens if you have the "huge" kernel installed and try to modprobe an included module. So maybe you get an error but it's already working???
Cave: I haven't tested dvgrab on my new setup because work is eating all my time :( I hope to have some spare time tomorrow to test it. If I were you and if the problem persisted I would just recompile the kernel (with the config file for Pat's "generic-smp" kernel) and create a new initrd.gz file if needed. This resolved any similar problems for me in the past. |
Quote:
2.6.24.5-smp Looks ok(?) |
I'm not sure if you can tell from this output if you are running the generic or huge kernel image, but doubt it. I would rather take a look in /boot and respectively your lilo.conf. If you have referenced "vmlinuz" as kernel, where is /boot/vmlinuz linked to?
|
Quote:
image="/boot/vmlinuz" root="/dev/hda1" label="Slackware" /boot/vmlinuz linked to vmlinuz-huge-smp-2.6.24.5-smp |
The IEEE1394 module is compiled into the kernel in the huge-smp kernel, and compiled as a module in the generic-smp kernel. This is probably your problem. You should switch to the generic kernel. Please don't ask how, try searching -- it's been explained several thousand times in these forums. It is recommended that you use the generic-smp kernel instead of the huge-smp kernel in the official documentation that came with your Slackware installation/upgrade:
Quote:
Quote:
|
D'oh! My bad... The one step I forgot to do was switching to generic the kernel. It was a late night!
Yep I searched and found the posts and other reference info for the kernel stuff. So now I've plugged in the DV camera and all working in Kino and checked dmesg! My daughter will be so happy now!!! Thanks for the help. BTW Am liking Slack a lot, had tried it many, many years ago (circa 1995!) when at uni but had never really taken it further when i was working. Then a few years back came back to try Linux again moving thru various distros (Suse 8, Mandrake and Debians) but wanted to try Slack again... And am quite happy with it! No guru so heaps to learn with Slack. At least it's a rock solid distro with enough of everything I need installed and anything more can be easily had/installed... with some learning! cheers |
Success
Changed to generic kernel and that did it.
Many thanks to everyone who took the time to help improve my knowledge. |
All times are GMT -5. The time now is 05:22 PM. |