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 :-(
Am 08.10.2016 um 14:27 schrieb 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 :-(
oh, and at's long it's open before the 'could not start' message the konqueror window where you double clicked on the file is unuseable and you can't even switch to a different tab which makes it really hard to switch to the tab with the "offending code" you want to change
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
-- Rex
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
It's usually an application bug in how it interacts with kdeinit/days (single vs multi instance detection)
-- Rex
-------- Original message -------- From: Reindl Harald h.reindl@thelounge.net Date: 10/13/16 11:39 AM (GMT-06:00) To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
_______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
Silly phone, make that dbus, not days
-- Rex
-------- Original message -------- From: Rex Dieter rdieter@unl.edu Date: 10/13/16 11:43 AM (GMT-06:00) To: KDE on Fedora discussion kde@lists.fedoraproject.org Subject: RE: KDEInit buggy with kcachegrind
It's usually an application bug in how it interacts with kdeinit/days (single vs multi instance detection)
-- Rex
-------- Original message -------- From: Reindl Harald h.reindl@thelounge.net Date: 10/13/16 11:39 AM (GMT-06:00) To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
_______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
pretty sure not kcachegrind because opening a diff with "kompare" by double-click in Konqueror has the *identical* behavior talking nonsense that "KDEinit could not open /usr/bin/kompare" *by close* it leading here too in open it once again after clkick away that silly popupd
Am 13.10.2016 um 18:45 schrieb Rex Dieter:
Silly phone, make that dbus, not days
-------- Original message -------- From: Rex Dieter rdieter@unl.edu Date: 10/13/16 11:43 AM (GMT-06:00) To: KDE on Fedora discussion kde@lists.fedoraproject.org Subject: RE: KDEInit buggy with kcachegrind
It's usually an application bug in how it interacts with kdeinit/days (single vs multi instance detection)
-------- Original message -------- From: Reindl Harald h.reindl@thelounge.net Date: 10/13/16 11:39 AM (GMT-06:00) To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
For kcachegrind, try changing
/usr/share/appilcations/kde4/kcachegrind.desktop
X-DBUS-ServiceName=... to X-DBUS-ServiceName=org.kde.kcachegrind
and restart your session (or at least re-run kbuildsycoca5/kbuildsycoca), and see if that helps. If so, confirms my suspicions
-- Rex ________________________________________ From: Reindl Harald h.reindl@thelounge.net Sent: Thursday, October 20, 2016 6:01:59 PM To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
pretty sure not kcachegrind because opening a diff with "kompare" by double-click in Konqueror has the *identical* behavior talking nonsense that "KDEinit could not open /usr/bin/kompare" *by close* it leading here too in open it once again after clkick away that silly popupd
Am 13.10.2016 um 18:45 schrieb Rex Dieter:
Silly phone, make that dbus, not days
-------- Original message -------- From: Rex Dieter rdieter@unl.edu Date: 10/13/16 11:43 AM (GMT-06:00) To: KDE on Fedora discussion kde@lists.fedoraproject.org Subject: RE: KDEInit buggy with kcachegrind
It's usually an application bug in how it interacts with kdeinit/days (single vs multi instance detection)
-------- Original message -------- From: Reindl Harald h.reindl@thelounge.net Date: 10/13/16 11:39 AM (GMT-06:00) To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
_______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
old: X-DBUS-ServiceName=io.github.kcachegrind new: X-DBUS-ServiceName=org.kde.kcachegrind
problem seems to be gone after change and "kbuildsycoca5" so the desktop files in the packages needs to be fixed
the whole dbugs dependencies are starting to make me angry
when you restart all services (except dbus itself) you can no longer login into kde which is also pretty new, not so long ago you even was able to restart dbus and "killall systemd" via SSH without rendering the machine unusable and now we have to reboot when we got pcre or similar updates which require to restart neraly every process
call thge script below und you won't ever be able to login into Plasma while openbox has no problem - there is no good reason when i sit in front of SDDM with no user active that whatever process is need couldn't be restartet, at least after restart the displaymanager
[root@srv-rhsoft:~]$ cat /usr/local/bin/restart-all-services.sh #!/usr/bin/dash echo "Schreibe Caches auf Festplatte" sync echo "Starte Dienste neu" systemctl condrestart acpid alsa-state apcupsd asterisk asteriskweb avahi-daemon clamav-milter clamd clamd-sa crond cups dbmail-imapd dbmail-lmtpd dbmail-pop3d dbmail-timsieved dhcpd dhcpd-guest dhcpd-vmware dm-event dnsmasq dovecot forward-flow-home forward-hosting haveged hostapd hostapd-guest httpd imapproxy irqbalance jabber lm_sensors lvm2-lvmetad mailgraph mdmonitor mediatomb monitor-dbmail-imapd monitor-dbmail-lmtpd monitor-dbmail-pop3d monitor-httpd mpdscribble named netatalk network-wan-bridge ntpd openvpn openvpn-as openvpn-flow openvpn-io openvpn-rh openvpn-server openvpn-south panel postfix postgrey preload pulsed pure-ftpd rbldnsd replication rngd rsyncd rsyslog rtkit-daemon serverstatus smartd smb smokeping spamassassin spamassassin-debug spamassassin-submission spamass-milter spamass-milter-submission sshd systemd-udevd trafficserver udisks2 unbound upower vmtoolsd vnstat xinetd echo "Starte systemd Prozesse neu" sleep 2 systemctl daemon-reexec
Am 21.10.2016 um 15:53 schrieb Rex Dieter:
For kcachegrind, try changing
/usr/share/appilcations/kde4/kcachegrind.desktop
X-DBUS-ServiceName=... to X-DBUS-ServiceName=org.kde.kcachegrind
and restart your session (or at least re-run kbuildsycoca5/kbuildsycoca), and see if that helps. If so, confirms my suspicions
-- Rex ________________________________________ From: Reindl Harald h.reindl@thelounge.net Sent: Thursday, October 20, 2016 6:01:59 PM To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
pretty sure not kcachegrind because opening a diff with "kompare" by double-click in Konqueror has the *identical* behavior talking nonsense that "KDEinit could not open /usr/bin/kompare" *by close* it leading here too in open it once again after clkick away that silly popupd
Am 13.10.2016 um 18:45 schrieb Rex Dieter:
Silly phone, make that dbus, not days
-------- Original message -------- From: Rex Dieter rdieter@unl.edu Date: 10/13/16 11:43 AM (GMT-06:00) To: KDE on Fedora discussion kde@lists.fedoraproject.org Subject: RE: KDEInit buggy with kcachegrind
It's usually an application bug in how it interacts with kdeinit/days (single vs multi instance detection)
-------- Original message -------- From: Reindl Harald h.reindl@thelounge.net Date: 10/13/16 11:39 AM (GMT-06:00) To: kde@lists.fedoraproject.org Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
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
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error? kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows what and after you are done with kcachegrind and close it pretends it could not be started and to make the fun perfect it starts it again
Reindl Harald wrote:
old: X-DBUS-ServiceName=io.github.kcachegrind new: X-DBUS-ServiceName=org.kde.kcachegrind
problem seems to be gone after change and "kbuildsycoca5" so the desktop files in the packages needs to be fixed
Now that we've established the application needs fixing, mind filing a bug now as I originally suggested?
-- Rex
Rex Dieter wrote:
Reindl Harald wrote:
old: X-DBUS-ServiceName=io.github.kcachegrind new: X-DBUS-ServiceName=org.kde.kcachegrind
problem seems to be gone after change and "kbuildsycoca5" so the desktop files in the packages needs to be fixed
Now that we've established the application needs fixing, mind filing a bug now as I originally suggested?
Nevermind kcachegrind at least, chatted with folks on irc and pushed a fix upstream, and will pull it into our packaging soon.
-- Rex
Am 21.10.2016 um 17:15 schrieb Rex Dieter:
Rex Dieter wrote:
Reindl Harald wrote:
old: X-DBUS-ServiceName=io.github.kcachegrind new: X-DBUS-ServiceName=org.kde.kcachegrind
problem seems to be gone after change and "kbuildsycoca5" so the desktop files in the packages needs to be fixed
Now that we've established the application needs fixing, mind filing a bug now as I originally suggested?
Nevermind kcachegrind at least, chatted with folks on irc and pushed a fix upstream, and will pull it into our packaging soon.
thx!
-
Reindl Harald -
Rex Dieter -
Rex Dieter