Re: How to set a recursevly PATH under wayland.

[Reindl Harald]

Am 12.05.23 um 15:15 schrieb Zener:

I'd like a recursevly path for exec in .desktop files under wayland.

As wiki 
https://wiki.archlinux.org/title/Environment_variables#Wayland_environment, i can add personal path in ~/.config/environment.d/envvars.conf.


So, adding in that file PATH=$PATH:/home/myhome/my/PATH it works for 
that directory, but I need as PATH all subdirectory too.


In .bashrc, for example, I solved just for the shell adding as below.

export PATH="$PATH:$(du -L ~/usr/bin/ | cut -f2 | tr '\n' ':' | sed 
's/:*$//')"


Can I use something somilar for the wayland enviroment?


https://linuxize.com/post/bashrc-vs-bash-profile/

but why for gods sake would someone want such microsoft-behavior which 
is the root cause for tons of security issues?

Re: Bringing Cantata under the KDE umbrella?

[Reindl Harald]

Am 21.02.23 um 07:04 schrieb Harald Sitter:

Part of the incubation process is to gather what's the team working on it.
https://community.kde.org/Incubator/Projects/DescriptionTemplate


+1. That said, what we could do is incubate into playground and see if
we can assemble the required "Healthy team (healthy proportion of
volunteers, inclusive towards new contributors, ideally more than one
developer)" if not the incubation would simply fail.


It feels wrong to incubate a project that is already out of
development. Especially when we already have a number of music
players...


I feel like there is a bit of nuance here. AFAIK neither libvlc nor
gstreamer have support for mpd so this does occupy a niche of its own.
Now, whether that justifies having yet another UI instead of investing
into backend abstraction of one of our existing UIs is another
question entirely. A question I would expect to get an answer TBH. Why
incubate cantata when we could make elisa or juk grow mpd support?
There is a substantial amount of code in the UI


it's not only the mpd support

features like cached lyrics, lastfm, wikipedia, serverside playlists 
software written to export lyrics so that they are present when you 
switch to info-mode


[harry@srv-rhsoft:~/.cache/cantata]$ disk-usage.sh
/home/harry/.cache/cantata
8136 Files17836 KB   17 MB : albums/
7142 Files21459 KB   20 MB : artists/
9800 Files  1267415 KB 1237 MB : covers/
4798 Files11289 KB   11 MB : covers-scaled/
  100738 Files   108256 KB  105 MB : lyrics/
   0 Files0 KB0 MB : scrobbling/
   1 Files7 KB0 MB : wikipedia/

Re: Bringing Cantata under the KDE umbrella?

[Reindl Harald]

Am 20.02.23 um 23:27 schrieb Tobias Leupold:

Am Montag, 20. Februar 2023, 23:15:41 CET schrieb Reindl Harald:

Am 20.02.23 um 22:45 schrieb Justin Zobel:

"Music player" daemon


Cantata is the client and don't play anything itself

but what do i expect from someone converting text mails to HTML, post a
one-liner on top of inline-quotes and use reply-all on a
maling-list...


Hey, we're quite a mellow crowd here I think. Stay nice, friendly and
professional everybody ;-)


sorry, but i can't stand such one-liners still hanging on "music player" 
which Cantata by definition isn't which was explained enough


mpd + cantata are a different beast than a "music player" playing local 
files


my homeserver continues playing the last track at the same position 
after reboot "long" before the graphical login appears and can be 
controlled by smatphone, my own website (using the native mpd protocol) 
or a GUI client like Cantata on whatever machine


and when it comes to mpd clients i have seen none within the past 15 
years which comes anywhere near to Cantata


especially on a KDE system - most other clients are coming with a ton of 
GTK/GNOME deps for half of the usability

Re: Bringing Cantata under the KDE umbrella?

[Reindl Harald]

Am 20.02.23 um 22:45 schrieb Justin Zobel:

"Music player" daemon


Cantata is the client and don't play anything itself

but what do i expect from someone converting text mails to HTML, post a 
one-liner on top of inline-quotes and use reply-all on a 
maling-list...


On Tue, 21 Feb 2023, 1:15 am Reindl Harald, <mailto:h.rei...@thelounge.net>> wrote:



Am 20.02.23 um 15:18 schrieb Aleix Pol:
 > From a product description perspective it definitely is a music
 > player. MPD is an implementation detail.

that must be why the first page of the settings is "library" with the
IP-Adress of your mpd server and other then you i am using mpd/canata
for many years :-)

https://github.com/CDrummond/cantata
<https://github.com/CDrummond/cantata>
About: Qt5 Graphical MPD Client

don't get me wrong but do you even know what MPD is?
https://www.musicpd.org/ <https://www.musicpd.org/>

a music player / server without any interface, the interface is by
definition a seperate application like canatata or android apps
connecting to mpd via tcp which can run on localhost but don't need to

 >> Am 20.02.23 um 13:18 schrieb Aleix Pol:
 >>> On Mon, Feb 20, 2023 at 12:28 AM Heiko Becker
mailto:heiko.bec...@kde.org>> wrote:
 >>>>
 >>>> On Sunday, 19 February 2023 23:36:22 CET, Albert Astals Cid wrote:
 >>>>> El diumenge, 19 de febrer de 2023, a les 16:29:24 (CET),
Heiko Becker va
 >>>>> escriure:
 >>>>>> Cantata is a Qt based MPD client, which was archived by its
 >>>>>> original author
 >>>>>> [1]. I started some porting to Qt6 but I wondered (and was
asked in
 >>>>>> #kde-devel today) if it would make sense to move it to KDE's
 >>>>>> infrastructure? Despite being archived, it still works quite
 >>>>>> nicely. And ...
 >>>>>
 >>>>> My only 2 concerns are:
 >>>>>
 >>>>>    * Is anyone going to work on it? I guess you?
 >>>>
 >>>> Yes.
 >>>
 >>> Part of the incubation process is to gather what's the team
working on it.
 >>>
https://community.kde.org/Incubator/Projects/DescriptionTemplate
<https://community.kde.org/Incubator/Projects/DescriptionTemplate>
 >>>
 >>> It feels wrong to incubate a project that is already out of
 >>> development. Especially when we already have a number of music
 >>> players...
 >>
 >> Cantata isn't a "music player"
 >> it's the by far best MPD client

Re: Bringing Cantata under the KDE umbrella?

[Reindl Harald]

Am 20.02.23 um 15:18 schrieb Aleix Pol:

From a product description perspective it definitely is a music
player. MPD is an implementation detail.


that must be why the first page of the settings is "library" with the 
IP-Adress of your mpd server and other then you i am using mpd/canata 
for many years :-)


https://github.com/CDrummond/cantata
About: Qt5 Graphical MPD Client

don't get me wrong but do you even know what MPD is?
https://www.musicpd.org/

a music player / server without any interface, the interface is by 
definition a seperate application like canatata or android apps 
connecting to mpd via tcp which can run on localhost but don't need to



Am 20.02.23 um 13:18 schrieb Aleix Pol:

On Mon, Feb 20, 2023 at 12:28 AM Heiko Becker  wrote:


On Sunday, 19 February 2023 23:36:22 CET, Albert Astals Cid wrote:

El diumenge, 19 de febrer de 2023, a les 16:29:24 (CET), Heiko Becker va
escriure:

