https://bugs.kde.org/show_bug.cgi?id=413590
--- Comment #6 from Jiri Tyr ---
I have provided more information above. Please change the status of the ticket
now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438717
Bug ID: 438717
Summary: Crash console after session close
Product: frameworks-kinit
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=438717
--- Comment #1 from Jiri Rohlicek ---
Hi,
If I have more sessions on tabs in one konsole window, closing those extra
sessions does not raise konsole crash.
Just only closing the last session in konsole window.
Jiri Rohlicek
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #2 from Jiri Slaby ---
Created attachment 139531
--> https://bugs.kde.org/attachment.cgi?id=139531=edit
~/.local/share/sddm/wayland-session.log
(In reply to Zamundaaa from comment #1)
> Can you reproduce it again and then
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #4 from Jiri Slaby ---
(In reply to Zamundaaa from comment #3)
> Hmm, there's a lot of (possibly unrelated) errors in that log before and
> after the crash which suggest there's either another bug in KWin or a bug in
> the graphi
https://bugs.kde.org/show_bug.cgi?id=436900
--- Comment #4 from Jiri Palecek ---
(In reply to Grzesiek11 from comment #3)
> Here is the Valgrind report:
> https://grzesiek11.stary.pc.pl/files/texts/436900_valgrind.log (~80 MiB, be
> warned).
Thank you. 80Mb, that's nothing :). Even em
https://bugs.kde.org/show_bug.cgi?id=436900
Jiri Palecek changed:
What|Removed |Added
CC||jpale...@web.de
--- Comment #1 from Jiri
https://bugs.kde.org/show_bug.cgi?id=417080
Jiri Palecek changed:
What|Removed |Added
CC||jpale...@web.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438789
Bug ID: 438789
Summary: kwin_wayland crashed in KWin::DrmGpu::updateOutputs
while un/re-plugging monitor
Product: kwin
Version: 5.22.0
Platform: openSUSE RPMs
OS:
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #9 from Jiri Slaby ---
(In reply to Zamundaaa from comment #8)
> It seems like the logging rules aren't applied, did you add them?
Ah, I am stupid. I am not using sddm for a couple of weeks as it doesn't start
any session, so the
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #10 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #9)
> BTW I also applied the patch from bug 439208#c3, but kwin still crashes with
> the very same backtrace.
Just checked with the core file:
> (gdb) l Drm
https://bugs.kde.org/show_bug.cgi?id=439325
Jiri Slaby changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=439325
Bug ID: 439325
Summary: crash while moving weston window
Product: plasmashell
Version: 5.22.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=439325
Jiri Slaby changed:
What|Removed |Added
Platform|Other |openSUSE RPMs
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=435751
--- Comment #6 from Jiri Slaby ---
*** Bug 439325 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439325
Jiri Slaby changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #14 from Jiri Slaby ---
(In reply to Zamundaaa from comment #13)
> Thanks for all the information, was really helpful in pinning it down.
Thanks, patched, waiting for no crashes :).
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=439270
Jiri Slaby changed:
What|Removed |Added
CC||jirisl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435751
Jiri Slaby changed:
What|Removed |Added
CC||txemafi...@gmail.com
--- Comment #5 from Jiri
https://bugs.kde.org/show_bug.cgi?id=439270
Jiri Slaby changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=435751
Jiri Slaby changed:
What|Removed |Added
CC||jirisl...@gmail.com
--- Comment #4 from Jiri
https://bugs.kde.org/show_bug.cgi?id=438789
Jiri Slaby changed:
What|Removed |Added
Attachment #139952|text/x-log |text/plain
mime type
https://bugs.kde.org/show_bug.cgi?id=438789
Jiri Slaby changed:
What|Removed |Added
Attachment #139531|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=228527
--- Comment #19 from Jiri Kosina ---
(In reply to Justin Zobel from comment #18)
> Thank you for the bug report.
>
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persis
https://bugs.kde.org/show_bug.cgi?id=441213
Bug ID: 441213
Summary: 428394
Product: plasmashell
Version: 5.22.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
https://bugs.kde.org/show_bug.cgi?id=441213
Jiri Slaby changed:
What|Removed |Added
Summary|428394 |[wayland] plasmashell leaks
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #3 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #2)
> (gdb) p/x $rax
> $5 = 0x31
Seems to be 0x31 every time. So no corruption, or a deterministic one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #1 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #0)
> It always used to work. Now I switched from X11 to wayland and kded5 crashes
> in XQueryExtension:
(No matter if I press it while in wayland or X11 window.)
-
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #2 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #0)
> > #3 0x7f550492bb3e in XQueryExtension
> > (dpy=dpy@entry=0x5628d28aa030, name=name@entry=0x7f54fc12e019
> > "XInputExtension", maj
https://bugs.kde.org/show_bug.cgi?id=440778
Bug ID: 440778
Summary: Crash when invoking send-keyboard-input shortcut
Product: frameworks-kded
Version: 5.84.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=440778
Jiri Slaby changed:
What|Removed |Added
Summary|Crash when invoking |Crash when invoking
|send
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #5 from Jiri Slaby ---
(In reply to Nate Graham from comment #4)
> Feel free to submit a merge request to fix it!
If I only knew what the root cause is -- I only described the symptoms... The
Display is callocated (so zeroed) and lock_
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #8 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #7)
> (In reply to David Redondo from comment #6)
> > We probably should not be in this X code path at all on Wayland?
>
> That's what I think too -- if I am in a
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #7 from Jiri Slaby ---
(In reply to David Redondo from comment #6)
> We probably should not be in this X code path at all on Wayland?
That's what I think too -- if I am in a wayland window. Not sure what should
happen when in Xwayl
https://bugs.kde.org/show_bug.cgi?id=350140
--- Comment #57 from Jiri Palecek ---
This should be fixed by https://phabricator.kde.org/D29616
Can you test it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447872
Bug ID: 447872
Summary: konsole starts with Root Shell as default
Product: konsole
Version: 21.12.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=447872
Jiri Slaby changed:
What|Removed |Added
CC||a.samir...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #11 from Jiri Slaby ---
(In reply to Ahmad Samir from comment #10)
> (In reply to Axel Braun from comment #9)
> > Same behaviour if you open a shell from dolphin with F4...
>
> Both use-cases use the same code, so it
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #1 from Jiri Slaby ---
This opens the profile just fine.
$ konsole --profile Shell
It's just [Desktop Entry].DefaultProfile cannot be loaded somehow and Root
Shell is used instead (and also set as the default).
The same profile is mis
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #2 from Jiri Slaby ---
Bisected to:
commit 50041fd02ee42cf2cd484f91869896419e09ef83 (HEAD)
Author: Ahmad Samir
Date: Wed Aug 11 13:38:12 2021 +0200
Simplify ProfileManager code
Now all the profiles are loaded in the constructor
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #5 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #4)
> (In reply to Ahmad Samir from comment #3)
> > I think I see what's causing this, I'll create an MR shortly.
>
> It's likely the endsWith...
And
Root S
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #4 from Jiri Slaby ---
(In reply to Ahmad Samir from comment #3)
> I think I see what's causing this, I'll create an MR shortly.
It's likely the endsWith...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #6 from Jiri Slaby ---
I believe you'll come up with sth like:
--- a/src/profile/ProfileManager.cpp
+++ b/src/profile/ProfileManager.cpp
@@ -211,7 +211,7 @@ void ProfileManager::loadAllProfiles(const QString
)
const QStringList
https://bugs.kde.org/show_bug.cgi?id=378152
Jiri Slaby changed:
What|Removed |Added
Version|19.04.2 |21.08.2
CC
https://bugs.kde.org/show_bug.cgi?id=378152
--- Comment #4 from Jiri Slaby ---
It's because QFont::fromString(const QString ) doesn't OR the
QFont::resolve_mask with QFont::StyleNameResolved the same as
QFont::setStyleName(const QString ) does. So this is an upstream (Qt)
bug. Reproducer
https://bugs.kde.org/show_bug.cgi?id=378152
Jiri Slaby changed:
What|Removed |Added
URL||https://bugreports.qt.io/br
https://bugs.kde.org/show_bug.cgi?id=433993
Jiri Slaby changed:
What|Removed |Added
CC||jirisl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=433993
Jiri Slaby changed:
What|Removed |Added
CC||alf...@gmail.com
--- Comment #17 from Jiri Slaby
https://bugs.kde.org/show_bug.cgi?id=444861
Jiri Slaby changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=446101
Bug ID: 446101
Summary: Crash in KWin::DrmPipeline::setCursor
Product: kwin
Version: 5.23.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Blocks||446101
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=445894
Bug ID: 445894
Summary: Crash in KWin::DrmOutput::updateCursor -> malloc():
unsorted double linked list corrupted
Product: kwin
Version: 5.23.2
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=378152
--- Comment #12 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #7)
> Confirmed. The qt fix doesn't help (obviously; but is a bug too). Commenting
> out the line (patch attached) indeed helps.
I actually need both changes in both
https://bugs.kde.org/show_bug.cgi?id=378152
--- Comment #7 from Jiri Slaby ---
Created attachment 143440
--> https://bugs.kde.org/attachment.cgi?id=143440=edit
workaround patch
(In reply to Ahmad Samir from comment #6)
> I am not sure it's the same issue as that upstream bug; th
https://bugs.kde.org/show_bug.cgi?id=378152
--- Comment #10 from Jiri Slaby ---
(In reply to Ahmad Samir from comment #8)
> Commenting out that line breaks the "draw intense colours in bold fonts"
> option, very tricky stuff :)
Sure, that's why the patch is marked as a worka
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #3 from Jiri Slaby ---
Created attachment 144500
--> https://bugs.kde.org/attachment.cgi?id=144500=edit
drm_info without TB
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #4 from Jiri Slaby ---
Today I encountered a little different crash: a bit different stack trace. But
still a heap corruption and still KWin::DrmGpu::updateOutputs is common.
> #5 0x7f9fea02fe8c in malloc_printerr (str=str@en
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #2 from Jiri Slaby ---
Created attachment 144499
--> https://bugs.kde.org/attachment.cgi?id=144499=edit
drm_info with TB
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #6 from Jiri Slaby ---
(In reply to Zamundaaa from comment #5)
> If you plug in and out without suspend, does that ever cause problems?
Yes, sometimes -- still under KWin::DrmBackend::updateCursor() and further.
Note that e
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Version|5.23.2 |5.23.3
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=428394
--- Comment #13 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #12)
> (In reply to David Edmundson from comment #11)
> > *** Bug 441213 has been marked as a duplicate of this bug. ***
>
> FTR I'd say it's gone now. I didn
https://bugs.kde.org/show_bug.cgi?id=428394
--- Comment #12 from Jiri Slaby ---
(In reply to David Edmundson from comment #11)
> *** Bug 441213 has been marked as a duplicate of this bug. ***
FTR I'd say it's gone now. I didn't have to kill plasma for at least a month (I
don't even remem
https://bugs.kde.org/show_bug.cgi?id=452254
Bug ID: 452254
Summary: Window switch "their" monitor after unplug+replug
(maybe regression of 5.24)
Product: kwin
Version: 5.24.0
Platform: openSUSE RPMs
OS:
https://bugs.kde.org/show_bug.cgi?id=452247
--- Comment #4 from Jiri Slaby ---
(In reply to Nate Graham from comment #2)
> If it affects non-KDE apps and Window Rules don't fix it, it's not an issue
> with the X11-specific code to position windows, as that only affects certain
> KD
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #16 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #15)
> Can you confirm that this issue is gone in 5.24 beta?
Waiting for beta to reach factory (a couple of days, I assume):
https://build.opensuse.org/request/show/947
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #17 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #14)
> Anyway, if I do this in 5.23.5, it seems to fix the problem.
Not completely, kwin still crashes, but elsewhere. Still memory corruption.
Still waiting for 5.24 b
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #19 from Jiri Slaby ---
*** Bug 446101 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446101
Jiri Slaby changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=446101
Bug 446101 depends on bug 445894, which changed state.
Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc():
unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
What|Removed
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Blocks||449773
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=446101
Jiri Slaby changed:
What|Removed |Added
Depends on||449773
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=449773
Bug ID: 449773
Summary: Conditional jump or move depends on uninitialised
value in KWin::DrmPipeline::checkTestBuffer
Product: kwin
Version: 5.24.0
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449773
Bug 449773 depends on bug 445894, which changed state.
Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc():
unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
What|Removed
https://bugs.kde.org/show_bug.cgi?id=446101
Bug 446101 depends on bug 445894, which changed state.
Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc():
unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
What|Removed
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #21 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #20)
> Not sure what valgrind doesn't like, I don't see issues with that code right
> off the bat.
I reorganized the conditions to one per line:
> 303 c
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #22 from Jiri Slaby ---
Finding out the culprit in the == operand:
> 305 const auto = [this, backend, ](const
> QSharedPointer ){
> 306 const auto = supportedModifiers(buf->format());
> 307
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #24 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #23)
> > So it's the pointer returned by backend->drmFormat(m_output);
>
> drmFormat() returns an integer. can you add a default member initializer
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Version|5.23.3 |5.23.5
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #8 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #7)
> Most likely, kwin overwrites the data it shouldn't. It would be great if you
> could run kwin with valgrind, but it can make the computer very unusable.
You'
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #14 from Jiri Slaby ---
Created attachment 145902
--> https://bugs.kde.org/attachment.cgi?id=145902=edit
fix
This DrmGpu::findWorkingCombination code is completely gone in master since:
commit e2a0863843f92ab1f2f8d0c785a86570fc04d
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #12 from Jiri Slaby ---
Created attachment 145901
--> https://bugs.kde.org/attachment.cgi?id=145901=edit
valgrind output
Looks promising (complete log attached):
> ==3522== Invalid read of size 1
> ==3522==at 0xCEAD79C
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #10 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #9)
> You can temporarily remove the capabilities by using setcap -r. When you're
> done, sudo setcap CAP_SYS_NICE=+ep /path/to/kwin_wayland
As I wrote, that quits
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #13 from Jiri Slaby ---
Shouldn't the delete in DrmGpu::findWorkingCombination be preceded by
allPipelines.removeLast() (or something like that)?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476082
--- Comment #1 from Jiri Prchal ---
At server I see that it uses wrong keys:
2023-10-27T11:28:17.596774+02:00 server sshd[3101997]: Connection from
172.25.162.3 port 58006 on 172.25.162.1 port 10022 rdomain ""
2023-10-27T11:28:17.758707+02
https://bugs.kde.org/show_bug.cgi?id=476037
Jiri Slaby changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=476081
Bug ID: 476081
Summary: ip wildcard in known_hosts not functional
Classification: Frameworks and Libraries
Product: kio-extras
Version: 21.12.3
Platform: Ubuntu
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=476082
Bug ID: 476082
Summary: sftp doesn't connect
Classification: Frameworks and Libraries
Product: kio-extras
Version: 21.12.3
Platform: Ubuntu
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=476036
--- Comment #1 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #0)
> STEPS TO REPRODUCE
> 1. switch from one desktop to another
> 2. maybe vertical maximization and restore to original size is needed
> before, I don't know for su
https://bugs.kde.org/show_bug.cgi?id=476036
Bug ID: 476036
Summary: content of the terminal is misrendered/missing a part
Classification: Applications
Product: konsole
Version: 23.08.1
Platform: openSUSE
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=476037
Bug ID: 476037
Summary: external monitor disabled temporarily upon DPMS on
Classification: Plasma
Product: plasmashell
Version: 5.27.8
Platform: openSUSE
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=453090
--- Comment #4 from Jiri Palecek ---
A similar problem with nautilus was already discussed here:
https://bugzilla.samba.org/show_bug.cgi?id=14983
They resolved it by handling/ignoring EINVAL returns:
https://gitlab.gnome.org/GNOME/gvfs/-/issues/611
https://bugs.kde.org/show_bug.cgi?id=453090
--- Comment #2 from Jiri Palecek ---
(In reply to Harald Sitter from comment #1)
> I take it your credentials are correct? If so please file this upstream at
> bugzilla.samba.org you are getting EINVAL which seems an entirely
> unreasonab
https://bugs.kde.org/show_bug.cgi?id=453090
Bug ID: 453090
Summary: Can't connect to a Windows samba share with samba-libs
4.16
Product: kio-extras
Version: 21.12.3
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=452758
Jiri Slaby changed:
What|Removed |Added
CC||jirisl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=363139
Jiri Slaby changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=463462
Jiri Slaby changed:
What|Removed |Added
CC||jirisl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=310677
Jiri Slaby changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=463727
Jiri Palecek changed:
What|Removed |Added
CC||jpale...@web.de
--- Comment #1 from Jiri
101 - 200 of 252 matches
Mail list logo