Bug#737095: qdbus segfaults

2014-02-04 Thread Lisandro Damián Nicanor Pérez Meyer 
The fix will be included in 5.2.1.

To hack around the bug, uninstall qt5-default and export QT_SELECT:=5 when 
building apps.

Thanks for your report!

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-02-04 Thread Lisandro Damián Nicanor Pérez Meyer 
On Monday 03 February 2014 08:51:17 Philipp Marek wrote:
[snip] 
> $ gdb -ex r --args qdbus org.kde.kmail2 /kmail2/kmail_composer_1
> Program received signal SIGSEGV, Segmentation fault.
> 0x774eb082 in QMetaProperty::typeName() const () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> (gdb) bt
> #0  0x774eb082 in QMetaProperty::typeName() const () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #1  0x00405d72 in ?? ()
> #2  0x76beb995 in __libc_start_main (main=0x404090, argc=0x3,
> ubp_av=0x7fffe0e8, init=, fini=,
> rtld_fini=,
> stack_end=0x7fffe0d8) at libc-start.c:276
> #3  0x00406563 in ?? ()

I have kmail runnning and opened a composer window. Then:

lisandro@tonks:~$ gdb -ex r --args qdbus -qt4 org.kde.kmail2 
/kmail2/kmail_composer_1
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/qtchooser...(no debugging symbols found)...done.
Starting program: /usr/bin/qdbus -qt4 org.kde.kmail2 /kmail2/kmail_composer_1
warning: no loadable sections found in added symbol-file system-supplied DSO at 
0x77ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
process 7526 is executing new program: /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Error: org.freedesktop.DBus.Error.UnknownObject
No such object path '/kmail2/kmail_composer_1'
[Inferior 1 (process 7526) exited with code 02]
(gdb) quit

lisandro@tonks:~$ gdb -ex r --args qdbus -qt5 org.kde.kmail2 
/kmail2/kmail_composer_1
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/qtchooser...(no debugging symbols found)...done.
Starting program: /usr/bin/qdbus -qt5 org.kde.kmail2 /kmail2/kmail_composer_1
warning: no loadable sections found in added symbol-file system-supplied DSO at 
0x77ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
process 7536 is executing new program: /usr/lib/x86_64-linux-gnu/qt5/bin/qdbus
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Error: org.freedesktop.DBus.Error.UnknownObject
No such object path '/kmail2/kmail_composer_1'
[Inferior 1 (process 7536) exited with code 02]
(gdb) quit

Another team mate can find it using kmail 4:4.11.3-1, but I'm running sid's 
4:4.11.5-1.

Do you happen to have mixed KDE stuff? ie, from testing and sid, or 4.11.3 and 
4.11.5.

Kinds regards, Lisandro.

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-02-02 Thread Philipp Marek 
> Excellent, so most probably solved by qt 5.2.0, as we can't reproduce
> it with that version.
Well, I can.

 
> Good news: I'm currently compiling qt5 to push it to unstable, so you
> have two options:
> 
> - apt-get install -t experimental qtbase5-dev=5.2.0+dfsg-6
> 
> or
> 
> - wait ~24hs and upgrade your system :)

$ dpkg-query -l | grep qt\S*5
ii  libqt5concurrent5:amd64 5.2.0+dfsg-7   
rc  libqt5core5:amd64   5.1.1+dfsg-6+b2
ii  libqt5core5a:amd64  5.2.0+dfsg-7   
ii  libqt5dbus5:amd64   5.2.0+dfsg-7   
ii  libqt5gui5:amd645.2.0+dfsg-7   
ii  libqt5network5:amd645.2.0+dfsg-7   
ii  libqt5opengl5:amd64 5.2.0+dfsg-7   
ii  libqt5opengl5-dev   5.2.0+dfsg-7   
ii  libqt5printsupport5:amd64   5.2.0+dfsg-7   
ii  libqt5sql5:amd645.2.0+dfsg-7   
ii  libqt5sql5-mysql:amd64  5.2.0+dfsg-7   
ii  libqt5test5:amd64   5.2.0+dfsg-7   
ii  libqt5widgets5:amd645.2.0+dfsg-7   
ii  libqt5xml5:amd645.2.0+dfsg-7   
ii  qdbus-qt5   5.2.0-9
ii  qt5-default 5.2.0+dfsg-7   
ii  qt5-qmake   5.2.0+dfsg-7   


