https://bugs.kde.org/show_bug.cgi?id=487779
--- Comment #3 from Bernie Innocenti ---
Found an existing bug in the Chromium bug tracker:
https://issues.chromium.org/issues/331796411
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487779
--- Comment #1 from Bernie Innocenti ---
Forgot to mention: videos play correctly, I wouldn't have noticed the issue
without looking in the journal.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487779
Bug ID: 487779
Summary: ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with
format= YUV_420_BIPLANAR and
usage=SCANOUT_CPU_READ_WRITE
Classification: Plasma
Product:
https://bugs.kde.org/show_bug.cgi?id=480834
Bug ID: 480834
Summary: Can't install cursor themes with "Get New..."
Classification: Applications
Product: systemsettings
Version: 5.93.0
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=420280
--- Comment #73 from Bernie Innocenti ---
I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
the Fedora COPR repo "hazel-bunny/ports".
I confirm it fixes this particular bug: the authentication window renders and
yo
https://bugs.kde.org/show_bug.cgi?id=420280
--- Comment #50 from Bernie Innocenti ---
I filed this Fedora bug to request upgrading signon-ui:
https://bugzilla.redhat.com/show_bug.cgi?id=2230099
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420280
--- Comment #43 from Bernie Innocenti ---
(In reply to Harald Sitter from comment #41)
> signon-ui 0.15 is even more ancient than ubuntu's.
Upstream seems dead:
https://launchpad.net/signon-ui
Arch has signon-ui 0.17, released on August 2015 f
https://bugs.kde.org/show_bug.cgi?id=420280
Bernie Innocenti changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=458746
--- Comment #2 from Bernie Innocenti ---
I figured out that the problem occurs when importing a WireGuard conf file with
IPv6 routes (Interface / Address contains IPv6 routes).
In this case, IPv6 / Method is switched to Manual, but the address list
https://bugs.kde.org/show_bug.cgi?id=458746
Bernie Innocenti changed:
What|Removed |Added
Platform|Archlinux |Fedora RPMs
Version|5.25.4
https://bugs.kde.org/show_bug.cgi?id=458746
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
Status
https://bugs.kde.org/show_bug.cgi?id=467772
Bernie Innocenti changed:
What|Removed |Added
Version|5.27.2 |5.27.6
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=467772
Bernie Innocenti changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=469465
--- Comment #4 from Bernie Innocenti ---
The message seems to come from gtk3-3.24.37-1.fc38.x86_64
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469465
--- Comment #3 from Bernie Innocenti ---
.config/gtk-3.0/gtk.css contains only this one line:
```
@import 'colors.css';
```
The offending lines seem to be from /usr/share/themes/Breeze/gtk-3.0/gtk.css
1649 and 1652:
```
1648 .normal-icons {
1649
https://bugs.kde.org/show_bug.cgi?id=469465
Bernie Innocenti changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469465
Bug ID: 469465
Summary: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size'
is not a valid property name
Classification: Plasma
Product: Breeze
Version: 5.27.4
Platform:
https://bugs.kde.org/show_bug.cgi?id=466845
Bug ID: 466845
Summary: kdialog crashed when clicking on parent directory
Classification: Applications
Product: kdialog
Version: 22.12.2
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=465613
--- Comment #2 from Bernie Innocenti ---
Stacktrace looks similar to https://bugs.kde.org/show_bug.cgi?id=425025
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465613
--- Comment #1 from Bernie Innocenti ---
Saw this in the console just before the crash:
ASSERT: "!term.isEmpty()" in file
/home/bernie/kde/src/baloo/src/engine/postingdb.cpp, line 75
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=465613
Bug ID: 465613
Summary: Crash in Baloo::PostingDB::get
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=256242
Bernie Innocenti changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=436318
--- Comment #21 from Bernie Innocenti ---
(In reply to devsk from comment #20)
> Or the devs you already have are interested only in next shiny thing than to
> fix bugs in their code...:-) Sure, we can't force devs to stick around
> foreve
https://bugs.kde.org/show_bug.cgi?id=459626
Bernie Innocenti changed:
What|Removed |Added
Summary|Plasmashell crashes due to |Plasmashell crashes due
https://bugs.kde.org/show_bug.cgi?id=370204
--- Comment #6 from Bernie Innocenti ---
Forgot to mention that I'm using a Wayland session and I'm using IBus rather
than XIM...
In case kimpanel isn't supposed to be used in this session, would it be
possible to hide it from the widgets list
https://bugs.kde.org/show_bug.cgi?id=370204
--- Comment #5 from Bernie Innocenti ---
Created attachment 152401
--> https://bugs.kde.org/attachment.cgi?id=152401=edit
ximpanel in Plasma 5.25.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370204
Bernie Innocenti changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=370204
--- Comment #4 from Bernie Innocenti ---
With Plasma 5.25.5, I see no icon at all for the Input Method widget
(ximpanel). Tested both on ArchLinux and on Fedora 37 beta.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459626
--- Comment #1 from Bernie Innocenti ---
plasmashell does *not* crash when using Plasma 5.25.5 Wayland session with the
same config.
Looks like a 5.26 regression introduced a few days or weeks ago.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=459626
Bug ID: 459626
Summary: Plasmashell crashes due to an Assertion failure in
screencasting.cpp
Classification: Plasma
Product: plasmashell
Version: master
Platform: Archlinux
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #10 from Bernie Innocenti ---
Better debug trace:
2022-09-04 21:42:40.000 HTTPProtocol::readBody:4454: EOD received! Left = "0"
2022-09-04 21:42:40.000 HTTPProtocol::cacheFileClose:4875:
HTTPProtocol::cacheFileClose()
2022-0
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #9 from Bernie Innocenti ---
I can reproduce this crash in plasma-discover too, it just takes longer because
the keep-alive timeout is 60 seconds instead of 5 seconds.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #8 from Bernie Innocenti ---
As you can see from the timestamps, there's a gap of 5 seconds between the end
of the request in HTTPProtocol::readBody() and the keepalive timeout:
Sep 04 20:59:10 goreboot kioslave5[173862
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #7 from Bernie Innocenti ---
I enabled debug logging in kio/src/ioslaves/http/http.cpp, and this is what I
got:
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sending Header:
Sep 04 20:59:09 goreboot kioslave5
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #6 from Bernie Innocenti ---
Ok, perhaps something is special about the virtual override in
HTTPProtocol::special() ?
As far as I understand, `HTTPProtocol::httpClose(keepAlive = true)` will set
timeoutData to 99, which causes special
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #5 from Bernie Innocenti ---
This is the MR: https://invent.kde.org/frameworks/kio/-/merge_requests/946
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458448
Bernie Innocenti changed:
What|Removed |Added
CC||sit...@kde.org
--- Comment #4 from Bernie
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #3 from Bernie Innocenti ---
This is the check that fails:
194 void verifyState(const char *cmdName)
195 {
196 KIO_STATE_ASSERT(finalState(),
197 Q_FUNC_INFO,
198
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #2 from Bernie Innocenti ---
I have 90 of these crashes in /var/lib/systemd/coredump/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458448
Bug ID: 458448
Summary: timeoutSpecialCommand() did not call finished() or
error()! Please fix the kio_http KIO slave
Product: frameworks-kio
Version: git master
Platform:
https://bugs.kde.org/show_bug.cgi?id=455575
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #23 from
https://bugs.kde.org/show_bug.cgi?id=443706
Bernie Innocenti changed:
What|Removed |Added
Version|5.23.90 |5.24.4
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454919
--- Comment #2 from Bernie Innocenti ---
I suspect Elite Dangerous triggers the bug by using a different screen
resolution when running full-screen.
I tried a different game on Steam, and switching between the game and the
desktop did not crash kwin
https://bugs.kde.org/show_bug.cgi?id=454919
--- Comment #1 from Bernie Innocenti ---
Journal:
```
Jun 05 23:28:15 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a
screencast cursor update because the compositor is slow
Jun 05 23:28:15 goreboot kwin_wayland[47828]: kwin_screencast
https://bugs.kde.org/show_bug.cgi?id=454919
Bug ID: 454919
Summary: ASSERT: "d->m_texture" in file
kwin/src/libkwineffects/kwingltexture.cpp, line 451
Product: kwin
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=453558
Bernie Innocenti changed:
What|Removed |Added
Version|5.91.0 |5.93.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=453558
--- Comment #1 from Bernie Innocenti ---
I can also reproduce the bug on Arch Linux with everything built from sources
(pre-5.26).
(but not bumping to CONFIRMED because I'm the reporter)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=453558
Bug ID: 453558
Summary: Floating (detached) Qt toolbar can't be dragged nor
re-attached to window
Product: frameworks-kwayland
Version: 5.91.0
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #25 from Bernie Innocenti ---
(In reply to Nate Graham from comment #23)
> Indeed, it is likely that this is the same as Bug 449948, which says that
> the issue is 100% reproducible if kwin_wayland has crashed and restarted
> auto
https://bugs.kde.org/show_bug.cgi?id=450950
Bernie Innocenti changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=450950
--- Comment #2 from Bernie Innocenti ---
Created attachment 147647
--> https://bugs.kde.org/attachment.cgi?id=147647=edit
knewstuff offering to download either v25 or v26
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451088
--- Comment #8 from Bernie Innocenti ---
Created attachment 147645
--> https://bugs.kde.org/attachment.cgi?id=147645=edit
screenshot for the plasma widgets explorer
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451088
Bernie Innocenti changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |ad...@leinir.dk
Component
https://bugs.kde.org/show_bug.cgi?id=15329
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=439135
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=436318
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=449948
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #22 from Bernie Innocenti ---
I wonder if there's any relation to bug #449948?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450950
Bug ID: 450950
Summary: Discover installs older version of "Win7 Volume Mixer"
instead of latest available
Product: Discover
Version: master
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=450949
Bug ID: 450949
Summary: Discover crashed in KNSBackend while uninstalling a
plasma widget
Product: Discover
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=425265
--- Comment #2 from Bernie Innocenti ---
Related bugs: #450948 and #413516
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413516
--- Comment #2 from Bernie Innocenti ---
Related bugs: #450948 and #425265
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450948
Bug ID: 450948
Summary: No installable candidates in the KNewStuff entry "..."
with id "..." on the backend "plasmoids.knsrc"
Product: Discover
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=425265
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
Status
https://bugs.kde.org/show_bug.cgi?id=413516
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=427739
--- Comment #4 from Bernie Innocenti ---
I filed this upstream NetworkManager bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/934
I feel that plasmashell also shouldn't block the whole UI while waiting for a
reply from
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #20 from Bernie Innocenti ---
I'm running Fedora 36 with Plasma 5.24.0 and I just installed the updates to
5.24.1.
I was going to restart the session to start using the updated desktop
components, but I hit this bug again.
ksmserver
https://bugs.kde.org/show_bug.cgi?id=415927
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=389935
Bernie Innocenti changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=415927
Bernie Innocenti changed:
What|Removed |Added
CC||nortex...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=389935
--- Comment #7 from Bernie Innocenti ---
Ok, this is just QColorDialog, and the color picker is still broken in Qt
6.2.3, as can be seen by running this example app:
/usr/lib64/qt6/examples/widgets/dialogs/standarddialogs/standarddialogs)
--
You
https://bugs.kde.org/show_bug.cgi?id=389935
Bernie Innocenti changed:
What|Removed |Added
Product|kcolorchooser |frameworks-kdelibs4support
https://bugs.kde.org/show_bug.cgi?id=389935
Bernie Innocenti changed:
What|Removed |Added
Platform|Neon Packages |Fedora RPMs
CC
https://bugs.kde.org/show_bug.cgi?id=450595
--- Comment #1 from Bernie Innocenti ---
Created attachment 146956
--> https://bugs.kde.org/attachment.cgi?id=146956=edit
file dialog with rendering issues
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450595
Bug ID: 450595
Summary: File list rendering glitches when scrolling / hovering
Product: frameworks-kio
Version: 5.91.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=368723
Bernie Innocenti changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=434968
Bernie Innocenti changed:
What|Removed |Added
Version|5.23.5 |5.24.0
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=449728
--- Comment #1 from Bernie Innocenti ---
Created attachment 146373
--> https://bugs.kde.org/attachment.cgi?id=146373=edit
Screenshot of Battery in Device Viewer
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449728
Bug ID: 449728
Summary: Battery "plugged in but still discharging" message
while not plugged in
Product: Powerdevil
Version: 5.23.90
Platform: Fedora RPMs
OS:
https://bugs.kde.org/show_bug.cgi?id=448517
Bernie Innocenti changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #11 from Bernie Innocenti ---
It just happened to me again with plasmashell from
plasma-workspace-5.23.90-2.fc36.x86_64.
Just before this, I did "something" that made the panel miss some button
release event, and th
https://bugs.kde.org/show_bug.cgi?id=434968
--- Comment #12 from Bernie Innocenti ---
Did someone just fix it?
I can no longer reproduce this on my desktop, which runs KDE built from git.
Still present in Fedora Rawhide, which runs 5.23.90
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #7 from Bernie Innocenti ---
I captured the the journal just before a plasmashell crash:
---cut---
trying to show an empty dialog
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.svg: :303:258: Could not add child
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #6 from Bernie Innocenti ---
Created attachment 145783
--> https://bugs.kde.org/attachment.cgi?id=145783=edit
Plasmashell freezing when you click Logout.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448517
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=434976
--- Comment #6 from Bernie Innocenti ---
(In reply to Nicolas Fella from comment #5)
> Please report this to Pipewire. Plasma is not involved in determining where
> audio should play, except for the case where the user explicitly moves a
&g
https://bugs.kde.org/show_bug.cgi?id=448150
--- Comment #4 from Bernie Innocenti ---
(In reply to Nate Graham from comment #1)
> That's expected; as of Bug 415073 it should still appear as long as there
> are any brightness controls in it. Is that the case for your
https://bugs.kde.org/show_bug.cgi?id=448150
--- Comment #3 from Bernie Innocenti ---
Created attachment 145741
--> https://bugs.kde.org/attachment.cgi?id=145741=edit
Empty Battery and Brightness popup
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448150
--- Comment #2 from Bernie Innocenti ---
Created attachment 145740
--> https://bugs.kde.org/attachment.cgi?id=145740=edit
battery applet icon with "X"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434968
Bernie Innocenti changed:
What|Removed |Added
Version|5.21.4 |5.23.5
Version Fixed In|5.22
https://bugs.kde.org/show_bug.cgi?id=434968
Bernie Innocenti changed:
What|Removed |Added
Resolution|FIXED |---
Summary|Snap-to-border halo
https://bugs.kde.org/show_bug.cgi?id=448150
Bug ID: 448150
Summary: Battery applet shown in system tray even if there are
no batteries
Product: plasmashell
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=443706
Bernie Innocenti changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=446830
--- Comment #2 from Bernie Innocenti ---
#4 0x77d2a7ef in Konsole::ViewManager::splitView (this=0x55827c20,
orientation=Qt::Horizontal)
at /home/bernie/kde/src/konsole/src/ViewManager.cpp:603
603 Q_ASSERT(currentSessionId >
https://bugs.kde.org/show_bug.cgi?id=446830
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
Status
https://bugs.kde.org/show_bug.cgi?id=442371
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=446501
--- Comment #4 from Bernie Innocenti ---
> Hmm, I tried reproducing this bug, and I hit another error:
Could you re-run plasma-discover under gdb and get a stack trace?
Is the plasma-discover-flatpak package installed? Any other backe
https://bugs.kde.org/show_bug.cgi?id=435161
--- Comment #10 from Bernie Innocenti ---
Just to be clear: I could 100% reproduce the crash in baloo_file with these
directory operations in my home:
cd ~
mkdir foo <- CRASH!
mv foo bar <- CRASH!
chmod -x bar <- CRASH!
https://bugs.kde.org/show_bug.cgi?id=435161
--- Comment #8 from Bernie Innocenti ---
On a tangential note, why didn't the autotests catch this regression?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435161
--- Comment #7 from Bernie Innocenti ---
I don't see how these asserts could have ever worked in the past. I traced back
the pathnames, and the '/' is appended to all directories with
normalizeTrailingSlash():
https://invent.kde.org/frameworks/baloo
1 - 100 of 145 matches
Mail list logo