https://bugs.kde.org/show_bug.cgi?id=417241
--- Comment #3 from sombrag...@sombragris.org ---
Ok, if poppler is the culprit, why xpdf, atril and even the PDF component of
claws-mail do not crash? Why is just okular the one crashing??
Something does not add-up, honestly.
Not reopening but I
https://bugs.kde.org/show_bug.cgi?id=415914
--- Comment #4 from Christoph Feck ---
Nate, do you remember if it was discussed somewhere that
QSGTexture::setFiltering() crashes are caused by NVIDIA state?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417179
--- Comment #4 from Aaron Bottegal ---
Repackaged results:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efe553d6880 (LWP 1072))]
Thread 31
https://bugs.kde.org/show_bug.cgi?id=417241
--- Comment #2 from Yuri Chornoivan ---
Patch for poppler btw.
https://gitlab.freedesktop.org/poppler/poppler/commit/eaeac5c7dba6f53acef3f0be6b226facecfc5f28.diff
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407338
Yuri Chornoivan changed:
What|Removed |Added
CC||sombrag...@sombragris.org
--- Comment #12
https://bugs.kde.org/show_bug.cgi?id=417241
Yuri Chornoivan changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
https://bugs.kde.org/show_bug.cgi?id=413007
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=416638
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=413434
--- Comment #11 from Nate Graham ---
Cool, thanks. The bug report tracking that one is Bug 415606.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417239
--- Comment #1 from Michail Vourlakos ---
Send your Latte layout file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417237
Nate Graham changed:
What|Removed |Added
CC||k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417237
Nate Graham changed:
What|Removed |Added
Version|master |5.18.0
Target Milestone|1.0
https://bugs.kde.org/show_bug.cgi?id=413058
Christoph Feck changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417242
--- Comment #1 from Juraj ---
Created attachment 125720
--> https://bugs.kde.org/attachment.cgi?id=125720=edit
Message context menu example
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417242
Bug ID: 417242
Summary: Message is rendered as unread even when read
Product: kmail2
Version: 5.13.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=417241
Bug ID: 417241
Summary: Okular: crash on loading a document
Product: okular
Version: 1.9.1
Platform: Slackware Packages
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=414171
--- Comment #17 from Christoph Feck ---
Harold, could you please clarify if this ticket should get closed after comment
16?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417127
--- Comment #5 from Nate Graham ---
That's very strange. What are the permissions on the config file? Are they set
correctly?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414553
--- Comment #6 from Christoph Feck ---
The error messages point to a setup problem. Qt crashes (i.e. shows a fatal
error message), because it cannot find a platform plugin. I don't think you can
expect help for this issue if it cannot be reproduced
https://bugs.kde.org/show_bug.cgi?id=406587
--- Comment #15 from Albert Astals Cid ---
Can you please be more specific?
What gives the "Aborted due to failure." error?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402066
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417240
Bug ID: 417240
Summary: Report bug dialog selects wrong (default) version when
opening bugzilla
Product: kmail2
Version: 5.13.2
Platform: Archlinux Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #11 from frmdstryr ---
When I change the scaling to 1.0 and the menu's show up at the correct location
as well and I can't get it to crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417229
--- Comment #1 from Alexandre Pereira ---
Can this be a duplicate of https://bugs.kde.org/show_bug.cgi?id=416840 ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416180
MarcP changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #10 from frmdstryr ---
Created attachment 125717
--> https://bugs.kde.org/attachment.cgi?id=125717=edit
New crash information added by DrKonqi
kdevelop (5.5.0) using Qt 5.13.2
- What I was doing when the application crashed:
Sorry I
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #12 from Arjen Hiemstra ---
The default for the render loop is primarily based on platform. It will check
to see if threaded OpenGL is available and if so, default to the threaded
render loop. See
https://bugs.kde.org/show_bug.cgi?id=412463
Christoph Feck changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #11 from Rinigus ---
Thanks! I presume that variable is acquired from underlying video card. Do you
know how that's done?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413434
--- Comment #10 from Dan Leinir Turthra Jensen ---
(In reply to Nate Graham from comment #8)
> All right, I'll open a VDG/HIG discussion.
>
> In the meantime, can you fix the bug that makes the background of the bottom
> row use the wrong color? Even
https://bugs.kde.org/show_bug.cgi?id=415606
Patrick Silva changed:
What|Removed |Added
CC||giv...@gmail.com
--- Comment #8 from Patrick
https://bugs.kde.org/show_bug.cgi?id=417212
Patrick Silva changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=417213
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=417187
--- Comment #9 from Julian Seward ---
(In reply to Stefan Maksimovic from comment #8)
> > We pretty much agree with your analysis [..]
Good!
So .. last Sunday, in discussion at Fosdem, one of the three of you
(not sure who) suggested that this might
https://bugs.kde.org/show_bug.cgi?id=417221
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/kde/
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #10 from Arjen Hiemstra ---
It's a Qt only variable, GL has little to do with the render loop. Since you
mention flatpak, most likely that overrides or ignores the value.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=399831
--- Comment #6 from Luke-Jr ---
Upstream Chromium seems to have major security issues every month. QtWebEngine
gets updated far less frequently, and often goes months or longer vulnerable to
easily exploited issues.
Won't you reconsider, please?
--
https://bugs.kde.org/show_bug.cgi?id=417022
--- Comment #6 from olignomi ---
(In reply to Nate Graham from comment #5)
> Looks like everything's there. What exactly was the problem?
What information is expected to be displayed after double-clicking on nvme0n1?
On nvme0n1p1 and following
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #9 from Rinigus ---
QSG_RENDER_LOOP=basic has been tested and improved the performance. Sorry, that
we did a while ago while discussing at Plasma Mobile IRC. Question is where its
set in Qt or GL, so I could start digging into why its
https://bugs.kde.org/show_bug.cgi?id=417239
Bug ID: 417239
Summary: Auto hide panel mode of Latte Dock "flickers" when
bringing up the Application Menu widget
Product: lattedock
Version: 0.9.8.1
Platform: Archlinux
https://bugs.kde.org/show_bug.cgi?id=417016
--- Comment #7 from Dmitry Kazakov ---
Git commit 8f9386edc79ce4c104d646b60dc080f2c475a3cb by Dmitry Kazakov.
Committed on 06/02/2020 at 16:51.
Pushed by dkazakov into branch 'krita/4.2'.
Fix update of shape layer after cancelling transform tool
https://bugs.kde.org/show_bug.cgi?id=417016
--- Comment #7 from Dmitry Kazakov ---
Git commit 8f9386edc79ce4c104d646b60dc080f2c475a3cb by Dmitry Kazakov.
Committed on 06/02/2020 at 16:51.
Pushed by dkazakov into branch 'krita/4.2'.
Fix update of shape layer after cancelling transform tool
https://bugs.kde.org/show_bug.cgi?id=417233
Dmitry Kazakov changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=417079
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=417151
--- Comment #9 from Milian Wolff ---
quite probably this is a 4K issue then, can you try to see if it reproduces
when you set the scale factor to 1? Obviously it will look like crap, but I
want to see if that fixes the issue for you or not.
And again,
https://bugs.kde.org/show_bug.cgi?id=416285
--- Comment #1 from Stefan Maksimovic ---
Did anyone have a chance to take a look at this in the meantime?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417202
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #8 from Arjen Hiemstra ---
Alternatively, launch with QSG_RENDER_LOOP=basic
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #7 from Arjen Hiemstra ---
As David mentioned:
(In reply to David Edmundson from comment #3)
> You can test if it's the known vsync issue by setting the render loop to
> basic in kcmshell5 qtquicksettings
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417238
Bug ID: 417238
Summary: Test memcheck/tests/vbit-test fails on mips64 BE
Product: valgrind
Version: 3.15 SVN
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=417237
Bug ID: 417237
Summary: Brightness control at the login SDDM screen
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=417237
Postix changed:
What|Removed |Added
CC||n...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=417230
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=413434
--- Comment #9 from Nate Graham ---
Started a Phab task here: https://phabricator.kde.org/T12655
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=298801
--- Comment #2 from Harald Sitter ---
Quick update: seems statvfs outright makes up its own meaning
https://github.com/samba-team/samba/blob/8b04590e4d8f817ad6d194bb9d622c18734e3011/source3/libsmb/libsmb_stat.c#L420
without unix extension the actual
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #6 from Rinigus ---
Its ARM device, no nvidia here. As its using libhybris (originally Android
phone), no surprise if something is off on GL level. So, vsync suspicion makes
sense. Any tips on how I can check whether vsync works properly?
https://bugs.kde.org/show_bug.cgi?id=413434
--- Comment #8 from Nate Graham ---
All right, I'll open a VDG/HIG discussion.
In the meantime, can you fix the bug that makes the background of the bottom
row use the wrong color? Even if it's just a matter of putting a Rectangle the
window
https://bugs.kde.org/show_bug.cgi?id=408665
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=415867
--- Comment #15 from r...@gmx.de ---
Now with the latest version no crash at anytime.
But the Face-recognition does not work.
Faced detection is working fine.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416751
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=163121
--- Comment #23 from launch...@startport.com ---
I found a work-around:
https://pryp.in/blog/19/zoom-the-screen-with-alt-scroll-in-kde.html
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417137
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=417182
--- Comment #4 from Nate Graham ---
Does it work if you use Rectangular Region mode instead?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=298801
Harald Sitter changed:
What|Removed |Added
CC||sit...@kde.org
--- Comment #1 from Harald
https://bugs.kde.org/show_bug.cgi?id=408665
--- Comment #4 from b.raz...@gmail.com ---
I'm not able to reproduce it in 5.17, seems to be resolved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417187
--- Comment #8 from Stefan Maksimovic ---
(In reply to Stefan Maksimovic from comment #7)
> Thank you for your reply, Julian.
>
> We pretty much agree with your analysis of the initial SB sequence as well as
> the first and second speculative
https://bugs.kde.org/show_bug.cgi?id=417187
--- Comment #7 from Stefan Maksimovic ---
Thank you for your reply, Julian.
We pretty much agree with your analysis of the initial SB sequence as well as
the first and second speculative disassembly.
A note for the first speculative disassembly: you
https://bugs.kde.org/show_bug.cgi?id=254313
--- Comment #10 from Harald Sitter ---
This is already on my radar and I am talking with people about it. It's not an
easy change (because it requires some restructuring in kpmcore), it's also not
a quick change, and I do agree with Kai that it's not
https://bugs.kde.org/show_bug.cgi?id=417236
Bug ID: 417236
Summary: Crash when right-clicking a tab
Product: kile
Version: 2.9.92
Platform: Debian stable
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=398582
--- Comment #9 from caulier.gil...@gmail.com ---
Champagne,
After around 100 commit, digiKam compile and link fine with the Microsoft
Visual C++ compiler :
https://build.kde.org/job/Extragear/job/digikam/job/kf5-qt5%20WindowsMSVCQt5.14/
Now we can
https://bugs.kde.org/show_bug.cgi?id=254313
--- Comment #9 from Nate Graham ---
Then someone should care about it. :) The user's data is the most important
thing to care about. We should warn them if it's about to be destroyed by an
impending hardware failure.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=254313
--- Comment #8 from Kai Uwe Broulik ---
"easily reproducible" because we thrash hard disks left and right, don't we?
But yeah, if you think so.. it's just that this bug will come up every time
before a release and realistically nobody will care about
https://bugs.kde.org/show_bug.cgi?id=268685
Harald Sitter changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=254313
Nate Graham changed:
What|Removed |Added
Severity|wishlist|critical
CC|
https://bugs.kde.org/show_bug.cgi?id=261196
Harald Sitter changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |fa...@kde.org
Product|kio-extras
https://bugs.kde.org/show_bug.cgi?id=163121
launch...@startport.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=411196
Matthias Fabinski changed:
What|Removed |Added
CC||matthias@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=229817
Harald Sitter changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.kde.org/show_bug.cgi?id=212801
Harald Sitter changed:
What|Removed |Added
Summary|Bug: permissions on smb:/ |(remote) uids mapped to
https://bugs.kde.org/show_bug.cgi?id=417235
Bug ID: 417235
Summary: KDE Partition manager crashes when moving screens
after creating ant ext4 fs on a SanDisk Cruzer blade.
Product: partitionmanager
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=413434
--- Comment #7 from Dan Leinir Turthra Jensen ---
(In reply to Nate Graham from comment #6)
> Fair enough. I'll be on the lookout, but I haven't seen a KDE dialog with
> only a close button on the bottom row. Nearly all of them instead have one
> of
https://bugs.kde.org/show_bug.cgi?id=417233
Dmitry Kazakov changed:
What|Removed |Added
Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=392000
Patrick Silva changed:
What|Removed |Added
Summary|k3b always asks twice to|When "Burn image..."
https://bugs.kde.org/show_bug.cgi?id=417234
Bug ID: 417234
Summary: DVD cannot be played
Product: dragonplayer
Version: 19.04
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=417233
Dmitry Kazakov changed:
What|Removed |Added
CC||dimul...@gmail.com
--- Comment #1 from Dmitry
https://bugs.kde.org/show_bug.cgi?id=416874
Anon changed:
What|Removed |Added
CC||bugs.kde@getnada.com
--- Comment #7 from Anon ---
https://bugs.kde.org/show_bug.cgi?id=388120
Patrick Silva changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Summary|cannot burn audio
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #5 from Arjen Hiemstra ---
Since this is a Sailfish OS (so presumably ARM) device, I doubt that is going
to provide anything but "file not found". :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #4 from David Edmundson ---
Also, as I'm curious if we can fix it, output of
sudo cat /sys/module/nvidia_drm/parameters/modeset
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=417233
Bug ID: 417233
Summary: Transforming vector shapes > Wait a while
> Krita goes unresponsive. ("Krita.exe is not
responding...")
Product: krita
Version: nightly build
https://bugs.kde.org/show_bug.cgi?id=417232
Bug ID: 417232
Summary: Plasma crashed after adjusting weatherreport applet
Product: plasmashell
Version: 5.17.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #2 from Arjen Hiemstra ---
The most likely cause of this is a lack of vsync in whatever driver your system
uses. There are a few related bugreports, but for example
https://bugreports.qt.io/browse/QTBUG-59300 mentions how animations will
https://bugs.kde.org/show_bug.cgi?id=407129
--- Comment #5 from felixbra...@quicknet.nl ---
(In reply to Vlad Zahorodnii from comment #4)
> X11 or Wayland?
X11
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417206
kernel_panic changed:
What|Removed |Added
CC|vic.m.iva...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=417231
Bug ID: 417231
Summary: "Minimize all windows" widget does not work as
expected while K3b burns a disc
Product: plasmashell
Version: 5.17.90
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=254313
Serhiy Zahoriya changed:
What|Removed |Added
CC||serhiy@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=417230
Bug ID: 417230
Summary: ShowItems does not work if folder is already open
Product: dolphin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=417227
--- Comment #3 from Bart Ribbers ---
Well it doesn't cleanly apply on Plasma Workspace 5.17.5, probably because
startplasmacompositor nowadays is startplasma-wayland.
However, just running "startplasma-wayland" without "dbus-run-session" in a TTY
https://bugs.kde.org/show_bug.cgi?id=417229
Bug ID: 417229
Summary: Wayland Plasma crash on startup
Product: plasmashell
Version: master
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords:
101 - 200 of 285 matches
Mail list logo