Bug#373177: kmplot: Looks for rgb.txt in wrong place

[Thomas Weber]

Package: kmplot
Version: 4:3.5.2-1+b1
Severity: normal

Hi, 

1.) Try to select a color for a plot
2.) Choose "Named Colors"

Error message:
Unable to read X11 RGB color strings. The following file location(s) were 
examined:
/usr/lib/X11/rgb.txt
/usr/X11R6/lib/X11/rgb.txt
/usr/openwin/lib/X11/rgb.txt

It should look in /etc/X11/rgb.txt or /usr/share/X11/rbg.txt (which is a
symlink). 

Thanks
  Thomas

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686-smp
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages kmplot depends on:
ii  kdelibs4c2a 4:3.5.3-1core libraries and binaries for al
ii  libc6   2.3.6-15 GNU C Library: Shared libraries
ii  libgcc1 1:4.1.1-3GCC support library
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libpng12-0  1.2.8rel-5.1 PNG library - runtime
ii  libqt3-mt   3:3.3.6-2Qt GUI Library (Threaded runtime v
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libstdc++6  4.1.1-3  The GNU Standard C++ Library v3
ii  libx11-62:1.0.0-6X11 client-side library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  zlib1g  1:1.2.3-11   compression library - runtime

Versions of packages kmplot recommends:
ii  kdeedu-data   4:3.5.2-1  shared data for KDE educational ap

-- no debconf information


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

Bug#372856: krandrtray does NOT correctly switch resolution on my setup

[Nikita V. Youshchenko]

While trying to add xrandr support to Xvnc, I faced a bug in xrandr 
implementation in XFree 4.x; maybe current Xorg also has it?

Bug is that xrandr stores the moment of last switch as 64-bit value. Then, 
in 'get configuration' request it sends this time to client as 32-bit 
value. In 'set configuration' request clents should return same value to 
the server. Idea is to check situation when other client has changed 
configuration since this client last read it.

Problem is with timestamp compare in implementation of 'set configuration' 
request. It compares 64 bit values; before that, it converts 32 bit value 
got from client to 64 bit value by guessing the 'nearest' 64bit value (see 
ClentTimeToServerTime() routine).
In practice this may result in comparison failure because of difference in 
higher word. This happens at least in two cases:
- if enough ime (about a month) passed since last configuration (or server 
startup)
- [much more probable] if system time went backwards at some moment (ntp? 
date -s?), X server manually increases higher word of it's server time to 
avoid server time going backwards.

If this problem raises, nor xrandr -s, not krandrtray, nor any other xrandr 
client is able to switch configuration until X server restarts.


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

Bug#372856: krandrtray does NOT correctly switch resolution on my setup

[VALETTE Eric RD-MAPS-REN]

Nikita V. Youshchenko wrote:
> While trying to add xrandr support to Xvnc, I faced a bug in xrandr 
> implementation in XFree 4.x; maybe current Xorg also has it?
> 
> Bug is that xrandr stores the moment of last switch as 64-bit value. Then, 
> in 'get configuration' request it sends this time to client as 32-bit 
> value. In 'set configuration' request clents should return same value to 
> the server. Idea is to check situation when other client has changed 
> configuration since this client last read it.
> 
> Problem is with timestamp compare in implementation of 'set configuration' 
> request. It compares 64 bit values; before that, it converts 32 bit value 
> got from client to 64 bit value by guessing the 'nearest' 64bit value (see 
> ClentTimeToServerTime() routine).
> In practice this may result in comparison failure because of difference in 
> higher word. This happens at least in two cases:
> - if enough ime (about a month) passed since last configuration (or server 
> startup)
> - [much more probable] if system time went backwards at some moment (ntp? 
> date -s?), X server manually increases higher word of it's server time to 
> avoid server time going backwards.
> 
> If this problem raises, nor xrandr -s, not krandrtray, nor any other xrandr 
> client is able to switch configuration until X server restarts.

Thanks for answering. However, problem is diffrérent there: xrandr works
and krandtray does not work. The thruth is that xrandr does display the
Mhz garbled :

 SZ:Pixels  Physical   Refresh
*0   1280 x 1024   ( 342mm x 272mm )  *-19557
 1   1400 x 1050   ( 342mm x 272mm )   -19557
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none

But at least if I do :
xrandr -S [0/1] it works and does change the resolution.

Note that it is a dual head setting with mergefb option set. When I use
the same config on single head, the MHz option are correctly displayed.

-- 
Eric Valette
France Telecom
Recherche & Developpement
Middleware et Plates-formes Avancées
tél : (+33) 2 99 12 45 71
mél : 


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

Bug#373220: kdvi crashes on logout

[fexpop]

Package: kdvi
Version: 4:3.5.3-1
Severity: normal


kdvi crashes on every logout from a KDE session. The logout gets stuck 
at that point until closing the KDE crash handler.

Here's the backtrace:

###

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232713440 (LWP 11315)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0xb67466d6 in KViewPart::writeSettings ()
   from /usr/lib/kde3/kviewerpart.so
#6  0xb67492be in KViewPart::~KViewPart () from 
/usr/lib/kde3/kviewerpart.so
#7  0xb78d1dfe in QPtrList::deleteItem () from 
/usr/lib/libkdeui.so.4
#8  0xb71fd614 in QGList::clear () from /usr/lib/libqt-mt.so.3
#9  0xb751d597 in KLibrary::~KLibrary () from /usr/lib/libkdecore.so.4
#10 0xb751dc23 in KLibLoader::close_pending () from 
/usr/lib/libkdecore.so.4
#11 0xb751e08e in KLibLoader::~KLibLoader () from 
/usr/lib/libkdecore.so.4
#12 0xb74c14ab in KLibLoader::cleanUp () from /usr/lib/libkdecore.so.4
#13 0xb756a3e3 in KApplication::~KApplication () from 
/usr/lib/libkdecore.so.4
#14 0x0805043f in ?? ()
#15 0xbff37044 in ?? ()
#16 0x0001 in ?? ()
#17 0x0001 in ?? ()
#18 0x in ?? ()

###

Kind regards,

Felix

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.9-jawaka-dvb
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kdvi depends on:
ii  kdelibs4c2a   4:3.5.3-1  core libraries and binaries for al
ii  kviewshell4:3.5.3-1  generic framework for viewer appli
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libfreetype6  2.2.1-2FreeType 2 font engine, shared lib
ii  libgcc1   1:4.1.1-3  GCC support library
ii  libqt3-mt 3:3.3.6-2  Qt GUI Library (Threaded runtime v
ii  libstdc++64.1.1-3The GNU Standard C++ Library v3
ii  zlib1g1:1.2.3-11 compression library - runtime

Versions of packages kdvi recommends:
ii  tetex-bin 3.0-16 The teTeX binary files

-- no debconf information


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

Bug#373220: kdvi crashes on logout

[Pierre Habouzit]

Le Mar 13 Juin 2006 18:04, [EMAIL PROTECTED] a écrit :
> Package: kdvi
> Version: 4:3.5.3-1
> Severity: normal
>
>
> kdvi crashes on every logout from a KDE session. The logout gets
> stuck at that point until closing the KDE crash handler.

the backtrace is useless, please provide a good one by installing the 
relevant -dbg packages, or this report will be closed.

thanks
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgp5al0La3x2o.pgp
Description: PGP signature

[bts-link] source package kdebase

[bts-link-upstream]

#
# bts-link upstream status pull for source package kdebase
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #368504
#  * http://bugs.kde.org/show_bug.cgi?id=119435
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 368504 + fixed-upstream
usertags 368504 - status-NEW
usertags 368504 + status-RESOLVED resolution-FIXED

thanks

[bts-link] source package kdegraphics

[bts-link-upstream]

#
# bts-link upstream status pull for source package kdegraphics
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #317984
#  * http://bugs.kde.org/show_bug.cgi?id=91809
#  * remote status changed: (?) -> NEW
usertags 317984 + status-NEW

thanks

[bts-link] source package kdepim

[bts-link-upstream]

#
# bts-link upstream status pull for source package kdepim
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #303138
#  * http://bugs.kde.org/show_bug.cgi?id=120448
#  * remote status changed: UNCONFIRMED -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 303138 + fixed-upstream
usertags 303138 - status-UNCONFIRMED
usertags 303138 + status-RESOLVED resolution-FIXED

thanks

Processed: [bts-link] source package kdepim

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #
> # bts-link upstream status pull for source package kdepim
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report for #303138
> #  * http://bugs.kde.org/show_bug.cgi?id=120448
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 303138 + fixed-upstream
Bug#303138: kmail: Trying to use / character in folder names makes odd error 
message.
Tags were: upstream
Tags added: fixed-upstream

> usertags 303138 - status-UNCONFIRMED
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 303138 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#373220: kdvi crashes on logout

[Pierre HABOUZIT]

On Tue, Jun 13, 2006 at 11:04:11PM +0200, Felix Homann wrote:
> On Tuesday 13 June 2006 21:58, you wrote:
> > the backtrace is useless, please provide a good one by installing the
> > relevant -dbg packages, or this report will be closed.
> >
> > thanks
> 
> Your reply is partially useless, please provide a good one by telling me what 
> the relevant -dbg packages are and how to use them, or I won't be able to 
> [EMAIL PROTECTED]
> help.
> 
> (Sorry, but your reply sounded a little harsh compared to the helpful tone 
> you 
> usually have on the debian-kde list..)
> 
> I've investigated a bit further and found out that the crash depends on the 
> dvi file opened. I've attached a .dvi and the corresponding .tex file which 
> reliably crash kdvi on logout. Just open the kdvi-crash.dvi with kdvi and log 
> out from your KDE session. I've tested it on 2 different machines (one 
> actually still using KDE 3.5.2).
> 
> And again, please, tell me how to produce a "good" backtrace. I'll gladly 
> send 
> it to you and the bug tracking system.

  you have to install qt-x11-free-dbg, kdebase-dbg, kdelibs-dbg and
probably kdegraphics-dbg packages, so that the backtraces are not full
of (no symbol found) meaning that the backtrace cannot be used to
anything useful.

  sorry for the tone, we just have too many of those backtraces thrown
at us daily, with no explanation on how to reproduce the bug, and the
user usualy think they were useful, and it's sometimes iritating.

  if you can provide a good backtrace, with the dvi file you sent + that
backtrace, I've enough to forward the bug upstream.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


signature.asc
Description: Digital signature

Processed: [bts-link] source package kdebase

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #
> # bts-link upstream status pull for source package kdebase
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report for #368504
> #  * http://bugs.kde.org/show_bug.cgi?id=119435
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 368504 + fixed-upstream
Bug#368504: kate: kwrite crash and doesn't save modifications on file.
Tags were: moreinfo unreproducible
Tags added: fixed-upstream

> usertags 368504 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 368504 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#372564: kwalletmanager very often crashes at KDE Logout

[John Stamp]

It looks like a problem with a patch in Debian's kdeutils branch update 
(r548145).

Under certain circumstances, kwalletmanager exits and deletes _dcopRef 
before it's actually been created.  We just need to create _dcopRef 
earlier.  I've attached a slight modification to the patch that seems to 
fix it for me.

John
--- kwallet/kwalletmanager.cpp
+++ kwallet/kwalletmanager.cpp
@@ -55,22 +55,31 @@
 	_shuttingDown = false;
 	KConfig cfg("kwalletrc"); // not sure why this setting isn't in kwalletmanagerrc...
 	KConfigGroup walletConfigGroup(&cfg, "Wallet");
+	_dcopRef = new DCOPRef("kded", "kwalletd");
 	if (walletConfigGroup.readBoolEntry("Launch Manager", true)) {
 		_tray = new KSystemTray(this, "kwalletmanager tray");
 		_tray->setPixmap(loadSystemTrayIcon("wallet_closed"));
 		QToolTip::add(_tray, i18n("KDE Wallet: No wallets open."));
-		connect(_tray,SIGNAL(quitSelected()),SLOT(shuttingDown()));
+		connect(_tray, SIGNAL(quitSelected()), SLOT(shuttingDown()));
 		QStringList wl = KWallet::Wallet::walletList();
+		bool isOpen = false;
 		for (QStringList::Iterator it = wl.begin(); it != wl.end(); ++it) {
 			if (KWallet::Wallet::isOpen(*it)) {
 _tray->setPixmap(loadSystemTrayIcon("wallet_open"));
 QToolTip::remove(_tray);
 QToolTip::add(_tray, i18n("KDE Wallet: A wallet is open."));
+isOpen = true;
 break;
 			}
 		}
+		if (!isOpen && kapp->isRestored()) {
+			delete _tray;
+			_tray = 0L;
+			kapp->exit();
+			return;
+		}
 	} else {
-		_tray = 0;
+		_tray = 0L;
 	}
 
 	_iconView = new KWalletIconView(this, "kwalletmanager icon view");
@@ -81,7 +90,6 @@
 	setCentralWidget(_iconView);
 	_iconView->setMinimumSize(320, 200);
 
-	_dcopRef = new DCOPRef("kded", "kwalletd");
 	_dcopRef->dcopClient()->setNotifications(true);
 	connect(_dcopRef->dcopClient(),
 		SIGNAL(applicationRemoved(const QCString&)),

Bug#373220: kdvi crashes on logout

[Felix Homann]

On Tuesday 13 June 2006 21:58, you wrote:
> the backtrace is useless, please provide a good one by installing the
> relevant -dbg packages, or this report will be closed.
>
> thanks

Your reply is partially useless, please provide a good one by telling me what 
the relevant -dbg packages are and how to use them, or I won't be able to 
[EMAIL PROTECTED]
help.

(Sorry, but your reply sounded a little harsh compared to the helpful tone you 
usually have on the debian-kde list..)

I've investigated a bit further and found out that the crash depends on the 
dvi file opened. I've attached a .dvi and the corresponding .tex file which 
reliably crash kdvi on logout. Just open the kdvi-crash.dvi with kdvi and log 
out from your KDE session. I've tested it on 2 different machines (one 
actually still using KDE 3.5.2).

And again, please, tell me how to produce a "good" backtrace. I'll gladly send 
it to you and the bug tracking system.

Kind regards,

Felix Homann


kdvi-crash.dvi
Description: TeX dvi file
\listfiles
\documentclass[11pt,liststotoc,a4paper,pagesize,headsepline]{scrreprt}
\pagestyle{headings}
\usepackage[latin1]{inputenc}
\usepackage{hyperref}
\begin{document}


\section{kdvi crashes on logout}
\label{sec:kdvi-crashes-logout}

kdvi reliably crashes on logout from a KDE session if this file is opened.

\end{document}


%%% Local Variables: 
%%% mode: latex
%%% TeX-master: "kdvi-crash"
%%% End: 

Bug#373220: kdvi crashes on logout

[Felix Homann]

On Tuesday 13 June 2006 23:13, Pierre HABOUZIT wrote:
>   you have to install qt-x11-free-dbg, kdebase-dbg, kdelibs-dbg and
> probably kdegraphics-dbg packages, so that the backtraces are not full
> of (no symbol found) meaning that the backtrace cannot be used to
> anything useful.

Thanks, I'll try this tomorrow.

>   sorry for the tone,

No problem, really :-)

