SliTaz Forum
You are not logged in.
Midori 0.4.4 crashes e.g. with kwick.de as well.
Better solution for me still is firefox or iron.
Hopefully the Midori developers get this fixed.
Offline
@mojo
,,I only speak english :-)"
What I want to talk about is really OT. How can we arrange that? (Chat programs I do not like, though...)
Offline
@aniguenni
Start midori in xterm.
When it crash's I get this error:
midori: cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed.
Aborted
kwick.de crashes,as well as if I type into the URL or search bar and hit enter.
Same issue with tazweb since it's somehow libwebkit related.
Problem only happens on my 2004 AthlonXP computer not a problem on the others.
There are bug reports on it as well as https sites causing crashes from some midori users.
Offline
@mojo Maybe your 2004 old schooler is sick. 
(Possibly bad caps O_O)
I just hope it don't have GSCs!
Has Midori crashed on weather.com for anybody?
With the early builds, I bet it would crash when I go to the local forecast section.
Offline
@mojo: I found on another forum about CAIRO_STATUS_SUCCESS' failed. this issue because libgcrypt 1.5.0. usually occurs when accessing url with password login. and can be solved with a downgrade version of libgcrypt. but, I do not know how.
Offline
when are you going to release slitaz 4.0 Stable (final) ?
Offline
@aniguenni
Please install this: http://people.slitaz.org/~mojo/packages/libgcrypt-1.4.6.tazpkg
It fixed all issues on my computer with midori 0.4.4 problems.
@rd.nmc
Thanks for the information on downgrading libgcrypt :-)
Offline
@ mojo
thank you for your assistance. i installed the above. but kwick.de still stucks. after that i did upgrade libgcrypt to 1.5.0 but without any effect. still stucking kwick website. ;-(
but this is not a major problem. the more important thing is to get my windows programs running such as garmin mapsource. on search engine i read that this will run stable with newer wine version as 1.2.3.
Offline
Hi everyone.
I've tried to run SliTaz on HP 6510b
No matter which version of 4.0 (RC1, RC2, RC3, rolling isos) I boot, no wireless networks are found.
Module for iwl3945 is detected and loaded I guess, just no networks visible.
I'm a beginner, please advice me how should I proceed to get workin wlan0
P.S. eth0 works fine.
This hint doesn't work for me http://forum.slitaz.org/topic/no-joy-on-toshibe-tecra-m7-with-iwl3945-wireless#post-4225
Offline
@ tazspider
maybe because of missing firmware?
try to install the related firmware iwl3945.
same problems i have had with my lifebook (module ipw2200). it shows the module after tazhw detect-pci but on dmesg | grep (your module) i got the message, that the firmware is missing. after installing, do the following steps:
modprobe -r iwl3945
modprobe iwl 3945
nano /etc/network.conf
and change the following:
WIFI="yes"
WIFI INTERFACE="eth0"
put your essid, mode, key and key type into the relevated places and if you have WPA, than don't forget
WPA-DRIVER="wext"
after that
/etc/init.d/network.sh restart
good luck ;-)
Offline
@aniguenni
Thank you. It works now 
Finally I can start testing Slitaz.
Offline
----- Boot Options
What is the difference between "SliTaz Live" and "SliTaz core Live"?
----- Group
In "/etc/group" both, tape and haldaemon have the same group identifier 26. Shouldn't the GID be unique?
----- LXpanel
The panel still disappears when the "Minimize all windows" applet is clicked. Since task manager reports that LXpanel is still running, I guess the panel has itself been "minimized". One way around this is to remove both default panels and to create a new blank panel. The "Minimize all windows" applet works normally in this panel.
----- Opera
After installation, Opera can be started in the "Live" and "Core Live" versions but not in "GTKonly Live", which returns in the terminal "Could not initialize Opera". There seem to be missing dependencies, either in the Opera package or in "GTKonly Live". In the other two Slitaz versions Opera works well until one tries to close it, which brings up an ugly looking Qt box saying:
It appears another Opera instance is using the same configuration directory because its lock file is active: /home/tux/.opera/lock
Do you want to start Opera anyway? y/n
... at the same time the terminal says:
opera [crash logging]: Crash log writing failed, error writing to file
/var/tmp/crash20120321000553.txt! Illegal instruction
----- Boot Log: Slitaz Live and Slitaz Core Live
Starting TazBox configuration...
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
after 3241 requests (3240 known processed) with 0 events remaining.
error setting MTRR (base = 0xe0000000, size = 0x08000000, type = 1) Invalid argument (22)
----- Boot Log: Slitaz GTKonly Live
Starting TazBox configuration...
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.1.log" for additional information.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
(yad:1352): Gtk-WARNING **: cannot open display: :1
----- GTKonly: wish list
- audio should be configured by default
- boot-up should prompt for keymap and locale
- GTK/Yad boxes for Tazpkg and Tazlito would be nice
Offline
I forgot to mention that I was using last night's "slitaz-rolling.iso", 2012-Mar-20 21:14:59.
Offline
Installed RC 3 on an older Dell laptop.
I have no internet.
wireless find my router, says it's connected & shows me signal strength but no internet.
With wired LAN I got nothing.
Doesn't seem like DHCP is working.
Any ideas?
Offline
WPA-PSK.
Though slitaz calls it just WPA I added "-PSK" to it with same affect.
It doesn't do anything when I put that into a terminal.
Actually, it seems like everything dies after I put in my passkey & hit connect.
i'm no longer able to see any of the wireless networks until I reboot.
Offline
@nitrogen_widget
try to do like I mentioned bevor to tazpider.
step-by-step in xterm (you need to have internet access to be prepared for downloading missing drivers):
1) type "su" <return>
2) type "root" <return> (to become administrator state)
3) type "tazhw detect-pci" <return> (to get info about the loaded kernel modules)
4) dmesg | grep [your module] <return> (to get information about the activity of ypur modules. if you get a message that firmware is missing, then continue the following)
5) tazpkg get-install [your missing driver] <return> (for downloading and installing the missing module
6) modprobe -r [your driver] <return> (for stopping the related module)
7) modprobe <return> (to restart the module)
8 ) nano /etc/network.conf <return> (to modify your network configuration and if necessary verify and change the following)
WIFI="yes" (for set wifi to accessibility)
WIFI_INTERFACE="eth0" (this has to be done for the use of the wifi. wlan0 won't work. don't know why but it is so)
WIFI_ESSID="your network" (as shown on your wifi net)
WIFI_MODE="your mode" (mostly used "managed")
WIFI_KEY="your wifi key" (needed for wep or wpa secured networks)
WIFI_KEY-TYPE="your specified wifi key type" (none if none, WEP or WPA. if for example WPA-2 only type WPA)
WPA-DRIVER="wext" (urgent to put in this argument if you have WPA Key Type)
9) <strg> + "o" (for saving the changes in network.conf)
10) <strg> + "y" (to overwrite the existing network.conf)
11) <strg> + "x" (to exit nano)
11) /etc/init.d/network.sh restart <return> (to restart teh new settings)
if everything went right than you'll have internet access by wlan now. if not, pls. do not hesitate to paste your outputs here.
Offline
@anniguenni
,,WIFI_INTERFACE="eth0" (this has to be done for the use of the wifi. wlan0 won't work. don't know why but it is so)"
Is this correct in general or only in case of a special adapter?
Offline
except guys, I don't even have wired LAN.
Any other distro I can boot up with & have at least wired LAN. (except tiny core)
That one don't like me either.
Offline
@anniguenni
In some cases it worked with
WIFI_INTERFACE="wlan1"
or
WIFI_INTERFACE="ra0"
so I question that this is a condition to be met under all circumstances.
@nitrogen_widget
In case you do not show output (of ifconfig, lsmod etc.) you behave indeed like nitrogen: non-reactive! ;-)
Offline
"try to do like I mentioned bevor to tazpider [...]"
In ma case just installing firmware helped
Another issue I found:
I'm using slitaz-core.iso from 20th of March. After taz-usb writefs (no matter which compression) and rebooting I get "Failed to execute login command". Only root account is working, it looks like tux has disappeared.
Is it me doing something wrong, or it's a known bug?
Offline
@tazpider
No, it is no bug. When you apply tazubs writefs only the filesystem, including root, but => not home, is written to /. When you boot the next time there is an empty home/tux account that can not login, of course.
The option tazlito writeiso writes the whole filesystem including /home/tux, but to /home/slitaz/disto/rootcd/boot/. There you find one rootfs.gz-file.
If you copy this to the partition you boot from all changes will have been stored and you have a working /home/tux-account.
Offline
@michaelbischof
I tried, but I get "Unable to mount the cdrom tocopy thekernel and needed files. [...]"
Didn't find anything helpful in man page. I'm using USBstick - do I have to burn a CD anyway?
Offline
I can't boot the RC3/Rolling - isos on my EEE-PC. Using unetbootin leads to an (often discussed) Kernel panic. The solid dd command doesn't lead to the goal bc it seems that the above mentioned isos aren't hybrid ones.
Will it be fixed on the 4.0 release? Already the RC2 worked on my EEE-PC well, so probably there is no much need to test the RC3. But at least I wanted to mention that there is this problem so that for the stable release, it could be fixed.
Offline
Syslogd with the -L argument does not listen on network interface, and so it still only logs locally. I've tried syslogd -L -R HOST:PORT too. Still nothing listening on port UDP 514.
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]