On Sun, May 10, 2015 at 5:43 PM, Jeremy Whiting jpwhit...@kde.org wrote:
Somehow kbuildsycoca5 is crashing here lately. I nuked my whole kde
prefix (/usr/local) and rebuilt with packaged qt from my distro
(arch). But kbuildsycoca5 is crashing every time I run it with some
issue in QByteArray.
Hey all,
Somehow kbuildsycoca5 is crashing here lately. I nuked my whole kde
prefix (/usr/local) and rebuilt with packaged qt from my distro
(arch). But kbuildsycoca5 is crashing every time I run it with some
issue in QByteArray. Has anyone seen this lately/before or know how I
can get past it?
It sure isn't. I've also tried nuking ~/.cache/ksycoca5* and such.
Same result. ~/.cache is owned by me and has decent permissions also.
On Sun, May 10, 2015 at 6:21 AM, Bhushan Shah bhus...@gmail.com wrote:
On Sun, May 10, 2015 at 5:43 PM, Jeremy Whiting jpwhit...@kde.org wrote:
Somehow
Also, while this is happening I did a package upgrade to see if it's a
Qt packaging problem. I got another update of Qt packages from the
arch repo (5.4.1-6 now) But I still get the same issues (kbuildsycoca5
crash and login dbus issue). I'll start a fresh rebuild and look later
today I guess.
On Sunday 10 May 2015 07:49:48 Jeremy Whiting wrote:
==2883== Address 0x is not stack'd, malloc'd or (recently) free'd
This must be a miscompilation, I see no other reason for the refcount of a
QByteArray to be at address 0x.
Try rebuilding kservice from scratch.
--
David
On Sunday 10 May 2015 08:24:48 Jeremy Whiting wrote:
Rebuilt kservice (and nuked my build folder and /usr/local just to be
doubly sure.) kbuildsycoca5 still crashes with this same backtrace, no
idea why. Could it be a bug in QtCore? Arch testing packages of Qt?
I doubt it. More likely a
I see. Some kde applications segfault (klettres, okular) other's run
ok (dolphin, khangman) I haven't tried others. As for qt binaries I
checked the binaries that come with the arch package, and assistant,
designer, qdbusviewer all work fine. Is there one in particular I
should check?
On Sun, May
Also, none of the recent patches on
https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/qt5
make me nervous, all seem to be pretty straightforward. Could it be
lower level as in my glibc is too new, or the compiler itself (GCC
5.1.0)
On Sun, May 10, 2015 at 8:54 AM, Jeremy
On Sunday 10 May 2015 06:13:15 Jeremy Whiting wrote:
#7 0x004363d0 in QLinkedListKSycocaResource::detach
(this=0x69b140) at /usr/include/qt/QtCore/qlinkedlist.h:99
Is that Qt4 or Qt5?
Use ldd on your kbuildsycoca5 binary to check which Qt libs it's using.
(and the next step if all
Yep, it's Qt5. After rebuilding everything trying to log into a plasma
session I get startkde: could not sync environment to dbus in
.xsession-errors, not much before that besides a bad dbus call. Seems
very similar to https://bugzilla.redhat.com/show_bug.cgi?id=1191171
I've never thought
Rebuilt kservice (and nuked my build folder and /usr/local just to be
doubly sure.) kbuildsycoca5 still crashes with this same backtrace, no
idea why. Could it be a bug in QtCore? Arch testing packages of Qt?
0x is -1, no? did it get decreased one too many times somehow?
On Sun, May 10,
El Diumenge, 10 de maig de 2015, a les 08:57:28, Jeremy Whiting va escriure:
Also, none of the recent patches on
https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/qt
5 make me nervous, all seem to be pretty straightforward. Could it be lower
level as in my glibc is too
I only built kf5/kde applications. Though I've no idea what compiler
was used to build the Qt packages. probably g++ 4.9 from arch stable I
bet. /me removes testing, downgrades the dozen packages from it and
will rebuild. Thanks for the tips both of you. Hopefully I can finish
the 15.04.1 release
\o/ KService built with a downgraded (4.9.1) g++ works fine. Sorry for
the noise. Should be able to detect this sort of problem quickly in
the future though. I'll stick with non testing arch for the time
being.
On Sun, May 10, 2015 at 10:07 AM, Jeremy Whiting jpwhit...@kde.org wrote:
I only
14 matches
Mail list logo
