KDE4 , I don't want kde4 I want kde4-workspace !
by Sérgio Basto
Hi,
As you may know we made some packages to maintain kde4 in F23 [1] and
[2] and now I prepare F24, but the more I dig, the more I am convinced
that what I want is kde4-workspace, instead plasma5-workspace, the rest
I use the system package. The short list of packages in my kde4 repo,
[1] 9, today I realize I can remove apper, because is the same of the
system, so less one , 8 .
In kde-baseapps the only thing I need to do, is re-enable build of
folderview package, the rest I could use the packages in the system, 7
.
Now the strange thing is kde-workspace package is built in koji , is
not retired but doesn't appears in repos !.
In conclusion if plasma5 workspace can coexist with kde(4)-workspace,
we could have the old "KDE4" in repos , and kde-workspace really work
well .
[1]
https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/packages/
[2]
https://copr.fedorainfracloud.org/coprs/peem/kde4-fedora/packages/
[3]
http://koji.fedoraproject.org/koji/packageinfo?packageID=13124
https://admin.fedoraproject.org/pkgdb/package/rpms/kde-workspace/
--
Sérgio M. B.
7 years, 1 month
ksmserver-logout-greeter seg faulting
by Ed Greshko
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often.
Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time:
10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer
logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not
provide a bug reporting address".
Has anyone seen this?
--
You're Welcome Zachary Quinto
7 years, 1 month
Kscreenlocker won't unlock
by Patrick O'Callaghan
On trying to login via the lockscreen, it gives no error but flashes
briefly and comes back again (i.e. is still locked). It's not a
password error. I have to use "loginctl unlock-sessions" from a console
to recover.
This is very recent (I update daily). The last update to kscreenlocker
was over a month ago so it must be some other component.
poc
7 years, 1 month
Re: How is Session Restore related to Autostart?
by Piotr Dobrogost
> ---------- Forwarded message ----------
> From: "Patrick O'Callaghan" <pocallaghan(a)gmail.com>
> To: kde(a)lists.fedoraproject.org
> Cc:
> Date: Wed, 05 Oct 2016 18:20:04 +0100
> Subject: How is Session Restore related to Autostart?
> I use Save Session with "Restore manually saved session" to try for a
> known desktop configuration on login. I say "try" because in various
> ways it doesn't completely work, as discussed in other threads. To
> attempt to get round some of the issues I also have a number of
> programs in Autostart, but it's never been clear to me what relation if
> any there is between these two things.
>
> Case in point: if I have program Foo in Autostart, but also save a
> session with Foo running, is the desktop after a new login expected to
> show two Foo instances or one (or none because of a conflict). Or is
> this simply not defined? Or does it depend on Foo itself?
Would like to know the answer for this, too.
When I turned restoring session on, all programs from autostart were
run when session was restored. I think autostart should be skipped
when restoring session.
Regards,
Piotr Dobrogost
7 years, 1 month
konsole
by Walter Cazzola
Dear all,
I'm using fedora 23 on my laptop and I was used to have always open two
konsole instances side by side each with different tabs and geometry
from working session to another.
But since the last update to konsole/KDE the two instances are not
saved/reopened correctly. At login I get two konsole instances with the
same geometry, in a different position and no tabs at all.
So now I have to restart them manually but:
- the flag --geometry has been removed so I can't call konsole with
the desired geometry
- the flag --tabs-from-file opens one extra tab (I've 14 tabs stored
but it opens 15 tabs instead)
Apart that it is a waste of time to manually restore the session work I
can't get it correct.
At the moment I'm using:
> rpm -qa | grep konsole
konsole5-16.08.1-2.fc23.x86_64
konsole-part-4.14.3-10.fc23.x86_64
konsole5-part-16.08.1-2.fc23.x86_64
and plasma 5.7.5
Is that possible to restore the old behavior and save/reopen my session
correctly?
Thank you in advance for any help
Walter
--
7 years, 1 month
KMail: anyone seeing this bizarre behaviour
by Timothy Murphy
Sometimes (about one time in three)
when I open KMail the message window is in a strange form.
Most of the entries in Inbox are threads,
I cannot change the date order by clicking on Date,
and the Subject, From and Date columns are squashed together on the left.
Basically, KMail in this state is unusable,
as I cannot access recent messages.
Closing KMail and re-opening it does not improve metters.
Logging out and in again occasionally works.
But usually I have to re-boot to get KMail back into normal form.
Is this part of the KDE/KDEinit bug(s) I've been reading about?
Any suggestion of a quicker way to return KMail to normal form?
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
7 years, 1 month
KDEInit buggy with kcachegrind
by Reindl Harald
not sure how to trigger it with other applications
but when i click on a cachegrind.out file (xdebug analysis) it opens
"kcachegrind" first fine BUT after close it a message "KDEInit could not
start '/usr/bin/kcachegrind'" and when i close that error message it's
opened again
that's very annoying if you want to open different files and each time
have to close two additional windows :-(
7 years, 1 month
Building Plasma from source: KWin does not build: Could NOT find
Qt5PlatformSupport
by Fredy Neeser
Hi Rex
Quick question for you on a problem with FindQt5PlatformSupport, which you
recently helped to fix in upstream KDE:
http://pkgs.fedoraproject.org/cgit/rpms/kwin.git/commit/?h=master&id=3c10...
Upstream fix:
https://git.reviewboard.kde.org/r/126234/
Summary:Fix build with Qt 5.6
I made some progress building Plasma from KDE sources (74 of 81 modules
build ok), but kwin is failing --
here's the relevant portion of kwin's cmake.log:
...
// All needed KF5... packages were found
// Next comes the output of find_package(Threads)
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
// Next some stuff is NOT found, but it's unclear which packages kwin is
looking for
// and whether any of this is mandatory
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Found EGL: /usr/lib64/libEGL.so (found version "1.5")
-- Found epoxy: /usr/lib64/libepoxy.so
-- Wayland: Egl requires Client
-- Found Wayland_Client: /usr/lib64/libwayland-client.so (found version
"1.10.0")
-- Found Wayland_Cursor: /usr/lib64/libwayland-cursor.so (found version
"1.10.0")
-- Found Wayland_Egl: /usr/lib64/libwayland-egl.so (found version "12.0.3")
-- Found
Wayland: /usr/lib64/libwayland-client.so;/usr/lib64/libwayland-cursor.so;/usr/lib64/libwayland-egl.so
(found suitable version "1.10.0", minimum required is "1.2") found
components: Cursor Egl
-- Found XKB: /usr/lib64/libxkbcommon.so (found suitable version "0.6.1",
minimum required is "0.5.0")
-- Could NOT find Libinput (missing: Libinput_LIBRARY
Libinput_INCLUDE_DIR) (Required is at least version "1.2")
-- Found UDev: /usr/include
-- Found Libdrm: /usr/lib64/libdrm.so (found suitable version "2.4.71",
minimum required is "2.4.62")
-- Could NOT find gbm (missing: gbm_LIBRARY gbm_INCLUDE_DIR)
-- Could NOT find libhardware (missing: libhardware_LIBRARY
libhardware_INCLUDE_DIR)
-- Could NOT find libhwcomposer (missing: libhwcomposer_LIBRARY
libhwcomposer_INCLUDE_DIR)
-- Could NOT find hybriseglplatform (missing: hybriseglplatform_LIBRARY
hybriseglplatform_INCLUDE_DIR)
// Next is an error "Could NOT find Qt5PlatformSupport (missing:
Qt5PlatformSupport_LIBRARY"
// triggered by cmake/modules/FindQt5PlatformSupport.cmake
CMake Error
at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
Could NOT find Qt5PlatformSupport (missing: Qt5PlatformSupport_LIBRARY
Qt5PlatformSupport_INCLUDE_DIR) (found version "5.6.1")
Call Stack (most recent call first):
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:388
(_FPHSA_FAILURE_MESSAGE)
cmake/modules/FindQt5PlatformSupport.cmake:89
(find_package_handle_standard_args)
CMakeLists.txt:244 (find_package)
// end of cmake.log
My kde/src/kwin/cmake/modules/FindQt5PlatformSupport definitely has the
upstream fix:
# Use pkg-config to get the directories and then use these values
# in the FIND_PATH() and FIND_LIBRARY() calls
find_package(PkgConfig)
pkg_check_modules(PKG_Qt5PlatformSupport QUIET Qt5Gui)
Any idea what FindQt5PlatformSupport may be missing?
What is meant by Qt5PlatformSupport_LIBRARY?
Also, please let me know if you see something under "Could NOT find ..."
which you think is mandatory.
Thank you!
- Fredy
Fredy Neeser
IBM Zurich Research Laboratory
7 years, 1 month
Building Plasma from source: networkmanager-qt: Could NOT find libnm-core,
check FindPkgConfig output above!
by Fredy Neeser
Hi list
I'm currently building Plasma directly from KDE sources because I need to
debug a multiscreen issue ...
After working around the build failures for the kf5_kservice and kf5_solid
packages (caused by flex-2.6.0-2.fc24.x86_64, see
https://bugzilla.redhat.com/show_bug.cgi?id=1364943), the next challenge is
a build error for networkmanager-qt:
$ kdesrc-build --build-only --include-dependencies networkmanager-qt
gives the following error in cmake.log:
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Checking for one of the modules 'NetworkManager'
-- Checking for one of the modules 'libnm'
CMake Error at cmake/FindNetworkManager.cmake:52 (MESSAGE):
Could NOT find libnm-core, check FindPkgConfig output above!
I then checked
kde/src/networkmanager-qt/cmake/FindNetworkManager.cmake,
which apparently falls into the outer ELSE clause shown below:
...
# Since NetworkManager 1.0.0 we need to find different
libraries
IF (NetworkManager_FIND_VERSION AND ("$
{NETWORKMANAGER_VERSION}" VERSION_LESS "1.0.0"))
PKG_SEARCH_MODULE( NM-UTIL libnm-util )
PKG_SEARCH_MODULE( NM-GLIB libnm-glib )
IF (NM-UTIL_FOUND AND NM-GLIB_FOUND)
IF (NOT NetworkManager_FIND_QUIETLY)
MESSAGE(STATUS "Found libnm-util: $
{NM-UTIL_LIBRARY_DIRS}")
MESSAGE(STATUS "Found libnm-glib: $
{NM-GLIB_LIBRARY_DIRS}")
ENDIF ()
ELSE ()
MESSAGE(FATAL_ERROR "Could NOT find libnm-util or
libnm-glib, check FindPkgConfig output above!")
ENDIF ()
ELSE ()
PKG_SEARCH_MODULE( NM-CORE libnm )
IF (NM-CORE_FOUND)
IF (NOT NetworkManager_FIND_QUIETLY)
MESSAGE(STATUS "Found libnm-core: $
{NM-CORE_LIBRARY_DIRS}")
ENDIF ()
ELSE ()
MESSAGE(FATAL_ERROR "Could NOT find libnm-core, check
FindPkgConfig output above!")
ENDIF ()
ENDIF ()
....
Here it does
PKG_SEARCH_MODULE( NM-CORE libnm )
but fails to find libnm. Fedora 24 does not have a libnm package, but only
libnm-qt:
# rpm -q libnm-qt
libnm-qt-0.9.8.3-4.fc23.x86_64
# rpm -q libnm-qt-devel
libnm-qt-devel-0.9.8.3-4.fc23.x86_64
According to Comment 2 in
https://bugzilla.redhat.com/show_bug.cgi?id=970035
the libnm-qt package once had a similar problem
"Could NOT find NetworkManager, libnm-util or libnm-glib, check
FindPkgConfig output above!"
which was supposedly fixed in 2013 ...
When I replace
PKG_SEARCH_MODULE( NM-CORE libnm )
with
PKG_SEARCH_MODULE( NM-CORE libnm-qt )
I still get "Could NOT find libnm-core, check FindPkgConfig output above!"
Any idea what's wrong here?
B.t.w., I have no idea why dnf installed an fc23 version for
libnm-qt-devel ...
Thanks,
Fredy Neeser
IBM Zurich Research Laboratory
7 years, 1 month
Broken users session management
by Germano Massullo
By several months, the entire management of multiple users sessions is
broken.
In past I used sometimes to leave my machine to another person, so I
locked my user session, and started another user "foo" session. Then
when user foo finished to use my machine, he ended his session, so I
unlocked mine and continued to work normally.
Now such actions are no longer possible in Plasma 5 because for unknown
reasons, the locked user session will be killed as soon you start
another user session.
Any feedbacks about?
7 years, 1 month