See https://bugs.kde.org/show_bug.cgi?id=404990 .
In short, it's not a bug in kmail or akonadi, but rather a "political" problem
because Google themselves blocked access.
Doesn't mean it shouldn't get fixed from the KDE side though, rather the
opposite.
But me personally don't really know what
Am Donnerstag, 30. Mai 2019, 00:02:08 schrieb Shinjo Park:
> I'd llike to ask whether KMid is maintained or not:
It uses drumstick as backend AFAIK, and I think the drumstick maintainer
talked about porting kmid to Qt5 somewhere.
Can't find it currently though...
Anyway, maybe ask at
http://drum
The latest change
(https://cgit.kde.org/kdiff3.git/commit/?id=638bd5a02893dde4a1927abd0c8a611b3b3ab6a1)
unfortunately breaks the build here:
/usr/lib/gcc/i586-suse-linux/8/../../../../i586-suse-linux/bin/ld:
CMakeFiles/kdiff3part.dir/pdiff.cpp.o: in function
`debugLineCheck(Diff3LineList&, i
Am Freitag, 14. September 2018, 16:36:10 schrieb Michael Reeves:
> Can some do a clean install and see if right clicking on a file brings up
> the kdiff3 context menu?
You mean right-clicking on a file in dolphin?
Seems to work fine here with latest git master, the kdiff3 menu does show up,
and
Am Freitag, 23. Februar 2018, 17:03:37 CET schrieben Sie:
> Fixed now thanks.
Thank you.
I can confirm that with latest master it is indeed being built here (without
libkde4-devel or "patching" it), and it does work fine as well... ;-)
Kind Regards,
Wolfgang
Am Dienstag, 20. Februar 2018, 01:47:26 schrieben Sie:
> I'll take a look thanks. Is it given error out out or just not building?
I should have been more detailed in the first place, sorry.
It is not being built at all. From the build log:
-- kabstractfileitemactionplugin.h found... NO
--
Am Samstag, 17. Februar 2018, 05:03:52 schrieb Wolfgang Bauer:
> While it builds fine in general, I couldn't get the kfileitemaction plugin
> to build, so that it shows up in dolphin's context menu e.g.
I think I found the reason meanwhile:
if I additionally install the *KDE4* d
I haven't looked at the code at all, I'll leave that up to others.
But one thing:
While it builds fine in general, I couldn't get the kfileitemaction plugin to
build, so that it shows up in dolphin's context menu e.g.
OTOH, the version from git://anongit.kde.org/scratch/thomasfischer/kdiff3.git
marked as submitted.
Review request for kdelibs.
Changes
---
Submitted with commit 2ab2745eb01f73355c490ac8d5d1837dec84fd6c by Albert Astals
Cid on behalf of Wolfgang Bauer to branch KDE/4.14.
Repository: kdelibs
Description
---
This is a "backport" of
https://quickgit.
fixed ASAP IMHO, even if the
problems exist since years.
- Wolfgang Bauer
On Sept. 14, 2016, 8:02 nachm., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.
/tmp any more.
Also tried with files on an USB stick, where a folder .Trash-XXX is used as
trash.
Thanks,
Wolfgang Bauer
Before, the build aborted because a suitable hunspell couldn't be found.
It also still builds fine with hunspell 1.3.
Thanks,
Wolfgang Bauer
marked as submitted.
Review request for KDE Frameworks, kdelibs and David Faure.
Changes
---
Submitted with commit 68af1d7e89b7fed136d4cc62b76c1c6ded2d94eb by Wolfgang
Bauer to branch master.
Bugs: 354597
https://bugs.kde.org/show_bug.cgi?id=354597
Repository: kio
Description
.
Thanks,
Wolfgang Bauer
tly re-appear for the
greeter as it should if you move the mouse/press a key to get rid of the
screensaver.
I'm using the patch on my systems for over two months now and haven't noticed
any unexpected results.
Thanks,
Wolfgang Bauer
marked as submitted.
Review request for kde-workspace, Thomas Lübking and Oswald Buddenhagen.
Changes
---
Submitted with commit 46f1055ffdcd2e068296576a7824012f42e9b9a8 by Wolfgang
Bauer to branch KDE/4.11.
Bugs: 268988 and 338018
http://bugs.kde.org/show_bug.cgi?id=268988
http
tingForMapNotify" (qt bug in event
> > handling? missing "XSync(dpy, false)"? events are being processed after
> > show) or "X11->time" being superseded by a more recent/future
> > XSetInputFocus call ("fixed" by passing CurrentTime)
&g
tingForMapNotify" (qt bug in event
> > handling? missing "XSync(dpy, false)"? events are being processed after
> > show) or "X11->time" being superseded by a more recent/future
> > XSetInputFocus call ("fixed" by passing CurrentTime)
&g
tingForMapNotify" (qt bug in event
> > handling? missing "XSync(dpy, false)"? events are being processed after
> > show) or "X11->time" being superseded by a more recent/future
> > XSetInputFocus call ("fixed" by passing CurrentTime)
&g
iewboard.kde.org/r/121755/#review83215
---
On Juli 29, 2015, 11:39 vorm., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> htt
tingForMapNotify" (qt bug in event
> > handling? missing "XSync(dpy, false)"? events are being processed after
> > show) or "X11->time" being superseded by a more recent/future
> > XSetInputFocus call ("fixed" by passing CurrentTime)
&g
a misunderstanding here: this is about kdm's login greeter.
There's no window manager running at all.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/12
and the patch is even part of
openSUSE's official package since January.
See also https://bugzilla.opensuse.org/show_bug.cgi?id=772344
Thanks,
Wolfgang Bauer
s on every input event.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119663/#review64072
---
On Aug. 8, 2014, 2:37
d of the
screensaver.
I'm using the patch on my systems for over two months now and haven't noticed
any unexpected results.
Thanks,
Wolfgang Bauer
/KHTML. The correct time
is shown now like in other browsers, including Konqueror/WebKit.
Thanks,
Wolfgang Bauer
also present in Frameworks5.
Diffs
-
kjs/date_object.cpp c8d776c
Diff: https://git.reviewboard.kde.org/r/118947/diff/
Testing
---
Loaded the test case from the bug report into Konqueror/KHTML. The correct time
is shown now like in other browsers, including Konqueror/WebKit.
Thanks,
Wolfgang Bauer
default).
Thanks,
Wolfgang Bauer
at is configured for X (or its
default).
Thanks,
Wolfgang Bauer
rated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118898/#review60866
-------
On June 23, 2014, 7:01 p.m., Wolfgang Bauer wrote:
>
> ---
> This is a
> On June 23, 2014, 5:13 p.m., Martin Gräßlin wrote:
> > kcmkgamma/init_kgamma.cpp, line 39
> > <https://git.reviewboard.kde.org/r/118898/diff/1/?file=283881#file283881line39>
> >
> > why delete config? I would just use a KSharedConfig::openConfig
>
>
anyway?
But that's not really related to this bugfix, I'd say...
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118898/#review60809
----
in 4.x, but the feature will be lost again
> >
> > Again, not super-privvy of the whole picture, but isn't color correction
> > the correct solution here?
>
> Wolfgang Bauer wrote:
> applykgammasettings is only called on login for people actually
>
value is not changed. It stays at what is configured for X (or its
default).
Thanks,
Wolfgang Bauer
in 4.x, but the feature will be lost again
> >
> > Again, not super-privvy of the whole picture, but isn't color correction
> > the correct solution here?
>
> Wolfgang Bauer wrote:
> applykgammasettings is only called on login for people actually
>
e user enters the KCM. But the point of this setting
is to be applied automatically on login/startup.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118898/#review60
ogout/login (or reboot), Gamma value
gets set correctly.
If there's no kgammarc file (or it contains no actual gamma settings), the
Gamma value is not changed. It stays at what is configured for X (or its
default).
Thanks,
Wolfgang Bauer
this myself for one month without any problems.
Thanks,
Wolfgang Bauer
ignal() by
default in glibc 2 and later as well, anyway.
Diffs
-
ksmserver/screenlocker/greeter/main.cpp 4cac94c
Diff: https://git.reviewboard.kde.org/r/118563/diff/
Testing
---
I'm using this myself for one month without any problems.
Thanks,
Wolfgang Bauer
d
the locker didn't quit, you still have to enter the password.
Thanks,
Wolfgang Bauer
rd.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
> ---
> >
> > KDE Workspaces 4.11.9 tagging:
> > Fr 25. Apr 01:59:00 CEST 2014
> >
> > Would you be ok to give Martin until
> > Fr 25. Apr 00:01:00 CEST 2014
> > and then push it (on my responsibility)?
>
> Wolfgang
> ---
> >
> > KDE Workspaces 4.11.9 tagging:
> > Fr 25. Apr 01:59:00 CEST 2014
> >
> > Would you be ok to give Martin until
> > Fr 25. Apr 00:01:00 CEST 2014
> > and then push it (on my responsibility)?
>
> Wolfgang
g/r/117091/#review56415
---
On April 24, 2014, 10:52 a.m., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard
it again after the latest changes.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review56190
---
On April 24, 2014, 1
password required, and
the locker didn't quit, you still have to enter the password.
Thanks,
Wolfgang Bauer
s m_ so one would assume
> > it's a member variable, but that looks more like a static variable.
> >
> > So better make it static and use the s_ prefix
>
> Wolfgang Bauer wrote:
> You're right. It is no member variable. No idea why I chose that name.
cannot resume the
session by entering the password.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
p object, so that the signalhandler can
call its methods.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review56294
------
patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
> On April 23, 2014, 7:41 a.m., Martin Gräßlin wrote:
> > Is that only relevant for the legacy (XSS) locker or also for the new
> > locker? I'm just wondering whether it needs to be ported to master
>
> Wolfgang Bauer wrote:
> Yes. I just tried, and the scre
Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117644/#review56240
---
On April 22, 2014, 10:41 p.m., Wolfgang Bauer wrote:
>
> ---
ell, so you cannot unlock.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review56241
---
On April 22, 2014, 10:34 p
the password.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
xt console in case of a password required, and
the locker didn't quit, you still have to enter the password.
Thanks,
Wolfgang Bauer
-)
>
> sigaction(SIGUSR1, &sa, NULL); // for later nullptr
>
> i doubt that you'll need another update for that, though.
>
> Wolfgang Bauer wrote:
> Well, should I change it?
>
> In kscreensaver/libkscreensaver/main.cpp they used si
and I even set the timeout to 1 minute).
I also tried to terminate kscreenlocker_greet manually by running "killall
kscreenlocker_greet" from a text console in case of a password required, and
the locker didn't quit, you still have to enter the password.
Thanks,
Wolfgang Bauer
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review56190
---
On April 22, 2014, 9:56 p.m., Wolfgang Bauer wrote:
>
> --
:
https://git.reviewboard.kde.org/r/117091/#review56209
---
On April 22, 2014, 9:56 p.m., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-m
rd.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
s way.
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review56190
---
On April 22, 2014, 9:28 p.m., Wolfgang Ba
rd.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
> On March 26, 2014, 11:07 p.m., Thomas Lübking wrote:
> > you could sighup or sigusr the greeter process and have it
> >
> > setImmediateLock(true);
> > desktopResized();
> >
> > in return
>
> Wolfgang Bauer wrote:
> I agree, this would b
this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
> On March 26, 2014, 11:07 p.m., Thomas Lübking wrote:
> > you could sighup or sigusr the greeter process and have it
> >
> > setImmediateLock(true);
> > desktopResized();
> >
> > in return
>
> Wolfgang Bauer wrote:
> I agree, this would b
a password to resume.
Without this patch no password dialog is shown, the user cannot resume the
session by entering the password.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Thanks,
Wolfgang Bauer
> On March 26, 2014, 11:07 p.m., Thomas Lübking wrote:
> > you could sighup or sigusr the greeter process and have it
> >
> > setImmediateLock(true);
> > desktopResized();
> >
> > in return
>
> Wolfgang Bauer wrote:
> I agree, this would b
> On March 26, 2014, 11:07 p.m., Thomas Lübking wrote:
> > you could sighup or sigusr the greeter process and have it
> >
> > setImmediateLock(true);
> > desktopResized();
> >
> > in return
>
> Wolfgang Bauer wrote:
> I agree, this would b
omatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117091/#review54247
---
On March 26, 2014, 5:58 p.m., Wolfgang Bauer wrote:
>
> ---
> This
t this patch no password dialog is shown, the user cannot resume the
session by entering the password.
With this patch this works: there is a password input field, the session is
unlocked when the user enters the password.
Other openSUSE users have tested this as well, see f.e.
https://bugzilla.novell.com/show_bug.cgi?id=864305#c4
Thanks,
Wolfgang Bauer
wed the 3D accelerator info
correctly in both cases.
With lspci removed completely it showed "unknown" as expected.
Thanks,
Wolfgang Bauer
957
Diff: https://git.reviewboard.kde.org/r/114737/diff/
Testing
---
Ran KInfocenter with lspci in /usr/bin/ (i.e. in the user's path) and /sbin/
(not in the user's path). The OpenGL module showed the 3D accelerator info
correctly in both cases.
With lspci removed completely it showed "unknown" as expected.
Thanks,
Wolfgang Bauer
ocess: Destroyed while process is
still running." message in the terminal.
I now call QProcess::waitForFinished() instead of QProcess::waitForReadyRead().
This works as well, and gets rid of that warning.
- Wolfgang Bauer
On Jan. 4, 2014, 5:54 p.m., Wolfgang B
> On Jan. 8, 2014, 8:10 a.m., Martin Gräßlin wrote:
> > If you have the possibility (build setup) please merge to master and fix
> > the merge conflict I expect to see :-) I merged 4.11 into master yesterday
> > so there should no be anything else which could conflict
.org/r/114841/#review47020
---
On Jan. 8, 2014, 9:59 a.m., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> ht
le, now it is blanked like
it was the case before 4.10.
Moving the mouse/pressing a key (to quit the Screen saver) makes the mouse
cursor appear again as it should, regardless of whether the screen is locked or
not.
Thanks,
Wolfgang Bauer
ay, right?
- Wolfgang
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114841/#review46960
---
On Jan. 5, 2014, 9:55 a.m., Wol
o quit the Screen saver) makes the mouse
cursor appear again as it should, regardless of whether the screen is locked or
not.
Thanks,
Wolfgang Bauer
wed the 3D accelerator info
correctly in both cases.
With lspci removed completely it showed "unknown" as expected.
Thanks,
Wolfgang Bauer
https://git.reviewboard.kde.org/r/114737/diff/
Testing
---
Ran KInfocenter with lspci in /usr/bin/ (i.e. in the user's path) and /sbin/
(not in the user's path). The OpenGL module showed the 3D accelerator info
correctly in both cases.
With lspci removed completely it showed &
in
- Verify that the process is still running (due to bug#224200)
- log out
- log in again
Now no "kblankscrn.kss" window is opened anymore (without the patch, a window
should appear)
Thanks,
Wolfgang Bauer
openSUSE's official KDE packages since September.
- Wolfgang Bauer
On Sept. 11, 2013, 1:15 a.m., Wolfgang Bauer wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard
Am Mittwoch, 13. November 2013, 18:42:33 schrieb Ben Cooksley:
> On Tue, Nov 12, 2013 at 2:21 AM, Wolfgang Bauer
wrote:
> >
> > Sorry, it was my fault.
> > And there's also commit
925af7a94eacbe7fef101c6e0f6415b1898d3bfe now.
>
> Hi Wolfgang,
>
> The
Am Sonntag, 10. November 2013, 10:32:08 schrieb Michael Pyne:
>
> I would recommend applying the patch to 4.11 and master and then
> investigating whether QProcess would be suitable for master (this might
> also help with KF5 and Windows porting, not that I expect KInfoCenter to do
> great things
Am Montag, 11. November 2013, 14:13:22 schrieben Sie:
> On Monday 11 November 2013 13:29:32 Hugo Pereira Da Costa wrote:
> > Hello,
> > I think commits
> > 9f70241d57f3ba1013b9f28650478c8bbb1233e0
> > 137dd285bdf821fd2c8a5c17e30dc9c1a6eca87b
> > 09ea308ab55505efe7aeaebcd4aef6292cd884e6
> >
> > ser
is not in the
user's path.
Without this patch, 3D Accelerator will be shown as "unknown" (because lspci
cannot be run, with this patch it works as intended.
I also tried with lspci in /usr/bin/ (i.e. in the path) and completely removed,
worked as expected (correct information in the former case, "unknown" in the
latter).
Thanks,
Wolfgang Bauer
> -Original Message-
> From: Rolf Eike Beer [mailto:k...@opensource.sf-tec.de]
> Sent: Sunday, November 10, 2013 9:11 AM
> To: kde-core-devel@kde.org; Wolfgang Bauer
> Cc: David Stephen Hubner
> Subject: Re: Review Request 113779: KInfocenter/OpenGL: fix
> ReadPipe()
" (because lspci
cannot be run, with this patch it works as intended.
I also tried with lspci in /usr/bin/ (i.e. in the path) and completely removed,
worked as expected (correct information in the former case, "unknown" in the
latter).
Thanks,
Wolfgang Bauer
creenshots
File Attachments
KCM without the patch
http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/9cb9ae8c-6614-49ea-aae2-fdbeb36dd71e__cursor.png
KCM with the patch
http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/f3cf8c6d-d2a0-4e96-8f77-75a53f66395f__cursor2.png
Thanks,
Wolfgang Bauer
XCreateFontCursor and then
> > somehow get the bitmaps hash (XGetImage and on the bits? No idea...)
> > For the moment i'll trust Fredrik more ;-)
>
> Wolfgang Bauer wrote:
> Well, according to https://bugs.kde.org/show_bug.cgi?id=248599#c6,
> size_fdiag in QCu
XCreateFontCursor and then
> > somehow get the bitmaps hash (XGetImage and on the bits? No idea...)
> > For the moment i'll trust Fredrik more ;-)
>
> Wolfgang Bauer wrote:
> Well, according to https://bugs.kde.org/show_bug.cgi?id=248599#c6,
> size_fdiag in QCu
XCreateFontCursor and then
> > somehow get the bitmaps hash (XGetImage and on the bits? No idea...)
> > For the moment i'll trust Fredrik more ;-)
>
> Wolfgang Bauer wrote:
> Well, according to https://bugs.kde.org/show_bug.cgi?id=248599#c6,
> size_fdiag in QCu
e Attachments
>
>
> KCM without the patch
>
> http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/9cb9ae8c-6614-49ea-aae2-fdbeb36dd71e__cursor.png
> KCM with the patch
>
> http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/f3cf8c6d-d2a0-4e96-8f77-75a53f66395f__cursor2.png
>
>
> Thanks,
>
> Wolfgang Bauer
>
>
without the patch
http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/9cb9ae8c-6614-49ea-aae2-fdbeb36dd71e__cursor.png
KCM with the patch
http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/f3cf8c6d-d2a0-4e96-8f77-75a53f66395f__cursor2.png
Thanks,
Wolfgang Bauer
reviewboard.kde.org/media/uploaded/files/2013/10/10/9cb9ae8c-6614-49ea-aae2-fdbeb36dd71e__cursor.png
KCM with the patch
http://git.reviewboard.kde.org/media/uploaded/files/2013/10/10/f3cf8c6d-d2a0-4e96-8f77-75a53f66395f__cursor2.png
Thanks,
Wolfgang Bauer
org/r/113127/diff/
Testing
---
- Add a trash plasmoid to the desktop, make sure widgets are unlocked.
- Click on the trash
- file manager gets started every time, without the patch nothing happens (most
of the time).
Thanks,
Wolfgang Bauer
13127/diff/
Testing
---
- Add a trash plasmoid to the desktop, make sure widgets are unlocked.
- Click on the trash
- file manager gets started every time, without the patch nothing happens (most
of the time).
Thanks,
Wolfgang Bauer
ocked.
- Click on the trash
- file manager gets started every time, without the patch nothing happens (most
of the time).
Thanks,
Wolfgang Bauer
ings.
- Wait for the screensaver to kick in
- Verify that the process is still running (due to bug#224200)
- log out
- log in again
Now no "kblankscrn.kss" window is opened anymore (without the patch, a window
should appear)
Thanks,
Wolfgang Bauer
e patch, a window
should appear)
Thanks,
Wolfgang Bauer
1 - 100 of 107 matches
Mail list logo
