urpmi --downgrade dbus-1.6.18-1.3.mga4 lib64dbus1_3-1.6.18-1.3.mga4 dbus-x11-1.6.18-1.3.mga4
urpmi --downgrade dbus-1.6.18-1.3.mga4 libdbus1_3-1.6.18-1.3.mga4 dbus-x11-1.6.18-1.3.mga4
No package named dbus-1.6.18-1.3.mga4
No package named libdbus1_3-1.6.18-1.3.mga4
No package named dbus-x11-1.6.18-1.3.mga4
urpmq --sources libdbus1_3-1.6.18-1.3.mga4
Never mind this I just saw the answer above as I refreshed the page. Thanks.Will the same commands work if my upgrade fails? I am asking this because I am also planning to test this on other 32bit and 64bit machines that I haven't updated for quite some time
urpmi --downgrade dbus-1.6.18-1.3.mga4 libdbus1_3-1.6.18-1.3.mga4 dbus-x11-1.6.18-1.3.mga4
urpmi --downgrade dbus-1.6.18-1.3.mga4 lib64dbus1_3-1.6.18-1.3.mga4 dbus-x11-1.6.18-1.3.mga4
tandrews16 wrote:I got "No package named libdbus1_3-1.6.18-1.3.mga4" both before and after using MCC to update the databases. MCC said all were up-to-date. But then I discovered I was still using whatever MIRRORLIST had assigned to me. (I thought I had changed that a while back) I changed to the US kernel.org mirror, and that took care of it. dbus now downgraded again.
Strange that whatever mirror I was using had the test packages but not the downgrade packages. Should I try the test packages again, now getting them from the kernel.org mirror? Doesn't seem like it would make a difference, but...
jkerr82508 wrote:If this is the "ultimate" solution, those packages will eventually be pushed to /core/updates. Since you already have them, MageiaUpdate will not report them as updates.
If there are more test versions produced before the update is validated for release, then MageiaUpdate will report as updates the packages that are eventually released.
If you are satisfied that your system is now running correctly, you can remove the three lines that you added to /etc/urpmi/skip-list.
The slightly slower login/logout may be due to the fact that the timeout for certain services has been increased.
Jim
[unklar@localhost ~]$ journalctl -b -a | grep -i dbus
Okt 24 13:26:51 localhost.localdomain systemd[1965]: Failed to open private bus connection: Failed to connect to socket /run/user/500/dbus/user_bus_socket: No such file or directory
[unklar@localhost ~]$ systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
[unklar@localhost ~]$ systemd-analyze blame | head
13.594s avahi-daemon.service
10.720s shorewall.service
2.846s upower.service
2.622s fedora-loadmodules.service
2.577s network.service
2.562s sensord.service
2.117s atieventsd.service
1.933s fedora-import-state.service
1.887s fedora-readonly.service
1.766s systemd-logind.service
[unklar@localhost ~]$ journalctl -b -p err
-- Logs begin at So 2013-12-15 19:20:13 CET, end at Fr 2014-10-24 13:26:56 CEST.
[unklar@localhost ~]$ rpm -qa | grep dbus
dbus-sharp-glib-0.5.0-3.mga4
dbus-1.6.18-1.6.mga4
lib64dbus1_3-1.6.18-1.6.mga4
ndesk-dbus-0.6.1a-9.mga4
lib64qtdbus4-4.8.6-1.mga4
lib64dbus-glib1_2-0.100.2-2.mga4
dbus-sharp-0.7.0-3.mga4
dbus-x11-1.6.18-1.6.mga4
python-dbus-1.2.0-5.mga4
[unklar@localhost ~]$ journalctl -b -a | grep -i dbus
Okt 24 19:31:40 localhost systemd[2045]: Failed to open private bus connection: Failed to connect to socket /run/user/500/dbus/user_bus_socket: No such file or directory
[unklar@localhost ~]$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
atieventsd.service loaded failed failed LSB: ATI Events Daemon
fedora-loadmodules.service loaded failed failed Load legacy module configuration
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
[unklar@localhost ~]$ systemd-analyze blame | head
14.431s ntpdate.service
6.204s network.service
6.033s systemd-logind.service
6.027s ntp-wait.service
6.007s avahi-daemon.service
5.015s atieventsd.service
5.002s systemd-udev-settle.service
3.395s shorewall.service
3.322s mandriva-everytime.service
3.243s plymouth-quit-wait.service
[unklar@localhost ~]$ journalctl -b -p err
-- Logs begin at Do 2013-10-03 19:18:49 CEST, end at Fr 2014-10-24 19:31:46 CEST. --
Okt 24 19:31:45 localhost pulseaudio[2339]: [pulseaudio] pid.c: Daemon already running.
[unklar@localhost ~]$ rpm -qa | grep dbus
lib64dbus-glib1_2-0.100.2-2.mga4
lib64qtdbus4-4.8.6-1.mga4
dbus-x11-1.6.18-1.6.mga4
python-dbus-1.2.0-5.mga4
dbus-1.6.18-1.6.mga4
python-slip-dbus-0.4.0-3.mga4
lib64dbus1_3-1.6.18-1.6.mga4
qt4-qtdbus-4.8.6-1.mga4
lib64dbusmenu-qt2-0.9.2-3.mga4
python-qt4-dbus-4.10.3-3.mga4
urpmi.update "Core Updates Testing"
urpmi --media "Core Updates Testing" dbus-1.6.18-1.7.mga4 lib64dbus1_3-1.6.18-1.7.mga4 dbus-x11-1.6.18-1.7.mga4
urpmi --media "Core Updates Testing" dbus-1.6.18-1.7.mga4 libdbus1_3-1.6.18-1.7.mga4 dbus-x11-1.6.18-1.7.mga4
jkerr82508 wrote:New test packages are becoming available:
https://bugs.mageia.org/show_bug.cgi?id=14251#c29
If the previous set of test packages did not resolve the problem for you, you should install these packages. Execute the following two commands:
- Code: Select all
urpmi.update "Core Updates Testing"
and, on a 64 bit system:
- Code: Select all
urpmi --media "Core Updates Testing" dbus-1.6.18-1.7.mga4 lib64dbus1_3-1.6.18-1.7.mga4 dbus-x11-1.6.18-1.7.mga4
on a 32 bit system:
- Code: Select all
urpmi --media "Core Updates Testing" dbus-1.6.18-1.7.mga4 libdbus1_3-1.6.18-1.7.mga4 dbus-x11-1.6.18-1.7.mga4
You do NOT need to activate the testing repo's.
Please report in the bug report if they solve the problem for you.
If they solve the problem, don't forget to remove the three lines that you added to /etc/urpmi/skip.list
Unless there are reports of problems with these packages, they will be released eventually as official updates.
Jim
┌─[doktor5000@Mageia4]─[18:02:21]─[~]
└──╼ curl ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/4/x86_64/media/core/updates_testing/ | grep dbus | grep '1.6.18-1.7.mga4'
######################################################################## 100,0%
-rw-r--r-- 1 ftp ftp 275619 Oct 25 09:22 dbus-1.6.18-1.7.mga4.x86_64.rpm
-rw-r--r-- 2 ftp ftp 1421724 Oct 25 09:22 dbus-doc-1.6.18-1.7.mga4.noarch.rpm
-rw-r--r-- 1 ftp ftp 23506 Oct 25 09:22 dbus-x11-1.6.18-1.7.mga4.x86_64.rpm
-rw-r--r-- 1 ftp ftp 27473 Oct 25 09:22 lib64dbus-devel-1.6.18-1.7.mga4.x86_64.rpm
-rw-r--r-- 1 ftp ftp 121744 Oct 25 09:22 lib64dbus1_3-1.6.18-1.7.mga4.x86_64.rpm
┌─[doktor5000@Mageia4]─[18:05:17]─[~]
└──╼ curl ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/4/i586/media/core/updates_testing/ | grep dbus | grep '1.6.18-1.7.mga4'
######################################################################## 100,0%
-rw-r--r-- 1 ftp ftp 279238 Oct 25 09:22 dbus-1.6.18-1.7.mga4.i586.rpm
-rw-r--r-- 2 ftp ftp 1421724 Oct 25 09:22 dbus-doc-1.6.18-1.7.mga4.noarch.rpm
-rw-r--r-- 1 ftp ftp 22287 Oct 25 09:22 dbus-x11-1.6.18-1.7.mga4.i586.rpm
-rw-r--r-- 1 ftp ftp 27472 Oct 25 09:22 libdbus-devel-1.6.18-1.7.mga4.i586.rpm
-rw-r--r-- 1 ftp ftp 122427 Oct 25 09:22 libdbus1_3-1.6.18-1.7.mga4.i586.rpm
┌─[doktor5000@Mageia4]─[18:05:58]─[~]
└──╼
Weatherlawyer wrote:I don't think it is a Mageia problem so much as a Firefox one. I should have started my own thread.
Return to The magician suggests...
Users browsing this forum: No registered users and 1 guest