On 25/02/18 21:25, Stephen Morris wrote:
On 26/2/18 7:55 am, John Pilkington wrote:
On 25/02/18 20:37, Stephen Morris wrote:
Hi,
Has anybody seen these messages before and know what is causing
them, and hence why yumex is getting them? These are potentially new
since the last system update.
(<class 'dbus.exceptions.DBusException'>, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), <traceback object
at 0x7fea6ad483b0>)
(yumex:3908): IBUS-WARNING **: Unable to connect to ibus: Could not
connect: Connection refused
(<class 'dbus.exceptions.DBusException'>, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), <traceback object
at 0x7fea6ad4ad88>)
07:31:35 : INFO - Can't detect the network connection state
(<class 'dbus.exceptions.DBusException'>, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), <traceback object
at 0x7fea6ad4cfc8>)
regards,
Steve
I use yumex - on my el7 (SL7) box; but I thought you were on f27,
where yumex itself is surely not recommended. My f26 box has a
bewildering set of package managers that seem to conflict in their
demands for access, but aren't dnf-dragora or yumex-dnf more appropriate?
I am on F27. I have dnfdragora installed but I don't like its gui
interface, yumex as a gui interface is ten times better than dnfdragora.
Yumex-dnf doesn't exist as a command on my system and a dnf whatprovides
yumex-dnf seems to be indicating it is provided by dnfdragora, but I
can't find it in the filelist in the dnfdragora packages.
In my view the dnf command line interface is hopeless at being able to
find what packages are provided by the various repositories, what they
are and what files they contain, compared to yumex which makes it
simple, so until a gui interface to the package system that is of the
same quality as yumex, that talks directly to dnf rather than through a
translation interface, is produced I've continued to use yumex.
The messages above I have never noticed before, which doesn't
necessarily mean they weren't produced, its just that now the warning
text is being displayed in yellow it now stands out and is hence more
noticeable.
regards,
Steve
I have always found the yumex gui a helpful source of package info too -
but at present on f26 yumex-dnf tells me that 'dnf is locked by another
process. Yum-extender will exit.'
I suspect that process is 'Discover', but Apper, dnf-dragora and
dragora-updater are lurking somewhere too. I don't necessarily want to
disable them completely but I would prefer them to do their routine
updates and then go to sleep.
John
I always see the initial 'can't detect network connection state' on
SL7, but it works. Atop shows high cpu loads for metadata operations
after package download.
John P
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
