Problem with kmail.
by Dragseth Roy Einar
Hi.
First of all, thanks for all the great work you all are doing in maintaining
this beast called KDE!
I've got a problem which can be described as follows:
When I've read a message in my inbox and move to the next unread one by
hitting the +-button, then the message I'm moving from isn't deselected. So
when I hit the delete button to delete the current message I'm also deleting
the one I read before. This is quite annoying, esp. when the previous one is
outside the visible part of the message list, then you have no clue that you
deleted another mail too. I can work around this by hitting + - LeftArrow -
RightArrow as that will clear the previous selection, but it becomes a bit
strainful on my fingers when I come to work on Monday morning...
Anyone else seeing this? I could not find any bugreports related to this at
the kde website so I thought I'd ask here first.
KDE Version 1.11.0 (KDE 4.2.00 (KDE 4.2.0), 4.2.0-15.fc10 Fedora)
Application E-Mail Client
Operating System Linux (x86_64) release 2.6.27.15-170.2.24.fc10.x86_64
Compiler gcc
r.
--
The Computer Center, University of Tromsø, N-9037 TROMSØ Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, Team Leader, High Performance Computing
Direct call: +47 77 64 62 56. email: roy.dragseth(a)uit.no
15 years, 2 months
Widget Configuration file
by Reuben D. Budiardja
Hello,
I accidentally removed the QuickLaunch widget that I painstakingly arranged
just now. After I added it, of course all my configuration for that particular
widget is gone. However, I have my daily backup of my home directory. Is there
a file that I can just restore to get my old configuration back ?
Thanks.
RDB
15 years, 2 months
Step back to 4.2.0
by Christoph Kaulich
Hi,
as I have some troubles and a bug filed, is there way to step back to 4.2.0?
Is there some kind of archive?
Thanks
Chris
15 years, 2 months
(OT) python file-truncate on fc10 zero-fills file: who to ask?
by John Pilkington
Hi: I'm asking here because this is the most fc10-oriented list that I
use and I thought someone might know the answer. I'd be happy to ask
elsewhere but don't know where might be the best place.
I'm trying to do shrink-to-fit with video files on fc10 after tcrequant
was deprecated. vamps looks as if it will do the job but I think I need
to chop off a few kb from the end of the input file first to avoid a
failure exit. I can do this with dd but that's slow and file truncation
would be better. I can't see a command-line truncate but since I am
hacking the mythburn.py script I thought I had found the answer here, in
truncate([size]) :
http://www.python.org/doc/2.5.2/lib/bltin-file-objects.html
I've tried that. The file size shrinks as required but the result is
zero-filled. Here's some stripped-down test code:
vobsize = os.path.getsize(source)
write("Initial vobsize is %s bytes" % vobsize)
vobsize -= 2048
f=open(source,'wb')
f.truncate( vobsize )
f.close()
vobsize = os.path.getsize(source)
write("vobsize after truncation is %s bytes" % vobsize)
Is this a known problem with python, or in its fc10 implementation?
Where would be the best place to ask how to do this job?
TIA
John Pilkington
15 years, 2 months
Size mismatch
by Eli Wapniarski
Hi Rex
This happens quite frequently. Please don't forget that I've configured repomd
Failed to fetch http://apt.kde-redhat.org/apt/kde-redhat//fedora/10/x86_64/testing/RPMS/k... Size mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
This happens quite frequently. Please don't forget that I've configured repomd
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years, 2 months
Plasma from KDE 4.2.1-3.FC10 segfaults at KDE startup (Fedora 10 / x86_64)
by Chris January
I have installed KDE 4.2.1-3.FC10 from the kde-redhat kde-testing
repository and plasma segfaults when KDE is
starting up. Can anyone tell me how to work out what's wrong?
I have also opened a kde-redhat Sourceforge bug tracker ticket:
2667738 but I'm not sure if that's the correct place to report bugs.
Backtrace:
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents
creation of proper backtraces, or the stack frame was seriously corrupted
in the crash.
(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 0x7feeda9e5840 (LWP 10713)]
0x0000003b7c4a7f50 in __nanosleep_nocancel () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7feeda9e5840 (LWP 10713))]
Thread 1 (Thread 0x7feeda9e5840 (LWP 10713)):
#0 0x0000003b7c4a7f50 in __nanosleep_nocancel () from /lib64/libc.so.6
#1 0x0000003b7c4a7da7 in __sleep (seconds=<value optimized out>) at
../sysdeps/unix/sysv/linux/sleep.c:138
#2 0x0000003f1746731f in ?? () from /usr/lib64/libkdeui.so.5
#3 0x0000003f17467c7a in KCrash::defaultCrashHandler () from
/usr/lib64/libkdeui.so.5
#4 <signal handler called>
#5 QTimer::stop (this=0x0) at kernel/qtimer.cpp:246
#6 0x000000000014c750 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#7 0x000000000014e8c0 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#8 0x0000003f14f59082 in QMetaObject::activate (sender=0x1cec4d0,
from_signal_index=<value optimized out>, to_signal_index=40, argv=0x4af) at
kernel/qobject.cpp:3069
#9 0x0000003f1ad18258 in ?? () from /usr/lib64/libplasma.so.3
#10 0x0000003f1ad17899 in Plasma::View::qt_metacall () from
/usr/lib64/libplasma.so.3
#11 0x000000000014e865 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#12 0x0000003f14f59082 in QMetaObject::activate (sender=0x193e850,
from_signal_index=<value optimized out>, to_signal_index=6, argv=0x4af) at
kernel/qobject.cpp:3069
#13 0x0000003f1acaddf8 in Plasma::Applet::itemChange () from
/usr/lib64/libplasma.so.3
#14 0x0000003f1acb9738 in Plasma::Containment::itemChange () from
/usr/lib64/libplasma.so.3
#15 0x0000003f1695b232 in QGraphicsItemPrivate::setPosHelper (this=<value
optimized out>, pos=<value optimized out>, update=true) at
graphicsview/qgraphicsitem.cpp:2364
#16 0x0000003f1acb92c5 in ?? () from /usr/lib64/libplasma.so.3
#17 0x0000003f1acb981f in Plasma::Containment::resizeEvent () from
/usr/lib64/libplasma.so.3
#18 0x0000003f169a2278 in QGraphicsWidget::event (this=0x193e850,
event=0x7fffe2a292d0) at graphicsview/qgraphicswidget.cpp:1249
#19 0x0000003f1638e7dd in QApplicationPrivate::notify_helper
(this=0x1750c80, receiver=0x193e850, e=0x7fffe2a292d0) at
kernel/qapplication.cpp:4084
#20 0x0000003f163969ca in QApplication::notify (this=0x1737aa0,
receiver=0x193e850, e=0x7fffe2a292d0) at kernel/qapplication.cpp:4049
#21 0x0000003f17404f3b in KApplication::notify () from
/usr/lib64/libkdeui.so.5
#22 0x0000003f14f435ec in QCoreApplication::notifyInternal (this=0x1737aa0,
receiver=0x193e850, event=0x7fffe2a292d0) at
kernel/qcoreapplication.cpp:602
#23 0x0000003f169a3156 in QGraphicsWidget::setGeometry (this=0x193e850,
rect=@0x7fffe2a29450) at graphicsview/qgraphicswidget.cpp:401
#24 0x0000003f169a0ab9 in QGraphicsWidget::resize (this=0x193e850,
size=@0x7fffe2a29770) at graphicsview/qgraphicswidget.cpp:331
#25 0x000000000014dfe6 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#26 0x000000000014eed9 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#27 0x0000000000153562 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#28 0x0000000000153741 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#29 0x00000000001558c7 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#30 0x0000003f14f59082 in QMetaObject::activate (sender=0x17468b0,
from_signal_index=<value optimized out>, to_signal_index=23, argv=0x4af) at
kernel/qobject.cpp:3069
#31 0x0000003f1acc4a1f in Plasma::Corona::containmentAdded () from
/usr/lib64/libplasma.so.3
#32 0x0000003f1acc623b in Plasma::Corona::loadLayout () from
/usr/lib64/libplasma.so.3
#33 0x0000003f1acc71e2 in Plasma::Corona::initializeLayout () from
/usr/lib64/libplasma.so.3
#34 0x0000000000152318 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#35 0x0000000000154485 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#36 0x00000000001558e8 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#37 0x0000003f14f59082 in QMetaObject::activate (sender=0x18c6d00,
from_signal_index=<value optimized out>, to_signal_index=4, argv=0x4af) at
kernel/qobject.cpp:3069
#38 0x0000003f14f5e3bf in QSingleShotTimer::timerEvent (this=0x18c6d00) at
kernel/qtimer.cpp:298
#39 0x0000003f14f53363 in QObject::event (this=0x18c6d00, e=0x193e850) at
kernel/qobject.cpp:1082
#40 0x0000003f1638e7dd in QApplicationPrivate::notify_helper
(this=0x1750c80, receiver=0x18c6d00, e=0x7fffe2a2a6e0) at
kernel/qapplication.cpp:4084
#41 0x0000003f163969ca in QApplication::notify (this=0x1737aa0,
receiver=0x18c6d00, e=0x7fffe2a2a6e0) at kernel/qapplication.cpp:4049
#42 0x0000003f17404f3b in KApplication::notify () from
/usr/lib64/libkdeui.so.5
#43 0x0000003f14f435ec in QCoreApplication::notifyInternal (this=0x1737aa0,
receiver=0x18c6d00, event=0x7fffe2a2a6e0) at
kernel/qcoreapplication.cpp:602
#44 0x0000003f14f70686 in QCoreApplication::sendEvent () at
kernel/qcoreapplication.h:213
#45 QTimerInfoList::activateTimers (this=0x1753f50) at
kernel/qeventdispatcher_unix.cpp:572
#46 0x0000003f14f6cd9d in timerSourceDispatch (source=<value optimized
out>) at kernel/qeventdispatcher_glib.cpp:164
#47 0x000000342da3779b in g_main_dispatch () at gmain.c:2144
#48 IA__g_main_context_dispatch (context=0x1753180) at gmain.c:2697
#49 0x000000342da3af6d in g_main_context_iterate (context=0x1753180,
block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#50 0x000000342da3b12b in IA__g_main_context_iteration (context=0x1753180,
may_block=1) at gmain.c:2841
#51 0x0000003f14f6ccff in QEventDispatcherGlib::processEvents
(this=0x1727280, flags=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:323
#52 0x0000003f164253df in QGuiEventDispatcherGlib::processEvents (this=0x0,
flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#53 0x0000003f14f41e92 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#54 0x0000003f14f4225d in QEventLoop::exec (this=0x7fffe2a2a990, flags=) at
kernel/qeventloop.cpp:200
#55 0x0000003f14f44524 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:880
#56 0x000000000014421b in kdemain () from /usr/lib64/libkdeinit4_plasma.so
#57 0x0000003b7c41e576 in __libc_start_main (main=0x400830 <_start+240>,
argc=1, ubp_av=0x7fffe2a2ac98, init=0x400860 <__libc_csu_init>, fini=<value
optimized out>, rtld_fini=<value optimized out>,
stack_end=0x7fffe2a2ac88) at libc-start.c:220
#58 0x0000000000400769 in _start ()
Regards,
Chris January
15 years, 2 months
Windows Opening Up On Top of Each Other
by Eli Wapniarski
I've got a dual screen setup. Does anyone know how to prevent Windows from Opening up ontop of each other. What I mean is lets say I;m looking at some mail, and then I open up Konqueror, I'm still looking at my mail, but then Konqueror opens up ontop of the application that I'm looking at. I would very much like it if Konqueror opened up someplace else, lets say on the other screen.
Does anyone know how I can make KDE behave this way or in some similar fashion.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years, 2 months