Cantata is a Qt based MPD client, which was archived by its
original author
[1]. I started some porting to Qt6 but I wondered (and was asked in
#kde-devel today) if it would make sense to move it to KDE's
infrastructure? Despite being archived, it still works quite
nicely. And ...


My only 2 concerns are:

   * Is anyone going to work on it? I guess you?


Yes.


Part of the incubation process is to gather what's the team working on it.
https://community.kde.org/Incubator/Projects/DescriptionTemplate

It feels wrong to incubate a project that is already out of
development. Especially when we already have a number of music
players...


Cantata isn't a "music player"
it's the by far best MPD client

Re: Bringing Cantata under the KDE umbrella?

[Reindl Harald]

Am 20.02.23 um 13:18 schrieb Aleix Pol:

On Mon, Feb 20, 2023 at 12:28 AM Heiko Becker  wrote:


On Sunday, 19 February 2023 23:36:22 CET, Albert Astals Cid wrote:

El diumenge, 19 de febrer de 2023, a les 16:29:24 (CET), Heiko Becker va
escriure:

Cantata is a Qt based MPD client, which was archived by its
original author
[1]. I started some porting to Qt6 but I wondered (and was asked in
#kde-devel today) if it would make sense to move it to KDE's
infrastructure? Despite being archived, it still works quite
nicely. And ...


My only 2 concerns are:

  * Is anyone going to work on it? I guess you?


Yes.


Part of the incubation process is to gather what's the team working on it.
https://community.kde.org/Incubator/Projects/DescriptionTemplate

It feels wrong to incubate a project that is already out of
development. Especially when we already have a number of music
players...


Cantata isn't a "music player"
it's the by far best MPD client

Re: Unknown protocol "konq"

[Reindl Harald]

Am 27.12.22 um 22:10 schrieb Luigi Toscano:

Reindl Harald ha scritto:


that starts with CTRL+F and a childish filter instead kfind


On the other hand, Ctrl-shift-f is the shortcut of the "Open KFind" menu
entry, which is the fist one of the "Tools" menu


maybe - but common in general over tons of software is CTRL+F and the 
need of dozens of different seachres is questionable when kfind exists 
as long as i can think


there is a "filter" for simple minded users at the bottom and a 
half-baked search for middle-minded users when there is kfind as 
ultimateive solution which just lacks "delete without trash" in the 
context menu to make it perfect


one task - one tool

the point is that the trivial appeareance of dolphin could have been 
implemented in konqueror an d instead waste development cycles in 
redundant software one could read the logs and fix errors


the load of trivial to face warnings in the codebase is large enough for 
many years - again: either read and fix them or don't clutter my 
logfiles all day long


--

[root@srv-rhsoft:~]$ uptime
 22:19:55 up  3:30,  5 users,  load average: 1,00, 0,62, 0,68

[root@srv-rhsoft:~]$ journalctl | grep 
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml" 
| grep "Dez 27" | wc -l

144

--

kioslave5[19113]: kf.coreaddons: Expected a KPluginFactory, got a 
KIOPluginForMetaData


Dez 27 22:09:20 srv-rhsoft.rhsoft.net kid3[18756]: QCommandLineParser: 
already having an option named "h"
Dez 27 22:09:20 srv-rhsoft.rhsoft.net kid3[18756]: QCommandLineParser: 
already having an option named "help-all"
Dez 27 22:09:20 srv-rhsoft.rhsoft.net kid3[18756]: QCommandLineParser: 
already having an option named "v"


Dez 27 22:15:03 srv-rhsoft.rhsoft.net plasmashell[1384]: 
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: 
QML SelectableLabel: Binding loop detected for property "implicitWidth"


Dez 27 22:08:24 srv-rhsoft.rhsoft.net plasmashell[1384]: 
file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:45:27: 
QML ScrollBar: Binding loop detected for property "visible"

Re: Unknown protocol "konq"

[Reindl Harald]

Am 27.12.22 um 19:58 schrieb Nicolas Fella:

Am 27.12.22 um 18:56 schrieb Reindl Harald:

Hi

for month now on Fedora you get a error message everytime you start
konqueror or open a new tab that the protocol "knoq" isn't known

nobody in the distro bugtarcker cares, recently again kf5/konqueror
updates and still the same issue

dunno what this protocol should be for, maybe a missing but obious
useless dependecny because besides the annoying message you need to
confirm all day long everything works

Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
Protocol Class of url QUrl("konq:blank") , isn't ':local', cancelling
job.
Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
couldn't create slave: "Unbekanntes Protokoll „konq“."


Please don't use the mailing list to report bugs, that's what
https://bugs.kde.org is for.


it's by far not about a single specific bug but flood users for years 
with a growing amount of logspam and now starting with information 
popups additionally to logs for a non existing issue because the 
application simply works after press ESC to get the messagebox closed




don't get me wrong but i am sick and tired of adding new syslog filters 
after each and every update - i can't fix that stuff below and 
developers don't read it


[root@srv-rhsoft:~]$ cat rsyslog.conf | grep stop | wc -l
573

i care about my logs and want them free from spam to see stuff i can do 
anything about instead burry it in useless floods


that (again don't get me wrong) nosense below should only appear when 
some debug flag is set, developers should set it and read the messages




# unwanted desktop messages
:msg,contains,"WARNING **: Property get or set does not have an 
interface string as first arg" stop

:msg, contains, "CdSane-DEBUG" stop
:msg, contains, "HDMI hot plug event" stop
:msg, contains, "HDMI status" stop
:msg, contains, "Activating service name='org.freedesktop.PolicyKit1'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.ConsoleKit'" stop

:msg, contains, "Activating service name='org.freedesktop.UPower'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.UPower'" stop

:msg, contains, "Activating service name='org.freedesktop.UDisks'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.UDisks'" stop
:msg, contains, "Activating via systemd: service 
name='org.freedesktop.RealtimeKit1'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.RealtimeKit1'" stop

:msg, contains, "Successfully made thread" stop
:msg, contains, "Activating via systemd: service 
name='org.freedesktop.ColorManager'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.ColorManager'" stop
:msg, contains, "Activating via systemd: service 
name='org.freedesktop.colord-sane'" stop
:msg, contains, "Successfully activated service 
'org.freedesktop.colord-sane'" stop

:msg, contains, "CHECK POWER STATUS spins up disk" stop
:msg, contains, "CHECK POWER STATUS returned 129, not ATA compliant" stop
:msg, contains, "Reloading\." stop
:msg, contains, "received packet on bond0 with own address" stop
:msg, contains, "Process '/usr/sbin/crda' failed with exit code 251" stop

# unwanted desktop messages Fedora 22
:msg, contains, "ignoring: Unit dnf-makecache.timer is masked" stop
:msg, contains, "GLib-GIO-Message: Using the 'memory' GSettings backend" 
stop

:msg, contains, "dbus-org.freedesktop.NetworkManager.service" stop
:msg, contains, "kuiserver: removing jobview" stop
:msg, contains, "kuiserver: making async call" stop
:msg, contains, "kuiserver: adding job contact" stop
:msg, contains, "kuiserver: current pending calls" stop
:msg, contains, "kuiserver: no more async calls left" stop
:msg, contains, "kuiserver: making async terminate" stop
:msg, contains, "kuiserver: this was because a pending" stop
:msg, contains, "Your keyboard setup doesn't provide a key to use for 
meta" stop


# unwanted desktop messages Fedora 24
:programname, isequal, "plasmashell" stop
:programname, isequal, "kwin_x11" stop
:programname, isequal, "kscreenlocker_greet" stop
:programname, isequal, "kdeinit4" stop
:programname, isequal, "kdeinit5" stop
:programname, isequal, "ksmserver" stop
:msg, contains, "QXcbConnection: XCB error" stop
:msg, contains, "QObject::connect" stop
:msg, contains, 
"org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml" stop

:msg, contains, "QPainter::" stop
:msg, contains, "

Re: Unknown protocol "konq"

[Reindl Harald]

Am 27.12.22 um 19:49 schrieb Nate Graham:

On 12/27/22 11:26, Reindl Harald wrote:
but given i use konqueror only as filemanager because dolphin with the 
lack of bookmarks is a joke


Dolphin has bookmarks, FWIW: https://i.imgur.com/ylXHTBf.jpg


OK, in the meantime it seem to have bookmarks which are empty while i 
was able at least to copy my tons of existing bookmakrs for all sort of 
local and remote points after it was ported to KF5 (hopefully KF5 to KF6 
will work smarter and not again start evvery ported application with all 
settings lost)


but it still appears like a stripped down konqueror for simple minded users

that starts with CTRL+F and a childish filter instead kfind

i didn't understand dolphin introduction at all back in the days and i 
still don't

Re: Unknown protocol "konq"

[Reindl Harald]

Am 27.12.22 um 19:26 schrieb Reindl Harald:

Am 27.12.22 um 19:20 schrieb Stefano Crocco:

On martedì 27 dicembre 2022 18:56:39 CET Reindl Harald wrote:

Hi

for month now on Fedora you get a error message everytime you start
konqueror or open a new tab that the protocol "knoq" isn't known

nobody in the distro bugtarcker cares, recently again kf5/konqueror
updates and still the same issue

dunno what this protocol should be for, maybe a missing but obious
useless dependecny because besides the annoying message you need to
confirm all day long everything works

Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
Protocol Class of url QUrl("konq:blank") , isn't ':local', cancelling 
job.

Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
couldn't create slave: "Unbekanntes Protokoll „konq“."


What version of Konqueror are you using? 


konqueror-22.12.0-1.fc36.x86_64


when you disable konqueoror preloading and start it the first time this 
message appears in the logs:


kf.service.services: KApplicationTrader: mimeType 
"x-scheme-handler/konq" not found

Re: Unknown protocol "konq"

[Reindl Harald]

Am 27.12.22 um 19:20 schrieb Stefano Crocco:

On martedì 27 dicembre 2022 18:56:39 CET Reindl Harald wrote:

Hi

for month now on Fedora you get a error message everytime you start
konqueror or open a new tab that the protocol "knoq" isn't known

nobody in the distro bugtarcker cares, recently again kf5/konqueror
updates and still the same issue

dunno what this protocol should be for, maybe a missing but obious
useless dependecny because besides the annoying message you need to
confirm all day long everything works

Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
Protocol Class of url QUrl("konq:blank") , isn't ':local', cancelling job.
Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core:
couldn't create slave: "Unbekanntes Protokoll „konq“."


What version of Konqueror are you using? 


konqueror-22.12.0-1.fc36.x86_64


Can you check that you have
webenginepart installed? It should be part of Konqueror itself, unless Fedora
decided to make a separate package. To be sure, please, check if you have all
of these files:


[harry@srv-rhsoft:/downloads]$ rpm -qa | grep -i webengine
qt5-qtwebengine-5.15.10-4.fc36.x86_64
kwebenginepart-22.12.0-1.fc36.x86_64


- libkwebenginepart.so (should be in /usr/lib64 or /usr/lib)
- webenginepart.so (should be in /usr/lib64/plugins or /usr/lib/plugins or in
a subdirectory, depending on the version)
- webenginepart.desktop (should be in /usr/share/kservices5)


[harry@srv-rhsoft:/downloads]$ rpm -q --file /usr/lib64/libkwebenginepart.so
kwebenginepart-22.12.0-1.fc36.x86_64


Also, could you please check in Konqueror Settings dialog which entries are
listed for the "Default web browser engine" in the General tab? Is there a
WebEngine entry?


yes

but given i use konqueror only as filemanager because dolphin with the 
lack of bookmarks is a joke and the "startpage" is ~/ i don't get the 
connection with webengine at all


KDE software writes ton of messages all day long to the syslog (80% of 
my rsyslog.conf are filters to supress that stuff) but now as it starts 
also coming up with messagesboxes can someone please stop this "trend"


there is no reason to come up with such annoying alerts the user can't 
do anything against as well as a user can't do anything with logspam 
like "plasmashell[1384]: 
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: 
QML SelectableLabel: Binding loop detected for property implicitWidth" 
and maintainers/developers obviously don't care


this is all stuff for debugging and developers but don't bother endusers 
with it please!

Unknown protocol "konq"

[Reindl Harald]

Hi

for month now on Fedora you get a error message everytime you start 
konqueror or open a new tab that the protocol "knoq" isn't known


nobody in the distro bugtarcker cares, recently again kf5/konqueror 
updates and still the same issue


dunno what this protocol should be for, maybe a missing but obious 
useless dependecny because besides the annoying message you need to 
confirm all day long everything works


Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core: 
Protocol Class of url QUrl("konq:blank") , isn't ':local', cancelling job.
Dez 27 18:51:00 srv-rhsoft.rhsoft.net kioexec[2417]: kf.kio.core: 
couldn't create slave: "Unbekanntes Protokoll „konq“."

Re: Question about KWrite's new tab behavior

[Reindl Harald]

Am 03.12.22 um 11:29 schrieb Tobias Leupold:

How can I get the old behavior with multiple instances instead of tabs back?!
We fear change :-D

Thanks in advance for the explanation!
[harry@srv-rhsoft:~/.local/share/applications]$ cat Kate\ \(New\ 
Window\).desktop

[Desktop Entry]
Comment=
Exec=kate --new -b %U
Icon=kate
Name=Kate (New Window)
NoDisplay=false
Path[$e]=
StartupNotify=true
Terminal=0
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=

Re: Reviewer for Konqueror needed

[Reindl Harald]

Am 01.11.22 um 09:31 schrieb Stefano Crocco:

On lunedì 31 ottobre 2022 23:52:20 CET Reindl Harald wrote:

Am 31.10.22 um 20:51 schrieb Stefano Crocco:

Hello to everyone,
I'm the current Konqueror maintainer


can you *please* restore close tabs by middle-click like in any other
browser? that got lost a few years ago with one of the KF5 updates and
is really annoying


Are you sure? On my system it works as expected. Maybe you don't have the
corresponding option enabled
then some random update disabled it - i use konqueror since 2006 as my 
primary file manager


but better not remember the unholy migration from KF4 to KF5 when old 
configs where completly ignored - for the sake of god read the old 
configs and write your new ones whereever you want, i don't care as user


with every Fedora dist-upgrade a few other apps where ported to KF5

i had this mess with KDE3->KDE4, KDE4->KDE5 was exactly identical 
terrible - if the same happens with KDE6 i switch to openbox



since this feature is off by default. It's in the
General page of the settings dialog.


well, i didn't expect that such expected basic behavior isn't enabled by 
default

Re: Reviewer for Konqueror needed

[Reindl Harald]

Am 31.10.22 um 20:51 schrieb Stefano Crocco:

Hello to everyone,
I'm the current Konqueror maintainer


can you *please* restore close tabs by middle-click like in any other 
browser? that got lost a few years ago with one of the KF5 updates and 
is really annoying

Re: New releases for bugfixes

[Reindl Harald]

Am 19.09.22 um 14:57 schrieb Neal Gompa:

On Sat, Sep 10, 2022 at 5:41 AM Reindl Harald  wrote:


Am 09.09.22 um 11:42 schrieb samuel ammonius:

Thanks. I hadn't thought of a lot of these issues before.

I think the biggest one is that If there's an update that the package
manager didn'tknow about, the user would have to update right after installing, 
and
the bug would come back if the user re-installed or updated the app. Sorry 
everybody

no the biggest issue on the userside is that nobody wants every random
application tamper the system

if i want applications asking me about updates i could have stayed at
windows and "yum upgrade" was the main reason for Linux

when you open that can of worms imagine where it ends

security wise it's a nightmare because you not only have the
distribution you need to trust - intrusion on any upstream would
directly hit you at any random point in time while distribution updates
are usually tested at least by some people and changes reviewed by
downstream maintainers

and who does the work and deal with bugreports "the update of kate
destroyed it on my system and i don't know why nor how i revert it"

with the package manager i type "dnf downgrade kate", file a bug against
the distribution and kde upstream isn't involved at all

upstream opensource developers write the code, that's it, they don't and
shouldn't need to care about every downstream distribution and it's
pitfalls - it's wasted time because that's what downstream component
maintainers are for

the fedora maintainer from kde likely has no knowledge about Gentoo,
Ubuntu, SuSE for good reasons and you think blow that load to upstream
developers would help anybody?


Well, actually, most of us do know each other and we do collaborate
from time to time. I personally know Fabian Vogt (the maintainer of
the KDE stack in SUSE distributions) and I talk to Rik Mills (the
Kubuntu maintainer) every once in a while. Same goes for Mageia,
OpenMandriva, Debian, and others.


don't change the fact that downstream and upstream are different worlds 
at the end of the day when it comes to apply a bufix patch



Admittedly, I don't know who works on KDE Plasma for Gentoo, but I'm
peripherally aware of their work.

As maintainers of KDE software in our respective distributions, it's
our job to bring our concerns upstream as needed. But also, when
distributions have a conflict, we *all* have to work together to
figure out a solution. If we don't, we risk a situation where KDE
eventually evolves into other similarly-sized desktop environment
projects where they give the downstream stakeholders the finger
because they don't trust them.


but the proposed idea was BYPASS you and apply updates directly from 
upstream



Also, many of the upstream KDE Plasma developers are in fact distro
developers. It's not the majority anymore like it was in the old days,
but a good chunk of them are.
but hardly the majority and even if that could change any time - 
especailly for small bugfix patches it's irrelevant when one comes to 
the idea apply them directly from upstream up to "build them local from 
source automagically"


the general rule is "upstream is upstream, distro is distro" and for the 
sake of god that don#t mean they don't talk to each other

Re: New releases for bugfixes

[Reindl Harald]

Am 09.09.22 um 11:42 schrieb samuel ammonius:

Thanks. I hadn't thought of a lot of these issues before.

I think the biggest one is that If there's an update that the package 
manager didn'tknow about, the user would have to update right after installing, and 
the bug would come back if the user re-installed or updated the app. Sorry everybody
no the biggest issue on the userside is that nobody wants every random 
application tamper the system


if i want applications asking me about updates i could have stayed at 
windows and "yum upgrade" was the main reason for Linux


when you open that can of worms imagine where it ends

security wise it's a nightmare because you not only have the 
distribution you need to trust - intrusion on any upstream would 
directly hit you at any random point in time while distribution updates 
are usually tested at least by some people and changes reviewed by 
downstream maintainers


and who does the work and deal with bugreports "the update of kate 
destroyed it on my system and i don't know why nor how i revert it"


with the package manager i type "dnf downgrade kate", file a bug against 
the distribution and kde upstream isn't involved at all


upstream opensource developers write the code, that's it, they don't and 
shouldn't need to care about every downstream distribution and it's 
pitfalls - it's wasted time because that's what downstream component 
maintainers are for


the fedora maintainer from kde likely has no knowledge about Gentoo, 
Ubuntu, SuSE for good reasons and you think blow that load to upstream 
developers would help anybody?


wasted time and resources

Re: New releases for bugfixes

[Reindl Harald]

Am 08.09.22 um 23:53 schrieb samuel ammonius:

 > and you marry upstream binaries with the distribution update-manager how?

You don't need to. The app can just check the latest bugfix for that 
version on git
and install it if it isn't installed. I don't understand why you stress 
the need for the
package manager to have anything to do with the update if it's just a 
bug fix


no it's not just a bugfix when you start mixing random binaries or self 
compiled stuff with distribution binaries


maybe you guys inform yourself how a linux distribution works - on 
Fedoar at example every Fedoar releaae builds everything from scratch 
with the same GCC, glibc and tons of other libraries which differ 
largely between distro releases


what you dream about is flatpak - sorry, one of my main reasons 
switching to linux was a central pakcage management

Re: New releases for bugfixes

[Reindl Harald]

Am 08.09.22 um 22:24 schrieb samuel ammonius:

 > because outside the windows world central package management is the norm
 > and based on "least privileges" applications must not have the
 > permissions to change itself

I didn't mean a background update. I meant the user could get a dialog or
notification asking them to update, and if they press "yes" they can 
enter their

root password and the app can update itself and restart.


and you marry upstream binaries with the distribution update-manager how?


 > and for each distribution with different dependencies and libraries

How does KDE have different dependencies for different distros? (To be 
honest
though, I only mentioned this method because I thought having multiple 
options

would advertise the idea in the second method)


in the way that distributions have different library versions


if you don't care for security


The security risk is very small, and it can be fixed in a lot of 
different ways. The
app could create a folder that only root can access within the /tmp 
folder. If even

that's not secure enough, the app could create source files with just
"#define MAIN_CPP_SOURCE" and compile with "-DMAIN_CPP_SOURCE=[the
source code] so that it never has to be stored on the disk before being 
compiled.


bla


 > which distribution installs a compiler by default so that one can avoid
 > touching it?

I don't think I've ever used one that /doesn't/ come with at least gcc 
installed


i didn't see a defualt install for a long time but have a compiler on 
99,9% of all systems is useless bloatware


I've tried Ubuntu, Debian, Fedora, and OpenSUSE. Now that I think about 
it though,
they don't come with g++ installed, and they definitely don't come with 
Qt headers

installed, but they don't take that much space

more space than some of my systems at a whole

It didn't take me 10 minutes to answer these questions in my head, so I 
don't
see why you're trying to scrap the idea so quickly for its faults 
instead of trying

to fix them. A bit of constructive criticism would be nice


a little bit of more realistic view for such nosense would be nice too

if anything you propose would become real i had to switch away from KDE

Re: New releases for bugfixes

[Reindl Harald]

Am 08.09.22 um 20:50 schrieb samuel ammonius:

Bug fixes don't change the entire package, only the executable, so
why can't apps just be programmed to update themselves? 


because outside the windows world central package management is the norm 
and based on "least privileges" applications must not have the 
permissions to change itself



could be precompiled binaries stored on the git repos of each project
for a few CPU architectures


and for each distribution with different depencdencies and libraries


or maybe the app could even recompile
itself inside /tmp 


if you don't care for security


since most systems KDE runs on come with a compiler
by default


which distribution installs a compiler by default so that one can avoid 
touching it?

Re: Unsubscribing from mailing list (was: Re: Porting a project to KDE)

[Reindl Harald]

Am 16.08.20 um 18:09 schrieb David Hurka:
> Send a mail with subject “help” to kde-devel-requ...@kde.org. That should 
> give 
> you instructions. You will need the “password” command and then the 
> “unsubscribe” command.

List-Unsubscribe: ,


> At least this is how I am used to work with mailing lists run by mailman.

every mailing list run by mailman has the headers above as well it tells
you in the welcome message how to unsubcribe

it's amazing that in 2020 still nobody is capable to operate a mail client

> On 8/16/20 3:12 PM Yiqing Yu wrote:
>> I have sent an email to kde-devel-unsubscr...@kde.org, but it was
>> undeliverable. This address is invalid.
>> Is there an alternative to unsubscribe me from the mailing list? Thanks.
>>
>> On Sun, Aug 16, 2020 at 6:02 PM Ben Cooksley  wrote:
>>> On Sun, Aug 16, 2020 at 3:45 PM Yiqing Yu  wrote:
 Please unsubscribe me from the list. Thanks!
>>>
>>> Hi Yiqing,
>>>
>>> You can do this on a self-service basis by sending an email to
>>> kde-devel-unsubscr...@kde.org.
>>>
>>> Following this you will receive an email with a link you need to click
>>> to complete the unsubscription process.
>>>
>>> Regards,
>>> Ben Cooksley
>>> KDE Sysadmin
>>>
 On Sun, Aug 16, 2020 at 11:30 AM Francois Blanchette <
>>>
>>> cfrankb.2...@gmail.com> wrote:
> On 8/15/20, Albert Astals Cid  wrote:
>> El divendres, 14 d’agost de 2020, a les 15:07:40 CEST, Francois
>>>
>>> Blanchette
>>>
>> va escriure:
>>> Hi
>>>
>>> My project is call LGCK builder.  It is a Game Construction Kit
>>> written in C++ using a combination of Qt5, OpenGL and SDL. In
>>>
>>> addition
>>>
>>> to the main IDE there is also a standalone Sprite Editor. The main
>>> engine implements the graphics, inputs and sounds components via a
>>> series of Interfaces which allows different implementers (right now
>>> SDL, OpenGL and SFML are fleshed out). Additional back-ends could be
>>> added by simply swapping one implementer for another. I think the
>>> design is unique because it is object-oriented which frees users
>>> from
>>> messing around with the old tile-2-tile formula.
>>>
>>> You can read more about on the official page
>>> https://cfrankb.com/lgck?main
>>>
>>> There is a 5 minute video explaining how to make a game
>>> https://www.youtube.com/watch?v=lN3gkZWr-PM
>>>
>>> The full source code can be found here:
>>> https://github.com/cfrankb/lgck-src
>>
>> You haven't made any commit to that project in the last 2 years,
>>>
>>> what's your
>>>
>> plan for it? Are you going to pick it up again?
>
> Hi Albert,
>
> The github ui only shows commits from the master branch and this
> paints an incomplete picture. I have been cranking out commits like
> crazy for past the month. 69 commits in total but they don't show up
> on the timeline.
>
> My plan is to continue cleaning up the code, get it up to standard and
> get some feedback. The feedback part is what i really need to work on
> because it gets to spend time where it most matter to improve the end
> result.
>
> I have prepare a new video that show case some of these new, up and
> coming ui improvements. Here is the 2020 LGCK Builder.
> https://www.youtube.com/watch?v=wukMgkmvXAY

Re: kdump all the things!

[Reindl Harald]

Am 07.09.19 um 17:34 schrieb Harald Sitter:
> I've made a thing that makes systemd-coredump easier to use and I for
> one use it as a replacement for drkonqi because it's both more
> reliable but also less UI faffing to get to what matters most to me...
> gdb.
> 
> https://invent.kde.org/sitter/kde-coredump
> 
> We could probably pursue extending it further and make it extragear or
> something if there's interest.

the subject is terrible!
https://en.wikipedia.org/wiki/Kdump_(Linux)

Re: Code Review: Spectacle

[Reindl Harald]

Am 05.05.19 um 22:44 schrieb Reindl Harald:
> 
> 
> Am 05.05.19 um 22:39 schrieb Nate Graham:
>>   On Sun, 05 May 2019 14:16:01 -0600 Reindl Harald 
>>  wrote 
>>  > Am 05.05.19 um 22:12 schrieb Nate Graham:
>>  > > As of 19.04, this is now an optional but off-by-default feature. Feel 
>> free to turn it on. :)
>>  > 
>>  > that's not the point
>>  > 
>>  > the point is that it makes sense for everything but *not* "rectangle
>>  > selection" and that i am tired after years now switch that checkbox on
>>  > and off for different use cases while before "Spectacle" all worked like
>>  > a charme out-of-the-box
>>
>>
>> I don't think you could have been switching that checkbox on for years since 
>> it was just added in the 19.04 release which came out a few days ago. But 
>> feel free to make the case that it should be on by default and submit a 
>> simple patch that does it. I don't really object, myself.
> 
> 
> what are you talking about?
> 
> * right next to delay there is a checkbox all the time "on click"
> * you can switch that checkbox on for years (at least on Fedora)
> * but it makes no sense apply it for every mode
> * when i select a rectangle from my screen for a screenshot
>   there is not point for an additional click
> * in case of screenshot of a window there is a point by say what window

see screenshot if it makes it to the list, there is a red mark around
the checkbox

Re: Code Review: Spectacle

[Reindl Harald]

Am 05.05.19 um 22:49 schrieb Reindl Harald
> Am 05.05.19 um 22:44 schrieb Reindl Harald:
>>
>>
>> Am 05.05.19 um 22:39 schrieb Nate Graham:
>>>   On Sun, 05 May 2019 14:16:01 -0600 Reindl Harald 
>>>  wrote 
>>>  > Am 05.05.19 um 22:12 schrieb Nate Graham:
>>>  > > As of 19.04, this is now an optional but off-by-default feature. Feel 
>>> free to turn it on. :)
>>>  > 
>>>  > that's not the point
>>>  > 
>>>  > the point is that it makes sense for everything but *not* "rectangle
>>>  > selection" and that i am tired after years now switch that checkbox on
>>>  > and off for different use cases while before "Spectacle" all worked like
>>>  > a charme out-of-the-box
>>>
>>>
>>> I don't think you could have been switching that checkbox on for years 
>>> since it was just added in the 19.04 release which came out a few days ago. 
>>> But feel free to make the case that it should be on by default and submit a 
>>> simple patch that does it. I don't really object, myself.
>>
>>
>> what are you talking about?
>>
>> * right next to delay there is a checkbox all the time "on click"
>> * you can switch that checkbox on for years (at least on Fedora)
>> * but it makes no sense apply it for every mode
>> * when i select a rectangle from my screen for a screenshot
>>   there is not point for an additional click
>> * in case of screenshot of a window there is a point by say what window
> 
> see screenshot if it makes it to the list, there is a red mark around
> the checkbox

