https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #20 from Claudius Ellsel ---
Playing around a bit, I noticed that when moving windows like Konsole to the
left-most display and closing them there, the size gets restored correctly. I
can also move the window over to the right primary
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #19 from Claudius Ellsel ---
The scope of this bug has drifted a bit (it used to be about a bug in Wayland,
while now it tracks stuff happening on X11 according to the title). I have
marked another bug as a duplicate of this now.
Since
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #18 from Claudius Ellsel ---
*** Bug 431230 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=431230
Claudius Ellsel changed:
What|Removed |Added
Resolution|NOT A BUG |DUPLICATE
--- Comment #11 from Claudius
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #10 from Claudius Ellsel ---
*** Bug 431235 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=431235
Claudius Ellsel changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=431234
Claudius Ellsel changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #9 from Claudius Ellsel ---
*** Bug 431234 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=431234
--- Comment #14 from Claudius Ellsel ---
Multi monitor it is. After deactivating one of mine, it works for me again.
As I suspected in the original bug report, this is strongly related, maybe even
a duplicate of https://bugs.kde.org/show_bug.cgi?id
https://bugs.kde.org/show_bug.cgi?id=427803
--- Comment #11 from Claudius Ellsel ---
I am still not convinced this is the root of the problem.
To me the simpler reason that the vertical images for 5.20 were "wrong" is the
more likely explanation currently. I mean, one can c
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #12 from Claudius Ellsel ---
(In reply to Martin Höher from comment #10)
> Dolphin still came up with the same, wrong window size. But otherwise, it
> still remembered all of the other settings (e.g. the last folder it ha
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #11 from Claudius Ellsel ---
Permissions for the dolphinrc file look sane. My user is shown as owner and the
owner has rw- permissions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #12 from Claudius Ellsel ---
I noticed that the line
`RestorePositionForNextInstance=false`
is added to the file for both Dolphin and Konsole when they are launched and
removed when they are closed. But that might not be related.
--
You
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #11 from Claudius Ellsel ---
Yes, I can confirm that the behavior is the same as for Dolphin.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427803
--- Comment #9 from Claudius Ellsel ---
Are you sure? See my comment there (I guess that is the algorithm you are
referring to?):
https://invent.kde.org/plasma/breeze/-/commit/c6cb949de22b092359dccf859a950d1336467a3a#note_167338.
To me it just seems
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #9 from Claudius Ellsel ---
Yes, the behavior is pretty awkward. It also seems to happen only on the
Tumbleweed system, Manjaro and the KDE Neon unstable VM don't seem to suffer
from this.
Problematic permissions *should* be covered
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #10 from Claudius Ellsel ---
Possibly, I'll make sure to check this for Konsole as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427803
Claudius Ellsel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=427803
Claudius Ellsel changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #8 from Claudius Ellsel ---
Created attachment 134806
--> https://bugs.kde.org/attachment.cgi?id=134806=edit
Screenshot of the settings window
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431235
Claudius Ellsel changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=431235
Claudius Ellsel changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431234
Claudius Ellsel changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431234
Claudius Ellsel changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=431450
Claudius Ellsel changed:
What|Removed |Added
Keywords||regression
CC
https://bugs.kde.org/show_bug.cgi?id=368063
--- Comment #27 from Claudius Ellsel ---
After witnessing the changes on the Numlock LED (before my keyboard did not
have one), I am wondering whether this also has something to do with SDDM or
Linux kernel options (at least when the option is set
https://bugs.kde.org/show_bug.cgi?id=427882
--- Comment #2 from Claudius Ellsel ---
Another option might be to go the "GNOME way" and have those stuff only appear
on one screen (they also achieve this with their displaymanager while SDDM just
mirrors the screen and doesn't know about o
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #6 from Claudius Ellsel ---
Will report back soon (the next time I come around booting to Tumbleweed).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #6 from Claudius Ellsel ---
I know and will try to report back soon!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427803
--- Comment #4 from Claudius Ellsel ---
I'll try to test soon on a KDE Neon unstable VM!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431235
Claudius Ellsel changed:
What|Removed |Added
Resolution|NOT A BUG |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #4 from Claudius Ellsel ---
I just saw that also the other file I uploaded contains the lines you mentioned
(while also containing `DP-1 HDMI-2 Window-Maximized 1440x2560=true`). So you
might already be referring to that file. I'll try
https://bugs.kde.org/show_bug.cgi?id=431234
--- Comment #3 from Claudius Ellsel ---
Forgot to answer the window rules question: No, I think I don't have any, at
least I never have manually created one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431234
Claudius Ellsel changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=425384
Claudius Ellsel changed:
What|Removed |Added
CC||aleix...@kde.org
https://bugs.kde.org/show_bug.cgi?id=431235
--- Comment #2 from Claudius Ellsel ---
That might be it, I'll have a look soon.
Is this not enabled by default (or overwritten on Tumbleweed)? At least on
Manjaro I think it was always on and also I think I read something about it
before.
--
You
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #8 from Claudius Ellsel ---
Spin offs:
- https://bugs.kde.org/show_bug.cgi?id=431234
- https://bugs.kde.org/show_bug.cgi?id=431235
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431235
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431235
Bug ID: 431235
Summary: Konsole does not remember the previous window size
Product: konsole
Version: 20.12.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=431234
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431234
Bug ID: 431234
Summary: Dolphin does not remember its window size
Product: dolphin
Version: 20.12.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #7 from Claudius Ellsel ---
Didn't know that and thought maybe the same bug got introduced by the "remember
position and size" feature. Will file separate reports, then.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #4 from Claudius Ellsel ---
The maximized part might be solved by
https://invent.kde.org/frameworks/kconfig/-/merge_requests/37, I'll try to test
when frameworks 5.78 land. The other issue with Konsole not remembering when
changing
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #3 from Claudius Ellsel ---
Created attachment 134618
--> https://bugs.kde.org/attachment.cgi?id=134618=edit
dolphinrc after maximizing
Sorry, the old dolphinrc attachement apparently was not taken after maximizing
the window, so h
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #2 from Claudius Ellsel ---
Created attachment 134617
--> https://bugs.kde.org/attachment.cgi?id=134617=edit
discoverrc
Discover works, though so adding a clean rc file for that as well (after
opening Discover, maximizing the win
https://bugs.kde.org/show_bug.cgi?id=431230
--- Comment #1 from Claudius Ellsel ---
Created attachment 134616
--> https://bugs.kde.org/attachment.cgi?id=134616=edit
konsolerc
konsolerc for comparison, maybe it gives helpful hints, also a "clean" file
after moving the old one
https://bugs.kde.org/show_bug.cgi?id=431230
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431230
Claudius Ellsel changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431230
Bug ID: 431230
Summary: Certain windows don't remember their window sizes
Product: frameworks-kconfig
Version: 5.77.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=423067
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=423067
--- Comment #13 from Claudius Ellsel ---
Alright. I did not think of this case myself. I wonder how Windows (or I think
GNOME) handles it, since they both have this shortcut. Maybe it maximizes first
and then moves the window up when pressed again
https://bugs.kde.org/show_bug.cgi?id=319700
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
CC
https://bugs.kde.org/show_bug.cgi?id=422630
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
Severity|minor
https://bugs.kde.org/show_bug.cgi?id=402081
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
Keywords
https://bugs.kde.org/show_bug.cgi?id=423545
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
Keywords
https://bugs.kde.org/show_bug.cgi?id=430557
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=430557
Bug ID: 430557
Summary: Bookmarks in the places panel that are on not mounted
drives don't work
Product: frameworks-kio
Version: unspecified
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=426813
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=429399
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=429778
--- Comment #14 from Claudius Ellsel ---
Another note: When setting the size to resize to, the field behaved a bit
sluggish. I did not want to use the arrows until I got to the desired size, so
I typed it in and tried to estimate where the exat size
https://bugs.kde.org/show_bug.cgi?id=429778
--- Comment #13 from Claudius Ellsel ---
Ah thanks for the insight. I did not know that there is a difference between
filesystem and partition. That might be an explanation for that behavior. I did
not notice an error when resizing the partition in KDE
https://bugs.kde.org/show_bug.cgi?id=429778
--- Comment #11 from Claudius Ellsel ---
Alright, thanks for your efforts!
The exact procedure was:
- Have a KDE Neon installation on Virtualbox (I guess 8GiB total size of the
image)
- Resize that image to (I guess) 16 GiB
- Expand the partition
https://bugs.kde.org/show_bug.cgi?id=429778
--- Comment #9 from Claudius Ellsel ---
Maybe it is something special with the Virtualbox disk image.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429778
--- Comment #7 from Claudius Ellsel ---
Mh, the thing is that it is a bit weird that gparted allowed me to increase the
size further. Not sure whether that had a real effect, though.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #14 from Claudius Ellsel ---
(In reply to Claudius Ellsel from comment #13)
> BTW: I might also have been wrong about the multi screen requirement, as I
> think I also experienced this when disabling a screen on openSUSE
> Tumb
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #13 from Claudius Ellsel ---
BTW: I might also have been wrong about the multi screen requirement, as I
think I also experienced this when disabling a screen on openSUSE Tumbleweed. I
might mix up different underlying problems here, though
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #11 from Claudius Ellsel ---
I know. I still experience the described bug on Wayland. Maybe not caused by
your changes, but it is there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #9 from Claudius Ellsel ---
(In reply to Nate Graham from comment #8)
> and non-primary left screens on X11 (the
> only platform affected)
To be clear, this happens on Wayland for me (but I think also on X11).
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=429943
Claudius Ellsel changed:
What|Removed |Added
Keywords||regression
CC
https://bugs.kde.org/show_bug.cgi?id=430085
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426354
--- Comment #10 from Claudius Ellsel ---
I also created https://bugs.kde.org/show_bug.cgi?id=430085 now to keep track of
the fix for the problem while folders are still loading.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430085
Bug ID: 430085
Summary: The text displaying that a folder is empty does not
wait for its content to load
Product: dolphin
Version: unspecified
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=426354
--- Comment #9 from Claudius Ellsel ---
Alright, follow up bug is https://bugs.kde.org/show_bug.cgi?id=430082.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430082
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=430082
Bug ID: 430082
Summary: Handle information of folders with (only) hidden files
differently
Product: dolphin
Version: unspecified
Platform: Other
OS: Other
https://bugs.kde.org/show_bug.cgi?id=426354
--- Comment #8 from Claudius Ellsel ---
Alright. I also saw the discussion in the MR about this after commenting here.
Personally I feel this should be treated differently (but not sure how other
file managers like Nautilus or Windows Explorer treat
https://bugs.kde.org/show_bug.cgi?id=426354
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426354
Claudius Ellsel changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=429774
--- Comment #6 from Claudius Ellsel ---
I forgot to test running from terminal. Here is the output (the first error
messages occurred right after launching it):
clel@claudius-virtualbox:~$ plasma-discover
Cyclic dependency detected between
"
https://bugs.kde.org/show_bug.cgi?id=428599
--- Comment #4 from Claudius Ellsel ---
Switching between windows and bringing Discover back to the foreground gives me
the same result as in the other attached screenshots.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429986
Bug ID: 429986
Summary: Opening another result opens that in a new pane
instead of replacing the already opened result
Product: Discover
Version: 5.20.4
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=428599
Claudius Ellsel changed:
What|Removed |Added
Keywords||accessibility, usability
--
You
https://bugs.kde.org/show_bug.cgi?id=428599
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=429774
Claudius Ellsel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=429774
--- Comment #4 from Claudius Ellsel ---
Just tested again, still happens reproducibly. I'll try to get a screen
capture.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426704
--- Comment #7 from Claudius Ellsel ---
I guess almost nobody thought of that :) It is not intuitive.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429102
Claudius Ellsel changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=429777
--- Comment #3 from Claudius Ellsel ---
Alright. For reference: https://gitlab.gnome.org/GNOME/gparted/-/issues/125.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429779
--- Comment #5 from Claudius Ellsel ---
I know, but I don't like Ubuntus bug reporting system (or rather the fact that
they don't tend to react that often). I just thought that it might be helpful
to report to a place where both sides are aware
https://bugs.kde.org/show_bug.cgi?id=429774
--- Comment #2 from Claudius Ellsel ---
I tested in a VM. Maybe related to the less powerful setup there. I also think
that I have seen it working, so might also be related to specific conditions.
I will try testing again in the near future and update
https://bugs.kde.org/show_bug.cgi?id=429779
--- Comment #3 from Claudius Ellsel ---
I guess, KDE Neon does not have a place to track upstream bugs for the software
they distribute?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353391
--- Comment #7 from Claudius Ellsel ---
Looks a bit like 128 TiB is used as starting value when the size is calculated.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426704
Claudius Ellsel changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=429102
--- Comment #6 from Claudius Ellsel ---
While writing my answer I finally got what you meant. I had the misconception
that trashing files would occupy new space which is not true (and also solved
for external drives recently). So the space is indeed
https://bugs.kde.org/show_bug.cgi?id=429102
--- Comment #4 from Claudius Ellsel ---
Did you comment on the right bug? If yes, I don't understand what you mean with
copy and how that is related to this report.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429775
--- Comment #2 from Claudius Ellsel ---
Nice, that was fast!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424754
--- Comment #24 from Claudius Ellsel ---
Since you seem to be familiar with compiling with kdesrc-build, what you could
try to do is to modify the code at the line you found to be possibly suspicious
and add debug output to see how the code behaves
https://bugs.kde.org/show_bug.cgi?id=400987
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--
You
https://bugs.kde.org/show_bug.cgi?id=424795
Claudius Ellsel changed:
What|Removed |Added
Keywords||usability, wayland
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=424795
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--
You
101 - 200 of 914 matches
Mail list logo
