https://bugs.kde.org/show_bug.cgi?id=260007
Thiago Macieira changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=264274
Thiago Macieira changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=290317
--- Comment #7 from Thiago Macieira ---
Not reopening, there is a similar bug but it has different behaviour.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=95733
Thiago Macieira changed:
What|Removed |Added
CC||thi...@kde.org
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=323273
Thiago Macieira changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=364779
--- Comment #7 from Thiago Macieira ---
Ok, I could reproduce this locally and I've got an strace:
This is forkfd creating the child process:
115218 clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fd10015b
https://bugs.kde.org/show_bug.cgi?id=364779
--- Comment #6 from Thiago Macieira ---
I see the forkfd_wait now. Since I can't see anything obviously wrong with the
QProcess code either, I'm going to guess this is caused by the process failing
to start too quickly.
But there's a unit for QProcess
https://bugs.kde.org/show_bug.cgi?id=364779
--- Comment #5 from Thiago Macieira ---
It's not forkfd. That has nothing to do with directories. The backtrace doesn't
even show it.
Can anyone show me what the child process is doing? A backtrace would help, but
an strace even more.
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=357611
--- Comment #9 from Thiago Macieira ---
There are still a lot of messages, but nowhere as many as before. I don't think
I should call this a flood anymore.
Messages are like:
[ 312.010] kded5(1693 1693): kscreen: starting external backend launcher f
https://bugs.kde.org/show_bug.cgi?id=354437
--- Comment #12 from Thiago Macieira ---
Actually, I just noticed that I misdiagnosed the problem.
The problem is that kscreen5 keeps a single configuration file for both my 45"
Samsung TV and my 23" Samsung monitor. The kded4 module was able to tell t
https://bugs.kde.org/show_bug.cgi?id=357611
--- Comment #7 from Thiago Macieira ---
5.6.2 here and it's still producing debugging output.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357392
--- Comment #3 from Thiago Macieira ---
kscreen 5.6.2, but same with older versions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=354437
--- Comment #11 from Thiago Macieira ---
Repeating: kscreen remembers the configuration but fails to apply it
[338791.653] kded5(1707 1707): kscreen: starting external backend launcher for
""
[338791.721] kded5(1707 1707): kscreen.kded:resetDisplay
https://bugs.kde.org/show_bug.cgi?id=357611
Thiago Macieira changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=357392
Thiago Macieira changed:
What|Removed |Added
CC||thi...@kde.org
--- Comment #1 from Thiago Mac
https://bugs.kde.org/show_bug.cgi?id=360408
--- Comment #3 from Thiago Macieira ---
Might be https://bugreports.qt.io/browse/QTBUG-51676
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356950
Thiago Macieira changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=356950
Thiago Macieira changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
CC|
https://bugs.kde.org/show_bug.cgi?id=354437
--- Comment #6 from Thiago Macieira ---
(In reply to Maciej Mrozowski from comment #4)
> Remember multi-monitor config is minor problem here, detecting screens
> whenever they change is more pressing. kscreen somewhat cannot catch up with
> output devic
https://bugs.kde.org/show_bug.cgi?id=354437
--- Comment #3 from Thiago Macieira ---
(In reply to Martin Kostolný from comment #2)
> I think this is fixed for Plasma 5.5.1, KF 5.17.
> @Thiago Macieira: can you confirm that?
Will answer when 5.5.1 drops in OpenSUSE Tumbleweed (currently 5.4.3).
-
20 matches
Mail list logo