Hi,
Unfortunately, I had no big success with playing with Google's OAuth Scopes.
But I found another solution ...
Gmail-Account > Data & Privacy > Apps and services > Third party apps
and services > Akonadi Service For Google Services
... I was able to send emails again via KMail.
[ INFO ]
OAuth 2.0 Scopes for Google APIs:
https://developers.google.com/identity/protocols/oauth2/scopes
Hi,
I upgraded yesterday my machine from bookworm/stable to trixie/testing.
KMail was used to check if I can send emails - this seems no more to work.
Seeing the same issue like Ariel Garcia in #1033462 (sorry partly in German):
We have an error during reading password "Entry not found"
We
Package: akonadi-backend-mysql
Version: 4:22.12.0-2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com
Dear Maintainer,
I removed akonadi-backend-mysql from my Debian/unstable AMD64 box as I need a
higher version of mariadb.
These changes were done on my latest upgrade:
-ii
On Thu, Sep 3, 2020 at 8:44 PM Christian Boltz
wrote:
>
> Hello,
>
> Am Donnerstag, 3. September 2020, 17:15:54 CEST schrieb Sedat Dilek:
> > root# LC_ALL=C dmesg -T | egrep apparmor | grep akonadi
> > [Thu Sep 3 15:27:34 2020] audit: type=1400 audit(1599139654.969:2
On Mon, Dec 17, 2018 at 3:00 PM Sedat Dilek wrote:
>
> "FWIW I also saw this behavior with (previously in experimental)
> 4:18.04.2-1, but not with current experimental's 4:18.08.3-1. Note
> that I do not use kopete, but just saw the bug and tried."
>
Just for th
Current workaround for me is to turn off "libjingle support" in the
preferences of kopete/testing.
- Sedat -
"FWIW I also saw this behavior with (previously in experimental)
4:18.04.2-1, but not with current experimental's 4:18.08.3-1. Note
that I do not use kopete, but just saw the bug and tried."
I upgraded to kopete/experimental...
root@iniza:~# dpkg -l | grep kopete
ii kopete
Hi,
my dmesg log is flooded by...
[ 6473.498769] libjingle-call[15398]: segfault at 48 ip
7fb49aaf5c73 sp 7ffe53ac8ce0 error 4 in
libcrypto.so.1.1[7fb49aab8000+1a]
[ 6473.498783] Code: 40 24 01 00 00 00 4c 89 e2 c7 40 50 01 00 00 00
0f ae f0 e8 ff 35 fc ff 85 c0 74 6c e8 86 4c fc ff
On Fri, Apr 1, 2011 at 3:03 PM, Sedat Dilek sedat.di...@googlemail.com wrote:
Hi,
I am just curious where the development and discussion to KDE-SC 4.6.x
is happening.
Regards,
- Sedat -
[1] http://qt-kde.debian.net/
[2] http://lists.debian.org/debian-qt-kde/
Wow huhu :-)
- Sedat
On Fri, Apr 1, 2011 at 3:23 PM, Ana Guerrero a...@debian.org wrote:
On Fri, Apr 01, 2011 at 03:03:07PM +0200, Sedat Dilek wrote:
Hi,
I am just curious where the development and discussion to KDE-SC 4.6.x
is happening.
Look in http://git.debian.org for pkg-kde repositories.
e.g.: http
Hi Fathi,
On Mon, May 19, 2008 at 9:12 AM, Fathi BOUDRA [EMAIL PROTECTED] wrote:
My guess: you have build kdebase-workspace in a non-clean environment
(dpkg-buildpackage), and you have libxcursor-dev installed.
It defines HAVE_XCURSOR and fails with undefined reference issue.
I'm not able
Package: kdebase-workspace
Version: 4.0.74-1 (UNRELEASED)
Severity: normal
Tags: patch
Hi,
I discovered a bug while building kdebase-workspace for kde4 v4.0.74-1.
$ tail -f BROKEN_kdebase-workspace_4.0.74-1_i386.build
Hi,
the above given patch [1] is NOT fixing the problem.
Maybe, it's interesting to know how I wanted to solve the problem.
My history of build-instructions...
$
DL_MIRROR=http://svn.mandriva.com/svn/packages/cooker/kdebase4-workspace/current/SOURCES;
$
Package: kdebase-workspace
Version: 4.0.72-1
Severity: important
Hi,
kdebase-workspace v4.0.72-1 seems also be infected on Sidux/i386,
see attached build-log.
On [1] I found a workaround to get rid of the problem, rude - but works ;-).
Shall I open a new bug-report or will you merge the
15 matches
Mail list logo
