Bug#488909: tasque: Returns error return value when launched again

2008-07-02 Thread Sebastian Dröge
forwarded 488909 http://bugzilla.gnome.org/show_bug.cgi?id=541190
thanks

Am Mittwoch, den 02.07.2008, 10:43 +1000 schrieb Brett Nash:
 Package: tasque
 Version: 0.1.6-1
 Severity: minor
 
 
 I run E17 without a system tray, so when I want to show my tasque window I
 click on the tasque icon in the menu.  
 
 Tasque (correctly) detects a running tasque instance, and that instance shows
 itself on the current desktop, and the new instance exits with a return code
 of 255 and prints the following message:
 [Debug]: Tasque is already running.  Exiting...
 
 Unfortunately e17 (correctly from my view) detects that the application failed
 to start and shows a dialog to this effect.
 
 Tasque really should not return an error code in this case (the debug message
 is fine).
 
 As a user, it seems to me like tasque started correctly (window appeared -
 that's what I wanted), a running process in the background is irrelevant to
 me.  (As a software developer it seems strange to return an error when there
 really isn't any error seems strange - a running process that couldn't be
 contacted would be an error).

Thanks, you're right. It should return 0 if nothing bad happend :)

I've forwarded your bug upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=541190


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Bug#488909: tasque: Returns error return value when launched again

2008-07-01 Thread Brett Nash
Package: tasque
Version: 0.1.6-1
Severity: minor


I run E17 without a system tray, so when I want to show my tasque window I
click on the tasque icon in the menu.  

Tasque (correctly) detects a running tasque instance, and that instance shows
itself on the current desktop, and the new instance exits with a return code
of 255 and prints the following message:
[Debug]: Tasque is already running.  Exiting...

Unfortunately e17 (correctly from my view) detects that the application failed
to start and shows a dialog to this effect.

Tasque really should not return an error code in this case (the debug message
is fine).

As a user, it seems to me like tasque started correctly (window appeared -
that's what I wanted), a running process in the background is irrelevant to
me.  (As a software developer it seems strange to return an error when there
really isn't any error seems strange - a running process that couldn't be
contacted would be an error).

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

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tasque depends on:
ii  libc6  2.7-10GNU C Library: Shared libraries
ii  libevolution3.0-cil0.17.1-2  CLI bindings for Evolution
ii  libglib2.0-cil 2.12.1-1  CLI binding for the GLib utility l
ii  libgnome2.0-cil2.20.1-1  CLI binding for GNOME 2.20
ii  libgtk2.0-cil  2.12.1-1  CLI binding for the GTK+ toolkit 2
ii  libmono-corlib2.0-cil  1.9.1+dfsg-1  Mono core library (2.0)
ii  libmono-sqlite2.0-cil  1.9.1+dfsg-1  Mono Sqlite library
ii  libmono-system-web2.0-cil  1.9.1+dfsg-1  Mono System.Web Library
ii  libmono-system2.0-cil  1.9.1+dfsg-1  Mono System libraries (2.0)
ii  libmono2.0-cil 1.9.1+dfsg-1  Mono libraries (2.0)
ii  libndesk-dbus-glib1.0-cil  0.4.1-1   CLI implementation of D-Bus (GLib 
ii  libndesk-dbus1.0-cil   0.6.0-1   CLI implementation of D-Bus
ii  libnotify0.4-cil   0.4.0~r2998-1 CLI library for desktop notificati
ii  mono-runtime   1.9.1+dfsg-1  Mono runtime

Versions of packages tasque recommends:
ii  evolution-data-server 2.22.1.1-2 evolution database backend server

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]