Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-16 Thread Thomas Müller

Hi,
Just got feedback from upstream.
0.6 will be released in Mid-April.
This release will be part of the next kubuntu release.

Any idea when squeeze freeze will start?

Thx

Tom

Am 14.03.2010 um 12:43 schrieb Evgeni Golov evg...@debian.org:


Hi Thomas,

do you have any ETA for the 0.6.0 release? If it's not tomorrow, maybe
it'll be better to have a 0.5.2 with the patch you linked to for the
time being?
Just thinking about a possible freeze soon.

Regards
Evgeni

--
Bruce Schneier can read and understand Perl programs.






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



Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-15 Thread Thomas Müller

Hi Evgeni,

I will contact upstream asap.
Ubuntu is already packaging 0.6-rc1.

0.6 is not too gar away I would guess.

Patching 0.5.2 will be easy...

We will see


Take care,

Tom

Am 14.03.2010 um 12:43 schrieb Evgeni Golov evg...@debian.org:


Hi Thomas,

do you have any ETA for the 0.6.0 release? If it's not tomorrow, maybe
it'll be better to have a 0.5.2 with the patch you linked to for the
time being?
Just thinking about a possible freeze soon.

Regards
Evgeni

--
Bruce Schneier can read and understand Perl programs.






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



Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-14 Thread Evgeni Golov
Hi Thomas,

do you have any ETA for the 0.6.0 release? If it's not tomorrow, maybe 
it'll be better to have a 0.5.2 with the patch you linked to for the 
time being?
Just thinking about a possible freeze soon.

Regards
Evgeni

-- 
Bruce Schneier can read and understand Perl programs.



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



Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-11 Thread Thomas Müller
Reproduced with 0.5.2.

Is already fixed upstream.
As soon as 0.6.0 will be released this issue can be closed.

THX,

Tom

Am Donnerstag, 11. März 2010 schrieb Sascha Korzen:
 Hi Tom,
 
 I used testing to confirm this bug.
 I disabled dbus: /etc/init.d/dbus stop
 and killed all remaining dbus processes,

This was the missing point - thx

 which were started from the X session.
 
 bye,
 Sascha
 


-- 
Thomas Müller (Thomas Mueller)

E-Mail:   thomas.muel...@tmit.eu
Packages: 
http://qa.debian.org/developer.php?login=thomas.muel...@tmit.eu

Powered by Debian


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


Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-10 Thread Sascha Korzen
found: 562974 0.5.2-3
thanks

I can confirm this bug still exists when dbus is turned off.
I tried to look at the patch from upstream, but their bug system is down.

best regards,
Sascha


Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-10 Thread Thomas Müller

Hi Sascha,

thanks for your feedback.

Can you please describe your setup and what did you do to get this error/core?

As soon as I can reproduce the bug on my system, it'll be easy to patch it.

THX,

Tom

Am Mittwoch, 10. März 2010 schrieb Sascha Korzen:
 found: 562974 0.5.2-3
 thanks
 
 I can confirm this bug still exists when dbus is turned off.
 I tried to look at the patch from upstream, but their bug system is down.
 
 best regards,
 Sascha
 


-- 
Thomas Müller (Thomas Mueller)

E-Mail:   thomas.muel...@tmit.eu
Packages: 
http://qa.debian.org/developer.php?login=thomas.muel...@tmit.eu

Powered by Debian


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


Bug#562974: quassel-client: Quassl client segfaults on first run

2010-03-10 Thread Sascha Korzen
Hi Tom,

I used testing to confirm this bug.
I disabled dbus: /etc/init.d/dbus stop
and killed all remaining dbus processes,
which were started from the X session.

bye,
Sascha


Bug#562974: quassel-client: Quassl client segfaults on first run

2010-02-19 Thread Thomas Müller
Am Freitag, 12. Februar 2010 schrieben Sie:
 On Wed, 10 Feb 2010, Thomas Müller wrote:
  Am Dienstag, 2. Februar 2010 schrieben Sie:
  Thanks, will try this shortly.
 
  -- Asheesh.
 
  Hi Asheesh,
 
  did you have the time to test the patch?
  I'd like to get this sorted out until end of Feb.
  Due to the high severity we can get in trouble with the squeeze release
  comming up in the next month.
 
  Please let me know if you have no time to take care so that I can setup a
  test environment on my side.
 
 I haven't had time to test it yet, sorry! I probably won't for the next
 couple of weeks.
 
 -- Asheesh.
 
Hi Asheesh,

I was not able to reproduce your bug.
My suspect was to turn off dbus, run quasselclient and see the crash.

But this did not work out.

Is dbus running on your machine?
Can you please update your dbus-x11 package? (I run 1.2.20-2)
Please install the debug packages for qt. (apt-get install libqt4-dbg)

Because we have no debug symbols for quassel at the moment:
Can you please recompile quassel with debug symbols?

Thanks alot,

Tom

-- 
Thomas Müller (Thomas Mueller)

E-Mail:   thomas.muel...@tmit.eu
Packages: 
http://qa.debian.org/developer.php?login=thomas.muel...@tmit.eu

Powered by Debian


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


Bug#562974: quassel-client: Quassl client segfaults on first run

2010-02-02 Thread Asheesh Laroia

Thanks, will try this shortly.

-- Asheesh.



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



Bug#562974: quassel-client: Quassl client segfaults on first run

