.ccrma.x86_64+rt x86_64
Distribution: "Fedora release 24 (Twenty Four)"
-- Information about the crash:
- What I was doing when the application crashed:
I was redoing edits on a JavaScript file by pressing Ctrl + Shift + Z
The crash does not seem to be reproducible.
-- Backtrace:
Application
https://bugs.kde.org/show_bug.cgi?id=451158
Be changed:
What|Removed |Added
CC||b...@gmx.com
--- Comment #2 from Be ---
I am also
https://bugs.kde.org/show_bug.cgi?id=107302
Be changed:
What|Removed |Added
CC||b...@gmx.com
--
You are receiving this mail because:
You
produce this with GNOME Wayland, so it seems to be an issue in the
interaction between KWin and Qt's Wayland QPA.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454779
--- Comment #1 from Be ---
Monitor scale factor does not affect this. The crucial aspect is whether the
top edges of the monitors are aligned in Display Configuration.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454850
Bug ID: 454850
Summary: URIs are not
Product: xdg-desktop-portal-kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
P
https://bugs.kde.org/show_bug.cgi?id=454850
Be changed:
What|Removed |Added
Summary|URIs are not|URIs are not encoded
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454779
--- Comment #4 from Be ---
Ping David, could you link to that upstream Qt bug?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
Bug ID: 465965
Summary: blurry red-on-black and black-on-red text with high
DPI scaling on Plasma Wayland with Intel UHD Graphics
770
Classification: Plasma
Product: kwin
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #1 from Be ---
Created attachment 156395
--> https://bugs.kde.org/attachment.cgi?id=156395&action=edit
Konsole with red text on black background
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #2 from Be ---
Created attachment 156396
--> https://bugs.kde.org/attachment.cgi?id=156396&action=edit
black text on red background in LibreOffice
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #3 from Be ---
Created attachment 156397
--> https://bugs.kde.org/attachment.cgi?id=156397&action=edit
red text on black background in LibreOffice
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #4 from Be ---
Created attachment 156398
--> https://bugs.kde.org/attachment.cgi?id=156398&action=edit
red text on white background in LibreOffice (looks okay)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #5 from Be ---
Created attachment 156399
--> https://bugs.kde.org/attachment.cgi?id=156399&action=edit
Kate with Breeze Light (looks okay)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #6 from Be ---
I am unable to reproduce this with Weston or GNOME (Wayland) running the same
applications.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #7 from Be ---
Created attachment 156403
--> https://bugs.kde.org/attachment.cgi?id=156403&action=edit
close up photo of Konsole with red text on black
I can see the blurriness when looking at the attached screenshots in Plasma
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #9 from Be ---
Those screenshots were taken with Spectacle. I'm not sure if this bug can be
captured by screenshots... which may hint that the bug is pretty low down in
the graphics stack. FWIW, I'm using a Samsung QN32Q60AAFX
https://bugs.kde.org/show_bug.cgi?id=465965
--- Comment #10 from Be ---
Are you able to see the difference with the photo rather than the screenshots?
It's most prominent comparing the red "A" with the purple "A".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465965
Be changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459682
Bug ID: 459682
Summary: kateprojectplugin.so undefined symbol error in
AppImage
Classification: Applications
Product: kate
Version: 22.08.1
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=184325
Be changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=342092
--- Comment #3 from Be ---
Uh, Amarok is a dead project at this point. I'm surprised the bugs haven't all
been closed already.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486092
Bug ID: 486092
Summary: playback does not advance to next track in playlist
Classification: Applications
Product: Elisa
Version: 24.02.1
Platform: Other
OS: Linux
Stat
https://bugs.kde.org/show_bug.cgi?id=472587
--- Comment #4 from Be ---
After updating to KDE 6, the file
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml
is still there for the lock screen, but the file that needs editing for the
login screen has moved
https://bugs.kde.org/show_bug.cgi?id=479130
--- Comment #9 from Be ---
For anyone coming here encountering this bug in Fedora 40: the Elisa version
24.02.2 with the fix is already available in updates-testing. Run `dnf update
--enablerepo=updates-testing elisa-player` to install it before it
https://bugs.kde.org/show_bug.cgi?id=433518
--- Comment #1 from Be ---
I took a quick look at how Elisa outputs audio and see it uses the very high
level QMediaPlayer class, so the bug might be upstream in Qt.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433518
Be changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=441879
Be changed:
What|Removed |Added
CC||b...@gmx.com
--- Comment #4 from Be ---
Rather than
RMATION
Refer to the attached backtrace. There seems to be an infinite (or extremely
deep) loop.
--
You are receiving this mail because:
You are watching all bug changes.
the Git view. It would be nice
to be able to discard specific lines and hunks within unstaged diffs to give
finer control than discarding all changes in the file.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443026
--- Comment #3 from Be ---
Thanks for the quick fix! I confirm this is fixed in the master branch. I am
glad I took the time to report the bug with a backtrace.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443026
Be changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0 |1
.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (Workstation Edition)
-- Information about the crash:
- What I was doing when the application crashed:
KDevelop was running the parser in the background. I did not have the KDevelop
window visible.
The crash can be reproduced sometimes
https://bugs.kde.org/show_bug.cgi?id=428442
Bug ID: 428442
Summary: preferences window is too tall for 768 px high screen
Product: kdevelop
Version: 5.6.0
Platform: Other
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=472587
Bug ID: 472587
Summary: option to hide clock from login & lock screens
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: RE
https://bugs.kde.org/show_bug.cgi?id=472587
--- Comment #1 from Be ---
I also hacked the Clock component in
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml
to set the visible property to always `false` to hide the clock from the lock
screen.
--
You
https://bugs.kde.org/show_bug.cgi?id=472587
Be changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=429672
--- Comment #3 from Be ---
Hiding the volume slider is an interesting idea. Maybe collapse it to just an
icon that pops out a vertical slider when pressed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431422
Bug ID: 431422
Summary: intermittent crash when finishing playing a track
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=431422
--- Comment #2 from Be ---
In Elisa's preferences "Music indexing" defaulted to "Scan the filesystem
directly". I tried switching that to "Use fast native indexer" but the crash
still occurs.
There is no pattern
the playlist
EXPECTED RESULT
I'm not sure what the best way to handle this would be. Should the playlist be
resizable by the user? Should it automatically resize to accommodate the track
title length? Should it just show the part of the track title that fits without
a horizontal scrollbar?
SOF
https://bugs.kde.org/show_bug.cgi?id=429670
Bug ID: 429670
Summary: seldomly played albums
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priori
: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: b...@gmx.com
Target Milestone: ---
It would be nice to be able to delete files and groups of files (albums,
artists, genres) from Elisa. I'm not sure where this would fit into the UI well
wi
https://bugs.kde.org/show_bug.cgi?id=429672
Bug ID: 429672
Summary: track progress/seek bar unusable at minimum width
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=429675
Bug ID: 429675
Summary: clicking tracks in "party mode" playlist does not
start playback if no track is currently playing
Product: elisa
Version: 20.08.3
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=430099
Bug ID: 430099
Summary: UI for removing album from playlist
Product: elisa
Version: 20.08.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=430099
--- Comment #2 from Be ---
I agree that would be a good way to implement this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430133
Bug ID: 430133
Summary: middle panel and playlist not touch flickable
Product: elisa
Version: 20.08.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=372774
Be changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #2 from Be ---
I have not
https://bugs.kde.org/show_bug.cgi?id=461427
Be changed:
What|Removed |Added
CC||b...@gmx.com
--- Comment #2 from Be ---
I am also
https://bugs.kde.org/show_bug.cgi?id=472587
--- Comment #11 from Be ---
Note that the GUI for configuring hiding the clock from the login screen will
be in 6.3, not 6.2. In 6.2, manually editing the SDDM theme's theme.conf.user
file to change `showClock = true` to `showClock = false` should
86_64/src/corelib/kernel/qobject.cpp:3976
#94 0x7fffb004c848 in ColumnView::visibleItemsChanged (this=0x0) at
src/layouts/KirigamiLayouts_autogen/include/moc_columnview.cpp:1274
#95 ContentItem::updateVisibleItems (this=0x5613c710) at
/home/be/kde/src/kirigami/src/layouts/columnview.cpp:72
https://bugs.kde.org/show_bug.cgi?id=472587
--- Comment #5 from Be ---
Merge requests for the lock screen:
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2365
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4499
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=472587
Be changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |b...@gmx.com
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=472587
--- Comment #6 from Be ---
Merge requests for login screen:
https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/74
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2366
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=433518
Bug ID: 433518
Summary: audio output does not work after restarting PulseAudio
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Sev
https://bugs.kde.org/show_bug.cgi?id=241032
Be changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
: wishlist
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: b...@gmx.com
Target Milestone: ---
It would be a nice feature if KDevelop popped up a desktop notification when a
build finishes so I don't have to keep watching it. If
https://bugs.kde.org/show_bug.cgi?id=376350
Be changed:
What|Removed |Added
CC||b...@gmx.com
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=376350
--- Comment #2 from Be ---
Created attachment 108890
--> https://bugs.kde.org/attachment.cgi?id=108890&action=edit
Mixxx Preferences window
another screenshot of the bug
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403484
Bug ID: 403484
Summary: many classes not resolved by C++ indexer
Product: kdevelop
Version: 5.3.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=403484
Be changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=241032
Be changed:
What|Removed |Added
CC||b...@gmx.com
--- Comment #2 from Be ---
I can reproduce
each step is not practical, as it slows down my system
dramatically as soon as the background parser starts. I can think of two
workarounds:
1. Add an action to KDevelop to suspend/resume background parsing that could be
bound to a global keyboard shortcut. This would require the user to remember
https://bugs.kde.org/show_bug.cgi?id=377389
--- Comment #2 from Be ---
I'm using an old Intel Core i5 2410M with 4GB of RAM.
--
You are receiving this mail because:
You are watching all bug changes.
-xdebug
It would be great to bring Xdebug support back to KDevelop 5.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493422
--- Comment #2 from Be ---
What is the use case for only showing the clock in the very specific situation
after the mouse or keyboard have been touched?
Turning the binary option into a three state option could do this, but I'm
unclear wha
https://bugs.kde.org/show_bug.cgi?id=107302
Be changed:
What|Removed |Added
CC|b...@gmx.com|
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=364354
Be changed:
What|Removed |Added
Resolution|BACKTRACE |FIXED
--- Comment #6 from Be ---
Whatever was causing
Wordpress project (PHP, CSS, JS) opened.
The crash can be reproduced every time.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current
the syntax:
function functionName (args) {stuff};
but not with functions defined as expressions assigned to a variable:
functionName = function (args) {stuff};
Considering that variables can be reassigned to a function expression at any
point, to support this something would have to be added to
https://bugs.kde.org/show_bug.cgi?id=368432
Bug ID: 368432
Summary: crash on startup
Product: kdevelop
Version: 5.0.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Prio
https://bugs.kde.org/show_bug.cgi?id=368432
--- Comment #1 from Be ---
Created attachment 100983
--> https://bugs.kde.org/attachment.cgi?id=100983&action=edit
GDB backtrace
--
You are receiving this mail because:
You are watching all bug changes.
disconnected my speaker
and let my computer be for a while. When I came back to my computer, I saw that
Amarok had crashed.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1"
https://bugs.kde.org/show_bug.cgi?id=364354
--- Comment #2 from Be ---
Okay, I installed debugging symbols for Amarok. I'll attach a new backtrace
when I get one, but I don't exactly know how to reproduce the issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364354
--- Comment #3 from Be ---
Created attachment 99668
--> https://bugs.kde.org/attachment.cgi?id=99668&action=edit
error when starting pavucontrol after quitting Amarok
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364354
--- Comment #4 from Be ---
Hm, so this may have something to do with PulseAudio. It happened again and I
left my computer for a while (after unplugging my speakers from my sound card).
When I came back, Amarok had not crashed, but my system was taking
https://bugs.kde.org/show_bug.cgi?id=299461
Be changed:
What|Removed |Added
CC||b...@gmx.com
--
You are receiving this mail because:
You
78 matches
Mail list logo