how i hate 1970 limits of 50 KB in 2019 - another try

Re: Code Review: Spectacle

[Reindl Harald]

Am 05.05.19 um 22:39 schrieb Nate Graham:
>   On Sun, 05 May 2019 14:16:01 -0600 Reindl Harald 
>  wrote 
>  > Am 05.05.19 um 22:12 schrieb Nate Graham:
>  > > As of 19.04, this is now an optional but off-by-default feature. Feel 
> free to turn it on. :)
>  > 
>  > that's not the point
>  > 
>  > the point is that it makes sense for everything but *not* "rectangle
>  > selection" and that i am tired after years now switch that checkbox on
>  > and off for different use cases while before "Spectacle" all worked like
>  > a charme out-of-the-box
> 
> 
> I don't think you could have been switching that checkbox on for years since 
> it was just added in the 19.04 release which came out a few days ago. But 
> feel free to make the case that it should be on by default and submit a 
> simple patch that does it. I don't really object, myself.


what are you talking about?

* right next to delay there is a checkbox all the time "on click"
* you can switch that checkbox on for years (at least on Fedora)
* but it makes no sense apply it for every mode
* when i select a rectangle from my screen for a screenshot
  there is not point for an additional click
* in case of screenshot of a window there is a point by say what window

Re: Code Review: Spectacle

