Crashes
by Steve Grubb
Hello,
I was curious about something. KDE has its own crash handling system.
How does this community track any metrics around code stability if
upstream gets reports? Kontact has segfaulted 20 times on me today.
Each time it says it cannot generate a bug report. Abrtd does not seem
to pick up anything. Shouldn't it? How does this community track
when a recent update suddenly starts making things crash? Kontact was
fine 3 weeks ago. I updated today (3 weeks of patches) and its crashing
all the time to the point its unusable. It won't generate a bug report,
abrtd seems not to notice either.
-Steve
3 years, 3 months
nntp (aka, usenet) client in kde?
by Gene Smith
I currently use t-bird with an nntp account pointing to gmane to read
this list and sereral others. Does kde have an nntp client program of
any sort? I don't see it as a possible new account type in kmail. Also,
search with kpackagekit yields nothing with "usenet" or "nntp" that is
kde specific.
-gene
3 years, 9 months
KDE Telepathy Bonjour account: This IM Account cannot be created - a
Telepathy Connection Manager named 'salut' is missing or it cannot
handle
protocol 'local-xmpp'. Please try installing salut with your package manager.
by Dennis Schridde
Hi!
I was trying to setup a Bonjour (local XMPP) account in KDE Plasma System Settings for KDE Telepathy. In `System Settings > Online Accounts > Create`, I clicked "Bonjour" in the list on the right. This action was answered with an error dialogue box: "This IM Account cannot be created - a Telepathy Connection Manager named 'salut' is missing or it cannot handle protocol 'local-xmpp'. Please try installing salut with your package manager." However, `telepathy-salut` is already installed on my machine. Does anyone have an idea how to debug this, or where I would find the actual error message that led to this?
I am using Fedora 27 KDE, with telepathy-salut currently being at version 0.8.1 (release 12.fc27), telepathy-mission control at version 5.16.4 (epoch 1, release 4.fc27) and ktp-accounts-kcm at version 17.12.1(release 1.fc27).
Best regards,
Dennis
4 years, 5 months
time to orphan/retire unmaintained uncommon kde4 language bindings?
by Rex Dieter
Looking over some broken deps reports, I came across some old packages:
kdebindings
smokeqt
smokekde
qyoto (csharp/mono)
kimono (csharp/mono)
ruby-qt
ruby-korundum
perl-Qt
Of these, the only one that's not a pure leaf package is perl-Qt (debconf-
kde depends on it).
any comment or objection to considering orphaning most (all minus
smokeqt/perl-Qt) or all of these ?
-- Rex
4 years, 6 months
Emacs key binding in KDE Plasma 5?
by Sherman Grunewagen
Just moved from Fedora 21 to F25. Under F21 I had a file ~/.gtkrc-2.0 which contained
gtk-key-theme-name = "Emacs"
This enabled basic Emacs cursor motion keyboard commands in text input boxes throughout KDE,
Firefox, &c. (Outside of input boxes, KDE shortcuts ruled.)
How can I get this same behaviour for Plasma 5 w/in F25? From reading around, I've created
~/.config/gtk-3.0/settings.ini
and inserted
[Settings]
gtk-key-theme-name = Emacs
in this empty file. This has given the desired result in Firefox and Thunderbird,
but not w/in arbitrary text boxes in KDE (e.g. Alt-F2). The ~/.gtkrc-2.0 file is still
intact, by the way. It seems to have no effect. Any ideas?
-Sherman
4 years, 6 months
KDE rebuild for RHEL8
by Troy Dawson
I know that RHEL8 isn't out yet, but I'd like to run KDE on my RHEL8
Beta. Even if it's just the basic KDE desktop.
I'm fine building it myself, but I'm having a hard time figuring out
the rebuild flow.
If I (or anyone) were to rebuild KDE for RHEL8, where do I start? and
then what's next?
There are base QT5 packages in RHEL8 beta. Do you think I would need
to rebuild QT5? Or just start with RHEL8's QT5 packages.
Thanks
Troy
4 years, 6 months
Re: "Basic graphics mode" feature and criterion discussion
by Kamil Paral
On Tue, Mar 26, 2019 at 9:31 PM Chris Murphy <lists(a)colorremedies.com>
wrote:
> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell, and sees no useful information on the screen
> that tells them why they're hung up; or even generically that "by now
> you should see a login screen and if you don't we've faceplanted
> somewhere, sorry".
>
> Maybe split the criterion:
>
> Basic criterion: installation media must have a basic video boot entry
> that uses the accepted fallback boot parameter(s), e.g. nomodeset. The
> criterion just means the media must have the menu entry, and that it
> passes something intentional for this purpose as a boot parameter.
>
Sounds good.
>
> Final criterion: installation media's basic video boot entry should
> either work (we get a successful graphical boot), or it should
> faceplant in some unambiguous way.
>
I'd rather require it to just work. Based on Ajax's response that the code
path is here to stay and they still need to support it because of VMs and
fresh new graphics cards.
4 years, 8 months
No sound over hdmi
by Alex Gurenko
Hello everyone, I found myself in a need to connect my Lenovo T460p laptop over HDMI to a TV and I have no sound going over HDMI.
I saw a thread about 4 months ago with no solution found back then.
I'm on Fedora 29 KDE, kernel 4.20.13-200.fc29.x86_64. I don't see that HDMI audio device becomes active neither via cli, no in gui. Video output works perfectly fine. I'm using bumblebee with nvidia proprietary drivers, not sure if that's relevant; aplay -l shows that HDMI is handled by intel's graphics:
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC293 Analog [ALC293 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
Found these two BZs [0][1] which kind of indicates it's been broken since F28:
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1684943
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1664816
Any ideas what can be done here?
4 years, 8 months