Re: Plasma 5 as a daily driver?
by Kevin Kofler
Duncan wrote:
> I haven't particularly minded the cashew here, especially after they
> changed it to fade out unless hovered over, but I never really understood
> why they insisted on it remaining for those really bothered by it, when
> its functionality was available elsewhere. So reading that there's an
> option to turn it off in plasma5 is good news, and given the option, I
> probably will as well.
kde-plasma-ihatethecashew does wonders on Plasma 4. :-)
> Of course, as you somewhat implied, one person's insignificant nitpick is
> someone else's absolutely critical feature, as the kde devs found out all
> too well in the kde3 -> kde4 upgrade. Thankfully, they're being less
> forceful about dropping support for what actually works in favor of new
> but broken stuff, this time around. If distros are forcing upgrades,
> that's on them and for me anyway could be a reason to switch distro, but
> at least the kde folks are being a bit more understanding about people's
> absolutely critical features, this time around, and continuing to provide
> at least minimal/security upgrades somewhat longer, for those who find
> their absolutely critical features are simply broken in the new version,
> and who thus need to wait awhile until they're either fixed or worst-case
> dropped as features entirely, so they know they have to find alternatives.
KDE upstream is actually no longer shipping any updates to kde-workspace
4.x, they even locked the repository to prevent everybody from committing
any fixes to it.
Kevin Kofler
7 years, 10 months
don't show list of users in sddm
by George Avrunin
Is there a way to get sddm to let the user type his/her username, and not
have a list of users showing on the login screen? I tried setting
HideUser, which did hide the listed users but I couldn't find any way for
one of those users to login. I'm sure I'm missing something obvious.
7 years, 10 months
Re: [kde] Plasma 5 as a daily driver?
by c. marlow
On 11/09/2015 01:40 PM, Ian Pilcher wrote:
> All in all, I find myself wondering if other people are really using
> Plasma 5 as a "daily driver" (or is my usage really so different that
> others aren't hitting these bugs).
Honestly I would say NO!
They ( the development staff) took out one feature that is keeping me on
KDE 4.
And that feature was called the multiple wallpapers on different
Virtural Desktops.
Now I didnt use multiple wallpapers, but I would put an Icon on one
desktop because thats the desktop I want that program to run on, and
then put another icon on another virtural desktop because thats where I
want that app to run. They the creators claim its because of " Security
Flaws and risks" my butt!
And when adding icons to the desktop they have this HORRIBLE clear box
around them in KDE 5, when you switch from Container view, to desktop
view and put my icons that I use the most on my desktop.
Christopher M
Running Kubuntu 14.04 and KDE 4.
7 years, 10 months
Re: Plasma 5 as a daily driver?
by Peter G.
Ian Pilcher wrote:
> I find myself wondering if other people are really
> using Plasma 5 as a "daily driver"...
It's a totally different world where I live :-) I've
been using Plasma 5 since the beta was released.
Excellent experience!
When the beta was first released, I noticed that there
was something curious about the virtual terminals, but
that appears to be long gone. It might just be that I
am using GDM, which is on Wayland, so it has claimed
vt1. In any case, all works fine.
I haven't yet plugged in my television, so I don't
know about having 2 displays yet. I really need to
give that a try. Perhaps tonight, since I rented a DVD
from the library ;-)
Konsole size? Is it that much of a problem to size it?
;-) I haven't given this a try, so I don't know
whether my system(s) is/are affected.
What used to be the ugly cashew is now known as the
Desktop Toolbox. I think it is entirely redundant,
since all of the commands it offers are accessible on
the right mouse button menu item Desktop Settings. You
can enable/disable the Desktop Toolbox on the Tweaks
page. I have always hated that thing, since it
disrupts the symmetry and aesthetics of the clean
desktop.
CapsLock is permanently disabled here. I have mapped
Compose to that key, which is useful to me. CapsLock
just caused me problems, getting hit by accident with
my thick fingers ;-)
I don't mean to discredit your/others' experience(s),
but it seems to me that a lot of people are nitpicking
about a lot of insignificant stuff. Oops! Did I say
that? :-O I guess if it's important to you ;-) but I
think we need to keep in mind that it's a work in
progress and the required functionality is all there.
I've never been a big fan of all the widgets anyway,
just a lot of clutter on the desktop and in the system
try. I guess for some of you it is important ;-)
7 years, 10 months
Re: Re: apper exclude packages?
by Jeremy Burcham
It upsets me enough to get rid of it and go with something else. No more
apper!
dnf remove apper
dnf install yumex-dnf
Done Son!
--
- Jeremy Burcham
7 years, 10 months
konsole: task suspended when change to VT
by Reindl Harald
what is that for new "feature" having a ssh-session with a active
command in console and switch to a VT with CTRL+ALT+F2 that the task is
supsended on the remote server?
that happened now while i went for a coffee as well as on the weekend
where i started a spamfirewall-train-script via SSH at 19:00 PM and
after come back home at 5:00 AM the next day switching back to the
desktop it continued work at the point i left the computer
the only explaination is that in the background a CTRL+Z signal is sent
when the desktop session is not active - why in the world?
7 years, 10 months
Panel autohide delay too long
by Orcan Ogetbil
On F-21. KDE 4.14.11.
The panels with autohide feature enabled take too long to appear when
I bring my mouse pointer to the edge of the screen. It takes about 1.5
seconds for the panel to appear.
Is this a feature? Does anyone know a way of configuring this? If
there is no such configuration, can someone familiar with the KDE
source tree point me to the code where this delay amount is hardcoded?
Thanks,
Orcan
7 years, 10 months
Plasmashell not starting anymore
by Florian Sievert
Dear all,
seems like today I pretty much hit the mine field. Fedora 23 KDE
experience is being so far the worsest release since 10 years easily.
There are so many seg faults occuring (krunner crashs all the time,
dolphin crash when using selection rectangle etc.). Now how plasmashell
suddenly freezed and denies to recover. I tried to find the
configuration and reset it, but I am not sure if I really found
everything so far (.cache, .config, .local/share). However it does not
fix the issue. Even when creating a new user the plasmashell seems to
immediatly freeze. I am running out of ideas what this might be caused.
When I am starting "plasmashell" from the console, it giving the
following messages, but not sure what exactly might be going wrong.
---
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
Known plasmoid ids: QHash(("org.kde.plasma.notifications",
11)("org.kde.plasma.networkmanagement", 21)("org.kde.plasma.battery",
18)("org.kde.plasma.mediacontroller", 19)("org.kde.plasma.bluetooth",
22)("org.kde.plasma.pkupdates", 16)("org.kde.plasma.printmanager",
12)("org.kde.ktp-contactlist", 20)("org.kde.plasma.devicenotifier",
13)("org.kde.plasma.clipboard", 17)("org.kde.plasma.volume",
15)("org.kde.kdeconnect", 14))
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to
assign [undefined] to QObject*
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:85: TypeError:
Cannot read property 'effectivePressed' of undefined
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to
assign [undefined] to QObject*
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:85: TypeError:
Cannot read property 'effectivePressed' of undefined
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ScrollArea.qml:48:
Error: Cannot assign to non-existent property "interactive"
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:286:
TypeError: Cannot read property '__wheelScrollLines' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:66:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:65:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:64:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:63:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:114:
TypeError: Cannot read property 'corner' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:91:
TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:91:
TypeError: Cannot read property of
null
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or
sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or
sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or
sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or
sibling.
Both point size and pixel size set. Using pixel
size.
Both point size and pixel size set. Using pixel
size.
Both point size and pixel size set. Using pixel
size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:428:5:
QML Text: Cannot anchor to a null item.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/clipboard.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/BluetoothApplet.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
networkmanager-qt: void
NetworkManager::NetworkManagerPrivate::propertiesChanged(const
QVariantMap&) Unhandled property "Devices"
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/StatusNotifierItem.qml:131:13:
QML Image: Failed to get image from provider: image://icon/
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/StatusNotifierItem.qml:131:13:
QML Image: Failed to get image from provider: image://icon/
---
Hoping that you guys might have an idea what to do in order to recover
from this?
Best regards,
Florian
7 years, 10 months
kde5 pager
by George Avrunin
I use an arrangement of 12 virtual desktops for different things I'm
working on, so the pager in the panel is too small to see. In kde 5, the
plasma pager widget seems to insist on having a right margin that, no
matter how I arrange the desktops (or how many I use) is blank; I can't
set it so that the images of the desktops actually fill the widget. So
there's desktop real estate that's wasted for this. That wasn't the case
with the pager in kde 4. I've encountered this on F22 and now on F23.
I searched (including looking around on kde.org) and I haven't been able to
find anything on this. Am I missing something, or is there some good
reason for the pager widget insisting on this extra blank space? I didn't
see any bugs filed for this, but I can file one in the Fedora and/or KDE
bugzillas.
(And the controls to change size, do settings, etc., only appear on the
right, even though I'd like to put the pager in the lower right corner
of my screen, but that's another issue.)
George
7 years, 10 months