[Reindl Harald]

Am 05.05.19 um 22:12 schrieb Nate Graham:
>   On Sun, 05 May 2019 13:57:49 -0600 Reindl Harald 
>  wrote 
>  > 
>  > 
>  > Am 05.05.19 um 21:44 schrieb Boudhayan Gupta:
>  > > Hi folks,
>  > > 
>  > > I've been hacking on Spectacle again :-P
>  > 
>  > if you are at it please bring back the sane behavior of "ksnapshot" to
>  > make "remember selection" default *but not* between sessions
> 
> As of 19.04, it now is. :)
> 
>  > 
>  > that worked so fine for all the years when you had to document some
>  > process with a ton of screenshots step by step where the selection is
>  > identical at every step
>  > 
>  > the same for "on click" - that makes no sense for a rectangle selection
>  > in most cases
> 
> As of 19.04, this is now an optional but off-by-default feature. Feel free to 
> turn it on. :)

that's not the point

the point is that it makes sense for everything but *not* "rectangle
selection" and that i am tired after years now switch that checkbox on
and off for different use cases while before "Spectacle" all worked like
a charme out-of-the-box

Re: Code Review: Spectacle

[Reindl Harald]

Am 05.05.19 um 21:44 schrieb Boudhayan Gupta:
> Hi folks,
> 
> I've been hacking on Spectacle again :-P

if you are at it please bring back the sane behavior of "ksnapshot" to
make "remember selection" default *but not* between sessions

that worked so fine for all the years when you had to document some
process with a ton of screenshots step by step where the selection is
identical at every step

the same for "on click" - that makes no sense for a rectangle selection
in most cases

it looks like "ksnapshot" but it's far from it#s uasability

there was a bugreport in context of "remember selection" where people
pretended that this behavior confuses users and hence it's not default

YES in the current implementation that i get my old random selection
from two weeks ago when press the print key is confusing, even for power
users like me, but that was fine before "ksnapshot" got replaced for
many years and i still don't get why when someone writes a replacement
for something why he doesn't even try to understand such basic behavior
and just change it

Re: Upcoming change to mail infrastructure -> SPF still broken

[Reindl Harald]

Am 04.07.2018 um 15:31 schrieb Luca Beltrame:
> Il giorno Wed, 4 Jul 2018 14:45:00 +0200 Reindl Harald
>  ha scritto:
> 
>> https://bugs.kde.org/show_bug.cgi?id=392685 2018-04-03 18:45:47
>> UTC
> 
> For the record, Sysadmin tickets should be filed through 
> Phabricator (https://go.kde.org/systickets) rather than Bugzilla:
> this makes sure that they won't get lost.

and how do you imagine that for *users* like me which just reading teh
devel-list and have no access with their bugzilla credentials there?

and even if i can register at https://identity.kde.org/ please make a
reality check how likely it is that people register here and there and
there too just to report a bug in KDE software in a way it's recognized

> (Bugzilla is still used for KDE software - this is for
> Sysadmin-related stuff)

that's why "bugs.kde.org" is in the product dropdown i guess - if
someone would take a look at new bugreports and be it only the
subjects this one would have been seen within 24 hours and internally
handed to the right group

-

if this contains one of my own machines i see the mistake not
configure "mynetworks" in /etc/postfix/main.cf proper within 24 hours
because i did "man grep", "man cron" and "man bash"

1   Jun 26 09:45:42 mail-gw postfix/smtpd[636481]: NOQUEUE: reject:
RCPT from mailnet.top[5.79.119.167]: 550 5.7.23
: Recipient address rejected: Message
rejected due to: SPF fail - not authorized. Please see
http://www.openspf.net/Why?s=mfrom;id=webmas...@mailnet.top;ip=5.79.119.167;r=contai...@thelounge.net;
from= to= proto=ESMTP
helo=

Re: Upcoming change to mail infrastructure -> SPF still broken

[Reindl Harald]

Am 04.07.2018 um 14:45 schrieb Reindl Harald:
> Am 04.07.2018 um 13:58 schrieb Ben Cooksley:
>>>> I'd be curious to know when you observed that, as I can find no trace
>>>> of such a message being carried by Bluemchen in recent times for that
>>>> address aside from one which was successfully delivered to you on Jun
>>>> 29 at 17:14:37 UTC
>>>
>>> NOW!
>>>
>>> https://bugs.kde.org/show_bug.cgi?id=392685#c1
>>
>> Please refrain from further use of exclamation marks, as it isn't
>> helping matters.
>>
>> Also, note that you've never reported this issue in the past, so from
>> my perspective this is entirely new, regardless of how it may be known
>> from your side (and your bug report was posted less than 24 hours ago)
> 
> https://bugs.kde.org/show_bug.cgi?id=392685
> 2018-04-03 18:45:47 UTC
> 3 months are not less than 24 hours

"a bug in Bugzilla which is responsible for this issue"

as mailadmin i tell you what: bug in bugzilla or not, when you enforce
SPF/DKIM/DMARC between your own servers you are asking for trouble,
that's what http://www.postfix.org/postconf.5.html#mynetworks is for

"by postbox.kde.org (Postfix)"

Re: Upcoming change to mail infrastructure -> SPF still broken

[Reindl Harald]

Am 04.07.2018 um 13:58 schrieb Ben Cooksley:
> On Wed, Jul 4, 2018 at 10:52 PM, Reindl Harald  wrote:
>> Am 04.07.2018 um 12:38 schrieb Ben Cooksley:
>>> On Wed, Jul 4, 2018 at 10:30 AM, Reindl Harald  
>>> wrote:
>>>> did you also notice and fix the long outstanding bugzilla SPF problems
>>>> within your own infrastructure before make checks even sharper?
>>>>
>>>> https://bugs.kde.org/show_bug.cgi?id=392685
>>>>
>>>> there are at leat *three* problems:
>>>> * the notify mails have the envelope-sender of the reoprter
>>>> * postbox.kde.org don't skip SPF checks from bluemchen.kde.org
>>>> * the SPF can not match because bluemchen.kde.org is not
>>>>   in the reporters SPF
>>>> * finally you send backscatter-bounces for each and every
>>>>   mail back to the reporter that the notify to the others
>>>>   was rejected by postbox.kde.org and so reports don't get attention
>>>> 
>>>> * don't use reporters enevlope sender to begin with
>>>> * don't SPF check inbound mail within the own infrastructure
>>>> * don't backscatter to the innocent reporter
>>>> 
>>>> : host postbox.kde.org[46.4.96.248] said: 550
>>>> 5.7.23 : Recipient address rejected: Message
>>>> rejected due to: SPF fail - not authorized. Please see
>>>> http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net;ip=208.118.235.41
>>>
>>> I'd be curious to know when you observed that, as I can find no trace
>>> of such a message being carried by Bluemchen in recent times for that
>>> address aside from one which was successfully delivered to you on Jun
>>> 29 at 17:14:37 UTC
>>
>> NOW!
>>
>> https://bugs.kde.org/show_bug.cgi?id=392685#c1
> 
> Please refrain from further use of exclamation marks, as it isn't
> helping matters.
> 
> Also, note that you've never reported this issue in the past, so from
> my perspective this is entirely new, regardless of how it may be known
> from your side (and your bug report was posted less than 24 hours ago)

https://bugs.kde.org/show_bug.cgi?id=392685
2018-04-03 18:45:47 UTC
3 months are not less than 24 hours

Re: Upcoming change to mail infrastructure -> SPF still broken

[Reindl Harald]

Am 04.07.2018 um 12:38 schrieb Ben Cooksley:
> On Wed, Jul 4, 2018 at 10:30 AM, Reindl Harald  wrote:
>> did you also notice and fix the long outstanding bugzilla SPF problems
>> within your own infrastructure before make checks even sharper?
>>
>> https://bugs.kde.org/show_bug.cgi?id=392685
>>
>> there are at leat *three* problems:
>> * the notify mails have the envelope-sender of the reoprter
>> * postbox.kde.org don't skip SPF checks from bluemchen.kde.org
>> * the SPF can not match because bluemchen.kde.org is not
>>   in the reporters SPF
>> * finally you send backscatter-bounces for each and every
>>   mail back to the reporter that the notify to the others
>>   was rejected by postbox.kde.org and so reports don't get attention
>> 
>> * don't use reporters enevlope sender to begin with
>> * don't SPF check inbound mail within the own infrastructure
>> * don't backscatter to the innocent reporter
>> 
>> : host postbox.kde.org[46.4.96.248] said: 550
>> 5.7.23 : Recipient address rejected: Message
>> rejected due to: SPF fail - not authorized. Please see
>> http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net;ip=208.118.235.41
> 
> I'd be curious to know when you observed that, as I can find no trace
> of such a message being carried by Bluemchen in recent times for that
> address aside from one which was successfully delivered to you on Jun
> 29 at 17:14:37 UTC

NOW!

https://bugs.kde.org/show_bug.cgi?id=392685#c1

"such a message being carried by Bluemchen in recent times for that
address aside from one which was successfully delivered to you on Jun 29
at 17:14:37 UTC" - yeah - when somebody *else* makes a comment i get
that notify but when i write a brugreport or comment a get that damned
backscatters below

 Weitergeleitete Nachricht 
Betreff: Undelivered Mail Returned to Sender
Datum: Wed,  4 Jul 2018 06:47:52 -0400 (EDT)
Von: Mail Delivery System 
An: li...@rhsoft.net

This is the mail system at host bluemchen.kde.org.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

   The mail system

: host postbox.kde.org[2a01:4f8:140:8302::4] said: 550
5.7.23 : Recipient address rejected: Message rejected
due to: SPF fail - not authorized. Please see
http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net
ip=2001:4830:134:8::100;r= (in reply to RCPT TO command)


 Weitergeleitete Nachricht 
Betreff: Undelivered Mail Returned to Sender
Datum: Wed,  4 Jul 2018 06:47:52 -0400 (EDT)
Von: Mail Delivery System 
An: li...@rhsoft.net

This is the mail system at host bluemchen.kde.org.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

   The mail system

: host postbox.kde.org[2a01:4f8:140:8302::4] said: 550
5.7.23 : Recipient address rejected: Message rejected
due to: SPF fail - not authorized. Please see
http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net;ip=2001:4830:134:8::100;r=
(in reply to RCPT TO command)


 Weitergeleitete Nachricht 
Betreff: Undelivered Mail Returned to Sender
Datum: Wed,  4 Jul 2018 06:47:52 -0400 (EDT)
Von: Mail Delivery System 
An: li...@rhsoft.net

This is the mail system at host bluemchen.kde.org.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

   The mail system

: host postbox.kde.org[2a01:4f8:140:8302::4]
said: 550 5.7.23 : Recipient address rejected:
Message rejected due to: SPF fail - not authorized. Please see
http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net;ip=2001:4830:134:8::100;r=
(in reply to RCPT TO command)

Re: Upcoming change to mail infrastructure

[Reindl Harald]

Am 03.07.2018 um 12:29 schrieb Ben Cooksley:
> We've recently completed configuration of a new mail server which will
> be replacing the current system which handles kde.org mail. This
> system will be assuming responsibility for mailing lists as well as
> authenticated mail sending for those who require that service.

did you also notice and fix the long outstanding bugzilla SPF problems
within your own infrastructure before make checks even sharper?

https://bugs.kde.org/show_bug.cgi?id=392685

there are at leat *three* problems:
* the notify mails have the envelope-sender of the reoprter
* postbox.kde.org don't skip SPF checks from bluemchen.kde.org
* the SPF can not match because bluemchen.kde.org is not
  in the reporters SPF
* finally you send backscatter-bounces for each and every
  mail back to the reporter that the notify to the others
  was rejected by postbox.kde.org and so reports don't get attention

* don't use reporters enevlope sender to begin with
* don't SPF check inbound mail within the own infrastructure
* don't backscatter to the innocent reporter

: host postbox.kde.org[46.4.96.248] said: 550
5.7.23 : Recipient address rejected: Message
rejected due to: SPF fail - not authorized. Please see
http://www.openspf.net/Why?s=mfrom;id=li...@rhsoft.net;ip=208.118.235.41

Re: Is there a way to set digitalclock plasmoid font size?

[Reindl Harald]

Am 17.06.2018 um 19:37 schrieb Roman Gilg:
> You need to edit the height property (change) in the horizontal panel mode.
> 
> https://cgit.kde.org/plasma-workspace.git/commit/applets/digital-clock/package/contents/ui/DigitalClock.qml?id=90ea27f49c84f0dffbbf79b29eaa14c57f31a24d
> 
> gives you an idea how it should be done.
> 
> I'm against making this configurable through ui because the digital
> clock code is pretty hacky as it is right now and making the size
> configurable would make it only worse.

most fonts are simply *useless* because without size control they are
too small or too big depending of your panel size - it's *really*
annoying for many years now

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

[Reindl Harald]

Am 20.11.2017 um 18:55 schrieb Brüns, Stefan:

On Montag, 20. November 2017 18:50:34 CET Reindl Harald wrote:

Am 20.11.2017 um 18:30 schrieb Thiago Macieira:

On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote:

hopefully this means also that filenames in the future don't contain
uppercase chars


Why would we want that?


well, i don't know many projects or people which create binaries other
than lowercase chars and using only lowercase filenames would avoid the
whole topic at it's root

to be honest: i am annyoed that "lsof | grep DEL | grep /usr" brings


OUCH!

Fixed that for you:
lsof | grep -E "\sDEL\s.*\s/usr"


you missed "what do you gain from uppercase chars in filenames?"

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

[Reindl Harald]

Am 20.11.2017 um 18:30 schrieb Thiago Macieira:

On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote:

hopefully this means also that filenames in the future don't contain
uppercase chars


Why would we want that?


well, i don't know many projects or people which create binaries other 
than lowercase chars and using only lowercase filenames would avoid the 
whole topic at it's root


to be honest: i am annyoed that "lsof | grep DEL | grep /usr" brings 
always these KDE processes for a long time


what do you gain from uppercase chars in filenames?

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

[Reindl Harald]

Am 20.11.2017 um 16:50 schrieb Harald Sitter:

Guten Abend Everyone!

To aid with use of our tarballs on Windows and case-insensitive file
systems, releaseme now makes sure [1] that the tarballs it generates
are safe to use in such contexts.

As this is a major problem for pretty much every source tarball as it
prevents people from doing Windows builds and/or unpack on exfat/fat32
this is considered a fatal flaw in the tarball. To that end if you use
releaseme you may want to run tarme now so your next release doesn't
get held up by case-insensitive file conflicts.

If you have any questions please do ask.

[1] https://phabricator.kde.org/R572:0936ab0e02551fe6d3e8ad07b97cd7d7d3d26838


hopefully this means also that filenames in the future don't contain 
uppercase chars


[root@rh:~]$ lsof | grep DEL | grep /usr
konqueror  8058 harry  mem   REG9,1 
26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0
QXcbEvent  8058  8059   harry  mem   REG9,1 
26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0
QDBusConn  8058  8060   harry  mem   REG9,1 
26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0
QThread8058  8061   harry  mem   REG9,1 
26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0
konqueror 23596 harry  mem   REG9,1 
26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0

Re: Suggestion to Remove KFloppy and hold back K3b

[Reindl Harald]

Am 16.02.2017 um 16:51 schrieb Martin Gräßlin:

Am 2017-02-16 09:16, schrieb Reindl Harald:

Am 16.02.2017 um 06:28 schrieb Martin Gräßlin:

Even xlib and xcb hardly protect against a malicious X server. And we
just cannot assume any more that X is running as root


really? i fear before we see X11 running without root in the wild it's
replaced by wayland


Sorry, but this is really a bad argument. This is exactly the push-back
we get which I talked about during my presentation at QtCon. When
someone tries to make the system more secure, people are actively
pushing back with stupid and wrong arguments. We as a community make the
NSA's job easier. We should be ashamed of us!

Now to your argument. Fedora ships Wayland in the wild. So what exactly
is your point? KFloppy also works on GNOME. Should we not consider GNOME
users for the security aspect?


you got me completly wrong

i only criticized "we just cannot assume any more" because i don't see 
that on my machines running KDE  and running Fedora 24 can't be 
considered as old software when F25 is realsed just a few weeks ago

Re: Suggestion to Remove KFloppy and hold back K3b

[Reindl Harald]

at least not on non-GNOME machines

https://github.com/sddm/sddm/issues/246
Tids commented on 23 Dec 2016
I'm also still waiting for rootless X with sddm.

Am 16.02.2017 um 09:16 schrieb Reindl Harald:

Am 16.02.2017 um 06:28 schrieb Martin Gräßlin:

Even xlib and xcb hardly protect against a malicious X server. And we
just cannot assume any more that X is running as root


really? i fear before we see X11 running without root in the wild it's
replaced by wayland

http://hansdegoede.livejournal.com/14446.html
"/etc/X11/Xwrapper.config" did not exist previously

cat /etc/X11/Xwrapper.config
needs_root_rights = auto

ps aux | grep X
root  6017  3.0  0.2 302840 95864 tty1 Ss+  09:11   0:06
/usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/

cat /etc/redhat-release
Generic release 24 (Generic)

Re: Suggestion to Remove KFloppy and hold back K3b

[Reindl Harald]

Am 16.02.2017 um 06:28 schrieb Martin Gräßlin:

Even xlib and xcb hardly protect against a malicious X server. And we just 
cannot assume any more that X is running as root


really? i fear before we see X11 running without root in the wild it's 
replaced by wayland


http://hansdegoede.livejournal.com/14446.html
"/etc/X11/Xwrapper.config" did not exist previously

cat /etc/X11/Xwrapper.config
needs_root_rights = auto

ps aux | grep X
root  6017  3.0  0.2 302840 95864 tty1 Ss+  09:11   0:06 
/usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/


cat /etc/redhat-release
Generic release 24 (Generic)

Re: kde on windows

[Reindl Harald]

Am 31.07.2016 um 07:32 schrieb Doug:

Gentlemen:

I don't know what you think you've accomplished by limiting KDE on
Windows to just 4 files. Sometimes it's necessary to use Windows, and it
is (WAS!) nice to
be able to use some KDE apps: Artha, KSnapshot, Dolphin, Find
Files-Folders, Okular, Gwenview, KPatience. And Kate--the only file you
left me that I use!
And I don't want Amarok--that seems to be what you get if you're not
careful!


there are likely not enough developer ressources to make windows a first 
class class target of KDE and before developer ressources are wasted for 
windows which could help to make the Linux version more stable und 
bugfree i would not want them wasted



I have several computers, and several Windows installs, as well as PCLOS
on all of them. I use PCLOS about 95% of the time, but when I need Windows,
damn it! I need it!


virtualization exists


Please reconsider your dismal advice and let me have the apps that make
Windows bearable! (32 and 64 bit, please!)


oh, i386 needs also to be actively supported for new software in 2016 - 
seriously?



Thanx--Doug McGarrett, KDE user for over 5 years


so a very new one (KDE 1.0 AFAIR was 1998-2000)


PS: Please advise me if or when you bring back the apps!


when somebody cares enough to do the work



signature.asc
Description: OpenPGP digital signature

Re: The situation of KWallet, and what to do about it?

[Reindl Harald]

Am 11.07.2016 um 21:27 schrieb Thomas Pfeiffer:

On 07.07.2016 18:43, Elvis Angelaccio wrote:

- We make encrypted password storage optional and non-default (easiest
solution, but not exactly in line with KDE's vision)

I disagree on this point. Even if KWallet were free of usability
issues, it would still provide a false sense of security. The user
thinks that his/her passwords are safe, while in fact they are not.
If we don't have enough manpower to develop and mantain a proper
keychain in Plasma, we should tell our users. This way they can make
sure that, for example, the unsafely stored Wi-Fi passphrase is not
used for other accounts. This is already closer to our vision than the
current situation.

My vote is: we either do it right, or we give up. If someone steps up
to fix this problem, great. Otherwise we should start to slowly port
away from KWallet.


Good point!
I still hope we'd find a secure solution, but no central storage may
indeed be better than an insecure one


no it's not

the alternative would be a passwords.txt on the desktop of many users 
with no autoclose or insecure passwords at all to remember them


hardly an improvement



signature.asc
Description: OpenPGP digital signature

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 04.08.2015 um 23:42 schrieb Dāvis Mosāns:

Learn to read.

If you *ship* GStreamer ...

It is completely legal to *use* the binary Fluendo plugin with a GPLed player.


Nope, it's not legal (I'm not lawyer) but even if you don't distribute
you still violate
GPL as you can't mix GPL with GPL incompatible license. Only difference is that
no one will know that you violate GPL, same as pirating...


completly nonsense

you can do whatever you want with GPL code at your own and you do not 
need to make the source of your changes public as long as you don't 
distribute the binary





signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 04.08.2015 um 17:23 schrieb Martin Sandsmark:

On Tue, Aug 04, 2015 at 05:06:11PM +0200, Thomas Lübking wrote:

https://en.wikipedia.org/wiki/Fluendo
You simply don't need the bad and ugly codecs (despite they're better
than the fluendo stuff and still gstreamer is inferior to vlc or mplayer
when it comes to performance and latency) for a
not-so-free-but-out-of-the-box experience.


Sorry for my ignorance, but I'm not exactly sure I follow here. What does
Fluendo do that makes it okay for Fedora to ship gstreamer?


it takes away the resposibility
https://fedoraproject.org/wiki/Installing_the_Fluendo_MP3_plugin



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 04.08.2015 um 17:34 schrieb Martin Sandsmark:

On Tue, Aug 04, 2015 at 05:31:18PM +0200, Thomas Lübking wrote:

Fluendo puchased the required licenses and provides (afaik binarly-only)
gstreamer plugins for those popular-but-patented codecs. And they allow
them to be shipped (for free)


Fedora ships commercial, closed source packages?


WHY don't you just read 
https://fedoraproject.org/wiki/Installing_the_Fluendo_MP3_plugin - and 
no - you don't need to click on any link there to understand the text on 
the page




signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 04.08.2015 um 17:41 schrieb Martin Sandsmark:

On Tue, Aug 04, 2015 at 05:36:34PM +0200, Reindl Harald wrote:

WHY don't you just read
https://fedoraproject.org/wiki/Installing_the_Fluendo_MP3_plugin - and no -
you don't need to click on any link there to understand the text on the page


I read it, and since the free decoder apparently isn't available anymore I
don't see the relevance of the page. No matter how many times you link it


what about learning to quote?
i answered your Fedora ships commercial, closed source packages?



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 04.08.2015 um 17:28 schrieb Martin Sandsmark:

