[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#269295: konsolekalendar does not insert events anymore



Package: konsolekalendar
Version: 4:3.3.0-2
Severity: grave
Tags: patch
Justification: renders package unusable

I used to insert (up to 3.2.3) many events using konsolekalendar.
As i updated to 3.3 this no loger works
Issuing such command:
/usr/bin/konsolekalendar --verbose --file=/path/to/calendar.cvs  -add --date 2004-08-29 --time 23:10 --end-date 2004-08-30 --end-time 00:10 --summary "Test insertion" --description "test"
i get a success report:
Insert Event <Verbose>:
  What:  Test insertion
  Begin: Sun Aug 29 23:10:00 2004
  End:   Mon Aug 30 00:10:00 2004
  Desc:  test
  Location:
Success: "Test insertion" inserted

If i omit --file parameter, i get these extra warnings before the success report:
kresources: WARNING: Could not connect ResourceAdded signal!
kresources: WARNING: Could not connect ResourceModified signal!
kresources: WARNING: Could not connect ResourceDeleted signal!
I couldn't enable notifications at the dcopserver!

either way, no new event is saved in calendar file 

Bug was reported to kde developers (http://bugs.kde.org/show_bug.cgi?id=88361)
 and is fixed in 3_3_BRANCH

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (910, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-zero
Locale: LANG=it_IT, LC_CTYPE=it_IT (ignored: LC_ALL set to it_IT@euro)

Versions of packages konsolekalendar depends on:
ii  kdelibs4               4:3.3.0-1.1       KDE core libraries
ii  libc6                  2.3.2.ds1-13      GNU C Library: Shared libraries an
ii  libgcc1                1:3.4.1-7         GCC support library
ii  libkcal2               4:3.3.0-2         KDE calendaring library
ii  libkdepim1             4:3.3.0-2         KDE PIM library
ii  libqt3c102-mt          3:3.3.3-4         Qt GUI Library (Threaded runtime v
ii  libstdc++5             1:3.3.4-6sarge1.2 The GNU Standard C++ Library v3

-- no debconf information



Reply to: