On Wednesday, 8 May 2024 16:15:03 CEST Soren Stoutner wrote:
> > And how else do you sync your contacts between your smartphone and KDE for
> > free? I'm definitely open to good suggestions.
>
> In my case a host a Nextcloud instance. For Android sync, I use DAVx5.
>
>
On Tuesday, 24 October 2023 13:50:25 CEST piorunz wrote:
> > Piotr didn't read/apply the whole of the Backtrace wiki page, that's their
> > only 'mistake'.
>
> Yes, for that I am sorry.
No need to apologize :) I put 'mistake' in quotes as I don't consider it a
mistake, just a step in a learning
On Tuesday, 24 October 2023 10:51:46 CEST Cosmo wrote:
> piorunz is so incompetent that he managed to discredit the whole of Debian
> in front of one of the prominent kde project managers. Nice job
Piotr didn't read/apply the whole of the Backtrace wiki page, that's their
only 'mistake'.
You
On Tuesday, 24 October 2023 13:16:18 CEST piorunz wrote:
> On 24/10/2023 12:03, Grzegorz Szymaszek wrote:
> > On Tue, Oct 24, 2023 at 11:57:46AM +0100, piorunz wrote:
> >> This KDE guideline should definitely be improved:
> >>
On Monday, 23 October 2023 20:19:42 CEST piorunz wrote:
> Can anyone tell me, how to obtain debugging symbols for KDE, so I can
> backtrace a crash with debugger properly? I use Debian Stable. Thank you.
Add the following line to your /etc/apt/sources.list and do `apt update`
deb
On Friday, 19 May 2023 13:11:01 CEST Luc Castermans wrote:
> I just upgraded the machine which was messed up earlier, fixed later, using:
>
> aptitude install -t experimental '~i ~V5\.27\.2'
> aptitude install -t experimental '~i ~V5\.103\.0'
I hadn't upgraded to those packages, but earlier
On Friday, 19 May 2023 09:19:31 CEST Martin Steigerwald wrote:
> % aptitude install -t experimental '~i ~V5\.27\.2'
You can use 'safe-upgrade' instead of 'install'
signature.asc
Description: This is a digitally signed message part.
On Friday, 19 May 2023 10:09:56 CEST Aurélien COUDERC wrote:
> Also if people here could find the time to try and mix some .2 and .5
> packages and report back, that would be useful to confirm it doesn't break
> more than it fixes. In particular mixing core components like kwin,
> libkscreen,
Package: libkf5coreaddons5
Version: 5.103.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm not sure exactly when it started happening, but lately when I run
`gitk` I get a whole bunch of what I consider debug info printed in my
Konsole window:
diederik@prancing-pony:~$
On Wednesday, 12 April 2023 13:18:46 CEST Martin Steigerwald wrote:
> There are issues with Plasma with most recent Qt 5.15.8+dfsg-6. I am
> aware of the following two:
>
> 1) Screen cannot be locked. After locking screen desktop is basically
> frozen but still shown.
>
> 2) Krunner segfaults,
On Friday, 10 February 2023 07:46:36 CET Borden wrote:
> which may be more productive.
What would be even more productive is the following:
- log in remotely before doing another test and open a screen/tmux session (or
open several distinct remote logins) and start:
- htop
- tail -f
On Wednesday, 25 January 2023 10:47:54 CET bagattin jerome wrote:
> I have the following error when I try to launch tileseditor
> (META+T): janv. 25 08:18:54 debian kwin_wayland_wrapper[952]: Failed to
> load QUrl("file:///usr/share/kwin/effects/tileseditor/qml/main.qml"):
>
On Tuesday, 24 January 2023 14:53:29 CET Diederik de Haas wrote:
> > Ah, held back due to libkf5screen7 still at 4:5.26.5-1
>
> FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8
>
> I did not have libkf5screen7 installed, even though I do have kscreen
> inst
On 24 January 2023 22:09:49 CET, "Miguel A. Vallejo" wrote:
>My apt only finds version 5.26.90-1
>
>Am I doing something wrong?
Nope.
That is the version number of the beta as also mentioned in Subject
On Tuesday, 24 January 2023 11:58:25 CET Martin Steigerwald wrote:
> Ah, held back due to libkf5screen7 still at 4:5.26.5-1
FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8
I did not have libkf5screen7 installed, even though I do have kscreen
installed. What seems odd is that
On Thursday, 22 December 2022 14:31:38 CET Martin Steigerwald wrote:
> > On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote:
> > > I think they above quoted script is absolutely horrific.
> >
> > I made that statement for 2 reasons:
> > 1) It tri
when not all packages get upgraded, that usually means something 'special'
is going on, like now with the Qt transition.
On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote:
> I think they above quoted script is absolutely horrific.
I made that statement for 2 reasons:
1) It tries
On Wednesday, 21 December 2022 11:01:07 CET Sedat Dilek wrote:
> P.S.: If you are Debian/unstable AMD64 user and are experienced
> enough, you can try on YOUR OWN RISK.
>
> To pass daily dist-upgrades I did the following:
>
> [ Set all QT v5.15.6 packages on hold ]
> root# VER="5.15..6" ; for p
On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote:
> i removed apper and things seems to be better.
> waiting for confirmation from the other guys too.
I didin't have apper installed to begin with, so maybe that's why I wasn't
seeing it?
> now only plasmashell crashes ;)
> ...
>
On Tuesday, 6 December 2022 13:45:40 CET Miguel A. Vallejo wrote:
> Since a few days ago I've been experiencing problems with KDE in a
> fully upgraded Sid.
>
> The symptoms are always the same: kded5 crashes a few minutes after
> boot and then icons from no KDE programs (like Telegram)
On Wednesday, 23 November 2022 16:56:43 CET Aurélien COUDERC wrote:
> >That indeed looks quite good :-)
> >Please do inform the Release Team about it (even if it's not 100% final).
>
> Ah yes, I still havn't do that.
> What's best ? Filing a pre-approval bug ?
I don't know tbh, best to ask to
On Saturday, 12 November 2022 11:50:53 CET Martin Steigerwald wrote:
> Dear Debian/Kubuntu Qt/KDE team developers,
>
> thank you dearly for the ambitious plan you set out in:
> https://wiki.debian.org/PkgQtKde/BookwormReleasePlans
That indeed looks quite good :-)
Please do inform the Release
On vrijdag 28 oktober 2022 06:58:45 CEST local10 wrote:
> there was no Konqueror window open when I was logging out of KDE
Check if there's still a konqueror process running and kill that before
logging out. Does that 'fix' it?
signature.asc
Description: This is a digitally signed message
On zondag 16 oktober 2022 14:00:52 CEST Aurélien COUDERC wrote:
> Now that the login screen bug seems to be fixed for everyone, I'd like to
> strongly recommend everyone who switched to the breeze SDDM theme due to
> the bug to switch back to debian-breeze.
>
> Debian-breeze is the default that
On vrijdag 14 oktober 2022 20:36:44 CEST Aurélien COUDERC wrote:
> >Should the following be added to that file for the tiny char issue?
> >fontSize=10
>
> I dont know but fixing the wallpaper path also fixes the font size for me so
> I'd prefer not touching anything else if not required.
I did
On Friday, 14 October 2022 14:49:01 CEST Aurélien COUDERC wrote:
> Alternatively you can add the following line :
> background=/usr/share/desktop-base/active-theme/login/background.svg
>
> at the end of this file :
> /usr/share/sddm/themes/debian-breeze/theme.conf
>
> until the package is fixed.
On Wednesday, 12 October 2022 17:07:35 CEST Joe McEntire wrote:
> I noticed the very tiny lettering too, switched themes from debian breeze to
> just breeze and swapped background to homewold and all is well.
That was an interesting hint ...
I switched (too) from Debian Breeze to just Breeze,
On Wednesday, 12 October 2022 11:07:05 CEST Sedat Dilek wrote:
> No background wallpaper in SDDM (white background) - only visible is
> the box where I can type my password.
I did have a background wallpaper in SDDM, but the password chars were REALLY
tiny. I could still login though.
On Monday, 20 June 2022 13:10:45 CEST Diederik de Haas wrote:
> - I had created a Filter rule, to filter out all the crypto spam. That rule
> seems to be gone now (and possibly others; I only have the rules from the
> Anti-Spam wizard left). And now I get the attached popup every tim
On Sunday, 19 June 2022 19:43:47 CEST Diederik de Haas wrote:
> I was now able to install kdepim-addons again.
Since I did that/those upgrade(s), I noticed 2 things:
- Before, when I logged into my KDE session I always got a request for my
KWallet password and when I then opened Kontact/KMail
On Friday, 17 June 2022 08:04:58 CEST Patrick Franz wrote:
> I was planning to upload KDE PIM 22.04.2 very soon (maybe this weekend
> already). And that of course will then be build against Qt 5.15.4.
Thanks for that update :-)
I was now able to install kdepim-addons again.
signature.asc
On Thursday, 16 June 2022 07:40:07 CEST Aurélien COUDERC wrote:
> Le 16 juin 2022 07:31:39 GMT+02:00, Luc Castermans
a écrit :
> >Yesterday I was able to install Plasma 5.25 from Experimental. All good
> >sofar.
>
> good to know, thanks for the feedback.
>
> There's an ongoing Qt 5 transition
On vrijdag 15 april 2022 12:10:55 CEST piorunz wrote:
> You mean I can install them manually, and they will stay as manually
> installed?
Manually installed applications, or applications marked as such, are (at least
with aptitude) treated differently.
> So only akonadi-server* kaddressbook*
On vrijdag 15 april 2022 12:40:34 CEST Martin Steigerwald wrote:
> KRunner module my trigger starting Akonadi
I think contact search is enabled by default, so that could be it.
signature.asc
Description: This is a digitally signed message part.
On Monday, 21 March 2022 13:16:17 CET Adriano Vilela Barbosa wrote:
> I'm running Debian Testing ...
> Last night an update came along which brought libpoppler from version
> 20.09 to version 22.02. However, nothing changed after the update:
> I'm still unable to sign pdfs.
>
> So, I wonder if
On donderdag 17 maart 2022 13:55:59 CET Gregorio Rodrigo wrote:
> I am facing a small bug/problem/new feature. I use a left handed mouse but
> the configuration is not saved every time I plug/unplug the mouse. It was
> working before the upgrade (left handled with the mouse, right handled with
>
On woensdag 16 maart 2022 23:03:03 CET Borden wrote:
> Is it safe to upgrade in testing yet? There are dozens of packages in the
> update queue and I'm afraid to hit dist-upgrade after the previous Plasma
> upgrade hobbled my computer for over a month.
A quick look at man:/apt didn't show a '-s'
Hi,
On the 14h apt update 'round' I noticed the following packages became
available:
bluedevil drkonqi kactivitymanagerd kde-config-sddm kgamma5 kinfocenter
kmenuedit konsole konsole-kpart kscreen ksshaskpass kwayland-integration
kwrited layer-shell-qt libkf5baloowidgets-bin
On Sunday, 27 February 2022 16:41:28 CET Patrick Franz wrote:
> > Thanks for the advice, but too late for me: my KDE is broken now.
> > You should ideally warn one or two days before packages are uploaded.
>
> I disagree with having to give a warning 2 days in advance. If you run
> unstable, you
On 07 Feb 2022 17:36:53 + mYnDstrEAm wrote:
> Please add fwupd and plasma-discover-backend-fwupd as a default package
https://bugs.debian.org/1003973 is a/the bug where default installation of
fwupd is discussed.
> included on Debian12/KDE. This would make "Discover" show available
On Tuesday, 25 January 2022 21:56:06 CET scott092...@aol.com wrote:
> I just now ran partitionmanager from the terminal, and as usual, got no info
> in the displayed window.
>
> Here is the terminal output:
>
>
>
Control: severity -1 important
On Saturday, 22 January 2022 19:02:27 CET Elijah wrote:
> pkg-deb (subprocess): decompressing archive
> '/var/cache/apt/archives/libqt5webenginecore5_5.15.8+dfsg-1_amd64.deb'
> (size=39497412) member 'data.tar': lzma error: compressed data is corrupt
What happens
Hi Paul,
On Thursday, 11 November 2021 14:56:29 CET Paul Gevers wrote:
> Nice screenshot. For the record, that hint wasn't there on my system.
> The other settings are the same, minus I have "OpenGL 2.0" as "Rendering
> backend".
It was my assumption that you (and others) didn't get that hint,
On Monday, 1 November 2021 11:57:52 CET shirish शिरीष wrote:
> Because there is no notification, it is difficult to know when Yakuake
> has started or not.
AFAIK it's always started as soon as you log in.
I would actually find an item in the notification area/systray a regression/bug
as it's
On Sunday, 31 October 2021 23:42:13 CET shirish शिरीष wrote:
> I am running yakuake on Debian-mate. But it seems that in the
> notification area for some reason yakuake is not seen :( . Sharing a
> screenshot of the notification area.
I'm running fully KDE and I don't have a notification entry
On Sunday, 17 October 2021 00:24:47 CEST Patrick Franz wrote:
> * A minor hiccup seems to be that the keybinding for KRunner (Alt+F2/
> Alt+Space) seems to have been lost as the option appears twice in
> systemsettings. But you can easily restore the default setting for the
> keybinding in the
On Friday, 15 October 2021 05:37:18 CEST Patrick Franz wrote:
> Unfortunately, the upload is not complete and upgrading only half of the
> packages can leave Plasma in an unusable state.
Yep ;-P
After installing (also) the updates from the 08:00 (CEST) repo update round,
it worked again *for me*
On Thursday, 14 October 2021 19:16:46 CEST Martin Steigerwald wrote:
> > The best way to do that is not using *dist*-upgrade but the
> > normal/safe- upgrade method ...
>
> Sometimes dist upgrade might be necessary as new packages are introduced
> or old ones are removed. Trying dist upgrade also
On Thursday, 14 October 2021 17:15:00 CEST Martin Steigerwald wrote:
> As usually take care with "apt dist-upgrade". Wait until the builds are
> complete.
The best way to do that is not using *dist*-upgrade but the normal/safe-
upgrade method ...
signature.asc
Description: This is a digitally
On zondag 19 september 2021 17:10:51 CEST Miguel A. Vallejo wrote:
> Removing ~/.config/plasma-org.kde.plasma.desktop-appletsrc and relogin
> did the trick, but lost all the personalization.
I've had similar problems a number of times now in the last few weeks.
Lost my task bar a couple of times
Control: reassign -1 libqgpgme7 1.16.0-1
Control: retitle -1 GPGMe does not take additional keyring into account to find
keys.
Control: affects -1 kmail
On woensdag 15 september 2021 10:56:59 CEST Sandro Knauß wrote:
> > Thanks for your assistance. I've save the signature as 'signature.asc' and
On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> But first make sue, that you are really have an valid bug. Please verify the
> signature in a konsole via gpg --verify. I expect, that it will fail with
> the same error.
Thanks for your assistance. I've save the signature as
Hoi,
On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> I'm quite sure, that this is not the issue of Kmail, as Kmail is using the
> GPGME to talk to gpg. So it will be an issue of libqgpgme7.
Ok. I noticed the issue in KMail, so I reported it against that package.
Feel free to
On dinsdag 7 september 2021 11:32:28 CEST Peter Green wrote:
> > Version: 4:21.08.0-1
>
> You filed this against the version in sid?
I run Sid as my daily driver, so yes. That's what I (almost?) always do.
> have you investigated whether earlier versions are also affected?
No, I did not.
On donderdag 2 september 2021 23:15:47 CEST Diederik de Haas wrote:
> KMail reports (after I signed it)
The signing part is irrelevant for reproducing the bug.
I experienced the exact same problem before I signed it.
signature.asc
Description: This is a digitally signed message part.
Package: kmail
Version: 4:21.08.0-2
Severity: normal
Recently I received a signed email from Debian Developer joostvb@d.o.
I imported his public key to my keyring as follows:
gpg --keyserver keyring.debian.org --recv-keys
0xB8FAC2E250475B8CE940A91957930DAB0B86B067
When selecting that mail,
Package: kleopatra
Version: 4:21.08.0-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
I had previously 'improved' my gnupg configuration, but that is (now)
deprecated.
So I moved my ~/.gnupg directory to a backup location to start anew.
If I
Control: tag -1 -a11y
On zondag 29 augustus 2021 13:42:40 CEST k_f wrote:
> the accessibility tag is wrong
signature.asc
Description: This is a digitally signed message part.
On vrijdag 27 augustus 2021 20:13:39 CEST MERLIN Philippe wrote:
> Sorry, for me the result of .
> export LANG=C; apt dist-upgrade -V
Maybe don't (normally) use dist-upgrade?
The normal/safe- upgrade is all you need in 99% of cases.
That sometimes, like in this case, means you have to wait a
On donderdag 26 augustus 2021 18:35:25 CEST Martin Steigerwald wrote:
> > I first upgraded my version 5.83 packages to the ones in unstable:
> > aptitude safe-upgrade ~i~V5.83.0 -t experimental
>
> In Experimental.
You're absolutely correct.
I mentioned it as I saw various 5.83
On donderdag 26 augustus 2021 14:35:08 CEST Martin Steigerwald wrote:
> > Can those of you who see this problem, please try the kmail package
> > https://download.opensuse.org/repositories/home:/npreining:/
> > debian-kde:/apps2108/Debian_Unstable/amd64/
> > kmail_21.08.0-1~np1_amd64.deb (for
> >
On maandag 23 augustus 2021 09:21:59 CEST Martin Steigerwald wrote:
> Norbert is uploading KDEPIM / Akonadi 21.08. Please wait for builds to
> complete their work.
>
> In generally be careful. Unstable is much more unstable again
If you stick to using 'safe-upgrade' you should be fine in
[I shouldn't have a meaningful voice in this, but my 0.02 ...]
Normally I would be strongly against disabling tests ...
On woensdag 18 augustus 2021 21:26:04 CEST Nicholas D Steeves wrote:
> I'm also concerned that the situation is fundamentally wrong: If tests
> need to be updated with every
Package: kontact
Version: 4:21.04.1-1
Severity: important
I'm filing it against kontact, but kmail is maybe more appropriate.
However with kontact I could generate a stacktrace, which failed with
kmail, so therefor I chose kontact. Feel free to reassign.
In 'Local Folder' I have a Mail-Achive
On zondag 27 september 2020 07:39:42 CEST Helge Kreutzmann wrote:
> Package: korganizer
> Version: 4:20.04.1-2
> Severity: minor
>
> In the logs I get the following error message:
> Aug 15 21:46:20 samd systemd[232194]: Configuration file
> /etc/xdg/autostart/org.kde.korgac.desktop is marked
Control: tag -1 affects kmail
The problem is caused by an incorrect modification of
https://salsa.debian.org/qt-kde-team/kde/messagelib/-/commits/master/debian/patches/series
Instead of adding (twice) a new/extra patch, it replaced the series.
Kind of like using '>' while you meant using '>>'.
Package: libkf5messagelist5abi1
Version: 4:20.08.3-3
Severity: important
Since upgrading of libkf5messagelist5abi1 KMail fails to load with the
following error message (I actually load it via Kontact):
"Cannot load part for Mail.
Cannot load library
It turns out that the wayland plasma session got selected and that crashed.
This is possibly/probably fixed with the -2 upload which happened a couple of
hours ago.
Manually selecting the 'normal' plasma session and then I could log in.
OP: Can you check whether the wayland session was
Control: tag -1 confirmed
Did a 'touch /etc/environment' and restarted sddm.service, but the problem
remained. Output is the same as in my previous message, minus the pam_env
error line.
Usually from within KDE, I can get a backtrace (DrKonqi?) easily, but that
won't work in this case as I
Package: sddm
Version: 0.19.0-1
Followup-For: Bug #973933
Got a very big upgrade (hadn't started my Sid system for several days), which
included sddm and after a reboot I got the sddm login screen.
But after giving my credentials, I got thrown back to the login screen.
'systemctl status
Control: forwarded -1 https://github.com/wang-bin/QtAV/issues/1309
Control: tag -1 upstream fixed-upstream
Fix is not yet included in a release though. Someone has opened an issue
requesting that: https://github.com/wang-bin/QtAV/issues/1334
signature.asc
Description: This is a digitally signed
On dinsdag 21 januari 2020 06:37:07 CET Pino Toscano wrote:
> as it was mentioned already in other threads on this list,
> Plasma 5.17.5 is available in experimental.
I used the following command to upgrade:
aptitude full-upgrade ~i~V5.14.5 -t experimental
So far I haven't seen any issues :)
On dinsdag 10 december 2019 15:37:12 CET Martin Jean-Fabrice wrote:
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>* What was the
On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote:
> do you have apparmor enabled? Maybe the Apparmor profile does not match
> anymore. Can you give it a try with aa-disable postgresql_akonadi?
I have akonadi-backend-postgresql and apparmor enabled and it is working for
me. I only
On woensdag 13 november 2019 11:39:08 CET Andrey Rahmatullin wrote:
> On Wed, Nov 13, 2019 at 12:01:51AM +0100, Diederik de Haas wrote:
> > I don't know if "Debian Package Tracker" is a Web Shortcuts which is part
> > of a normal installation or if I have
On dinsdag 12 november 2019 23:18:36 CET Miguel A. Vallejo wrote:
> The following packages were automatically installed and are no longer
> required: espeak-ng-data festival festival-freebsoft-utils festlex-cmu
> festlex-poslex festvox-kallpc16k icoutils kate-data katepart
> kde-runtime-data
On dinsdag 12 november 2019 23:42:35 CET Diederik de Haas wrote:
> As Luigi already indicated, you have old cruft (QT4) installed and you
> should get rid of them.
> The easiest way is to say Yes to the above suggestion.
> And then install phonon4qt5-backend-gstreamer, which will then
On dinsdag 12 november 2019 23:18:36 CET Miguel A. Vallejo wrote:
> The following packages have unmet dependencies:
> phonon-backend-gstreamer : Depends: phonon-backend-gstreamer-common (=
> 4:4.9.1-1) but it is not going to be installed
> The following actions will resolve these dependencies:
>
On dinsdag 12 november 2019 20:47:19 CET Miguel A. Vallejo wrote:
> I noticed that phonon-backend-gstreamer-common have been keep back
> since several weeks ago in Sid. If I try to update it manually apt
> wants to remove the entire KDE.
I don't have that problem on my Sid box.
Can you share the
On zaterdag 2 november 2019 10:16:20 CET Martin Steigerwald wrote:
> Hmmm, to me that looks like you are using a system wide PostgreSQL
> database. I am using a user based one.
>
> For a PostgreSQL database using as the user and using ~/.local/share/
> akonadi/db_data the KDE Userbase wiki has
In Sid the various PostgreSQL packages have been upgraded to version 12 and
I've just successfully upgraded to them.
I've read people say that upgrading PostgreSQL was complicated, but that's not
my experience. Here is what I did:
- quit KMail/Kontact/etc
$ akonadictl stop
[$ stop any other
Hi,
On maandag 28 oktober 2019 12:33:30 CET Sandro Knauß wrote:
> Mmh, okay now the question is, if Akonadi was functional before you deleted
> that file.
Yes, it was functional. AFAIK akonadi uses my OS credentials, so it doesn't/
shouldn't need any creds that could be stored in that file.
>
On vrijdag 25 oktober 2019 12:08:12 CEST John Scott wrote:
> You probably have apparmor-notify installed which displays the
> notifications.
That is correct.
signature.asc
Description: This is a digitally signed message part.
On donderdag 24 oktober 2019 21:30:22 CEST Sandro Knauß wrote:
> thanks for the reply. How this notification is displayed? Like any
> notification e.g. "new mail" or is just seen in dmesg?
I don't have "new mail" notifications, but I'd guess that's what I meant.
Every time an issue with AppArmor
On donderdag 26 september 2019 22:56:08 CEST Bob Weber wrote:
> Another trick that worked on 2 machines here is to set the numlock on in
> /etc/sddm.conf.
>
> My general section of sddm.conf looks like this now:
>
> [General]
> HaltCommand=
> RebootCommand=
> Numlock=on
>
> Hope this helps.
On donderdag 26 september 2019 22:56:08 CEST Bob Weber wrote:
> Another trick that worked on 2 machines here is to set the numlock on in
> /etc/sddm.conf.
>
> My general section of sddm.conf looks like this now:
>
> [General]
> HaltCommand=
> RebootCommand=
> Numlock=on
>
> Hope this helps.
On woensdag 23 oktober 2019 04:06:29 CEST Diederik de Haas wrote:
> Right after sending that, I get the following notification:
> Profile: /usr/bin/akonadiserver
> Operation: open
> Name: /home/diederik/.pgpass
> Denied: r
> Logfile: /var/log/kern.log
> For more inf
On woensdag 23 oktober 2019 04:02:45 CEST Diederik de Haas wrote:
> On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote:
> > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I
> > want to test further AppArmor support. If you use unstable, please gi
On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote:
> I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I
> want to test further AppArmor support. If you use unstable, please give it a
> try and give feedback if you see any new issues.
I just upgraded with
On woensdag 16 oktober 2019 03:54:45 CEST you wrote:
> you can change the config of OpenSSL to allow lower TLS versions to work.
> Better would be to urge that mail provider to upgrade their mail software as
> TLS < 1.2 really isn't secure.
>From
On maandag 21 oktober 2019 21:20:38 CEST Martin Steigerwald wrote:
> Careful with "apt dist-upgrade"
Use safe-upgrade
signature.asc
Description: This is a digitally signed message part.
On zaterdag 19 oktober 2019 19:18:36 CEST Brian R. wrote:
> I've set numlock "on" at login in KDE system settings, but after recent
> updates, the numlock state is no longer applied per user settings. Numlock
> must be turned on manually.
Sounds like you have the same problem as I reported here:
On zaterdag 21 september 2019 10:35:17 CEST Antonio wrote:
> after updating to the kde 5.62 framework the num lock key is always on
> at startup even if in the settings it was forced to stay off
I have the same problem, but reverse.
No matter what setting I have in Input Devices, it will not turn
On woensdag 16 oktober 2019 16:25:51 CEST Joshua Hudson wrote:
> Should I really have to provide an empty virtual package? I'm using
> pam_group so sound keeps playing in bkg while current virtual console has
> another user.
At least one DD thinks it should be a dependency. I haven't yet seen a
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=403950
Control: tag -1 upstream fixed-upstream
signature.asc
Description: This is a digitally signed message part.
On dinsdag 9 juli 2019 21:45:13 CEST Diego Russo wrote:
> With Debian Buster akonadi does not work anymore with aruba imap server,
My guess is that it is caused by the default configuration of OpenSSL 1.1,
which requires TLS 1.2 iirc. If that aruba imap server is using old software
that doesn't
On donderdag 11 juli 2019 21:53:33 CEST Demi wrote:
> I have to agree with Joshua -- programs like marble or kdenlive work
> just fine without systemd
On woensdag 20 maart 2019 15:44:30 CEST Michael Biebl wrote:
> The dependency seems correct.
> policykit without a working logind session seems
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=398324
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 +moreinfo +unreproducible
Control: severity -1 important
I noticed you specified the source package and not the binary package to report
the bug against. Normally not much of an issue, but it looks like you didn't
use or didn't share the whole output of reportbug, because it's
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=409375
signature.asc
Description: This is a digitally signed message part.
1 - 100 of 617 matches
Mail list logo