On Tue, Aug 04, 2015 at 05:26:40PM +0200, Reindl Harald wrote:

it takes away the resposibility


It takes away which responsibility?


the responsibility for a codec not included and hosted by the distribution?


https://fedoraproject.org/wiki/Installing_the_Fluendo_MP3_plugin


The links there are dead


how does that matter?

you asked What does Fluendo do that makes it okay for Fedora to ship 
gstreamer? and just could read the page






signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Help wanted to evolve KDEs music players

[Reindl Harald]

Am 01.08.2015 um 22:36 schrieb Thomas Lübking:

On Samstag, 1. August 2015 22:08:22 CEST, Stefan Derkits wrote:


And I'm not really sure how often a user would rate a music file in
Dolphin. On my system I don't even find the possibility to rate a file,
only to display the rating :)


Out of curiosity and semi-OT:
what's the point in rating *local* music anyway?
So I don't forget that I like Beethovens 4th better than his 2nd??


to decide if you want to hear a completly undefined playlist and hence 
songs you don#t hear all the time or just your personal favorites?




signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: Network Applet

[Reindl Harald]

Am 20.10.2013 11:59, schrieb Jan Grulich:
 * allow more than one connection to be expanded at a time
 I don't think is necessary to allow more than one connection to be expanded, 
 because mostly you are connected only
 via one connection (or only one is default route)

says who?

yes, the machine below is a Fedora KDE-Workstation and even with a simple
setup when VPN is a topic you have no longer one default route for all

my understanding of KDE is for powerusers and not for the
simple that is my network cable alone
__

[root@srv-rhsoft:~]$ route -n | wc -l
12

br0= WLAN/LAN Brdige
br1= Gust-WLAN/Virtual Device
eth0   = LAN
eth1   = WAN
eth2   = Virtual Devbice for Gust-WLAN-Bridge
tap0   = OpenVPN
vmnet8 = VMware NAT
wlan0  = Personal WLAN
waln1  = Guest WLAN

