Page 3 of 4
Re: Salix KDE 14.0RC2
Posted: 15. Jun 2013, 15:33
by mimosa
djemos and I have apparently both muddled KDE with Live
@Atip The simplest way to fix whatever has gone wrong is probably just to start again. SInce you must have only just installed this, that is, it is probably painless, whereas actually getting to the root of the problem might well be anything but.
Re: Salix KDE 14.0RC2
Posted: 16. Jun 2013, 06:47
by Atip
mimosa wrote:djemos and I have apparently both muddled KDE with Live
@Atip The simplest way to fix whatever has gone wrong is probably just to start again. SInce you must have only just installed this, that is, it is probably painless, whereas actually getting to the root of the problem might well be anything but.
I said:
Search me how that happens looking for modules 3.6.10.
I did search and found the culprit: in lilo.conf image= pointing to the wrong /boot/vmlinuz. Very much
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 03:04
by loukingjr
a couple things. I installed the 32bit version in VirtualBox and like 13.37, as I have mentioned before, for some odd reason it takes "forever", 10-15 seconds or more to set the hardware clock on boot and shutdown. the 64bit versions have no such problem. the other thing is, Qupzilla crashes fairly often if the desktop effects are enabled. Firefox has no such problem. that's it so far.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 12:18
by djemos
Running salix-kde-rc2 32 bit installed in virtualbox, enabling effects, qupzilla don't crash. Run as stable as rock. No crashes for the whole system either.
Also, I can see no delays on booting.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 12:21
by loukingjr
djemos wrote:Running salix-kde-rc2 32 bit installed in virtualbox, enabling effects, qupzilla don't crash. Run as stable as rock. No crashes for the whole system either.
well, Qupzilla is the only thing that crashes for me. I was trying to upload files to my DeviantArt account. beats me.
as far as the delay, I always had the delay on 32bit versions of Salix on VirtualBox and still do. Three different Macs and many versions of VirtualBox. I suppose it could be a quirk of a Mac host, VirtualBox and Salix. I've installed well over 400 Linux guests by now and 32bit Salix is the only one I see it in.
edit: Qupzilla was also crashing when I tried to upload images to my Picasa account.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 12:49
by loukingjr
it turns out desktop effects has nothing to do with Qupzilla crashing.
Code: Select all
louis@darkstar:~$ qupzilla
QupZilla: 0 extensions loaded
kfilemodule(2620) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf
Error loading services.
"
kfilemodule(2620) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
QFont::setPixelSize: Pixel size <= 0 (0)
QupZilla: Crashed :( Saving backtrace in /home/louis/.qupzilla/crashlog ...
Backtrace successfuly saved in /home/louis/.qupzilla/crashlog/Crash-2013-06-27T08:43:31.txt
Aborted
Code: Select all
============== BACKTRACE ==============
#0: qupzilla() [0x804a862]
#1: linux-gate.so.1(__kernel_sigreturn+0) [0xffffe400]
#2: /usr/lib/qt/lib/libQtCore.so.4(_ZN9QIODevice4readEPcx+0x2e) [0xb4b046ee]
#3: /usr/lib/qt/lib/libQtCore.so.4(_ZN9QIODevice4readEx+0x1c4) [0xb4b05034]
#4: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca5523) [0xb6950523]
#5: /usr/lib/qt/lib/libQtCore.so.4(_ZN9QIODevice4readEPcx+0x16c) [0xb4b0482c]
#6: /usr/lib/qt/lib/libQtCore.so.4(_ZN9QIODevice4readEx+0x1c4) [0xb4b05034]
#7: /usr/lib/qt/lib/libQtCore.so.4(_ZN16QIODevicePrivate4peekEx+0x45) [0xb4b05125]
#8: /usr/lib/qt/lib/libQtCore.so.4(_ZN9QIODevice4peekEx+0x36) [0xb4b06136]
#9: /usr/lib/libQupZilla.so.1(_ZN14NetworkManager13createRequestEN21QNetworkAccessManager9OperationERK15QNetworkRequestP9QIODevice+0x207) [0xb74da647]
#10: /usr/lib/libQupZilla.so.1(_ZN19NetworkManagerProxy13createRequestEN21QNetworkAccessManager9OperationERK15QNetworkRequestP9QIODevice+0x6b) [0xb74d74bb]
#11: /usr/lib/qt/lib/libQtNetwork.so.4(_ZN21QNetworkAccessManager4postERK15QNetworkRequestP9QIODevice+0x28) [0xb4d365b8]
#12: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca5bae) [0xb6950bae]
#13: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca7d09) [0xb6952d09]
#14: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca6966) [0xb6951966]
#15: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca69d3) [0xb69519d3]
#16: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca7320) [0xb6952320]
#17: /usr/lib/qt/lib/libQtWebKit.so.4(+0xca20cb) [0xb694d0cb]
#18: /usr/lib/qt/lib/libQtWebKit.so.4(+0xb4cac8) [0xb67f7ac8]
#19: /usr/lib/qt/lib/libQtWebKit.so.4(+0xa951c1) [0xb67401c1]
#20: /usr/lib/qt/lib/libQtWebKit.so.4(+0xa9bb19) [0xb6746b19]
#21: /usr/lib/qt/lib/libQtWebKit.so.4(+0xa9c267) [0xb6747267]
#22: /usr/lib/qt/lib/libQtWebKit.so.4(+0xf2c55f) [0xb6bd755f]
#23: /usr/lib/qt/lib/libQtWebKit.so.4(+0xf2f2f4) [0xb6bda2f4]
#24: /usr/lib/qt/lib/libQtWebKit.so.4(+0xf2f6f4) [0xb6bda6f4]
#25: /usr/lib/qt/lib/libQtWebKit.so.4(+0xaa12e4) [0xb674c2e4]
#26: /usr/lib/qt/lib/libQtWebKit.so.4(+0xc8be44) [0xb6936e44]
#27: /usr/lib/qt/lib/libQtWebKit.so.4(+0xc8c435) [0xb6937435]
#28: /usr/lib/qt/lib/libQtWebKit.so.4(+0x7822d7) [0xb642d2d7]
#29: /usr/lib/qt/lib/libQtWebKit.so.4(+0x639f1f) [0xb62e4f1f]
#30: [0xa93ba0c9]
#31: /usr/lib/qt/lib/libQtWebKit.so.4(+0x100e4a1) [0xb6cb94a1]
I have no idea what any of this means or how to fix it.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 13:09
by gapan
loukingjr wrote:well, Qupzilla is the only thing that crashes for me.
What is the webkit package that you are using? Are you using the webkit package that came with the iso or have you upgraded it?
There is a newer one in the repos since a couple of weeks which should fix a lot of stability problems (at least it does with midori).
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 13:14
by loukingjr
/var/log/packages/webkit-1.8.3-i486-3gv
I just upgraded everything.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 13:26
by gapan
See how it behaves with the new one then.
Re: Salix KDE 14.0RC2
Posted: 27. Jun 2013, 13:27
by loukingjr
gapan wrote:See how it behaves with the new one then.
if that's the new one it still crashes.
edit: running kernel 3.2.45-smp btw