https://bugs.kde.org/show_bug.cgi?id=421714
--- Comment #2 from real ---
Tried it again. No problem. Close it out.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421714
Bug ID: 421714
Summary: plasma panel crashes when adding when adding browser
widget
Product: plasma-browser-integration
Version: unspecified
Platform: Mint (Ubuntu based)
https://bugs.kde.org/show_bug.cgi?id=421714
real changed:
What|Removed |Added
Summary|plasma panel crashes when |plasma panel crashes when
|adding
https://bugs.kde.org/show_bug.cgi?id=485475
Bug ID: 485475
Summary: Every torrent from a torrent sharing site makes
ktorrent use 100% cpu and only respond to kill -9
Classification: Applications
Product: ktorrent
Version: 24.02.2
https://bugs.kde.org/show_bug.cgi?id=483305
Bug ID: 483305
Summary: When moving windows, the "all-scroll" cursor is used
instead of "move"
Classification: Plasma
Product: kwin
Version: 6.0.1
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=435902
Real Name changed:
What|Removed |Added
Version|7.1.0 |unspecified
CC
https://bugs.kde.org/show_bug.cgi?id=434290
Real Name changed:
What|Removed |Added
CC||zuurve...@outlook.com
--- Comment #3 from Real
https://bugs.kde.org/show_bug.cgi?id=475291
Bug ID: 475291
Summary: Plasma crashes when I press Super+1 to launch a pinned
Firefox shortcut
Classification: Plasma
Product: plasmashell
Version: 5.27.8
Platform: Fedora RP
https://bugs.kde.org/show_bug.cgi?id=475937
Bug ID: 475937
Summary: Unable to print in landscape mode
Classification: Applications
Product: gwenview
Version: 23.08.1
Platform: Fedora RPMs
OS: Linux
Status: REPOR
https://bugs.kde.org/show_bug.cgi?id=461169
Real Name changed:
What|Removed |Added
CC||zuurve...@outlook.com
--- Comment #1 from Real
https://bugs.kde.org/show_bug.cgi?id=455021
Real Name changed:
What|Removed |Added
CC||zuurve...@outlook.com
--- Comment #8 from Real
https://bugs.kde.org/show_bug.cgi?id=455021
--- Comment #9 from Real Name ---
Oh, OK, installing kpipewire solves the issue for me. Definitely a Fedora bug
as it had to be pulled automatically when I updated.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463377
Real Name changed:
What|Removed |Added
CC||zuurve...@outlook.com
--- Comment #3 from Real
https://bugs.kde.org/show_bug.cgi?id=463377
--- Comment #4 from Real Name ---
Forgot to add that starting plasmashell from the terminal with
QSG_RENDER_LOOP=basic makes the problem far, far worse, if it helps debugging.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463377
--- Comment #5 from Real Name ---
New find: starting plasmashell with mesa_glthread=false fixes the issue for me.
Mesa 22.3 enables GL threads by default.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463377
--- Comment #7 from Real Name ---
(In reply to Jeremi Campagna from comment #6)
> (In reply to Real Name from comment #5)
> > New find: starting plasmashell with mesa_glthread=false fixes the issue for
> > me. Mesa 22.3 enables GL thr
https://bugs.kde.org/show_bug.cgi?id=463377
--- Comment #12 from Real Name ---
Created attachment 155112
--> https://bugs.kde.org/attachment.cgi?id=155112&action=edit
drirc to test Plasma with mesa_glthread disabled
I just recalled that Mesa allows you to work around application bugs
https://bugs.kde.org/show_bug.cgi?id=416065
Real name changed:
What|Removed |Added
CC||angel...@gmail.com
--- Comment #2 from Real name
https://bugs.kde.org/show_bug.cgi?id=416065
--- Comment #3 from Real name ---
Hello again
Tested with Debian 11 KDE, I can unlock LUKS container, but in order to see
logical volumes I had to install udisks2-lvm2, after that I can see logical
volumes (LV) into /dev/mapper and I can see it in KDE
https://bugs.kde.org/show_bug.cgi?id=397284
--- Comment #3 from Real Name ---
The problem is one of those where you just need to try to import a file
format that is normally accepted. The problem isn't one that lends
itself to screen shots.
Dave
On 3/31/19 3:03 AM, Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=397284
Bug ID: 397284
Summary: Not able to Import Data
Product: kaddressbook
Version: unspecified
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=397284
--- Comment #1 from Real Name ---
Not able to import database of addresses from an external source. File format
is CSV.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=397438
Bug ID: 397438
Summary: Not Able to Import Data
Product: kaddressbook
Version: unspecified
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=397438
Real Name changed:
What|Removed |Added
Target Milestone|--- |15.08
--- Comment #1 from Real Name ---
Import
https://bugs.kde.org/show_bug.cgi?id=393865
Bug ID: 393865
Summary: Brush delay
Product: krita
Version: 3.3.1
Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NO
https://bugs.kde.org/show_bug.cgi?id=494773
Bug ID: 494773
Summary: summary
Classification: I don't know
Product: kde
Version: unspecified
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=494002
Bug ID: 494002
Summary: KDE Connect will crash constantly after pairing a
device
Classification: Applications
Product: kdeconnect
Version: 24.08.1
Platform: Android
https://bugs.kde.org/show_bug.cgi?id=494002
--- Comment #1 from Real Name ---
Android app version is 1.32.4
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=494002
--- Comment #2 from Real Name ---
I could work around the instability by disabling Bigscreen Remote, Mouse
Receiver, Presentation Remote and Receive Remote Keypresses on the phone before
it starts to crash. After I pair the phone it says "devic
https://bugs.kde.org/show_bug.cgi?id=412707
--- Comment #4 from Tim E. Real ---
Thanks for looking into this.
Lately it seems to be behaving much better.
Now at least, if a crash occurs, it seems that upon reboot the temp files are
gone.
I find that I am having to do much less manual cleanup
https://bugs.kde.org/show_bug.cgi?id=412707
--- Comment #6 from Tim E. Real ---
Hm, you are right. I put a file in there and it was gone on reboot.
It surely was not working at the time of this bug report.
In fact at the time, Konsole was also leaving a lot of trash that was not
cleared even on
https://bugs.kde.org/show_bug.cgi?id=412707
--- Comment #7 from Tim E. Real ---
I suppose this report could be closed now, as the particular reported problem
has gone away, with respect to the leftover reboot tmp files.
Thank you.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=412707
--- Comment #9 from Tim E. Real ---
Ah yes. Good idea I suppose, since we do still have to manually clear the temp
files out
after a non-lockup crash to the desktop.
The trouble for me was when KDevelop occasionally crashed by locking up the
computer
https://bugs.kde.org/show_bug.cgi?id=382289
--- Comment #5 from Tim E. Real ---
Hi thanks for taking a look.
The bug remains very elusive, I still cannot pin down exactly what triggers it.
Here is one thing that does usually trigger it, virtually every time:
Occasionally KDevelop will crash
https://bugs.kde.org/show_bug.cgi?id=412705
--- Comment #3 from Tim E. Real ---
Thank you for the response.
Konsole (ver 19.08.1) does not crash, nor the system.
The only thing I can think of that might be unusual
is that I leave Konsole open when I shut down,
ie. I leave Konsole open all the
https://bugs.kde.org/show_bug.cgi?id=412705
--- Comment #4 from Tim E. Real ---
Verified: Konsole cleans up after itself if I manually close it.
But Konsole does not clean up if left open and reboot.
I began with a clean plate and started Konsole and verified
it cleans up if I close it.
But
https://bugs.kde.org/show_bug.cgi?id=412705
--- Comment #5 from Tim E. Real ---
I almost forgot, KDevelop is another app that populates the /tmp folder.
KDevelop does not leave anything there upon reboot, and cleans up despite
being a 600lb gorilla having a big project open and many huge temp
https://bugs.kde.org/show_bug.cgi?id=412705
--- Comment #7 from Tim E. Real ---
Thanks for the tip. I did not know that about QTemporayFile.
It does not appear to specifically mention that in the docs.
I began using that class in our app recently.
I read a topic somewhere "How long do temp
https://bugs.kde.org/show_bug.cgi?id=412705
Bug ID: 412705
Summary: Konsole leaves hundreds of megabytes in thousands of
temp history files
Product: konsole
Version: unspecified
Platform: openSUSE RPMs
OS: L
https://bugs.kde.org/show_bug.cgi?id=412707
Bug ID: 412707
Summary: KDevelop leaves hundreds of megabytes of temp files if
it crashes
Product: kdevelop
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=379790
Bug ID: 379790
Summary: MDI SubWindows are frozen (non-responsive) with Breeze
and Oxygen
Product: Breeze
Version: 5.9.5
Platform: Other
OS: Linux
Stat
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #3 from Tim E. Real ---
Created attachment 105534
--> https://bugs.kde.org/attachment.cgi?id=105534&action=edit
Frozen MDI test UI file 1
Open in Qt5Designer or Creator. The MDI sub windows are frozen
in Breeze or Oxygen.
--
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #4 from Tim E. Real ---
Wow. I never tried saving/re-opening a test-case UI file before.
This fresh suse installation is on Breeze by default.
So the attached UI file's MDI sub windows are frozen even without
previewing the form. The
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #5 from Tim E. Real ---
Wow! When the attached UI file is opened, it is not only the
MDI sub windows that are affected - it is the ENTIRE QMainWindow
containing the QMDIArea.
In fact, I am unable to even move the window around in
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #10 from Tim E. Real ---
(In reply to Hugo Pereira Da Costa from comment #7)
> Can you check with oxygen-demo5 if the mdi-window tab is responsive there ?
> It is, here.
Yes. In the openSuSE Tumbleweed.
There's no oxygen-d
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #11 from Tim E. Real ---
(In reply to Hugo Pereira Da Costa from comment #8)
> Created attachment 105543 [details]
> another ui file with mdi windows, that work
>
> Can you test this ui locally (it has mdi windows, no styles
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #12 from Tim E. Real ---
(In reply to Hugo Pereira Da Costa from comment #9)
> Here at least it seems setting the stylesheet creates the freeze.
> Removing it on your ui file unfreezes things
> Adding it on mine freezes thi
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #20 from Tim E. Real ---
Created attachment 105939
--> https://bugs.kde.org/attachment.cgi?id=105939&action=edit
Simple cmake based Qt MDI program sets stylesheet
Hi, can you spare some more time? 5.10 packages came down the line
https://bugs.kde.org/show_bug.cgi?id=379790
--- Comment #22 from Tim E. Real ---
(In reply to Hugo Pereira Da Costa from comment #21)
> (In reply to Tim E. Real from comment #20)
> > Created attachment 105939 [details]
> > Simple cmake based Qt MDI program sets stylesheet
>
https://bugs.kde.org/show_bug.cgi?id=379790
Tim E. Real changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=382289
Bug ID: 382289
Summary: Long-standing bug: Bookmarks are often forgotten.
Product: kdevelop
Version: 5.1.1
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Se
https://bugs.kde.org/show_bug.cgi?id=496919
Bug ID: 496919
Summary: Global menu: Not working properly with our Qt app's
dynamic menus
Classification: Plasma
Product: plasmashell
Version: 6.2.3
Platform: openSUSE
https://bugs.kde.org/show_bug.cgi?id=496919
--- Comment #1 from Tim E. Real ---
Update: We learned about the Qt::AA_DontUseNativeMenuBar flag and have included
in the app.
The app now works fine while such global menus are in use.
Although, this means it is unable to participate in these global
https://bugs.kde.org/show_bug.cgi?id=488270
Real Name Here changed:
What|Removed |Added
CC||lastminutejanedoe@protonmai
https://bugs.kde.org/show_bug.cgi?id=500210
--- Comment #2 from Real Name Here ---
After creating a blank profile, I discovered the brightness slider only works
in SDR if ICC profiles are disabled. Should I instead report this as a kwin
issue?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=500210
Real Name Here changed:
What|Removed |Added
Summary|Screen brightness control |ICC profiles disable
|no
https://bugs.kde.org/show_bug.cgi?id=500036
Real Name Here changed:
What|Removed |Added
CC||lastminutejanedoe@protonmai
https://bugs.kde.org/show_bug.cgi?id=500210
Bug ID: 500210
Summary: Screen brightness no longer works in SDR on Wayland
Classification: Plasma
Product: plasmashell
Version: 6.3.0
Platform: openSUSE
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=500210
--- Comment #1 from Real Name Here ---
I'm not sure if this is relevant, but kscreen-doctor reports both brightness
and dimming support in Plasma 6.3, whereas only brightness support is indicated
in 6.2.5
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=500210
Real Name Here changed:
What|Removed |Added
Summary|Screen brightness no longer |Screen brightness control
https://bugs.kde.org/show_bug.cgi?id=500036
--- Comment #18 from Real Name Here ---
(In reply to Zamundaaa from comment #17)
> Okay, that sounds similar to what I saw. I'm not sure where it could come
> from, but let's keep this open until it's fully solved.
Are the
https://bugs.kde.org/show_bug.cgi?id=500210
Real Name Here changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=500210
--- Comment #8 from Real Name Here ---
(In reply to Zamundaaa from comment #7)
> Please try to set the brightness to 50%, and afterwards attach the output of
> kscreen-doctor -o and the file ~/.config/kwinoutputconfig.json
# kscreen-doctor -o
https://bugs.kde.org/show_bug.cgi?id=500210
Real Name Here changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
64 matches
Mail list logo