>   we just have too many of those backtraces thrown 
> at us daily, with no explanation on how to reproduce the bug, and the
> user usualy think they were useful, and it's sometimes iritating.

Maybe, the KDE crash handler should not provide backtraces without the 
relevant -dbg libraries. If it wouldn't provide useless backtraces you 
wouldn't have to bother about them. 
 
BTW, I actually thought kdvi would crash with *every* .dvi opened since it 
does so with every .dvi I produce. Your reply caused me to investigate 
further. So it's all for good!

>   if you can provide a good backtrace, with the dvi file you sent + that
> backtrace, I've enough to forward the bug upstream.

I've already send a bug report to upstream as #129099. Please, let me know if 
you would prefer me sending further information to the Debian-,  KDE- or both 
bug tracking systems.

Kind regards,

Felix 


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

Bug#372564: kwalletmanager very often crashes at KDE Logout

[John Stamp]

Duh.  Well that was a dumb way for me to submit a new patch.

How about this instead?  Drop 14_kwalletmanager.diff in debian/patches and 
recompile.

John
diff -urN kdeutils-3.5.3.orig/kwallet/kwalletmanager.cpp kdeutils-3.5.3/kwallet/kwalletmanager.cpp
--- kdeutils-3.5.3.orig/kwallet/kwalletmanager.cpp	2006-06-13 14:00:19.0 -0700
+++ kdeutils-3.5.3/kwallet/kwalletmanager.cpp	2006-06-13 14:01:05.0 -0700
@@ -55,6 +55,7 @@
 	_shuttingDown = false;
 	KConfig cfg("kwalletrc"); // not sure why this setting isn't in kwalletmanagerrc...
 	KConfigGroup walletConfigGroup(&cfg, "Wallet");
