Package: plasma-workspace
Version: 4:5.12.5-1
Severity: normal
Dear Maintainer,
after update to Buster I found that I cannot use virtualization (KVM/QEMU,
virt-manager) on KDE Plasma 5.12
since clipboard is constantly freezing. I tested this behaviour both with
Debian VM with Plasma and Windows
Package: okular
Version: 4:16.08.2-1+b1
Severity: normal
Dear Maintainer,
* What led up to the situation?
When browsing my NAS through smb on Dolphin, I clicked on a PDF file in order
to open it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I attempted
Forgot to attach screenshot.
Phil
Package: dolphin
Version: 4:16.08.3-3
Severity: minor
Dear Maintainer,
* What led up to the situation?
I try to create a new folder and the create folder dialog comes up.
* What exactly did you do (or not do) that was effective (or
ineffective)?
As above, not sure if it's something t
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fca9b0e8940 (LWP 31782))]
Thread 7 (Thread 0x7fca7b75e700 (LWP 31794)):
#0 0x7fcab21c315f in pthread_cond_wait@@GLIBC_2.3
I haven't checked event categories but when I create a journal entry and try
to tag it (first time I've tried journaling), I get a similar problem. I added
'linux' as a tag and when I opened up the journal entry again to check my
tags, I had like 5 'linux' tags.
Phil
ii libstdc++6 6.3.0-18
ii phonon4qt5 4:4.9.0-4
Versions of packages korganizer recommends:
ii kdepim-doc 4:16.04.3-3
korganizer suggests no packages.
-- no debconf information
*** /home/phil/ダウンロード/korganizer-20170903-151749.kcrash.txt
Application: korganizer (5.2.3)
Qt
Package: kleopatra
Version: 4:16.04.2-2+b2
Severity: normal
Dear Maintainer,
* What led up to the situation?
By opening Settings in Kleopatra -> Settings -> Kleopatra settings, I get a
wave of error messages.
* What exactly did you do (or not do) that was effective (or
ineffective)?
+1
Philippe Merlin
ss thoughts so far. I've not
discovered everything about debian yet, but I am getting to understand
things a little better each day.
Regards
Phil Hannent
Rather than just being happy that unstable has the new version and
that it is transitioning into Lenny, the build dependencies should
record this, so that people building in unusual environments (such as
porting the package to a Debian-like system) can see the necessity.
Phil
--
To
On Tue, Jul 13, 2004 at 11:50:17PM +0200, Dominique Devriese wrote:
> Phil Edwards writes:
>
> > The patch only downgrades the severity of the diagnostic.
>
> That is not true. The debugging output is disabled in non-debug
> builds like debian's build, and the patch
The patch only downgrades the severity of the diagnostic. I'd still like
to know whst an end-user like me can do to avoid /hundreds/ of these useless
messages every time a KDE program is run, especially if there's not going to
be another KDE release after the current 3.2.3, which doesn't have the
This happens to me every couple of days, and a tap of Alt always gets
it back. I've never used OpenOffice, though, and never noticed klipper's
behavior tied to any other app in particular. (I'll try to take note
in the future.)
Using 3.2.2-1 here.
Phil
Package: kdm
Version: 4:3.2.2-1
Severity: minor
Since KDE 3.2 was first packaged, I've been seeing an annoying oddity.
Normally, if you use Alt-N (or mouse through the dropdown menu) at the KDM
login screen to drop to a console, KDM starts its normal countdown clock.
If you don't login after a mi
On Thu, May 20, 2004 at 08:19:15PM -0700, Frank Jas wrote:
>
> >On this box, the hardware beep /must/ work. And it works fine, outside
> >of KDE. But once KDE starts up, artsd takes over the system beep, and
> >artsd doesn't work. The "System Bell" module has its checkbox next to
> >"use the syste
Got desperate and moved to 2.6.5 and ALSA, all sources from sid. Built the
pcspkr module into the kernel, rather than leaving it separate (when would
I /not/ want it loaded?), and built all the sound modules.
KDE continues to take control of the system beep. It now works at the
console, even wh
Package: kdelibs4
Version: 4:3.2.2-1
Severity: minor
File: kdecore
Trying to running any KDE 3.1 or 3.2 binary causes these messages to flood
the screen (or the .xsession-errors file, depending on how they're started):
KThemeStyle cache seems corrupt!
kdecore (KIconLoader): WARNING: Icon
On Fri, Apr 23, 2004 at 04:09:14PM -0500, Chris Cheney wrote:
>
> It should still work on 2.4 as well but I don't run 2.4.x anymore
> since I moved to the amd64 arch. I will try to build a recent 2.4
> kernel for my box to see if I can test it. Which 2.4 kernel are you
> using?
2.4.22, and kde fr
On Fri, Apr 23, 2004 at 03:52:19PM -0500, Chris Cheney wrote:
> It works perfect here on 2.6.6-rc1
I'm running a 2.4 kernel. All was well until KDE 3.2 decided to annihilate
anything in the computer which could make sound. (I wanted a quieter
system, but not this quiet.)
> but I had to make su
Package: arts
Version: 1.2.2-1
Severity: grave
My first thought was 'critical', following its description of "makes
unrelated software on the system break," but surely this can't be that
hard to fix...
On this box, the hardware beep /must/ work. And it works fine, outside
of KDE. But once KDE
On Thu, Apr 15, 2004 at 08:48:42AM +0200, Dominique Devriese wrote:
> Phil Edwards writes:
>
> > I have no /idea/ what the options do. That's why I looked at the
> > man page!
>
> Well, neither do we.
Oh, wonderful.
> For now, you'll have to do
On Wed, Apr 14, 2004 at 10:31:49PM +0200, Dominique Devriese wrote:
> Phil Edwards writes:
>
> > Imagine my joy when the artsd man page lists nothing but "fixme" in
> > every paragraph and for every option. You have no idea how
> > frustrating this is. Why did
Package: libarts1
Version: 1.2.2-1
Severity: normal
I am trying to debug a sound problem that has stumped everybody that's
looked at it so far. I track it down to a running "artsd" with lots of
odd-looking parameters on its command line.
Imagine my joy when the artsd man page lists nothing but "
I also tried deleting .kde/share/apps/knotes. Upon next login, knotes still
spawned a new [Display] note (but only one, instead of dozens). Changing
the preferences as to default width and text font doesn't have an effect,
either; I can see the correct changes are saved to .kde/config/knotesrc,
I'll add that this bug has the additional feature of pegging the CPU at
100% when knotes->quit is clicked. Sending the knotes process SIGTERM seems
to do no additional harm.
26 matches
Mail list logo
