https://bugs.kde.org/show_bug.cgi?id=486210
Bug ID: 486210
Summary: Missing future-proofing "fix" for clang >= 16
Classification: Frameworks and Libraries
Product: Phonon
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=274170
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #21 from RJVB
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #260 from RJVB ---
(In reply to Nate Graham from comment #259)
> Is there such an option for GTK and/or other toolkits?
How is that relevant if KDE already has a sync service that apparently does
what I'm suggesting? I have no idea w
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #258 from RJVB ---
(In reply to brenbarn from comment #257)
> (In reply to Nate Graham from comment #253)
> > "ALERT! Changing this only affects KDE apps! It will not affect the way
> > dates are expresse
https://bugs.kde.org/show_bug.cgi?id=330356
--- Comment #42 from RJVB ---
On Thursday January 05 2023 09:23:08 Filipe Azevedo wrote:
>My issue is not that the panel remain visible as per say, but that a ghost of
>it remain on the desktop, so clicking this ghost does nothing.
>From w
https://bugs.kde.org/show_bug.cgi?id=141267
--- Comment #25 from RJVB ---
Created attachment 153715
--> https://bugs.kde.org/attachment.cgi?id=153715=edit
kwalletd "make foreground" patch (for 5.60.0)
Ensures that the pw dialog always opens in front.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=141267
--- Comment #24 from RJVB ---
Password dialogs aren't FS modal on MSWin nor the Mac OS (except the ones
unlocking the screensaver).
I run self-built frameworks, patched for my convenience (convictions, etc).
I'll attach the one I use to ensure
https://bugs.kde.org/show_bug.cgi?id=141267
--- Comment #21 from RJVB ---
I can see how that could be an advantage to some people, but it'd be a no-go
for me. If something wants me to enter a password
1) I want to be able to let that pend while I finish something else (could be
watching a movie
https://bugs.kde.org/show_bug.cgi?id=401600
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
--- Comment #3 from RJVB ---
I have
https://bugs.kde.org/show_bug.cgi?id=337356
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=413876
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=408725
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=419831
RJVB changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=412469
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #7 from RJVB ---
Because my system doesn't run anything newer than Qt 5.9
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #5 from RJVB ---
Besides being in the MacPorts camp HB still wouldn't allow me to run Qt 5.15 .
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #3 from RJVB ---
That's going to be tricky because KInit is a tier-3 fw and I am still blocked
on 5.60.0 on my Mac. I'll see if any relevant changes have been made to the
code paths involved here, to what extent I can backport them and what
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #222 from RJVB ---
Doesn't Qt have to be configured to use ICU, or is that only on non-linux/unix
platforms (Mac included)?
ICU uses hardcoded locale definitions?
FWIW, the specialty library approach I mentioned could of course provide
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #219 from RJVB ---
And what happened to the "there are no [more] KDE apps" (certainly not as
opposed to "mere" Qt apps) I got whacked with only a few years back, when the
KF5 frameworks were nothing more and not
https://bugs.kde.org/show_bug.cgi?id=439639
--- Comment #7 from RJVB ---
Not broken, just not updated. At least, that was the case in July 2021. I've
had it working for some time since but it seems something may have changed yet
again.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #47 from RJVB ---
> The problem is that currentIndex is 0 and it never bails out. This is with
> the very latest release.
IIRC this is one of the things my patch addresses.
--
You are receiving this mail because:
You are watching a
)
Qt Version: 5.9.8
Frameworks Version: 5.60.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Windowing system: X11
Distribution: Ubuntu 14.04.6 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I quit KDevelop. I have my personal patch that helps
https://bugs.kde.org/show_bug.cgi?id=450529
--- Comment #5 from RJVB ---
Erm, if the digiKam version is too old to run on 12.x it probably shouldn't run
at all, not simply lose all settings and then work again after resetting them.
And if an update of digiKam itself causes this kind of factory
https://bugs.kde.org/show_bug.cgi?id=450529
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB
https://bugs.kde.org/show_bug.cgi?id=353935
--- Comment #5 from RJVB ---
(In reply to Christoph Cullmann from comment #4)
> This got fixed long ago.
Any idea when (roughly)?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448092
--- Comment #21 from RJVB ---
Given how I remember having experienced this issue but cannot find any trace of
having found a fix, I'd say it's still there and just doesn't express itself
(like any self-respecting Heisenbug ;) )
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=412529
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |MOVED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #43 from RJVB ---
I also am continuing to get hangs on exit, but a while back I implemented a
failsafe, a simple timer that raises a SIGHUP if the application doesn't exit
normally within 1 minute after starting the final cleanup. Nowadays
https://bugs.kde.org/show_bug.cgi?id=448092
--- Comment #14 from RJVB ---
Is it possible that not all debug information is included in the app bundle?
This ticket has been ringing a bell for me, I seem to recall getting a crash
under similar conditions long ago, on my Intel Mac. Sadly (or maybe
https://bugs.kde.org/show_bug.cgi?id=372638
--- Comment #6 from RJVB ---
Ah, the diplomatic approach ... and now we wait for someone to complain that
s/he doesn't know what a disk is? ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375548
--- Comment #3 from RJVB ---
Sorry, no idea, I'm stuck at 5.60.0 for now. That version does still have
issues with the context menu in KTextEditor views, especially in KDevelop.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448092
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #5 from RJVB
https://bugs.kde.org/show_bug.cgi?id=413025
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #203 from RJVB ---
Since blaming all of this on Qt is the default: you can actually hire them to
implement or change something in Qt.
Personally I think that the fact that KDE is built on Qt doesn't change the
fact that Qt =/= KDE
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #187 from RJVB ---
(In reply to Nate Graham from comment #182)
> To my knowledge, fixing this requires one of the following:
> 1. Change the Qt locale system to support the feature
> 2. Abandon the-in Qt locale system for this and
https://bugs.kde.org/show_bug.cgi?id=382013
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=446721
Bug ID: 446721
Summary: Figuring out "The file or folder \"\" does not exist"
popup
Product: frameworks-kio
Version: 5.60.0
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=361958
--- Comment #9 from RJVB ---
Sure, and if you run it on different machines you remove a few other potential
possibilities for unexpected or at least unwanted interaction.
IOW, it (partly) defeats the purpose of being able to open several projects
https://bugs.kde.org/show_bug.cgi?id=446319
--- Comment #2 from RJVB ---
This doesn't just apply to "super old Qt" of course,but whatever :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446319
Bug ID: 446319
Summary: [Proposal] legacy Qt5 branch
Product: qca
Version: Git
Platform: Other
OS: All
Status: REPORTED
Severity: wishlist
Priority:
https://bugs.kde.org/show_bug.cgi?id=442674
Bug ID: 442674
Summary: Extension side-effects on unsupported platforms
Product: plasma-browser-integration
Version: unspecified
Platform: Other
OS: macOS
Status:
https://bugs.kde.org/show_bug.cgi?id=403913
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #8 from RJVB ---
Isn't
https://bugs.kde.org/show_bug.cgi?id=440580
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #2 from RJVB
https://bugs.kde.org/show_bug.cgi?id=440466
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #2 from RJVB
https://bugs.kde.org/show_bug.cgi?id=405556
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB
https://bugs.kde.org/show_bug.cgi?id=439091
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=438201
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #11 from RJVB
https://bugs.kde.org/show_bug.cgi?id=439639
--- Comment #4 from RJVB ---
Also, kaccnt-providers-git/providers/google.provider.in has the following:
```
o/oauth2/auth?access_type=offlineapproval_prompt=force
o/oauth2/token
http://localhost/oauth2callback
https://bugs.kde.org/show_bug.cgi?id=439639
RJVB changed:
What|Removed |Added
Summary|kio-gdrive (built against |kio-gdrive (built against
|qtkeychain
https://bugs.kde.org/show_bug.cgi?id=439639
--- Comment #2 from RJVB ---
Restarting kdeinit5 from a terminal gives me some useful output (finally). I'm
seeing
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
but also
kf5.kio.core: error() called twice! Please fix
https://bugs.kde.org/show_bug.cgi?id=439639
--- Comment #1 from RJVB ---
Actually, it would seem that I need to re-authenticate each time the kwallet
has been closed. Does that mean some crucial information is not being stored
there?!
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=439639
Bug ID: 439639
Summary: kio-gdrive (built against qtkeychain!) not allowed to
connect via "Akonadi Resources for Google Services"
and needs regular re-authentication with a private
https://bugs.kde.org/show_bug.cgi?id=438981
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB ---
I
https://bugs.kde.org/show_bug.cgi?id=419967
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #7 from RJVB
https://bugs.kde.org/show_bug.cgi?id=439611
Bug ID: 439611
Summary: libkdcraw should propagate the ${LIBS} from libraw.pc
Product: libkdcraw
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=439492
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=439491
RJVB changed:
What|Removed |Added
Resolution|WORKSFORME |UPSTREAM
--- Comment #3 from RJVB ---
my bad, I must
https://bugs.kde.org/show_bug.cgi?id=439491
RJVB changed:
What|Removed |Added
Blocks||439492
See Also
https://bugs.kde.org/show_bug.cgi?id=439492
Bug ID: 439492
Summary: TextCreator::create() crashes in QSyntaxHighligher.
Product: kio-extras
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=439491
Bug ID: 439491
Summary: SyntaxHighlighter::SyntaxHighlighter(QObject*) should
NOT use a default nullptr
Product: frameworks-syntax-highlighting
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #4 from RJVB ---
Well, this is strange, I'm convinced that DrKonqi showed me a backtrace of the
same bug, but I must have gotten confused.
I am positive though that it didn't suggest bug 415340 - evidently I would not
have filed another
https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #1 from RJVB ---
And FWIW, PageView::capability() needs to check every one of the QActions in
the d-ptr before accessing them, because aViewContinuous, aViewMode and
aTrimMargins can all turn out to be a nullptr.
Add a qDebug if you want
Version: 5.9.8
Frameworks Version: 5.60.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Windowing system: X11
Distribution: Ubuntu 14.04.6 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I had checked the Print Preview and closed it by hitting
https://bugs.kde.org/show_bug.cgi?id=430949
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #53 from RJVB ---
FWIW
https://bugs.kde.org/show_bug.cgi?id=434430
Bug ID: 434430
Summary: useless warning messages about markup
Product: frameworks-ki18n
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=352883
RJVB changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=349475
RJVB changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=356585
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=342962
RJVB changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=355452
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=355432
RJVB changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=343778
RJVB changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=347112
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=371489
--- Comment #16 from RJVB ---
And I said create two ADDITIONAL styles, one smaller, one larger, so that all 3
camps (assuming there are indeed 3) have a choice.
But it should be possible to make the padding (as well as the size of elements)
scalable
https://bugs.kde.org/show_bug.cgi?id=371489
--- Comment #14 from RJVB ---
(In reply to Nate Graham from comment #12)
> I don't think this is an actionable issue, sorry. :( There is a vocal
> contingent of users on both sides of this issue: right now, we get bug
> reports and compla
https://bugs.kde.org/show_bug.cgi?id=387061
--- Comment #45 from RJVB ---
(In reply to Wolfgang Bauer from comment #44)
> I do use QtWebKit with konqueror, and opening large OBS logs (which are just
> text files) do take a while.
TBH, Konqueror is such a multipurpose tool that I have n
https://bugs.kde.org/show_bug.cgi?id=387061
--- Comment #43 from RJVB ---
(In reply to Wolfgang Bauer from comment #42)
> Have you tried in Chromium though? (which is what QtWebEngine is based upon)
Current versions of Firefox tend to consume more memory than Chromium - in
fact,I underst
https://bugs.kde.org/show_bug.cgi?id=387061
--- Comment #39 from RJVB ---
A pure text email of 35Mb is massive too, but eating around 4Gb of RAM for that
isn't just massive. That's what you meant, right, not 4Mb for displaying just
the part that fits in your window (which would seem reasonable
https://bugs.kde.org/show_bug.cgi?id=393416
--- Comment #59 from RJVB ---
I indeed did not implement any kind of event handling, if memory serves me well
the backend just queries the current state. My argument was that there was
little reason to implement event handling (or indeed support
https://bugs.kde.org/show_bug.cgi?id=393416
--- Comment #55 from RJVB ---
Hi Gilles,
Better new year to you too (I'm calling it 2020bis for the time being...) ;)
No, I haven't contined work on the Mac backend for Solid. I was under the
impression that I mapped just about all the relevant
https://bugs.kde.org/show_bug.cgi?id=430714
Bug ID: 430714
Summary: KDevelop: QML icon load failure in Welcome plugin
messes up icon loading elsewhere
Product: kdevelop
Version: git master
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=429962
--- Comment #2 from RJVB ---
Any idea why adding a slot in the ExpandingTree class didn't work?
I didn't expect that you'd be doing some additional code maintenance, or I
would have suggested that it would be nice if one could close the drop-down
menu
https://bugs.kde.org/show_bug.cgi?id=429962
Bug ID: 429962
Summary: KDevelop/quickopen : QMetaMethod::invoke prints error
message
Product: kdevplatform
Version: git master
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=429815
RJVB changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=429815
--- Comment #5 from RJVB ---
Apologies, my bad. The failure is in DebugSession::handleVersion() in
plugins/gdb/debugsession.cpp (line 288 to be precise).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429815
--- Comment #3 from RJVB ---
> it's a bit of a mystery to me why the code builds as is.
Got that: newer versions of QVersionNumber::fromString() can take a
QStringView, which has a ctor taking a QStringRef.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=429815
--- Comment #2 from RJVB ---
I don't think we have to be concerned with the potential additional overhead of
creating a copy of the string as `toString()` appears to do? I don't see
anything about a new cast operator in the Qt 5.15 documentation
https://bugs.kde.org/show_bug.cgi?id=429815
RJVB changed:
What|Removed |Added
Version|unspecified |git master
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=429815
Bug ID: 429815
Summary: #8831937ffe4 broke compatiblity with older Qt5
versions
Product: kdevelop
Version: unspecified
Platform: Other
OS: Other
https://bugs.kde.org/show_bug.cgi?id=374722
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=370257
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=369207
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=381544
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=398750
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=384866
--- Comment #2 from RJVB ---
I don't think it's a good idea to handle GUI events anywhere but on the main
thread - on Mac at least. Unless you meant to call KDirWatch::addDir() on its
own thread?
This ticket is 2 years old. It's not impossible that I
https://bugs.kde.org/show_bug.cgi?id=378523
--- Comment #78 from RJVB ---
I should have seen the Phab PR above or at least the previous comment, but
somehow didn't.
Why only strip the Regular styleName? The property is redundant at best and I
think that the synthetic font argument applies
https://bugs.kde.org/show_bug.cgi?id=426190
Bug ID: 426190
Summary: [KDevelop] : C++ code highlighter glitch
Product: kdevelop
Version: 5.5.80
Platform: Compiled Sources
OS: All
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=330356
--- Comment #34 from RJVB ---
Re: mouse-over: I used to be able to get the panel to hide (or go under) again
by waving the mouse over it.
I wonder, wouldn't it be a solution to add a setting to tell panels never to
bring themselves to the front
https://bugs.kde.org/show_bug.cgi?id=425560
--- Comment #13 from RJVB ---
(In reply to tcanabrava from comment #12)
> on eachothers backs.
Are you sure that's what you wanted to say?
> Yes, it does come as a surprise for me, as those blogs are federated on the
> planet, and the
https://bugs.kde.org/show_bug.cgi?id=425560
--- Comment #11 from RJVB ---
(In reply to tcanabrava from comment #10)
> This specific feature has been showcased on the kde app release news, my
> blogpost about changes in konsole and nate's "kde weekly blogpost", so it's
> no
1 - 100 of 1336 matches
Mail list logo