2010-01-31 Thread Thomas Müller
Am Dienstag, 29. Dezember 2009 schrieben Sie:
 Package: quassel-client
 Version: 0.5.1-1
 Severity: grave
 Justification: renders package unusable
 
 
 When I install quassel-client from Debian sid and run it on
 my system, I get the following output:
 
 Quassel IRC:  0.5.1   7cae1afb038dd318da11c3bce23c9240eed0
 #  0 quasselclient0x082af322 Quassel::logBacktrace(QString const)
 #  1 quasselclient0x08297f58 Quassel::handleSignal(int)
 #  2  0x00e7e400 __kernel_sigreturn
 #  3 libQtCore.so.4   0x00276750 QVariant::QVariant(QVariant const)
 #  4 libQtDBus.so.4   0x005ae6a0 QDBusPendingReplyData::argumentAt(int)
  const #  5 quasselclient0x080f7137
  DesktopNotificationBackend::DesktopNotificationBackend(QObject*) #  6
  quasselclient0x080dc17a MainWin::init()
 #  7 quasselclient0x080d0806 QtUiApplication::init()
 #  8 quasselclient0x080ce296 main
 #  9 libc.so.60x00730b35 __libc_start_main
 # 10 quasselclient0x080cd731 0x
 
 It seems to be segfaulting. Do you have any suggestions?
 
 Does it work for others? If so, maybe there's something environmental
 on my system it's allergic to, and we can get a fix upstreamed.
 
 (I'm happy to let the maintainer or other Quassel developers log in to my
  machine to try things.)
 
 -- Asheesh.
 
 -- System Information:
 Debian Release: squeeze/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
  'experimental') Architecture: i386 (i686)
 
 Kernel: Linux 2.6.30-8-generic (SMP w/2 CPU cores)
 Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to
  en_US.UTF-8) Shell: /bin/sh linked to /bin/bash
 
 Versions of packages quassel-client depends on:
 ii  dbus-x11  1.2.14-3   simple interprocess messaging
  syst ii  libc6 2.10.1-7   GNU C Library: Shared
  libraries ii  libgcc1   1:4.4.0-6  GCC support library
 ii  libqt4-dbus   4:4.5.3-4  Qt 4 D-Bus module
 ii  libqt4-network4:4.5.3-4  Qt 4 network module
 ii  libqt4-webkit 4:4.5.3-4  Qt 4 WebKit module
 ii  libqtcore44:4.5.3-4  Qt 4 core module
 ii  libqtgui4 4:4.5.3-4  Qt 4 GUI module
 ii  libstdc++64.4.0-6The GNU Standard C++ Library
  v3 ii  quassel-data  0.5.1-1distributed IRC client
  using a cen
 
 Versions of packages quassel-client recommends:
 pn  quassel-core  none (no description available)
 
 quassel-client suggests no packages.
 
 -- no debconf information
 

Is your dbus-daemon running?
In case not I'd assume you detected a bug in the upstream code, which was most 
likly fixed yesterday:
http://bugs.quassel-irc.org/projects/quassel-
irc/repository/revisions/42ff4d2a759746ccd65440a0dfc2e233e0b777ed

Maybe you get the chance to apply these changes to the code and test.


THX,

Tom

-- 
Thomas Müller (Thomas Mueller)

E-Mail:   thomas.muel...@tmit.eu
Packages: 
http://qa.debian.org/developer.php?login=thomas.muel...@tmit.eu

Powered by Debian


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


Bug#562974: quassel-client: Quassl client segfaults on first run

2009-12-29 Thread Asheesh Laroia
Package: quassel-client
Version: 0.5.1-1
Severity: grave
Justification: renders package unusable


When I install quassel-client from Debian sid and run it on
my system, I get the following output:

Quassel IRC:  0.5.1   7cae1afb038dd318da11c3bce23c9240eed0 
#  0 quasselclient0x082af322 Quassel::logBacktrace(QString const) 
#  1 quasselclient0x08297f58 Quassel::handleSignal(int) 
#  2  0x00e7e400 __kernel_sigreturn 
#  3 libQtCore.so.4   0x00276750 QVariant::QVariant(QVariant const) 
#  4 libQtDBus.so.4   0x005ae6a0 QDBusPendingReplyData::argumentAt(int) 
const 
#  5 quasselclient0x080f7137 
DesktopNotificationBackend::DesktopNotificationBackend(QObject*) 
#  6 quasselclient0x080dc17a MainWin::init() 
#  7 quasselclient0x080d0806 QtUiApplication::init() 
#  8 quasselclient0x080ce296 main 
#  9 libc.so.60x00730b35 __libc_start_main 
# 10 quasselclient0x080cd731 0x 

It seems to be segfaulting. Do you have any suggestions?

Does it work for others? If so, maybe there's something environmental
on my system it's allergic to, and we can get a fix upstreamed.

(I'm happy to let the maintainer or other Quassel developers log in to my 
machine
to try things.)

-- Asheesh.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-8-generic (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages quassel-client depends on:
ii  dbus-x11  1.2.14-3   simple interprocess messaging syst
ii  libc6 2.10.1-7   GNU C Library: Shared libraries
ii  libgcc1   1:4.4.0-6  GCC support library
ii  libqt4-dbus   4:4.5.3-4  Qt 4 D-Bus module
ii  libqt4-network4:4.5.3-4  Qt 4 network module
ii  libqt4-webkit 4:4.5.3-4  Qt 4 WebKit module
ii  libqtcore44:4.5.3-4  Qt 4 core module
ii  libqtgui4 4:4.5.3-4  Qt 4 GUI module
ii  libstdc++64.4.0-6The GNU Standard C++ Library v3
ii  quassel-data  0.5.1-1distributed IRC client using a cen

Versions of packages quassel-client recommends:
pn  quassel-core  none (no description available)

quassel-client suggests no packages.

-- no debconf information



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