$ gdb -ex r --args qdbus org.kde.kmail2 /kmail2/kmail_composer_1
Program received signal SIGSEGV, Segmentation fault.
0x774eb082 in QMetaProperty::typeName() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x774eb082 in QMetaProperty::typeName() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00405d72 in ?? ()
#2  0x76beb995 in __libc_start_main (main=0x404090, argc=0x3, 
ubp_av=0x7fffe0e8, init=, fini=, 
rtld_fini=, 
stack_end=0x7fffe0d8) at libc-start.c:276
#3  0x00406563 in ?? ()


Regards,

Phil


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#737095: qdbus segfaults

2014-01-31 Thread Lisandro Damián Nicanor Pérez Meyer 
On Friday 31 January 2014 08:52:51 Philipp Marek wrote:
> > Almost everything :) qt5-default will not pull the rest of the new
> > stuff.
> > 
> > But please, before upgrading anything, please send the output of
> > 
> > dpkg -l qt5-dbus
> 
> $ dpkg -l qt5-dbus
> dpkg-query: no packages found matching qt5-dbus
> $ dpkg -l qdbus-qt5 libqt5dbus5
> ii  libqt5dbus5:amd645.1.1+dfsg-6+b2
> ii  qdbus-qt55.1.1-2

Excellent, so most probably solved by qt 5.2.0, as we can't reproduce it with 
that version.

> > So we can be sure of what exact version we are talking about. After
> > that I'll tell you how to upgrade the rest.
> 
> Yes, please?

Good news: I'm currently compiling qt5 to push it to unstable, so you have two 
options:

- apt-get install -t experimental qtbase5-dev=5.2.0+dfsg-6

or

- wait ~24hs and upgrade your system :)

-- 
http://mx.grulic.org.ar/lurker/message/20081108.174208.4f42e55c.es.html
Así se corrobora el software legal en Argentina

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-01-30 Thread Philipp Marek 
> Almost everything :) qt5-default will not pull the rest of the new
> stuff.
> 
> But please, before upgrading anything, please send the output of
> 
> dpkg -l qt5-dbus
$ dpkg -l qt5-dbus
dpkg-query: no packages found matching qt5-dbus
$ dpkg -l qdbus-qt5 libqt5dbus5
ii  libqt5dbus5:amd645.1.1+dfsg-6+b2   
ii  qdbus-qt55.1.1-2   

 
> So we can be sure of what exact version we are talking about. After
> that I'll tell you how to upgrade the rest.
Yes, please?
 

> qt5-default should only be used if you are developing things. Else
> apps will just use the Qt version they where compiled for. You don't
> need to do anything.
> 
> OTOH, if you are developing things, you can avoid qt5-default too.
> 
> Thanks and I'll wait for your reply to this mail :)
Well, cl-qt needs the header files, so I'll just keep that installed.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#737095: qdbus segfaults

2014-01-30 Thread Lisandro Damián Nicanor Pérez Meyer 
reassign 737095 qdbus-qt5 5.1.1-2
thanks

On Thursday 30 January 2014 15:22:45 Philipp Marek wrote:
> > 1) Try calling qdbus with:
> > 
> > gdb -ex r --args qdbus -qt4 org.kde.kmail2 /kmail2/kmail_composer_1
> 
> That works.

OK, now we know it's Qt5's qdbus which is crashing. I'm so reassigning it.

> > 2)
> > 
> > If you are using unstable you might want to try Qt 5.2.0 from
> > experimental.
> 
> Hmmm, I got qt5-default=5.2.0something - but that's not enough.
> 
> libqt5core5 has no 5.2.0 - what else should get upgraded?

Almost everything :) qt5-default will not pull the rest of the new stuff.

But please, before upgrading anything, please send the output of

dpkg -l qt5-dbus

So we can be sure of what exact version we are talking about. After that I'll 
tell you how to upgrade the rest.


> > 3) Remove qt5-default. That will make qt4 the default Qt stack. If you
> > want to develop stuff under Qt5 you can always use CMake or export
> > QT_SELECT=qt5, see [0]
> 
> Well, I wanted to get to QT5 at some time ...
> 
> So I don't really have an opinion about which way to choose.

qt5-default should only be used if you are developing things. Else apps will 
just use the Qt version they where compiled for. You don't need to do 
anything.

OTOH, if you are developing things, you can avoid qt5-default too.

Thanks and I'll wait for your reply to this mail :)


-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-01-30 Thread Philipp Marek 
> 1) Try calling qdbus with:
> 
> gdb -ex r --args qdbus -qt4 org.kde.kmail2 /kmail2/kmail_composer_1
That works.
 