br0: flags=4675UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST  mtu 1500
inet 192.168.7.2  netmask 255.255.255.0  broadcast 192.168.7.255
ether 24:be:05:1a:c0:27  txqueuelen 0  (Ethernet)
RX packets 16455  bytes 3459475 (3.2 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13284  bytes 6685829 (6.3 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br1: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
inet 192.168.10.1  netmask 255.255.255.0  broadcast 192.168.10.255
ether 28:10:7b:ca:be:52  txqueuelen 0  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419UP,BROADCAST,RUNNING,PROMISC,MULTICAST  mtu 1500
ether 24:be:05:1a:c0:27  txqueuelen 1000  (Ethernet)
RX packets 13183  bytes 3289640 (3.1 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 10200  bytes 3934711 (3.7 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 20  memory 0xf7e0-f7e2

eth1: flags=67UP,BROADCAST,RUNNING  mtu 1500
inet **.**.**.**  netmask 255.255.255.0  broadcast 255.255.255.255
ether 00:50:8d:b5:cc:de  txqueuelen 1000  (Ethernet)
RX packets 9056524  bytes 10416431487 (9.7 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 6900996  bytes 1563347260 (1.4 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 16  memory 0xf7cc-f7ce

eth2: flags=4355UP,BROADCAST,PROMISC,MULTICAST  mtu 1500
ether da:a5:3f:9c:d0:19  txqueuelen 500  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1444
inet 192.168.8.241  netmask 255.255.255.0  broadcast 192.168.8.255
ether 5a:27:d8:c7:7e:cc  txqueuelen 500  (Ethernet)
RX packets 897500  bytes 376796062 (359.3 MiB)
RX errors 0  dropped 16308  overruns 0  frame 0
TX packets 983016  bytes 491210698 (468.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmnet8: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
inet 192.168.196.1  netmask 255.255.255.0  broadcast 192.168.196.255
ether 00:50:56:c0:00:08  txqueuelen 1000  (Ethernet)
RX packets 164721  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 565701  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
ether 28:10:7b:ca:be:51  txqueuelen 1000  (Ethernet)
RX packets 3269  bytes 452877 (442.2 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 8406  bytes 3612636 (3.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
ether 28:10:7b:ca:be:52  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: [Nepomuk] Nepomuk - Moving away from Strigi

[Reindl Harald]

Am 08.10.2012 22:53, schrieb Martin Sandsmark:
 I am arguing against the entire reason for having this thread. Vishesh 
 shouldn't have to go around worrying about this crap just because RedHat has 
 bad lawyers and has double standards when it comes to the software they are 
 shipping.

not so easy in the US

 My suggestion would be that we just take a stand and force RedHat to re-
 evaluate their stance on ffmpeg (or software that is covered by software 
 patents in general, like the kernel itself), so we don't have to deal with 
 this bullshit in the future.

besides the redhat / patent / law discussion:

if the plugin-system is flexible enough that you can install
any however linked plugin later without introduce dependecies
for any core-component which sould be optional - all perfect

in this case nothing is touching the lawyers and the enduser
loving a as much as tiny sezup does not get more and more
packages as cross-dependecnies

IMHO this is the right way to go in any software-development
and at the begin it was NOT clear if the core would introduce
ffmpeg and wahtever else dependencies for whatever distribution



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: [PATCH] Automatically reload files modified on disk.

[Reindl Harald]

Am 27.10.2011 20:18, schrieb Søren Holm@home:
 Torsdag den 27. oktober 2011 16:13:44 Reindl Harald skrev:
 this does perfectly work since many years if you are using fuse-sshfs /
 curlftpfs what is always the better solution since the kio-parts are
 randomly broken and not useable if you need to rely on them in any way
 
 Harald, why do you keep insist that auto-reload should not be implemented in 
 some form?
 
 I am perfectly aware that the patch I posted has a bit rough. But it worked, 
 and I was actually convinved that everyone would agree with me that auto-
 reload is a feature that kate must have.

you missunderstood me

nothing against tis feature, but please not as default because this would
have the potential to destroy work of people who do not expect or want this



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: [PATCH] Automatically reload files modified on disk.

[Reindl Harald]

Am 21.10.2011 13:10, schrieb Esben Mose Hansen:
 Kate is pretty terrible, popping up a dialog asking me to reload even though 
 there is no unsaved 
 data. I hate dialogs popping up when I am writing something, especially for 
 trivial issues.

but there was a change on the file-system and you NEED to know this because it
is pretty useless to edit a file what is changed on disk and overwrite changes
of other people

kate is doing nearly all perfect

the only missing option is do not notify me about future changes of this file

so you cold open logfiles without permanently popups
AND you are noticed if somebody changed a file you have opened before

what never must happen is to reload automatically, there are really no
usecases to do this without any warning, really no



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: [PATCH] Automatically reload files modified on disk.

[Reindl Harald]

Am 17.10.2011 08:30, schrieb Søren holm:
 Mandag den 17. oktober 2011 01:17:54 Reindl Harald skrev:

 please do NOT reload files automatically

 the right way is to DETECT a change and open a dialog ONCE
 to reload from disk per session, kate do it the right way
 currentyl with only one weakness: if you say ignore and
 another process is writing permanently to a file (like a
 logfile) kate should only once came with the promt instead
 every moment again
 
 I think it depends on the work situation. Having multiple files opened. And 
 all 
 of them suddenly changed, it is anoying to have to clock reload.

you should take a closer look at kate

what i mean is that i can decide in the prompt that i
want not noticed about changes in this session

 Working with source-files in git and checking out a different branch many 
 files 
 change. It is actually this particullar schenario automatic reload is for I 
 think.
  
 reload automatically is absolutly unacceptable because
 there are many reasons files on disk could be changed
 and if i say NO do not reload because i am working on
 this file currently it has a good reason
 
 Ok - than there should be a checkbox to explicitly enable automatic reload

again: please take a close look at kate!

i do not know for which program you search a solution but
kate has one and should be reference how to deal with cganges




signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: [PATCH] Automatically reload files modified on disk.

[Reindl Harald]

Am 17.10.2011 00:45, schrieb Thomas Lübking:
 Am Sun, 16 Oct 2011 23:42:32 +0200
 schrieb Søren holm s...@sgh.dk:
 
 Hi

 I know this patch should problably include some sort of checkbox for 
 specifying
 behavior, but on the other hand QtCreator and other editors reload
 files automatically by default. What do you say?

please do NOT reload files automatically

the right way is to DETECT a change and open a dialog ONCE
to reload from disk per session, kate do it the right way
currentyl with only one weakness: if you say ignore and
another process is writing permanently to a file (like a
logfile) kate should only once came with the promt instead
every moment again

reload automatically is absolutly unacceptable because
there are many reasons files on disk could be changed
and if i say NO do not reload because i am working on
this file currently it has a good reason



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

why are bugs ignored over months?

[Reindl Harald]

https://bugs.kde.org/show_bug.cgi?id=270414

why in the world does nobody care about bugs like
basic-operations (and rename a file is really one
since many years) for half a year?

does nobody upstream use the folder-view?

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

Am 21.09.2011 12:17, schrieb Brad Hards:
 On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote:
 https://bugs.kde.org/show_bug.cgi?id=270414

 why in the world does nobody care about bugs like
 basic-operations (and rename a file is really one
 since many years) for half a year?
 I see lots of comments, so many people care. However there are a lot of 
 negative comments, so working on such a bug is pretty disheartening for a 
 developer. 

 When I read stuff that is nasty, mean or abusive, I often find something else 
 to 
 do. Remember that this is a hobby for almost all developers.

 Another way to look at this is why haven't you fixed it in the last six 
 months. If you don't know how, why haven't you learned? 

because i am no kde-developer?
because i am not introduced the bug?
because i have not the knowledge and time to learn fix kde-bugs?
because there are users out there which are not developers?

because i did first not thing that even a bugreport is needed for
such a bug jumping in everybodys face multiple times each day?



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

Am 21.09.2011 13:47, schrieb Boudewijn Rempt:
 On Wednesday 21 September 2011 Sep, Reindl Harald wrote:

 what exactly are you missing in the difference between developers / users

 my user-support is writing bug-reports, this is what i can do
 and this bugreport is the best sample that nobody is interested in the
 help of users - so the developers have two options: test their code
 or reply to bugreports

 who do you think you are tell everybody he has to shut up if the
 if he is no kde-developer and can not fix bugs on his own?
 Well, Brad is one of the kde core developers... He's got a right to tell 
 people they need to start considering helping out.

well, since he is not using @kde.org address how sould i know if he is
a core developer or one of the way too much peopole crying it's free
software, use it as it is or stop using it the whole day?


 For this bug, it seems that the author of the code has disappeared in October 
 2010, before the report was opened. At least, I cannot find any commits by 
 him to the folderview code anymore. Which sort of explains why nothing 
 happened

there is someshting terrible broken if bugs from a 4.6 major release
are not reviewed before 4.7/4.7.1

 An organisation like KDE cannot hire developers if people develop other 
 interests and stop working on their code. It might even take quite a bit of 
 time before anyone notices someone isn't around anymore. And then there's no 
 guarantee anyone will pick up on the slack. What KDE needs is a constant 
 stream of new volunteers who are prepared to take over existing code.

i know but try to understand users who was affected hardly be the 4.0
release because upstream communicated WAY TOO LATE that 4.0 is not
for endusers and the time where this was communicated where too late
for fedora as example because they changed the whole packaging for
4.0 since in the whole software-world 4.0 means final version
and not developers only

so after that and living for years with hughe troubles especially
on systems with nvidia-graphics it is frustrating seeing such bugs
introduced and feeling nobody cares, the same for the whole
sftp-kio rewrite last year which was a) not finished/buggy as hell and
b) pushed to a stable 4.x-release to spit in the users face instead
testing/finishing the replacement BEFORE push it to the users

 Personally, and speaking as a KDE developer, I never have noticed this bug 
 myself because I don't use a folderview on my desktop. Had I used folderview, 
 I might still not have noticed because I might not have used it for renaming 
 files. Had I used folderview and I had I tried to rename files, I still might 
 not have noticed the bug because I might have used the mouse to leave the 
 text entry field.
how will you use the mouse for that?

since the last invasive change there are no popups for file-rename
this happens currently inline and you have to press enter or on some
special places directly by the file to rename, if you click somewhere
the folderview or on the desktop you will not leave this dialog

this is the next bug in the folder-view:
* if konqueror/dplhin settings says rename in popups respect it
* there is no question about DELETE a file


 Getting nasty and impatient helps nobody, is not constructive, is not polite, 
 doesn't teach anyone a lesson or makes anyone eager to please you. It's 
 counter-productive.

i agree - but what should you do as user if a bug hits you multiple each hour
since half a year and their is not other feedback as me too?



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

Am 21.09.2011 14:14, schrieb todd rme:
 On Wed, Sep 21, 2011 at 2:10 PM, Reindl Harald h.rei...@thelounge.net wrote:
 i agree - but what should you do as user if a bug hits you multiple each hour
 since half a year and their is not other feedback as me too?
 
 Do what everyone else does and go through the proper channels.

what are the proper channels?
i thought bugtracker is

 Everyone has their own pet bugs, but you don't see many emails on the
 mailing lists like this. Why do you think that is?

i can not say much about this because i subscribed to the devel-list
today only because bugzilla does not interest upstream and update to
4.7.1 today with no chance made me tired







signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

Am 21.09.2011 15:08, schrieb Lydia Pintscher:
 The bug is fixed. As Aaron said this thread will end here.

thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43

this was the only result i have hoped with my initial mail
instead all the non helpfull fix it by yourself-rants



signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

Am 21.09.2011 15:39, schrieb Aaron J. Seigo:
 On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote:
 Am 21.09.2011 15:08, schrieb Lydia Pintscher:
 The bug is fixed. As Aaron said this thread will end here.
 thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43

 this was the only result i have hoped with my initial mail
 instead all the non helpfull fix it by yourself-rants
 i will revert the fix in the 4.7 branch tomorrow unless you do the following:

 a) apologize to everyone on this list for wasting their time and diminishing 
 our community with your behaviour without any bullshit about how the results 
 justified the means. i made the fix in spite of, not because of, you and your 
 behaviour. despite me doing something nice, you are still squarely in the 
 wrong.

well, i apologize for some bad words from me
i apologize for the not friendly-enough inital mail

but i do NOT apologize for bringing a long existing bug
to the mailing-list in the hope it will get fixed


 see, you're not the only one who can play stupid games!

if you think i am playing games you did not understand my intention
NOBODY here is playing games, there is software, there are bugs,
they should be fixed and this has nothing to do with playing games

my intention is only reporting bugs if they are there
not more, not less

my intention is to prevent new normal users giving up frustrated
because of usability-problems on th emain-desktop

if this is bad, yes then my intentions are bad




signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

Re: why are bugs ignored over months?

[Reindl Harald]

 game when it comes to bugs (x+1 users on x+1 distros) that stay 
 unfixed for weeks and months? Especially if it is a regression.

 Sven

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe 

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm




signature.asc
Description: OpenPGP digital signature

 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe