Hullo, all,
I'm using Squeeze and I'm assuming that the kdebluetooth packages work, even
if they're still using the old Qt3 libraries. Of course, kbluetooth does not
recognise my tablet's Bluetooth system even though hcitool does. Yes, I've
triple-checked that I'm a member of *both* the netde
2009 at 6:59 AM, Borden Rhodes
wrote:
> > Hullo, all,
> >
> > I'm using Squeeze and I'm assuming that the kdebluetooth packages work,
> > even if they're still using the old Qt3 libraries. Of course, kbluetooth
> > does not recognise my tablet's
I just discovered that Konqueror has been saving passwords in
.kde/share/apps/kwallet/kdewallet.kwl even though the rest of my KDE
installation is updated to KF5. I want to know what passwords have
been stored in kdewallet.kwl so I don't lose them.
I've tried to open the file in kwalletmanager5 to
>> You could try to copy the kwallet-files to a KDE4-system (maybe a
>> live-System from a USB-drive) and export it as XML-file.
I'm thinking that this is what I'll have to do, too. That and file a
bug that KWallet is officially ransomware.
> On my system the contents of the KDE 4 kwallet has been
>>> You could try to copy the kwallet-files to a KDE4-system (maybe a
>>> live-System from a USB-drive) and export it as XML-file.
> I'm thinking that this is what I'll have to do, too. That and file a
> bug that KWallet is officially ransomware.
I tried that, but it seems that the KDE developers a
> If you have enough disk-space, you could build a jessie chroot with
> debootstrap
Could you explain how that would help me? If the Wheezy version of
KWallet couldn't open the file, what would Jessie accomplish?
> I suggest you bring that issue to upstream at bugs.kde.org
>
> Please post a link
>> If you have enough disk-space, you could build a jessie chroot with
>> debootstrap
> Could you explain how that would help me? If the Wheezy version of
> KWallet couldn't open the file, what would Jessie accomplish?
I stand corrected. I was using the Jessie Live CD, not the Wheezy Live CD.
>>
OK, so I stumbled upon https://barlog.rusu.info/valentin/blog/?p=300 ,
and comment 6 explains the problem: the whole thing's borked because
"something (that i don’t have the time to investigate) has changed in
qt5 and the existing kwalletd code, when linked against it, is unable
to correctly handle
Good morning,
Around the time of the KF5 upgrade on Stretch, typing into Kicker's
search box krashed Plasma. I notice that it doesn't do that anymore,
but the search box also doesn't generate any search results. Is it
working for anybody else and, if so, what do I have to
install/clear/configure t
and taskbar not working.
> Finally, remember to change your /etc/apt/sources.list back to testing or
> stretch, followed by an apt-get update.
>
> Tim
> On Tuesday, July 19, 2016 03:08:29 AM Borden Rhodes wrote:
>> Good morning,
>>
>> Around the time of the KF5 upg
As the subject says, on my Debian Stretch laptop, attempting to use
the KDE print settings or KUser prompts me to login with the root
account. This is a problem because I installed Debian with the root
account locked out. I thought Polkit was supposed to have taken care
of all of this. Perhaps I'm
If it helps, after an X server update on Sunday, my computer took
almost fifteen minutes to start SDDM. Turns out that there is a
problem with xserver-xorg-input-wacom stalling the whole thing. Notes
on the X server PTS say that there's a transition under way to the
next X server. It's possible tha
I was floored when I saw that they released Stretch. There are so many
broken packages on my system that I can't imagine they'd release them.
I expect *a lot* of complaints to roll in.
On 19 June 2017 at 19:30, Jimmy Johnson wrote:
> Only for someone who is difficult, no knowledge and obviously no fun.
>
> Cheers,
> --
> Jimmy Johnson
I'm not sure if you were trying to come across as clever, but the
Internet stripped out your tone and you just came across as an
unpleasant jerk.
On 19 June 2017 at 21:09, Jimmy Johnson wrote:
> Positive criticism is always welcome. :)
Believe me, I've tried. The graphical interfaces for reportbug and
reportbug-ng don't work. The former whines about a missing GTK
dependency which is installed and running, the latter gives mangled
output th
I noticed that KTimeTracker's been pulled from Debian Buster for a
while. I tried to do some upstream research and it seems to be buried
in KDEPIM's source code. Does anyone familiar with the KDE community
know whether it's been abandoned?
I have a problem with web browsers going rogue and locking up my
computer such that I have to hard restart. I want to set
vm.overcommit_memory=2 to try to invoke the OOM killer before a
browser locks up my computer. When I do, though, SDDM will start
normally, I'll log in but it'll freeze up whilst
On Wed, 21 Aug 2019 at 11:44, Erwan David wrote:
> I got notified that some bug I had opened against amarok was closed due
> to amarok being retired. I had already switched to cantata since buster
> install...
Not quite. As John mentioned, Amarok got pulled because it uses the
obsolete Qt4 librar
On Thu, 22 Aug 2019 at 03:48, Geoff wrote:
> Last update March 7, 2018. I think it's a goner unfortunately. Trying to get
> used to clementine instead...
Last human commit to the master branch was on 28 July
(https://cgit.kde.org/amarok.git/log/). I haven't given up hope yet.
As one of the Amarok refugees, I'm using JuK to play music until
either Team Amarok ports to Qt5 or a suitable replacement is uploaded.
Maybe JuK is a terrible program that I shouldn't use. However, it's
part of the KDE package so I'm using it.
I'm running into hangs and crashes (with no debugging
I know that there have been some major upgrades to the Qt, KDE and KDE
PIM packages in the past few weeks.
One of these new "features" that I just discovered in Buster is that
all new events that I try to create in KOrg save as full-day events no
matter what I enter. When I try to open the event t
the right way to do that. I tried deleting the calendar folder
store in Akonadi and re-adding it, but that didn't help.
I'm very grateful for your help.
> hefee
>
> On Mittwoch, 6. November 2019 08:22:53 CET Borden Rhodes wrote:
> > I know that there have been some majo
Thank you for looking through the log file.
On Thu, 14 Nov 2019 at 21:05, Sandro Knauß wrote:
>
> the log file is not very helpful, as this is the Akonadi one. Can you crate
> the
> log file from korganizer?
After setting up the .ini file you suggested, I ran
$ korganizer &> korg_debug.txt
and
So it seems that it's not only broken for me. Others are getting the
same symptoms: https://bugs.kde.org/show_bug.cgi?id=410167 and it
seems that they're no closer to figuring it out than I am.
Just in case anybody else runs into this issue.
On Fri, 15 Nov 2019 at 02:10, Borden Rho
>
Regional Settings -> Date & Time and changed the time zone to another
one and back to my locale and the problem *seems* to have gone away.
Even if it doesn't, I think this is where the problem lies.
On Mon, 18 Nov 2019 at 00:58, Borden Rhodes wrote:
>
> So it seems that it&#
On Thu, 19 Dec 2019 at 12:10, Gary Dale wrote:
>
> I'm running bullseye on an AMD64 system.
>
> When I create or edit an event, I can't set or change the time. No
> matter what I do, it reverts to 12:00 AM after I save the event.
> Moreover, the Apply button stays greyed out unless I modify some o
My Wacom-based touchscreen works fine in X with only libinput
installed. In Wayland, the touchscreen, stylus and all other features
are completely unresponsive. I found complaints a few years old that
this was a known defect. However, references to it in
https://community.kde.org/Plasma/Wayland_Sho
Good afternoon,
I'm following up on a message for which I don't believe I received a
response on 29 May. I'm trying to transition to Plasma using Wayland
instead of X, and I'm encountering many stability and usability
problems.
In general, should Plasma on Wayland in Bullseye be stable enough for
On Fri, 19 Jun 2020 at 13:10, Gary Dale wrote:
>
> I've opened another (previously saved) session and tried it there and
> KATE recognizes the \n properly so it's not the version of KATE that's
> at fault. I've tried switching the End-Of-Line mode between Unix and
> MS-DOS (and back) but that didn
On Mon, 29 Jun 2020 at 09:36, Marco Möller
wrote:
>
> Interested to discover Wayland without risking to lose my much
> personalized settings for my KDE Plasma X11 desktop environment (and
> without drawing in new desktop apps), is it enough to simply install
> package kwin-Wayland?
> Are there an
> Use ps x to see how many copies of wpa_supplicant are running. If you have
> multiple copies started from the command line the wifi won't stay connected.
> I had the same problem.
Thank you for the suggestion. I checked when it started dropping and, not only
was there one instance of wpa_supplic
On Wed, 10 Jun 2020 at 23:16, Ihor Antonov wrote:
>
> Hi Borden,
>
> Unfortunately packaging KDE/Plasma is hard and it takes a lot of time, so
> there is also a noticeable delay between upstream releases and packages
> availability. Keep testing is the minimum we can do for Debian. But if you
> ha
On Mon, 6 Jul 2020 at 03:48, Xavier Brochard wrote:
>
> Good bug reports for something like this include backtrace infos.
> You need to install kmail-dbg (or -dbgsym) package.
> When Kmail will hang again, use gdb and bt to produce a backtrace (I
> can't remember exactly, sorry).
Is there no equi
On Tue, 18 Aug 2020 at 11:11, Lisandro Damián Nicanor Pérez Meyer
wrote:
>
> I was asked if this move has anything to do with code quality or
> licensing. The answer is a huge no, Qt is a **great** project which we
> love. As stated before it's mostly about lack of free time to properly
> maintain
Good evening,
What the rough timeline is for KF5 5.75 to enter testing? Is it weeks?
Months? Sometime next year?
I know everybody is overworked and underpaid so there are no promises.
I ask because I want to fiddle with the KSyntaxHighlighting features
in the new versions of KatePart. If the turn
On Tue, 27 Oct 2020 at 15:30, Sandro Knauß wrote:
Thank you for your response
> I don't understand what you try to do.
This is what I'm trying to do:
https://invent.kde.org/frameworks/syntax-highlighting/-/issues/3
Upstream says that I need 5.75, but perhaps the features are available
in the 5.74
On Mon, 9 Nov 2020 at 16:20, Lisandro Damián Nicanor Pérez Meyer
wrote:
> That also means you have great expectations from us :-D
Are we being unreasonable assuming that we can turn our computers off
and back on and have them still boot?
> But let me assure you that if this kind of things happen
On Tue, 10 Nov 2020 at 14:48, Brad Rogers wrote:
> Impossible to achieve. There's simply far too much that can go wrong to
> cover every single (corner) case there may be.
Is there anything to learn from this experience that can help us in
future? Controls are never perfect, and there's always a
Confirmed I can use my computer again. Thank you.
Back to my earlier question, though, have we learnt anything in this
experience that can help us avoid unbootable KDE problems in the
future?
On Thu, 12 Nov 2020 at 20:36, Gary Dale wrote:
>
> However the point of testing is to do testing.
I understand that. But I want to make sure that my three points are understood:
1) An unbootable computer is not a "testing" system. It's an
"unstable" system. The update that broke KDE was foreseeab
On Thu, 12 Nov 2020 at 23:32, Norbert Preining wrote:
> Nothing related to plasma can make your system unbootable, that is FUD.
> You can change the desktop session to any other and run it.
Does my computer power on and POST? Yes.
Do the kernel and systemd complete their start up routines? Yes.
C
41 matches
Mail list logo
