compatibility is enabled and gnome-keyring-daemon is
found on the system. Skipping gpg/ssh-agent startup.
env: kdeinit4: No such file or directory
env: qdbus: No such file or directory
. Somehow, the remnants of a KDE program are hanging around somewhere.
I've no idea what qdbus is, or where
On Sun, Nov 2, 2014 at 6:38 AM, Nikos Chantziaras rea...@gmail.com wrote:
What happened? Where are the KDE settings for my monitor?
from kde-misc/kscreen postinstall:
LOG: postinst
Disable the old screen management:
# qdbus org.kde.kded /kded org.kde.kded.unloadModule randrmonitor
# qdbus
get these messages when trying to startx:
xfce4-session: GNOME compatibility is enabled and gnome-keyring-daemon
is found on the system. Skipping gpg/ssh-agent startup.
env: kdeinit4: No such file or directory
env: qdbus: No such file or directory
. Somehow, the remnants
On 04/11/14 18:28, Douglas J Hunley wrote:
On Sun, Nov 2, 2014 at 6:38 AM, Nikos Chantziaras rea...@gmail.com wrote:
What happened? Where are the KDE settings for my monitor?
from kde-misc/kscreen postinstall:
LOG: postinst
Disable the old screen management:
# qdbus org.kde.kded /kded
or directory
env: qdbus: No such file or directory
. Somehow, the remnants of a KDE program are hanging around somewhere.
I've no idea what qdbus is, or where I've got it configured.
$ eix qtdbus
[I] dev-qt/qtdbus (4.8.5(4){tbz2}@01/12/13): The DBus module for the Qt
toolkit
Have you got -qt4
On Wed, 15 Jan 2014 22:35:34 +, Alan Mackenzie wrote:
I've emerged qtdbus, and the qdbus error message has gone. But I
can't for the life of me locate the package containing kdeinit4. I've
looked through /usr/portage/kde-base/, but can't identify the KDE base
package I need. equery
On 16/01/2014 00:35, Alan Mackenzie wrote:
I've emerged qtdbus, and the qdbus error message has gone. But I can't
for the life of me locate the package containing kdeinit4. I've looked
through /usr/portage/kde-base/, but can't identify the KDE base package I
need. equery only works
--user $XUSER kded kded
loadedModules | grep -q klaptopdaemon) ||
( test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r
/proc/$(pgrep -n kded4)/environ && su - $XUSER -c "eval $(echo -n
'export '; cat /proc/$(pgrep -n kded4
versions prior 4.4. And looking at the ebuilds, for qt versions
prior to 4.4, the -qdbus option (which I suppose provides the program)
is enabled if the dbus USE flag is set. Bug #147399 is about this
problem, but it seems it's fixed now.
I'm sorry I can't help you further about this :-(
--
gentoo-user
requiring things).
There doesn't appear to be a connection for acpi, at least qdbus | grep
-i acpi returns nothing. Could you add a line to /etc/sudoers to allow
your script, or the command it needs, to be run as root without a
password?
--
Neil Bothwick
Do radioactive cats have 18 half-lives
On Sun, 12 Jan 2014 10:05:26 +, Alan Mackenzie wrote:
xfce4-session: GNOME compatibility is enabled and
gnome-keyring-daemon is found on the system. Skipping gpg/ssh-agent
startup. env: kdeinit4: No such file or directory env: qdbus: No such
file or directory
You'll want to start
Hi, Neil.
On Wed, Jan 15, 2014 at 11:01:35PM +, Neil Bothwick wrote:
On Wed, 15 Jan 2014 22:35:34 +, Alan Mackenzie wrote:
I've emerged qtdbus, and the qdbus error message has gone. But I
can't for the life of me locate the package containing kdeinit4. I've
looked through /usr
startup. env: kdeinit4: No such
file or directory
env: qdbus: No such file or directory
. Somehow, the remnants of a KDE program are hanging around somewhere.
I've no idea what qdbus is, or where I've got it configured.
$ eix qtdbus
[I] dev-qt/qtdbus (4.8.5(4){tbz2}@01/12/13): The DBus
: qdbus: No such
file or directory
The gnome-keyring-daemon comes from gnome-base/gnome-keyring; as for
the other files not found, they seem to be started from somewhere in
your config. I'd suggest `grep -r '\(kde\|qdbus\)' /etc` to check where
these are launched from. Maybe in ~/.config you might
Hello, Alan.
On Thu, Jan 16, 2014 at 06:54:27AM +0200, Alan McKinnon wrote:
On 16/01/2014 00:35, Alan Mackenzie wrote:
I've emerged qtdbus, and the qdbus error message has gone. But I can't
for the life of me locate the package containing kdeinit4. I've looked
through /usr/portage/kde
: No such file or directory
env: qdbus: No such file or directory
. Somehow, the remnants of a KDE program are hanging around somewhere.
I've no idea what qdbus is, or where I've got it configured.
--
Alan McKinnon
alan.mckin...@gmail.com
--
Alan Mackenzie (Nuremberg, Germany).
: kdeinit4: No such file or directory
env: qdbus: No such file or directory
.
You'll want to start with inspecting ~/.xinitrc; from there on, look
into the configuration of both your session and X itself.
My ~/.xinitrc contains but a single line, exec startxfce4. It's not
obvious, from
e: exec [-cl] [-a name] [command [argument ...]] [redirection ...]*
Sway configs aren't shells scripts. In shell, you'd run
'dbus-update-activation-environment --all' alone. Does qdbus --session
output any errors or just a bunch of names and numbers?
SDDM should set up a D-Bus session bus, I believe.
to check wayland or xwayland applications from
within wayland, run in a terminal:
qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole
I moved to wayland 2-3 years ago for the opposite reasons to you. After the
odd update(s) Xorg had started playing up with two monitors, causing the
Plasma T
/assistant-5.3.2*
=dev-qt/designer-5.3.2*
=dev-qt/linguist-5.3.2*
=dev-qt/linguist-tools-5.3.2*
=dev-qt/pixeltool-5.3.2*
=dev-qt/qdbus-5.3.2*
=dev-qt/qdbusviewer-5.3.2*
=dev-qt/qdoc-5.3.2*
=dev-qt/qtconcurrent-5.3.2*
=dev-qt/qtcore-5.3.2*
=dev-qt/qtdbus-5.3.2*
=dev-qt/qtdeclarative-5.3.2*
=dev-qt
the issue.
Thanks for the clue, or at least triggering me to find it.
qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole
I moved to wayland 2-3 years ago for the opposite reasons to you.
After the
odd update(s) Xorg had started playing up with two monitors, causing
the
Plasma Task
startup-id
>> > dbus-update-activation-environment --all*
>> >
>> > However, I noticed that if I try running this line by itself in a
>> terminal,
>> > I get this output:
>> >
>> >
>> > *jamie@localhost ~ $ exec --no-startup-id
>
th: 1920, height: 26)
>> for output: WL-1
>>
>>
>> On Tue, Nov 28, 2023 at 12:31 AM Arsen Arsenović
>> wrote:
>>
>>>
>>> Jamie Getty writes:
>>>
>>> > I'm not sure what you mean by *wrap it in dbus-run-session*.
>>> >
on-environment --allbash: exec: --: invalid
> optionexec:
> > usage: exec [-cl] [-a name] [command [argument ...]] [redirection ...]*
>
> Sway configs aren't shells scripts. In shell, you'd run
> 'dbus-update-activation-environment --all' alone. Does qdbus --session
> output any
] kde-frameworks/kfilemetadata-5.26.0-r1:5/5.26::gentoo
USE="-debug -epub -exif -ffmpeg -libav -pdf -taglib {-test}" 129 KiB
[nomerge ] kde-plasma/kwin-5.8.3:5::gentoo USE="handbook -debug -gles2
-multimedia {-test}"
[ebuild N ] kde-plasma/kdecoration-5.8.
ebuild R] dev-python/html5lib-0.999-r1::gentoo USE="{-test}"
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild U ] virtual/perl-IO-Compress-2.69.1_rc::gentoo
[2.69.0::gentoo] 0 KiB
[ebuild NS] dev-lang/vala-0.34.3:0.34::
yzmq:0
dev-python/requests:0 dev-python/setuptools:0 dev-python/simplejson:0
dev-python/sip:0/12 dev-python/six:0 dev-python/ssl-fetch:0
dev-python/urlgrabber:0 dev-python/urllib3:0 dev-qt/designer:4
dev-qt/designer:5/5.9 dev-qt/linguist-tools:5/5.9 dev-qt/qdbus:5/5.9
dev-qt/qt3support:4 dev-qt/qtblu
27 matches
Mail list logo