+	_dcopRef = new DCOPRef("kded", "kwalletd");
 	if (walletConfigGroup.readBoolEntry("Launch Manager", true)) {
 		_tray = new KSystemTray(this, "kwalletmanager tray");
 		_tray->setPixmap(loadSystemTrayIcon("wallet_closed"));
@@ -89,7 +90,6 @@
 	setCentralWidget(_iconView);
 	_iconView->setMinimumSize(320, 200);
 
-	_dcopRef = new DCOPRef("kded", "kwalletd");
 	_dcopRef->dcopClient()->setNotifications(true);
 	connect(_dcopRef->dcopClient(),
 		SIGNAL(applicationRemoved(const QCString&)),

Bug#373220: kdvi crashes on logout

[Pierre Habouzit]

forwarded 373200 http://bugs.kde.org/129099
thanks

Le Mar 13 Juin 2006 23:36, Felix Homann a écrit :
> >   if you can provide a good backtrace, with the dvi file you sent +
> > that backtrace, I've enough to forward the bug upstream.
>
> I've already send a bug report to upstream as #129099. Please, let me
> know if you would prefer me sending further information to the
> Debian-,  KDE- or both bug tracking systems.

the best for us is that you answer on the KDE bug tracker questions, I 
will set the debian bug as "forwarded" to the kde one, and one tool I 
wrote (called bts-link) will monitor upstream changes so that we 
automatically know when it's fixed and all is for the best for us in 
that scheme.

if you can send a useful backtrace + the dvi that causes the crash 
yourself, you would spare us a lot of time :D
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpoyhpsLGPO1.pgp
Description: PGP signature

Processed: Re: Processed: Re: Bug#373220: kdvi crashes on logout

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # crap, I mixed up the bug #
> notforwarded 373200
Bug#373200: xkbsel: FTBFS: Failed to satisfy Build-Depends dependency for 
xkbsel: xlibs
Removed annotation that Bug had been forwarded to http://bugs.kde.org/129099.

> forwarded 373220 http://bugs.kde.org/129099
Bug#373220: kdvi crashes on logout
Noted your statement that Bug has been forwarded to http://bugs.kde.org/129099.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#373263: KDE won't allow me to select "classic" X cursors

[Thomas Martinsen]

Package: kde
Version: 5:47
Severity: normal

Using my old distrobution, I selected "no theme" in KDE to get the 
orginal cursors from Xorg.
Now, when using Debian Etch, there are 10 themes, but only three of them 
are actually different.

When I select "no theme", I just get the default theme.
I've uploaded a screenshot, http://tnet.no/kdebug.jpg,
as you see, the previewed theme does not look anything like the orginal 
Xorg cursors.


-- System Information:
Debian Release: testing/unstable
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-486
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 
(charmap=ISO-8859-15)


Versions of packages kde depends on:
ii  kde-amusements5:47   the K Desktop Environment 
games an
ii  kde-core  5:47   the K Desktop Environment 
core mod
ii  kdeaccessibility  4:3.5.2-1  accessibility packages from 
the of
ii  kdeaddons 4:3.5.2-1  add-on plugins and applets 
provide
ii  kdeadmin  4:3.5.2-1  system adminstration tools 
from th
ii  kdeartwork4:3.5.2-1  themes, styles and more 
from the o
ii  kdegraphics   4:3.5.2-1  graphics apps from the 
official KD
ii  kdemultimedia 4:3.5.2-2  multimedia apps from the 
official
ii  kdenetwork4:3.5.2-1  network-related apps from 
the offi
ii  kdepim4:3.5.2-1  KDE Personal Information 
Managemen
ii  kdeutils  4:3.5.2-1  general purpose utilities 
from the
ii  kdewebdev 4:3.4.3-2  web development apps from 
the offi


kde recommends no packages.

-- debconf-show failed



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

Bug#250743: krfb: server disconnects with first action after entering password

[Filipus Klutiero]

Tell me if you need any log file, or other information.

We would need to see the error messages on the disconnection to confirm 
that you are experiencing the same bug as the submitter.



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

Processed: tagging 250743

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 250743 + moreinfo
Bug#250743: krfb: server disconnects with first action after entering password.
There were no tags set.
Tags added: moreinfo

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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