> 2)
> 
> If you are using unstable you might want to try Qt 5.2.0 from
> experimental.
Hmmm, I got qt5-default=5.2.0something - but that's not enough.

libqt5core5 has no 5.2.0 - what else should get upgraded?


> 3) Remove qt5-default. That will make qt4 the default Qt stack. If you
> want to develop stuff under Qt5 you can always use CMake or export
> QT_SELECT=qt5, see [0]
Well, I wanted to get to QT5 at some time ...

So I don't really have an opinion about which way to choose.


Thanks for the quick answer!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#737095: qdbus segfaults

2014-01-30 Thread Lisandro Damián Nicanor Pérez Meyer 
[snip]
> But those symbols are Qt5 related. Do you happen to have qt5-default
> installed?

If you have qt5-default installed, please allow me to sugegst some stuff to 
see what could be going wrong:

1) Try calling qdbus with:

gdb -ex r --args qdbus -qt4 org.kde.kmail2 /kmail2/kmail_composer_1

2) 

If you are using unstable you might want to try Qt 5.2.0 from experimental.

3) Remove qt5-default. That will make qt4 the default Qt stack. If you want to 
develop stuff under Qt5 you can always use CMake or export
QT_SELECT=qt5, see [0]

[0] 


Kinds regards, Lisandro.

-- 
If for every rule there is an exception, then we have established that there
is an exception to every rule.  If we accept "For every rule there is an
exception" as a rule, then we must concede that there may not be an exception
after all, since the rule states that there is always the possibility of
exception, and if we follow it to its logical end we must agree that there
can be an exception to the rule that for every rule there is an exception.
  Bill Boquist

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-01-30 Thread Lisandro Damián Nicanor Pérez Meyer 
tag 737095 unreproducible moreinfo
thanks

On Thursday 30 January 2014 08:58:47 Ph. Marek wrote:
> Package: qdbus
> Version: 4:4.8.5+git209-g718fae5+dfsg-1
> Severity: normal
> 
> With kmail running, and an compose window open, qdbus crashes for me:
> 
> 
> $ gdb -ex r --args qdbus org.kde.kmail2 /kmail2/kmail_composer_1
> 
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> method void org.kde.kmail.mailcomposer.send(int how)
> 
> property readwrite bool org.qtproject.Qt.QMainWindow.documentMode
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x7750b082 in QMetaProperty::typeName() const () from
> /usr/lib/x86_64 -linux-gnu/libQt5Core.so.5
> (gdb) bt
> #0  0x7750b082 in QMetaProperty::typeName() const () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #1  0x00405b5d in ?? ()
> #2  0x76c33995 in __libc_start_main (main=0x404090, argc=0x3,
> ubp_av=0x7fffe0d8, init=, fini=,
> rtld_fini=,
> stack_end=0x7fffe0c8) at libc-start.c:276
> #3  0x004063ca in ?? ()

But those symbols are Qt5 related. Do you happen to have qt5-default 
installed?

-- 
$ make war
make: *** No rule to make target `war'.  Stop.  Try `love' instead
  David Gravereaux

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#737095: qdbus segfaults

2014-01-30 Thread Ph. Marek 
Package: qdbus
Version: 4:4.8.5+git209-g718fae5+dfsg-1
Severity: normal

With kmail running, and an compose window open, qdbus crashes for me:


$ gdb -ex r --args qdbus org.kde.kmail2 /kmail2/kmail_composer_1

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
method void org.kde.kmail.mailcomposer.send(int how)

property readwrite bool org.qtproject.Qt.QMainWindow.documentMode

Program received signal SIGSEGV, Segmentation fault.
0x7750b082 in QMetaProperty::typeName() const () from /usr/lib/x86_64
-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x7750b082 in QMetaProperty::typeName() const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00405b5d in ?? ()
#2  0x76c33995 in __libc_start_main (main=0x404090, argc=0x3,
ubp_av=0x7fffe0d8, init=, fini=,
rtld_fini=,
stack_end=0x7fffe0c8) at libc-start.c:276
#3  0x004063ca in ?? ()



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qdbus depends on:
ii  libc6   2.17-97
ii  libgcc1 1:4.8.2-14
ii  libqt4-xml  4:4.8.5+git209-g718fae5+dfsg-1
ii  libqtcore4  4:4.8.5+git209-g718fae5+dfsg-1
ii  libqtdbus4  4:4.8.5+git209-g718fae5+dfsg-1
ii  libstdc++6  4.8.2-14
ii  qtchooser   39-g4717841-2

qdbus recommends no packages.

qdbus suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org