Processing commands for cont...@bugs.debian.org:
# doesn't affect stable
tags 564058 + squeeze sid
Bug #564058 {Done: Fathi Boudra f...@debian.org} [k3b] k3b: recommends
obsolete kdebase-kio-plugins
Ignoring request to alter tags of bug #564058 to the same tags previously set
End of message,
Processing commands for cont...@bugs.debian.org:
tag 567470 + upstream
Bug #567470 [krusader] krusader: diskdir for compatibility with total commander
Added tag(s) upstream.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tag 567470 + upstream
thanks
Hi,
that's an upstream wishlist and i can't do much at distribution level.
please, open a bug report on :
http://sourceforge.net/tracker/?atid=106488group_id=6488func=browse
and let us know the bug number to track it.
Thanks.
Cheers,
Fathi
Hi,
I cannot reproduce. Opening a fresh krusader install, bring me krusader wizard.
Some seconds later, I have the default view.
Could you attach to the bug report a screenshot of the issue ?
Could you try to remove ~/.kde/share/config/krusaderrc and retry ?
Thanks.
Cheers,
Fathi
FYI: The status of the gtk-qt-engine source package
in Debian's testing distribution has changed.
Previous version: 1:1.1+svn5-2
Current version: 1:1.1+svn5-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the kdesudo source package
in Debian's testing distribution has changed.
Previous version: 3.4.2.1-1
Current version: 3.4.2.3-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the k3b source package
in Debian's testing distribution has changed.
Previous version: 1.0.5-3
Current version: 1.70.0~beta1-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
Am Donnerstag, 25. Februar 2010 schrieben Sie:
Hi,
have you reproduced with version 1.0.5-3 or 1.70.0~beta1-2 ?
Cheers,
Fathi
Oh, sorry, you are right: I should have mentioned, that I am using
1.70.0~beta1-2.
Further versions worked perfectly for me.
Cheers
Hans